El Thursday 21 August 2008 08:09:51 Rockson Li (zhengyli) escribió: > Hi folks, > > RFC3261 > 16.6 Request Forwarding > 2. Request-URI > > The Request-URI in the copy's start line MUST be replaced with > the URI for this target. If the URI contains any parameters > not allowed in a Request-URI, they MUST be removed. > > But I don't see which parameter(s) is/are not allowed in Req-URI, > Since as per BNF below, it looks like all SIP-URI / SIPS-URI / > absoluteURI is ok for Req-URI > > SIP-URI = "sip:" [ userinfo ] hostport uri-parameters [ > headers ] > uri-parameters = *( ";" uri-parameter) > uri-parameter = transport-param / user-param / method-param > / ttl-param / maddr-param / lr-param / other-param > > Request-URI = SIP-URI / SIPS-URI / absoluteURI > > > Could anybody clarify please?
The only real illegal URI parameter in Request-URI is "method": 19.1.5 Forming Requests from a URI An implementation MUST include any provided transport, maddr, ttl, or user parameter in the Request-URI of the formed request. If the URI contains a method parameter, its value MUST be used as the method of the request. **The method parameter MUST NOT be placed in the Request-URI.** Unknown URI parameters MUST be placed in the message's Request-URI. -- Iñaki Baz Castillo [EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
