On Tue, 2012-07-24 at 18:12 +0530, Pranab Bohra wrote:
> From rfc 4566 -
>
> "In general, <value> is either a number of fields delimited by a single
> space character or a free format string, and is case-significant
> unless a specific field defines otherwise."
>
> I would infer that <value> is case-significant as well.
I've searched RFC 4566 and the only appearances of "significant" and
"sensitive" are these:
section 5 (applicable to all lines)
In general, <value> is either a number of fields delimited by a single
space character or a free format string, and is case-significant
unless a specific field defines otherwise.
section 6
a=charset:<character set>
... The character set identifier is
a US-ASCII string and MUST be compared against the IANA
identifiers using a case-insensitive comparison.
There are an assortment of examples showing some values as upper-case
and some as lower-case. But that appears to simply be how the values
are defined.
http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xml,
section "proto", agrees with RFC 4566 section 5.14 that some values of
<proto> are upper-case and some are lower-case:
<proto> is the transport protocol. The meaning of the transport
protocol is dependent on the address type field in the relevant
"c=" field. Thus a "c=" field of IP4 indicates that the transport
protocol runs over IP4. The following transport protocols are
defined, but may be extended through registration of new protocols
with IANA (see Section 8):
* udp: denotes an unspecified protocol running over UDP.
* RTP/AVP: denotes RTP [19] used under the RTP Profile for Audio
and Video Conferences with Minimal Control [20] running over
UDP.
* RTP/SAVP: denotes the Secure Real-time Transport Protocol [23]
running over UDP.
Similarly,
http://www.iana.org/assignments/rtp-parameters/rtp-parameters.xml
section "RTP Payload Format media types" shows some values in upper-case
and some in lower-case. Thus one must specify:
a=rtpmap:97 L16/48000/2
a=rtpmap:98 t140c
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
