draft-ietf-mmusic-connectivity-precon-01.txt   draft-ietf-mmusic-connectivity-precon-02.txt 
MMUSIC Working Group F. Andreasen MMUSIC Working Group F. Andreasen
Internet-Draft Cisco System, Inc. Internet-Draft Cisco System, Inc.
Expires: April 22, 2006 G. Camarillo Expires: December 3, 2006 G. Camarillo
Ericsson Ericsson
D. Oran D. Oran
Cisco Systems, Inc Cisco Systems, Inc
D. Wing D. Wing
Cisco Systems, Inc. Cisco Systems, Inc.
October 19, 2005 June 1, 2006
Connectivity Preconditions for Session Description Protocol Media Connectivity Preconditions for Session Description Protocol Media
Streams Streams
draft-ietf-mmusic-connectivity-precon-01.txt draft-ietf-mmusic-connectivity-precon-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 40 skipping to change at page 1, line 40
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 April 22, 2006. This Internet-Draft will expire on December 3, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a new connectivity precondition for the Session This document defines a new connectivity precondition for the Session
Description Protocol precondition framework described in RFC 3312 Description Protocol precondition framework described in RFC 3312
(and its update, RFC4032). A connectivity precondition can be used (and its update, RFC4032). A connectivity precondition can be used
to delay session establishment or modification until media stream to delay session establishment or modification until media stream
connectivity has been verified successfully. The method of connectivity has been verified successfully. The method of
verification may vary depending on the type of transport used for the verification may vary depending on the type of transport used for the
media. For reliable connection-oriented transports such as TCP media. For reliable connection-oriented transports such as TCP
skipping to change at page 2, line 29 skipping to change at page 2, line 29
3.2. Operational semantics . . . . . . . . . . . . . . . . . . 4 3.2. Operational semantics . . . . . . . . . . . . . . . . . . 4
3.3. Status type . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Status type . . . . . . . . . . . . . . . . . . . . . . . 4
3.4. Direction tag . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Direction tag . . . . . . . . . . . . . . . . . . . . . . 4
3.5. Precondition strength . . . . . . . . . . . . . . . . . . 5 3.5. Precondition strength . . . . . . . . . . . . . . . . . . 5
4. Verifying connectivity . . . . . . . . . . . . . . . . . . . . 6 4. Verifying connectivity . . . . . . . . . . . . . . . . . . . . 6
4.1. Procedures for connection-oriented transports . . . . . . 7 4.1. Procedures for connection-oriented transports . . . . . . 7
4.2. Procedures for datagram transports . . . . . . . . . . . . 8 4.2. Procedures for datagram transports . . . . . . . . . . . . 8
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 14 6. Security Considerations . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.1. Normative References . . . . . . . . . . . . . . . . . . . 15 8.1. Changes since -01 . . . . . . . . . . . . . . . . . . . . 15
8.2. Informative References . . . . . . . . . . . . . . . . . . 15 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18 Intellectual Property and Copyright Statements . . . . . . . . . . 18
1. Introduction 1. Introduction
The concept of a Session Description Protocol (SDP) [2] precondition The concept of a Session Description Protocol (SDP) [2] precondition
in the Session Initiation Protocol (SIP) [SIP] is defined in RFC3312 in the Session Initiation Protocol (SIP) [SIP] is defined in RFC3312
[4] (updated by RFC4032 [6]). A precondition is a condition that has [4] (updated by RFC4032 [6]). A precondition is a condition that has
to be satisfied for a given media stream in order for session to be satisfied for a given media stream in order for session
establishment or modification to proceed. When the precondition is establishment or modification to proceed. When the precondition is
skipping to change at page 15, line 5 skipping to change at page 15, line 5
to the SDP session descriptions. S/MIME [5] is the natural choice to to the SDP session descriptions. S/MIME [5] is the natural choice to
provide such end-to-end integrity protection, as described in RFC provide such end-to-end integrity protection, as described in RFC
3261 [3]. 3261 [3].
7. IANA Considerations 7. IANA Considerations
IANA is hereby requested to register a RFC 3312 precondition type IANA is hereby requested to register a RFC 3312 precondition type
called "conn" with the name "Connectivity precondition". The called "conn" with the name "Connectivity precondition". The
reference for this precondition type is the current document. reference for this precondition type is the current document.
8. References 8. Change Log
8.1. Normative References 8.1. Changes since -01
There are no changes since the previous version of the document.
9. References
9.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[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.
skipping to change at page 15, line 32 skipping to change at page 15, line 38
[5] Peterson, J., "S/MIME Advanced Encryption Standard (AES) [5] Peterson, J., "S/MIME Advanced Encryption Standard (AES)
Requirement for the Session Initiation Protocol (SIP)", Requirement for the Session Initiation Protocol (SIP)",
RFC 3853, July 2004. RFC 3853, July 2004.
[6] Camarillo, G. and P. Kyzivat, "Update to the Session Initiation [6] Camarillo, G. and P. Kyzivat, "Update to the Session Initiation
Protocol (SIP) Preconditions Framework", RFC 4032, March 2005. Protocol (SIP) Preconditions Framework", RFC 4032, March 2005.
[7] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A [7] Rosenberg, J., "Interactive Connectivity Establishment (ICE): A
Methodology for Network Address Translator (NAT) Traversal for Methodology for Network Address Translator (NAT) Traversal for
Offer/Answer Protocols", draft-ietf-mmusic-ice-05 (work in Offer/Answer Protocols", draft-ietf-mmusic-ice-08 (work in
progress), July 2005. progress), March 2006.
8.2. Informative References 9.2. Informative References
[8] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, [8] Postel, J., "Transmission Control Protocol", STD 7, RFC 793,
September 1981. September 1981.
[9] Stone, J., Stewart, R., and D. Otis, "Stream Control [9] Stone, J., Stewart, R., and D. Otis, "Stream Control
Transmission Protocol (SCTP) Checksum Change", RFC 3309, Transmission Protocol (SCTP) Checksum Change", RFC 3309,
September 2002. September 2002.
[10] Rosenberg, J., Weinberger, J., Huitema, C., and R. Mahy, "STUN [10] Rosenberg, J., Weinberger, J., Huitema, C., and R. Mahy, "STUN
- Simple Traversal of User Datagram Protocol (UDP) Through - Simple Traversal of User Datagram Protocol (UDP) Through
skipping to change at page 16, line 9 skipping to change at page 16, line 16
[11] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video [11] Schulzrinne, H. and S. Casner, "RTP Profile for Audio and Video
Conferences with Minimal Control", STD 65, RFC 3551, July 2003. Conferences with Minimal Control", STD 65, RFC 3551, July 2003.
[12] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the [12] Yon, D. and G. Camarillo, "TCP-Based Media Transport in the
Session Description Protocol (SDP)", RFC 4145, September 2005. Session Description Protocol (SDP)", RFC 4145, September 2005.
[13] Andreasen, F., "A No-Op Payload Format for RTP", [13] Andreasen, F., "A No-Op Payload Format for RTP",
draft-wing-avt-rtp-noop-03 (work in progress), May 2005. draft-wing-avt-rtp-noop-03 (work in progress), May 2005.
[14] Kohler, E., "Datagram Congestion Control Protocol (DCCP)", [14] Kohler, E., "Datagram Congestion Control Protocol (DCCP)",
draft-ietf-dccp-spec-11 (work in progress), March 2005. draft-ietf-dccp-spec-13 (work in progress), December 2005.
Authors' Addresses Authors' Addresses
Flemming Andreasen Flemming Andreasen
Cisco System, Inc. Cisco System, Inc.
499 Thornall Street, 8th Floor 499 Thornall Street, 8th Floor
Edison, NJ 08837 Edison, NJ 08837
USA USA
Email: fandreas@cisco.com Email: fandreas@cisco.com
skipping to change at page 18, line 41 skipping to change at page 18, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 12 change blocks. 
15 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/