RE: [Speechsc] Re: Query in the Handling of List Type headers

As you point out, the specification only permits multiple copies of the
header if the value for the header is a comma-separated list, so the
answer is no - it is not legal to have multiple Lexicon-Search-Order
headers.

In a future version of MRCP it may be worthwhile to make the behavior
(and possibly syntax) of all list-valued headers consistent.

-- dan

________________________________

From: sreekanth [mailto:sreekanthm@huawei.com] 
Sent: Monday, March 12, 2007 1:18 AM
To: Pete Cordell
Cc: speechsc@ietf.org; Saravanan Shanmugham (sarvi)
Subject: [Speechsc] Re: Query in the Handling of List Type headers

Hi ,

I am resending the same mail which has been posted before after removing
the boilerplate at the end.. Pls consider this and reply.

The section 6.2. Generic Message Headers of the draft explains the
handling of List type headers..

Multiple headers with the same name MAY be present in a message if and
only if the entire value for that header is defined as a comma-separated
list [i.e., #(values)].

There are some headers like Lexicon-Search-Order,
Vendor-Specific-Parameters, Voice-Name which are Non-Singleton or List
type headers, but are not COMMA seperated..

Is it correct for the MRCP implementation to send message with Multiple
Lexicon-Search-Order headers??

Pls clarify on this..

Thanking you in advance..

Sreekanth