> -----Original Message----- > From: Paul Kyzivat [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 04, 2008 12:10 AM > > Hadriel Kaplan wrote: > > > > Anyway, no my problem with the draft is it's trying to fix things that > either aren't broken, or are broken for everything else and should not be > fixed in this specific document. (and I'd debate how they should be fixed, > but that's another topic) > > You mean the way 3261 was simplified by not saying much about multipart > and not requiring that it be supported, because that wasn't broken in > 2543?
That's not a relevant analogy and you know it. :) 3261 was an update for the base draft of SIP, upon which everything else was dependent, for all intents and purposes. Are you claiming this info draft is of that type? Will the changes we make in here apply to all other RFCs, or all other message types, which normatively reference 3261 for their mechanics? Hardly. Do we need to fix all known issues of RFC 3261 and all known problems of all its extensions which could possibly occur in an INFO message transaction, simply because they can happen in an INFO and this INFO update happens to be on our plate right now? Because this multi-part thing is only like #32 on the Billboard top-100 list of rfc3261 problems. This is an update to the INFO RFC, to address known problems with INFO - and in particular the problem of support-negotiation and message context. If you're claiming its scope is broader, we have a big disconnect, because that was not my understanding of WG consensus for this work. For example, I don't think we need to define how to make RFC 4474 work for INFO if it crosses B2BUA's. That's a general problem for all messages. (nevermind the fact we can't agree on a solution) Nor do I think we need to copy text from draft-ietf-sip-ipv6-abnf-fix into this draft, even though that applies to INFO, because that draft addresses problems for all message types. There's nothing "special" about this multi-part issue for INFO over any other request method. -hadriel _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
