From: "Chaney, Charles \(SNL US\)" <[EMAIL PROTECTED]>
Should the other contact binding reflect the remaining
(time-to-live) expiration value or be updated to reflect the new
registration (or refresh), i.e., all are reported with the same
expires value. I cannot point to any definitive requirement in
RFC3261.
The relevent text is the description of how a 200 response to a
REGISTER is constructed, in section 10.3, item 8:
8. The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar. The response SHOULD include a Date header field.
Admittedly, that doesn't make a lot of sense. I believe that the
third sentence should have been written:
Each Contact value MUST feature an "expires" parameter
indicating its REMAINING expiration interval (WHICH WAS
chosen by the registrar).
The "expires" parameter wouldn't be of any value if it didn't give the
remaining expiration time of the contact it is attached to.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
