On Fri, 2006-01-06 at 11:19 +0530,
[EMAIL PROTECTED] wrote:
> The ambiguity exists in the "contact" header.
>
> Contact = ("Contact" / "m" ) HCOLON
> ( STAR / (contact-param *(COMMA contact-param)))
> contact-param = (name-addr / addr-spec) *(SEMI contact-params)
>
> Since the contact can have multiple contact-params separated by comma and
> the grammar for
> contact-param supports addr-spec which doesnt have the "< LANGLE" and
> ">RANGLE" demarcators.
I assume you mean something like this:
Contact: sip:aaa,[EMAIL PROTECTED], sip:[EMAIL PROTECTED]
In my copy of RFC 3261, I have written a note on "contact-param" saying
"See last paragraph of section 20 for further information on
disambiguating contact-param." That paragraph reads:
The Contact, From, and To header fields contain a URI. If the URI
contains a comma, question mark or semicolon, the URI MUST be
enclosed in angle brackets (< and >). Any URI parameters are
contained within these brackets. If the URI is not enclosed in angle
brackets, any semicolon-delimited parameters are header-parameters,
not URI parameters.
So the example I presented above is invalid.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
