Subject: [Speechsc] mrcpv2-01: tokens versus letters or numbers

From: "Eric Burger" <[email-masked]>
Date: Fri, 30 Jan 2004 16:05:12 -0500

Channel Identifier (S 5.4)

Why is the channel identifier hex?  Why is it not just a token -- a handle passed back and forth?

Also, the text still says the low two characters indicate the resource, but we have the @resource construction that makes the encoding redundant.

Is there any reason for this being a number and not a string?  If it is a string, I could see it being case sensitive to expand the token space, or leave it case insensitive, as there is no limit to the length of the string.

Should there be a length of the string?

Proxy-Sync-Id, Logging-Tag
Same thing here.  Why is it a letter string and not a token?  This really is a cookie.

Recognizer Context Block
Is this always ASCII printable A-Z characters?  Does the server community need this to be a binary object?

Failed URI Cause
Is this supposed to be the code and text from the protocol, e.g., if http?  If so, the ABNF does not allow spaces.

Input from the server community welcome, too.

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