IETF DataTracker: draft-ietf-mmusic-sdp-new
This draft is replaced by
This version is intended to address
the GenART comments received during IESG review.
In addition the discussion of sharing ports between "m=" lines
has been removed from section 5.14, since there was no consensus
on that approach.
The complete list of changes is as follows:
I believe this is now ready to go to the RFC Editor.
This version corrects a problem with the email address ABNF.
This version clarifies signalling of non-contiguous ports for RTP and
The changes in this version are to fix section references in IANA
considerations, and expand "Encoding Considerations"; and to clarify
that the username and unicast-address in "o=" lines may be chosen to
obfuscate the actual values, provided this does not compromise the
global uniqueness of the field.
Changes in this version are:
There's a single change in this version: to remove the underspecified
"control" and "data" media types, aligning the SDP media types with MIME
media types. If there's a use for these media types they can be registered
separately. They've been removed here in the interests of getting the base
Running a diff with -18 will show many changes, due to differences in
the way the latest version of xml2rfc formats drafts. The main items
to note are:
These address the majority of comments received, although I have made
no attempt to better specify the "control" and "data" media types.
Changes in this version are: update ABNF for "proto"; clarify second
paragraph of Section 9.2.3, regarding use of RTP payload types as "fmt"
values; register the "RTP/SAVP" profile and its "fmt" namespace; and
clarify that only a single "a=fmtp:" attribute is allowed for each format.
This version removes TCP from allowable proto values, since this will
be defined by the comedia spec; specifies that "a=rtpmap:" is not
allowed at the session level; and clarifies the set of registered
Changes in this version:
The changes in this version are as follows:
Reformat and add table of contents. No technical changes.
Update IANA registration requirements for attributes and fmt values;
clarify UDP port usage;
disallow X- prefix payload format names (previously deprecated);
update references and make other editorial fixes.
Revert change to media-description ABNF, and instead fix the description
of "c=" to be consistant.
Add definition of decimal-uchar to ABNF (copied from RFC 3108)
Clarify the limitations of the k= field.
Split references into normative and informative sections
Clarify and tighten the rules in the IANA considerations section.
Editorial and formatting clean-ups.
In the media-description ABNF definition, the "*" in connection-field was
redundant and has been removed since connection-field defines itself as
optional; the X- notation for experimental parameters has been deprecated;
the example on page 23 has been corrected; the definition of email-safe
in the ABNF has been corrected; and the ABNF for "r=" has been corrected
to handle initial repeat of "0", matching examples.
Notes that RFC 2044 is obsoleted by RFC 2279, and corrects
Note relation to the offer/answer model, for use with SIP. Update use
of RFC 2119 terms. Clarify that "a=sendrecv" is the default, if none
of "sendonly", "recvonly", "inactive", or "sendrecv" is specified.
Make assorted editorial clarifications.
This version fixes the description of IPv6 multicast, especially
around TTL vs hop count. It also allows "a=rtpmap:" to be a session
level attribute, in addition to a media level, as discussed on the
Updates ABNF to be consistent with RFC 2234 and SDP/IPv6.
Changes since previous version: clarify that RTCP is still sent in an
a=recvonly session (similarly for sendonly and inactive); fix ABNF to
include a unicast-address element, allowing comedia to align with both
this and RFC2327; use "s= " rather than "s=-", fix ABNF to reflect that
s= is mandatory, and clarify that s= lines needs to be non-empty and
SHOULD contain ISO 10646 formatted content.
Changes in this version include:
For "b=", note that modifiers may specify that alternate units are
to be used, but that the modifiers specified in this draft use the
default of kilobits per second. Clarify meaning when there are "c="
lines containing multiple addresses with multiple ports specified
on the "m=" lines.
This draft is essentially identical to RFC 2327. It is made
available to stimulate discussion of corrections and clarifications
which need to be made in order to advance SDP to a draft standard RFC.
This draft defines the Session Description Protocol, SDP. SDP is
intended for describing multimedia sessions for the purposes of session
announcement, session invitation, and other forms of multimedia session
initiation. This draft is eventually intended to replace 2327.