Just to correct the context here : This bug was not FOUND at SIPit, in any test scenario. But, was rather pointed out by me as an issue in the spec.
While it is unlikely that we would face this issue in a "real" situation, as Christer said, it will be helpful (and unambiguous) for parser implementors. Regards Satya T -----Original Message----- From: Christer Holmberg [mailto:[EMAIL PROTECTED] Sent: Saturday, December 15, 2007 6:06 PM To: Jonathan Rosenberg Cc: [email protected] Subject: RE: VS: [Sip] SIPit21: BNF future-proofing problem? Hi, >Correction, yes. Essential? Hardly. > >This is another question around essential corrections. I think they not >only need to clearly represent a bug or a fix, but need to be one that >is important enough to merit documenting. Just like software, sometimes >you don't ever bother fixing those sev 5s. Ever. So, who makes the decission whether a bug (I guess we all agree it IS a bug) is "important enough"? My understanding is that this bug was found at SIPit, so it is not pure "theoretical". I do agree with you that it shouldn't occur that often, because I see no reason why one would need to use the affected characters. But, never the less, the fix MAY be important from a parser implementation perspective. Regards, Christer -Jonathan R. Christer Holmberg wrote: > Hi, > > No matter how we'll fix this, I guess it would be a valid essential > correction? > > Regards, > > Christer > > ________________________________ > > Lähettäjä: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Lähetetty: to 6.12.2007 21:09 > Vastaanottaja: [email protected] > Aihe: Re: [Sip] SIPit21: BNF future-proofing problem? > > > > From: Jonathan Rosenberg <[EMAIL PROTECTED]> > > This strikes me as a problem in theory and not in practice. AFAICT, the > only characters you can't use are ascii 0x00-0x19 (0x20 is space and is > possible through the LWS construct as Christer pointed out). Is there a > practical use case for any of these? They are: > > HT (horizontal tab) should be included, but that's also in LWS. As > for the remaining characters, I don't think that anyone has ever > *intended* that they be used in SIP headers, and their inclusion in > quoted-pair was a typographical error. > > Dale > > > _______________________________________________ > Sip mailing list https://www1.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 > > > > > _______________________________________________ > Sip mailing list https://www1.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 > -- Jonathan D. Rosenberg, Ph.D. 499 Thornall St. Cisco Fellow Edison, NJ 08837 Cisco, Voice Technology Group [EMAIL PROTECTED] http://www.jdrosen.net <http://www.jdrosen.net/> PHONE: (408) 902-3084 http://www.cisco.com <http://www.cisco.com/> _______________________________________________ Sip mailing list https://www1.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 _______________________________________________ Sip mailing list https://www1.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
