Hi
See this paragraph from RFC 2543
The Retry-After general-header field can be used with a 503 (Service
Unavailable) response to indicate how long the service is expected to
be unavailable to the requesting client and with a 404 (Not Found),
600 (Busy), or 603 (Decline) response to indicate when the called
party anticipates being available again. The value of this field can
be either an SIP-date or an integer number of seconds (in decimal)
after the time of the response.
A REGISTER request MAY include this header field when deleting
registrations with "Contact: * ;expires: 0". The Retry-After value
then indicates when the user might again be reachable. The registrar
MAY then include this information in responses to future calls.
Regards
Ranjit
Mascon Communication Technologies
http://www.masconit.com
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 05, 2001 5:15 AM
Subject: [Sip-implementors] Shouldn't Retry-After be a general header ??
Hi All,
As per the RFC, Retry-After is a response header.
But section 6.38 (Retry-After) reads :
A REGISTER request MAY include this header field when
deleting registrations with "Contact: *;expires: 0". The Retry-After
value then indicates when the user might again be reachable.
If Retry-After can be used in a request as above, shouldn't it
be classified as a general header rather than a response header?
Thanks in advance,
Subhash Nayak
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
