This looks to be a bug in either RFC-3261(SIP). Both of these RFCs (3261
& 2234) specify the same in contradicting ways. It's also said that SIP
is in conformance with ABNF syntax defined by RFC-2234.
RFC-3261 says
<< RFC-3261
The following two header fields are not equivalent:
Warning: 370 devnull "Choose a bigger pipe"
Warning: 370 devnull "CHOOSE A BIGGER PIPE"
/ RFC-3261 >>
RFC-2234 says
<<<< RFC-2234
NOTE: ABNF strings are case-insensitive and
the character set for these strings is us-ascii.
Hence:
rulename = "abc"
and:
rulename = "aBc"
will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC" and "ABC".
To specify a rule which IS case SENSITIVE,
specify the characters individually.
For example:
rulename = %d97 %d98 %d99
or
rulename = %d97.98.99
/RFC-2234 >>>>
Should we assume whatever mentioned in 3261 is an updation over 2234 OR
raise a bug against SIP-RFC ???
Thanks & Regards,
Nataraju A.B.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Attila
Sipos
Sent: Friday, December 09, 2005 3:41 PM
To: Ajit Kumar; Madhuri Sakhare; [email protected]
Subject: Re: [Sip-implementors] Case insensitive parameters
Hi Ajit,
Can you give examples of "quoted strings" that you refer to?
It's just that RFC3261 refers to RFC 2822 and says:
>>
>> Characters will be specified either by a decimal value
>> (e.g., the value %d65 for uppercase A and %d97 for lowercase A) or
by
>> a case-insensitive literal value enclosed in quotation marks
(e.g.,
>> "A" for either uppercase or lowercase A).
>>
So if the quoted string you refer to is
the same as the "value enclosed in quotation marks"
then your answer might not be correct.
Regards,
Attila
http:/www.vegastream.com
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] Behalf
>> Of Ajit Kumar
>> Sent: 09 December 2005 04:30
>> To: 'Madhuri Sakhare'; [email protected]
>> Subject: Re: [Sip-implementors] Case insensitive parameters
>>
>>
>> The quoted strings are case sensitive and rest is case insensitive
>> unless specified as you have said below.
>> Regards
>> Ajit
>>
>>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf
>> Of Madhuri
>> Sakhare
>> Sent: Thursday, December 08, 2005 9:26 PM
>> To: [email protected]
>> Subject: [Sip-implementors] Case insensitive parameters
>>
>> Hi All,
>>
>>
>>
>> "Field names are always case-insensitive. Unless otherwise
>> stated in the
>> definition of a particular header field, field values,
>> parameter names,
>> and parameter values are case-insensitive. Tokens are always
>> case-insensitive".
>>
>>
>>
>> So, Can we take by default parameters as insensitive unless
>> specified?
>> Also can you share which parameters are case-insensitive and
>> which are
>> case-sensitive.
>>
>> Please reply it ASAP.
>>
>>
>>
>> Thanks in advance,
>>
>> Madhuri
>>
>>
>>
>>
>>
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>>
>> _______________________________________________
>> 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
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
