Gaurav Taneja wrote:
>
> Hi,
>
> Could someone clarify the following?
>
> 1. RFC 2543-bis(2), pg. 30, sec. 4.2.6
>
> "Having the proxy server interpret the 'q' parameter is not sufficient
> to guide proxy behavior, as it is not clear, for example, how long it is
> supposed to wait between trying addresses".
>
> How is the 'q' parameter used here?
The q value is used in the Contact header to indicate the relative pref-
erence of the locations to proxy the request. For a parallel forking
proxy, the q value is immaterial since it may fork to all locations regard-
less of their q value. A serial forking proxy, on the other hand, may
sort the locations on the q value and contact each location in turn. The
paragraph above, I believe, is trying to outline this problem since the
proxy will not know how long it is supposed to wait between trying
addresses.
> 2. RFC 2543-bis(2), pg. 30, sec. 4.2.6
>
> All current registrations MUST share the same action value.
> Registrations that have a different action than current registrations
> for the same user MUST be rejected with status of 409
> (Conflict).
>
> What does the "action" value indicate?
redirect or proxy.
> 3. RFC 2543-bis(2), pg. 31, sec. 4.3
>
> "A server that receives a SIP-URL with illegal elements removes them
> before further processing".
>
> Is this required? The server could generate class 4xx response - bad
> request in this case.
Not quite; for instance, the From (and To) SIP header must not contain
transport-param, ttl-param, maddr-param, or headers. A server receiving
a From (To) SIP URL with these parameters should simply ignore them.
Likewise, if the R-URI contains a method parameter, it should be ignored
instead of elicting a 4xx response.
Hmmm, looking at Table 2, headers are not allowed in R-URI; I always assumed
they were -- oh well...
- vijay
--
Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org}
Internet Software and eServices Group
Lucent Technologies/Bell Labs Innovations 263 Shuman Blvd., Rm 1A-413
Naperville, Illinois 60566 Voice: +1 630 224 0216 Fax: +1 630 713 0184
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
