________________________________________ From: [email protected] [[email protected]] On Behalf Of Harbhanu sahai [[email protected]]
>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 ? ________________________________________ What is the purpose of the ETSI test case? My understanding is that it is to test whether your device complies, in particular, that it *accepts* non-upper-case input. You are correct that no 3261-compliant device will *send* such a string. But that is not the question -- your device is required to *accept* such a string anyway. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
