draft-ietf-mmusic-sdp-media-content-01.txt   draft-ietf-mmusic-sdp-media-content-02.txt 
MMUSIC Working Group J. Hautakorpi MMUSIC Working Group J. Hautakorpi
Internet-Draft G. Camarillo Internet-Draft G. Camarillo
Expires: August 20, 2006 Ericsson Expires: September 7, 2006 Ericsson
February 16, 2006 March 6, 2006
The SDP (Session Description Protocol) Content Attribute The SDP (Session Description Protocol) Content Attribute
draft-ietf-mmusic-sdp-media-content-01.txt draft-ietf-mmusic-sdp-media-content-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 20, 2006. This Internet-Draft will expire on September 7, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a new Session Description Protocol (SDP) media- This document defines a new Session Description Protocol (SDP) media-
level attribute, 'content'. The 'content' attribute defines the level attribute, 'content'. The 'content' attribute defines the
content of the media stream in more detailed level than the media content of the media stream in more detailed level than the media
skipping to change at page 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Related Techniques . . . . . . . . . . . . . . . . . . . . . . 3 3. Related Techniques . . . . . . . . . . . . . . . . . . . . . . 3
4. Motivation for the New Content Attribute . . . . . . . . . . . 4 4. Motivation for the New Content Attribute . . . . . . . . . . . 4
5. The Content Attribute . . . . . . . . . . . . . . . . . . . . 5 5. The Content Attribute . . . . . . . . . . . . . . . . . . . . 5
6. The Content Attribute in the Offer/Answer Model . . . . . . . 6 6. The Content Attribute in the Offer/Answer Model . . . . . . . 6
7. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
8. Operation with SMIL . . . . . . . . . . . . . . . . . . . . . 7 8. Operation with SMIL . . . . . . . . . . . . . . . . . . . . . 7
9. Security Considerations . . . . . . . . . . . . . . . . . . . 7 9. Security Considerations . . . . . . . . . . . . . . . . . . . 7
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
11. Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . . 8 11. Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . . 9
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
12.1. Normative References . . . . . . . . . . . . . . . . . . 9 12.1. Normative References . . . . . . . . . . . . . . . . . . 9
12.2. Informational References . . . . . . . . . . . . . . . . 9 12.2. Informational References . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . . . 11 Intellectual Property and Copyright Statements . . . . . . . . . . 12
1. Introduction 1. Introduction
SDP [1] is a protocol that is intended for describing multimedia SDP [1] is a protocol that is intended for describing multimedia
sessions for the purposes of session announcement, session sessions for the purposes of session announcement, session
invitation, and other forms of multimedia session initiation. One of invitation, and other forms of multimedia session initiation. One of
the most typical use cases of SDP is the one where it is used with the most typical use cases of SDP is the one where it is used with
SIP [5]. SIP [5].
There are situations where one application receives several similar There are situations where one application receives several similar
skipping to change at page 6, line 18 skipping to change at page 6, line 18
audio stream could be e.g., a sound of a jungle. Another example audio stream could be e.g., a sound of a jungle. Another example
is the video of the conference room while the main is the video of is the video of the conference room while the main is the video of
the speaker. This is similar to the 'live' role in H.239. the speaker. This is similar to the 'live' role in H.239.
user-floor: This indicates that a user level floor control is user-floor: This indicates that a user level floor control is
required. In other words, this is meant for system without any required. In other words, this is meant for system without any
mechanism for floor control, and where a human needs to figure out mechanism for floor control, and where a human needs to figure out
whether an act of floor control, e.g., saying 'over', is needed or whether an act of floor control, e.g., saying 'over', is needed or
not. Typical use case for this is e.g., a situation where the not. Typical use case for this is e.g., a situation where the
other endpoint of the connection is a walkie-talkie type of other endpoint of the connection is a walkie-talkie type of
device. device.
txp: This indicates that the media stream is originated from the txp: This indicates that the media stream is originated from a
Telecommunications Device for the Deaf (TDD), and it requires textphone, and it requires special behavior from the receiving
special behavior from the receiving application. Typical use case application. Typical use case for this is e.g., a connection
for this is e.g., a connection where one endpoint is an analog where one endpoint is an analog textphone of a kind that cannot
TDD, and the other one is a native IP based text telephone. handle two-way simultaneous text communication, and the other one
is a native IP based real time text capable terminal. The human
normally needs to apply formal turntaking habits, and need to
figure out to what extent it is possible to interrupt the other
part if needs arise.
All of the values can be used with any media type. Application can All of the values can be used with any media type. Application can
make decision on how to handle a single media stream based on both make decision on how to handle a single media stream based on both
media type and the value of 'content' attribute. Therefore the media type and the value of 'content' attribute. Therefore the
situation, where one value of 'content' attribute occurs more than situation, where one value of 'content' attribute occurs more than
once in a single session descriptor, is not problematic. once in a single session descriptor, is not problematic.
6. The Content Attribute in the Offer/Answer Model 6. The Content Attribute in the Offer/Answer Model
This specification does not define a means to discover whether or not This specification does not define a means to discover whether or not
skipping to change at page 8, line 37 skipping to change at page 8, line 39
subregistry: subregistry:
Value of 'content' attribute Reference Description Value of 'content' attribute Reference Description
---------------------------- --------- ----------- ---------------------------- --------- -----------
slides RFC xxxx Presentation slides slides RFC xxxx Presentation slides
speaker RFC xxxx Image from the speaker speaker RFC xxxx Image from the speaker
sl RFC xxxx Sign language sl RFC xxxx Sign language
main RFC xxxx Main media stream main RFC xxxx Main media stream
alt RFC xxxx Alternative media stream alt RFC xxxx Alternative media stream
user-floor RFC xxxx User level floor control req. user-floor RFC xxxx User level floor control req.
txp RFC xxxx Media is originated from TDD txp RFC xxxx Media from a textphone
Note for the RFC Editor: The 'RFC xxxx' in the above should be a
reference to the coming RFC number of this draft.
As per the terminology in RFC 2434 [4], the registration policy for As per the terminology in RFC 2434 [4], the registration policy for
new values for the 'content' parameter shall be 'Specification new values for the 'content' parameter shall be 'Specification
Required'. Required'.
11. Acknowledges 11. Acknowledges
Arnoud van Wijk and Roni Even provided valuable ideas for this Arnoud van Wijk and Roni Even provided valuable ideas for this
document. document.
 End of changes. 7 change blocks. 
13 lines changed or deleted 20 lines changed or added

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