From: =?iso-8859-1?Q?Andreas_Bystr=F6m?= <[EMAIL PROTECTED]>
What is the expected content of the Timestamp header in RFC3261? In the
example on page 178 I found this:
"Timestamp: 54"
Is another "kind of timestamp" (full date and time) also allowed? Like
"Timestamp: 11142006114432"
(year 2006, month 11, day 14 and so on, you get it)
I guess that it should be an integeer like in the first case, but if the
second is allowed as well I guess I have to take different actions in a
parser (since the second example wont fit in a unsigned int variable). Right
now I have a UA sending a Timestamp header like my second example, and I'm
not sure if it is wrong in that UA, or if it is the parser implementation
that is to strict.
RFC 3261, section 25.1:
Timestamp = "Timestamp" HCOLON 1*(DIGIT)
[ "." *(DIGIT) ] [ LWS delay ]
delay = *(DIGIT) [ "." *(DIGIT) ]
Section 20.38 Timestamp:
The Timestamp header field describes when the UAC sent the request to
the UAS.
See Section 8.2.6 for details on how to generate a response to a
request that contains the header field. Although there is no
normative behavior defined here that makes use of the header, it
allows for extensions or SIP applications to obtain RTT estimates.
Section 8.2.6.1 Sending a Provisional Response
When a 100 (Trying) response is generated, any Timestamp header field
present in the request MUST be copied into this 100 (Trying)
response. If there is a delay in generating the response, the UAS
SHOULD add a delay value into the Timestamp value in the response.
This value MUST contain the difference between the time of sending of
the response and receipt of the request, measured in seconds.
This, it appears that the first field is arbitrarily chosen by the
sender, and the delay field is added by the recipient to indicate any
delay in processing.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
