From: "J Jayakumar" <[EMAIL PROTECTED]> In RFC 3261 under section 10.2.4 it has been specified that the 200 ok response from a registrar may or may not have a expires parameter in the contact header. And in Section 10.3. 8 it has been said that the 200 ok from a registrar MUST have a expires parameter in the contact header.
Absolutely speaking, 10.3 item 8 says that any 200 responses generated must have an expires on each contact. 10.2.4 says how the UA must process 200 responses which do not have an expires on each contact. It's possible that this is a leftover from RFC 2543, that it allowed responses to be generated that did not have expires parameters on contacts. In practice, the question seems moot, because if there are multiple contacts for an AOR, the registrar has to keep separate expiration timers for each of them, so it's more convenient to apply an expires parameter to each contact than to determine a "global" expiration, and then apply expires parameters to each contact with a different expiration (which will be all but one of them, or all of them). Normatively, we'll have to see how bug 682 is resolved. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
