Subject: [Speechsc] request-id

From: "Reifenrath, Klaus" <[email-masked]>
Date: Fri, 7 May 2004 09:02:14 -0400

Currently it is only required that the request-id is a unique identifier. 
In MRCPv1 client and server could make use of the command sequence number
(CSeq header field) of the RTSP message. 
In MRCPv2 the request-id can take over this part, if it meets the following
requirements:
The initial value of the request-id is arbitrary, but MUST be less than
2**31.
Consecutive requests within a MRCP session MUST contain strictly
monotonically
increasing and contiguous request-id's; request-id's do not wrap around.

Klaus

_______________________________________________
Speechsc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/speechsc