draft-ietf-mmusic-offer-answer-examples-03.txt   draft-ietf-mmusic-offer-answer-examples-04.txt 
MMUSIC Working Group A. Johnston MMUSIC Working Group A. Johnston
Internet-Draft MCI Internet-Draft MCI
Expires: December 29, 2004 R. Sparks Expires: January 6, 2005 R. Sparks
dynamicsoft dynamicsoft
June 30, 2004 July 8, 2004
Session Description Protocol Offer Answer Examples Session Description Protocol Offer Answer Examples
draft-ietf-mmusic-offer-answer-examples-03 draft-ietf-mmusic-offer-answer-examples-04
Status of this Memo Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with and any of which I become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
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 35 skipping to change at page 1, line 35
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 December 29, 2004. This Internet-Draft will expire on January 6, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document gives examples of Session Description Protocol (SDP) This document gives examples of Session Description Protocol (SDP)
offer answer exchanges. Examples include codec negotiation and offer answer exchanges. Examples include codec negotiation and
selection, hold and resume, and addition and deletion of media selection, hold and resume, and addition and deletion of media
skipping to change at page 2, line 29 skipping to change at page 2, line 29
3.2 Hold with Two Streams . . . . . . . . . . . . . . . . . . 13 3.2 Hold with Two Streams . . . . . . . . . . . . . . . . . . 13
4. Addition and Deletion of Media Streams . . . . . . . . . . . . 14 4. Addition and Deletion of Media Streams . . . . . . . . . . . . 14
4.1 Second Audio Stream Added . . . . . . . . . . . . . . . . 14 4.1 Second Audio Stream Added . . . . . . . . . . . . . . . . 14
4.2 Audio then Video Added . . . . . . . . . . . . . . . . . . 15 4.2 Audio then Video Added . . . . . . . . . . . . . . . . . . 15
4.3 Audio and Video, then Video Deleted . . . . . . . . . . . 16 4.3 Audio and Video, then Video Deleted . . . . . . . . . . . 16
5. Third Party Call Control (3pcc) . . . . . . . . . . . . . . . 18 5. Third Party Call Control (3pcc) . . . . . . . . . . . . . . . 18
5.1 No Media, then Audio Added . . . . . . . . . . . . . . . . 18 5.1 No Media, then Audio Added . . . . . . . . . . . . . . . . 18
5.2 Hold and Unhold 2 . . . . . . . . . . . . . . . . . . . . 19 5.2 Hold and Unhold 2 . . . . . . . . . . . . . . . . . . . . 19
5.3 Hold and Unhold 3 . . . . . . . . . . . . . . . . . . . . 20 5.3 Hold and Unhold 3 . . . . . . . . . . . . . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. Changes since -00 . . . . . . . . . . . . . . . . . . . . . . 21 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
8. Changes since -01 . . . . . . . . . . . . . . . . . . . . . . 21 8. Informative References . . . . . . . . . . . . . . . . . . . . 21
9. Changes since -02 . . . . . . . . . . . . . . . . . . . . . . 21
10. Informative References . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22
Intellectual Property and Copyright Statements . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . 23
1. Overview 1. Overview
This document describes offer answer examples of Session Description This document describes offer answer examples of Session Description
Protocol (SDP) based on RFC 3264 [1]. The SDP in these examples are Protocol (SDP) based on RFC 3264 [1]. The SDP in these examples are
defined by RFC 2327 [2]. The offers and answers are assumed to be defined by RFC 2327 [2]. The offers and answers are assumed to be
transported using a protocol such as Session Initiation Protocol transported using a protocol such as Session Initiation Protocol
(SIP) [3]. (SIP) [3].
skipping to change at page 16, line 4 skipping to change at page 16, line 4
accepted by Bob. accepted by Bob.
[Offer] [Offer]
v=0 v=0
o=alice 2890844526 2890844526 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844526 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
m=audio 49170 RTP/AVP 0 m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/800 a=rtpmap:0 PCMU/8000
[Answer] [Answer]
v=0 v=0
o=bob 2808844564 2808844564 IN IP4 host.biloxi.example.com o=bob 2808844564 2808844564 IN IP4 host.biloxi.example.com
s= s=
c=IN IP4 host.biloxi.example.com c=IN IP4 host.biloxi.example.com
t=0 0 t=0 0
m=audio 49172 RTP/AVP 0 m=audio 49172 RTP/AVP 0
a=rtpmap:0 PCMU/8000 a=rtpmap:0 PCMU/8000
skipping to change at page 21, line 16 skipping to change at page 21, line 16
6. Security Considerations 6. Security Considerations
SDP offer and answer messages can contain private information about SDP offer and answer messages can contain private information about
addresses and sessions to be established between parties. If this addresses and sessions to be established between parties. If this
information needs to be kept private, some security mechanism in the information needs to be kept private, some security mechanism in the
protocol used to carry the offers and answers must be used. For SIP, protocol used to carry the offers and answers must be used. For SIP,
this means using TLS transport and/or S/MIME encryption of the SDP this means using TLS transport and/or S/MIME encryption of the SDP
message body. message body.
7. Changes since -00 7. IANA Considerations
- Added asymmetrical codec and attribute examples
8. Changes since -01
- Removed asymmetrical codec and attribute examples
- Updated references
9. Changes since -02
- Updated references
- Added sampling rate to iLBC rtmap lines
- Added sampling rate to telephone-event rtmap lines
- Fixed order of c= line in 4.1 Second Answer
- Fixed a= line in 4.3 Answer This document introduces no IANA considerations.
10 Informative References 8 Informative References
[1] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with [1] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
Session Description Protocol (SDP)", RFC 3264, June 2002. Session Description Protocol (SDP)", RFC 3264, June 2002.
[2] Handley, M. and V. Jacobson, "SDP: Session Description [2] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998. Protocol", RFC 2327, April 1998.
[3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[4] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF Digits, [4] Schulzrinne, H. and S. Petrack, "RTP Payload for DTMF Digits,
Telephony Tones and Telephony Signals", RFC 2833, May 2000. Telephony Tones and Telephony Signals", RFC 2833, May 2000.
[5] Rosenberg, J., Peterson, J., Schulzrinne, H. and G. Camarillo, [5] Rosenberg, J., Peterson, J., Schulzrinne, H. and G. Camarillo,
"Best Current Practices for Third Party Call Control (3pcc) in "Best Current Practices for Third Party Call Control (3pcc) in
the Session Initiation Protocol (SIP)", BCP 85, RFC 3725, April the Session Initiation Protocol (SIP)", BCP 85, RFC 3725, April
2004. 2004.
[6] Duric, A. and S. Andersen, "RTP Payload Format for iLBC Speech", [6] Duric, A. and S. Andersen, "RTP Payload Format for iLBC Speech",
draft-ietf-avt-rtp-ilbc-04 (work in progress), December 2003. draft-ietf-avt-rtp-ilbc-05 (work in progress), June 2004.
Authors' Addresses Authors' Addresses
Alan Johnston Alan Johnston
MCI MCI
100 South 4th Street 100 South 4th Street
St. Louis, MO 63102 St. Louis, MO 63102
EMail: alan.johnston@mci.com EMail: alan.johnston@mci.com
 End of changes. 

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