draft-ietf-mmusic-sdp-new-09.txt   draft-ietf-mmusic-sdp-new-10.txt 
Internet Engineering Task Force MMUSIC WG Internet Engineering Task Force MMUSIC WG
INTERNET-DRAFT Mark Handley/ACIRI INTERNET-DRAFT Mark Handley/ACIRI
draft-ietf-mmusic-sdp-new-09.txt Van Jacobson/Packet Design draft-ietf-mmusic-sdp-new-10.txt Van Jacobson/Packet Design
Colin Perkins/ISI Colin Perkins/ISI
17 May 2002 27 May 2002
Expires: November 2002 Expires: November 2002
SDP: Session Description Protocol SDP: Session Description Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
skipping to change at page 7, line 26 skipping to change at page 7, line 26
When many session descriptions are being distributed by SAP, or any When many session descriptions are being distributed by SAP, or any
other advertisement mechanism, it may be desirable to filter other advertisement mechanism, it may be desirable to filter
announcements that are of interest from those that are not. SDP announcements that are of interest from those that are not. SDP
supports a categorisation mechanism for sessions that is capable of supports a categorisation mechanism for sessions that is capable of
being automated. being automated.
5.6. Internationalization 5.6. Internationalization
The SDP specification recommends the use of the ISO 10646 character sets The SDP specification recommends the use of the ISO 10646 character sets
in the UTF-8 encoding (RFC 2044) to allow many different languages to be in the UTF-8 encoding (RFC 2279) to allow many different languages to be
represented. However, to assist in compact representations, SDP also represented. However, to assist in compact representations, SDP also
allows other character sets such as ISO 8859-1 to be used when desired. allows other character sets such as ISO 8859-1 to be used when desired.
Internationalization only applies to free-text fields (session name and Internationalization only applies to free-text fields (session name and
background information), and not to SDP as a whole. background information), and not to SDP as a whole.
6. SDP Specification 6. SDP Specification
SDP session descriptions are entirely textual using the ISO 10646 SDP session descriptions are entirely textual using the ISO 10646
character set in UTF-8 encoding. SDP field names and attribute names character set in UTF-8 encoding. SDP field names and attribute names
use only the US-ASCII subset of UTF-8, but textual fields and attribute use only the US-ASCII subset of UTF-8, but textual fields and attribute
skipping to change at page 46, line 26 skipping to change at page 46, line 26
[7] ISO/IEC 10646-1:1993. International Standard -- Information [7] ISO/IEC 10646-1:1993. International Standard -- Information
technology -- Universal Multiple-Octet Coded Character Set (UCS) technology -- Universal Multiple-Octet Coded Character Set (UCS)
-- Part 1: Architecture and Basic Multilingual Plane. Five -- Part 1: Architecture and Basic Multilingual Plane. Five
amendments and a technical corrigendum have been published up amendments and a technical corrigendum have been published up
to now. UTF-8 is described in Annex R, published as Amendment 2. to now. UTF-8 is described in Annex R, published as Amendment 2.
[8] D. Goldsmith and M. Davis, ``Using Unicode with MIME'', RFC1641, [8] D. Goldsmith and M. Davis, ``Using Unicode with MIME'', RFC1641,
July 1994 July 1994
[9] F. Yergeau, ``UTF-8, a transformation format of Unicode and ISO [9] F. Yergeau, ``UTF-8, a transformation format of ISO 10646'',
10646'', RFC 2044, October 1996 RFC 2279, January 1998
[10] ITU-T Recommendation H.332 (1998): "Multimedia Terminal for [10] ITU-T Recommendation H.332 (1998): "Multimedia Terminal for
Receiving Internet-based H.323 Conferences", ITU, Geneva. Receiving Internet-based H.323 Conferences", ITU, Geneva.
[11] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, [11] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston,
J. Peterson, R. Sparks, M. Handley, E. Schooler ``SIP: Session J. Peterson, R. Sparks, M. Handley, E. Schooler ``SIP: Session
Initiatation Protocol'', RFC 3261, May 2002. Initiatation Protocol'', RFC 3261, May 2002.
[12] H. Schulzrinne, A. Rao and R. Lanphier, ``Real Time Streaming [12] H. Schulzrinne, A. Rao and R. Lanphier, ``Real Time Streaming
Protocol (RTSP)'' RFC 2326, April 1998. Protocol (RTSP)'' RFC 2326, April 1998.
[13] S. Bradner, ``Key words for use in RFCs to Indicate Requirement [13] S. Bradner, ``Key words for use in RFCs to Indicate Requirement
Levels'', RFC 2119, March 1997. Levels'', RFC 2119, March 1997.
[14] J. Rosenberg and H. Schulzrinne, ``An Offer/Answer Model with [14] J. Rosenberg and H. Schulzrinne, ``An Offer/Answer Model with
SDP'', RFC 3264, May 2002. SDP'', RFC 3264, May 2002.
[15] C. Huitama, ``RTCP Attribute in SDP'', RFC XXXX, May 2002 [15] C. Huitema, ``RTCP Attribute in SDP'', RFC XXXX, May 2002
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/