If we are strict on the interpretation, then any implementation is free to send upper/lower case. But we can see that the spec. is leaning towards the version being implemented in the upper case. I'd say, lower-case implementation are right as well, but are not self-respecting.
Regards, Brez On Sun, May 8, 2011 at 8:11 AM, Harbhanu sahai <[email protected]>wrote: > >To phrase it more clearly, devices MUST send upper-case here, but they > >MUST accept both upper-case and lower-case and mixtures thereof. > >Dale > > Does it mean that peers sending in lower case, or any other permutation, is > complaint 3261 peer? > Or is this provision incorporated within implementations to allow error > tolerance ? > > As per my understanding there are other texts in RFC which overlays some > more rules over the BNF, such as the one for name-addr usage, when > addr-spec contains comma etc, in Contact like headers. > > In other words, as per the text - "The SIP-Version string is > case-insensitive, but implementations MUST send upper-case" > Does 3261 doesn't mandate any UAC to send version string in upper-case ? > And thus any UAC which doesn't do so isn't non-compliant to 3261 ? > To be precise - Is that ETSI testcase for 3261 conformance correct ? > > > Thanks to all ! > > Regards, > Harbhanu > > > *************************************************************************************** > This e-mail and attachments contain confidential information from HUAWEI, > which is intended only for the person or entity whose address is listed > above. Any use of the information contained herein in any way (including, > but not limited to, total or partial disclosure, reproduction, or > dissemination) by persons other than the intended recipient's) is > prohibited. If you receive this e-mail in error, please notify the sender by > phone or email immediately and delete it! > > ________________________________________ > From: Harbhanu sahai > Sent: 05 May 2011 17:57:43 > To: Iñaki Baz Castillo > Cc: [email protected] > Subject: RE: [Sip-implementors] Reg. SIP version string > > >>But as per BNF grammar in RC 3261, they MUST accept lowercase. > > Do you mean *uppercase* here ?? > > RFC 3261 - 25.1 Basic Rules - > > Request-Line = Method SP Request-URI SP SIP-Version CRLF > Status-Line = SIP-Version SP Status-Code SP Reason-Phrase CRLF > > SIP-Version = "SIP" "/" 1*DIGIT "." 1*DIGIT > > > > *************************************************************************************** > This e-mail and attachments contain confidential information from HUAWEI, > which is intended only for the person or entity whose address is listed > above. Any use of the information contained herein in any way (including, > but not limited to, total or partial disclosure, reproduction, or > dissemination) by persons other than the intended recipient's) is > prohibited. If you receive this e-mail in error, please notify the sender by > phone or email immediately and delete it! > > ________________________________________ > From: Iñaki Baz Castillo [[email protected]] > Sent: 05 May 2011 16:09:56 > To: Harbhanu sahai > Cc: [email protected] > Subject: Re: [Sip-implementors] Reg. SIP version string > > 2011/5/5 Harbhanu sahai <[email protected]>: > > Is this testcase correct as per 3261 text ? > > Yes, RFC 3261 says that devices must use upper-case for SIP version > field. But as per BNF grammar in RC 3261, they MUST accept lowercase. > > > > > -- > Iñaki Baz Castillo > <[email protected]> > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
