05.05.2011 21:58, Olle E. Johansson wrote: > 5 maj 2011 kl. 13.42 skrev Iñaki Baz Castillo: > > >> 2011/5/5 Olle E. Johansson<[email protected]>: >> >>>> 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. >>>> >>>> >>> Was the rule changed between SIP 1.0 and SIP 2.0? >>> >> Where is defined SIP 1.0? maybe you mean RFC 2543 (also SIP 2.0) ? :) >> >> >> >>> That's often a reason why we have to send one thing, but accept other >>> syntaxes as well. >>> >> At least RFC 2543 states the same: >> >> http://tools.ietf.org/html/rfc2543#section-4.3.1 >> >> 4.3.1 SIP Version >> >> Both request and response messages include the version of SIP in use, >> and follow [H3.1] (with HTTP replaced by SIP, and HTTP/1.1 replaced >> by SIP/2.0) regarding version ordering, compliance requirements, and >> upgrading of version numbers. To be compliant with this >> specification, applications sending SIP messages MUST include a SIP- >> Version of "SIP/2.0". >> >> > So I guess it stays a mystery. Maybe just a precaution for poor > implementations, which is a good thing. Having a test require lower case must > be considered a bug. >
What really annoys me in SIP is case-insensitivity... A waste of system resources and a source of bugs. -- Regards, Evgeniy Khramtsov, ProcessOne. xmpp:[email protected]. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
