My short term goal: gather input from others on interop issues they've seen which are common; add those to the list; refine the list of issues by deciding, per-issue, what can be given a BCP recommendation vs. what cannot; then publish. Long term goal: I don't know. I know there are interop problems with SIP... LOTS of interop problems with SIP. And I think it would be better for SIP and all of us if we tried to resolve them, at least the more common ones. Some of them are the fault of the RFC's, and some of them are vendor issues/bugs; and we probably need to go through each one at least at a high level to determine if we care and how to address them. For the RFC ones, I am not sure anything can be done about them - making RFC changes may make things worse. Or they may make things worse for a brief time, and make things better in the long run. PRACK, for example, may be something we can fix with a change that is painful at first, but better in the long run. Or another example is getting rid of the visual-separators concept. My goal was just to start the list - I am in no way claiming this is the top 10 either. Obviously I am just one person and there are lots of people who see interop issues. But even just for me it's not my top 10 - I forgot to add a few more common ones. But I figured I'd submit a list and start it going. -hadriel > -----Original Message----- > From: Elwell, John [mailto:john.elwell@xxxxxxxxxxx] > Sent: Tuesday, March 10, 2009 1:46 PM > > Without commenting on specifics, I agree with the general principle, > that there are lots of common sources of interop problems, and anything > we could do to try to reduce these problems would be good. Each one of > the topics requires a lot of discussion to determine what we want to do. > However, what are your expectations? For example, do you want to develop > the present draft to the extent of providing a single BCP covering these > and perhaps other problem areas that we might identify? Or do you want > to see these addressed during the revving of RFC 3261 etc.? Or does each > topic need to be dealt with separately? > _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
