inline... Attila Sipos wrote: > It's not legal. > > The " would have to be escaped > > So this would be ok > Contact: <sip:[EMAIL PROTECTED]:5060;tgrp=%22name2%22> > > I mean, I don't know for sure it's not legal but > such a trivial change (to allow the ") is so > unnecessary that I doubt it would be allowed. > It would break all SIP parsers for a start - > usually when new parameters are introduced they > agree with the standard grammar. > > In this case for a uri-parameter, all new parameters > have to agree with the definition of other-param: > > other-param = pname [ "=" pvalue ] > pname = 1*paramchar > pvalue = 1*paramchar > paramchar = param-unreserved / unreserved / escaped > param-unreserved = "[" / "]" / "/" / ":" / "&" / "+" / "$" > > No double quote characters are allowed in the paramchar. > > single quote is ok - so the following would be allowed too: > Contact: <sip:[EMAIL PROTECTED]:5060;tgrp='name2'>
But note that in this case the quote characters are part of the attribute value which is almost certainly not what is wanted or expected here. Thanks, Anders > > > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of Valentin Nechayev > Sent: Fri 23/05/2008 18:26 > To: [email protected] > Subject: [Sip-implementors] quoted URI parameters (especially, tgrp) > > Hi, > > is there a new RFC or even draft which allows syntax like > > Contact: <sip:[EMAIL PROTECTED]:5060;tgrp="name2"> > > ? > > According to RFC3261, quotes aren't allowed for pvalue, but seems > style as shown is common at least for two vendors. > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
