Hi,
you might want to look at rfc 2119 ("Key words for use
in RFCs to Indicate Requirement Levels")
http://www.ietf.org/rfc/rfc2119.txt
3. SHOULD This word, or the adjective "RECOMMENDED", mean that there
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course.
So, it is recommended that a Date header is inserted
and you can, if you like, use the information in that header to
set an internal clock.
But you don't have to do either.
MUST > SHOULD > MAY
( I don't like SHOULD - if it's recommended, why not make things
a MUST? I'm sure this would make things more interoperable!!
But anyway... )
Regards,
Attila
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Iñaki Baz
Castillo
Sent: 03 March 2008 08:30
To: [email protected]
Subject: [Sip-implementors] Is "Date" header mandatory in a REGISTER's 200OK?
Hi, I'm sure that "Date "header is not mandatory at all in the 200 OK to a
REGISTER. In fact I don0t know a registrar adding it.
But RFC 3261 says:
------------------------------------------------------------------
10.3 Processing REGISTER Requests
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.
------------------------------------------------------------------
But it also says:
------------------------------------------------------------------
10.2.5 Setting the Internal Clock
If the response for a REGISTER request contains a Date header field,
the client MAY use this header field to learn the current time in
order to set any internal clocks.
------------------------------------------------------------------
So? is that "Date" header a SHOULD or a MAY?
--
Iñaki Baz Castillo
[EMAIL PROTECTED]
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
