Nir Hasson ha scritto: > Hi all, > > In RFC4475 (SIP torture), the following Request-URI considered to be > illegal, because it contains escaped header (%3C, %3E): > > sip:[EMAIL PROTECTED]:example.com%3E SIP/2.0 > > But, looking at the BNF rules at RFC3261 (below) it seem that header > can be > escaped (definition of hname for instance). > Am I missing something? > > > [cut]
In general the headers must escape all disallowed characters. Please refer also to rfc 3261 table 1 page 152 to see what URI's components are allowed in the several fields in which URIs can appear. As you will see, headers are not allowed in request-URI field. On page 151 it is stated that "Elements processing URIs SHOULD ignore any disallowed components if they are present." For the implementation your UAC MUST not generate a request-URI with headers, and your UAS SHOULD ignore any headers in request-URI in a received request. So the posted example must not be generated by a UAC, but should be processed by a UAS. -- Marco Ambu Abbeynet S.p.a. <http://www.abbeynet.it> E-mail: [EMAIL PROTECTED] VoIP address: <sip:[EMAIL PROTECTED]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
