draft-ietf-mmusic-sdp-new-00.txt   draft-ietf-mmusic-sdp-new-01.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-00.txt Van Jacobson/Packet Design draft-ietf-mmusic-sdp-new-01.txt Van Jacobson/Packet Design
Colin Perkins/ISI Colin Perkins/ISI
17 November 2000 Expires: September 2001
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
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 15, line 10 skipping to change at page 15, line 10
It is illegal for the slash notation described above to be used for It is illegal for the slash notation described above to be used for
IP unicast addresses. IP unicast addresses.
Bandwidth Bandwidth
b=<modifier>:<bandwidth-value> b=<modifier>:<bandwidth-value>
o This specifies the proposed bandwidth to be used by the session or o This specifies the proposed bandwidth to be used by the session or
media, and is optional. media, and is optional.
o <bandwidth-value> is in kilobits per second o <bandwidth-value> is in kilobits per second by default. Modifiers
may specify that alternative units are to be used (the modifiers
defined in this memo use the default units).
o <modifier> is a single alphanumeric word giving the meaning of the o <modifier> is a single alphanumeric word giving the meaning of the
bandwidth figure. bandwidth figure.
o Two modifiers are initially defined: o Two modifiers are initially defined:
CT Conference Total: An implicit maximum bandwidth is associated with CT Conference Total: An implicit maximum bandwidth is associated with
each TTL on the Mbone or within a particular multicast each TTL on the Mbone or within a particular multicast
administrative scope region (the Mbone bandwidth vs. TTL limits administrative scope region (the Mbone bandwidth vs. TTL limits
are given in the MBone FAQ). If the bandwidth of a session or are given in the MBone FAQ). If the bandwidth of a session or
skipping to change at page 21, line 18 skipping to change at page 21, line 20
In such a case, the ports used depend on the transport protocol. In such a case, the ports used depend on the transport protocol.
For RTP, only the even ports are used for data and the corresponding For RTP, only the even ports are used for data and the corresponding
one-higher odd port is used for RTCP. For example: one-higher odd port is used for RTCP. For example:
m=video 49170/2 RTP/AVP 31 m=video 49170/2 RTP/AVP 31
would specify that ports 49170 and 49171 form one RTP/RTCP pair and would specify that ports 49170 and 49171 form one RTP/RTCP pair and
49172 and 49173 form the second RTP/RTCP pair. RTP/AVP is the 49172 and 49173 form the second RTP/RTCP pair. RTP/AVP is the
transport protocol and 31 is the format (see below). transport protocol and 31 is the format (see below).
It is illegal for both multiple addresses to be specified in the If multiple addresses are specified in the ``c='' field and multiple
``c='' field and for multiple ports to be specified in the ``m='' ports are specified in the ``m='' field, a one-to-one mapping from
field in the same session description. port to the corresponding address is implied. For example:
c=IN IP4 224.2.1.1/127/2
m=video 49170/2 RTP/AVP 31
would imply that address 224.2.1.1 is used with ports 49170 and
49171, and address 224.2.1.2 is used with ports 49172 and 49173.
o The third sub-field is the transport protocol. The transport o The third sub-field is the transport protocol. The transport
protocol values are dependent on the address-type field in the protocol values are dependent on the address-type field in the
``c='' fields. Thus a ``c='' field of IP4 defines that the ``c='' fields. Thus a ``c='' field of IP4 defines that the
transport protocol runs over IP4. For IP4, it is normally expected transport protocol runs over IP4. For IP4, it is normally expected
that most media traffic will be carried as RTP over UDP. The that most media traffic will be carried as RTP over UDP. The
following transport protocols are preliminarily defined, but may be following transport protocols are preliminarily defined, but may be
extended through registration of new protocols with IANA: extended through registration of new protocols with IANA:
- RTP/AVP - the IETF's Realtime Transport Protocol using the - RTP/AVP - the IETF's Realtime Transport Protocol using the
 End of changes. 4 change blocks. 
6 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/