Subject: RE: [Sip] Open issue #100: case sensitivity of URL parameter valu es

From: Robert Sparks <[email-masked]>
Date: Fri, 18 Jan 2002 10:59:02 -0500

To follow up and close this thread:

bis-06 will state

The userpart of a SIP URI is compared case sensitive.
All other components are compared case-insensitive unless
the definition of the component specifies otherwise.

RjS

> -----Original Message-----
> From: Henning G. Schulzrinne [mailto:[email-masked]]
> Sent: Wednesday, September 26, 2001 7:32 PM
> To: Anders Kristensen
> Cc: [email-masked]
> Subject: Re: [Sip] Open issue #100: case sensitivity of URL parameter
> values
> 
> 
> Anders Kristensen wrote:
> > 
> 
> > The parts defining individual parameters say whether the 
> *value* of that
> > param is CS or not. My reading is that param names always are CS.
> 
> Unfortunately, the HTTP URL doesn't seem to have parameters (as in
> ;foo=bar).
> 
> Just to be sure we're talking about the same thing: there are two
> parameters in SIP, the URL parameters (like transport and 
> maddr) and the
> header parameters (as those found in abundance in the Contact header
> definition). There is no strict necessity that the two are treated the
> same. It is, unfortunately, not even clear whether header parameters
> (such as the 'q' parameter in HTTP) are CI or CS, although it is quite
> possible that I overlooked some statement in 2616 to that effect. 
> 
> I just looked at 2617 (Basic and Digest Authentication), since it has
> lots of parameters. According to Section 1.2:
> 
>    The realm directive (case-insensitive) is required for all
>    authentication schemes that issue a challenge. The realm value
>    (case-sensitive), ...
> 
> Thus, this is a case where the parameter name (realm, in this case) is
> CI. The other parameters in 2617 don't seem to say.
> 
> However, according to the BNF,
> 
>   "literal"
>       Quotation marks surround literal text. Unless stated otherwise,
>       the text is case-insensitive.
> 
> Thus, all the others are also CI.
> 
> It would be helpful if we can get further evidence of common 
> practice in
> HTTP, SMTP or kin.
> 
> -- 
> Henning Schulzrinne   http://www.cs.columbia.edu/~hgs
> 
> _______________________________________________
> Sip mailing list  http://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email-masked] for questions on current sip
> Use [email-masked] 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-masked] for questions on current sip
Use [email-masked] for new developments on the application of sip