On Mon, 2008-12-01 at 14:56 -0500, Arjun Nair wrote: > Scott Lawrence wrote: > > to be unambiguous, I'd make that: > > > > <uri><sip:[EMAIL PROTECTED];Route=my.path.com></uri> > > > > This doesn't validate as anyURI (using sipx-validate-xml).
Hmmm... not too surprising. The reason I suggested the angle brackets (<...>) is that in SIP we have the problem that semi-colon delimited parameters are ambiguous without the angle brackets, unless you know what part of a SIP message the uri value came from. They can be either field parameters or uri parameters. Looking back at RFC 3680, it becomes clear that the encoding you suggest below is correct: The "uri" element contains the URI associated with that contact. The "display-name" element contains the display name for the contact. The "display-name" element MAY contain the xml:lang attribute to indicate the language of the display name. The "unknown-param" element is used to convey contact header field parameters that are not specified in RFC 3261. One example are the user agent capability parameters specified in [11]. Each "unknown- param" element describes a single contact header field parameter. The name of the parameter is contained in the mandatory name attribute of the "unknown-param" element, and the value of the parameter is the content of the "unknown-param" element. since the 'path' we want to convey is a header field parameter, it belongs in unknown-param. > Here's my latest proposal: > > Reg-info xml: > > <?xml version="1.0"?> > <reginfo xmlns="urn:ietf:params:xml:ns:reginfo" > version="1" state="partial"> > <registration aor="sip:[EMAIL PROTECTED]" id="a7" state="active"> > <contact id="76" state="active" event="registered" > duration-registered="0"> > <uri>sip:[EMAIL PROTECTED]</uri> > <unknown-param name=path>my.path.com</unknown-param> > </contact> > </registration> > </reginfo> > > > This validates, and it should maintain interop/backward compatibility for > reg-info. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
