Praveen ha scritto: >Hi , > As per Sec 25.1 of RFC 3261 a userinfo part of SIP URI can >contain *","* as acceptable character. But the SIP URI's can appear in >multiples separated by COMMA in headers like Record-Route/ Route/ >Contact etc.,. contradicting the said rule. How we distinguish whether >it is a user part or another followed URI, since COMMA is only separator > >for the list. > >Excerpts of the rule from RFC is as below > >userinfo = ( user / telephone-subscriber ) [ ":" password ] "@" > >user = 1*( unreserved / escaped / user-unreserved ) > >user-unreserved = "&" / "=" / "+" / "$" / *","* / ";" / "?" / "/" > >Record-Route = "Record-Route" HCOLON rec-route *(*COMMA* rec-route) > > >Thanks, >praveen > > 1) URI in the form of "addr-spec": if the userinfo field is present also
character '@' is present to separate user part from host. 2) URI in the form of "(name-addr / addr-spec)": name-addr form MUST be used so the URI is enclosed between angular brackets "<>". 3) Lists of URIs are never composed by addr-spec (for example Contact, From, To, ...). I have not found any expression like *(COMMA addr-spec). 1) sip:my,[EMAIL PROTECTED] --> OK 2) <sip:my,[EMAIL PROTECTED]>,<sip:my,[EMAIL PROTECTED]>,sip:[EMAIL PROTECTED] --> OK 3) sip:my,[EMAIL PROTECTED],sip:my,[EMAIL PROTECTED] --> NEVER HAPPENS Point 2 is a 'generalization' to all headers containing a list of URIs of what RFC 3261 says. > From RFC 3261, chapter 20: 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. Marco Ambu Abbeynet _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
