draft-ietf-mmusic-connectivity-precon-04.txt   draft-ietf-mmusic-connectivity-precon-05.txt 
MMUSIC Working Group F. Andreasen MMUSIC Working Group F. Andreasen
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track G. Camarillo Intended status: Standards Track G. Camarillo
Expires: July 26, 2008 Ericsson Expires: April 27, 2009 Ericsson
D. Oran D. Oran
D. Wing D. Wing
Cisco Systems, Inc. Cisco Systems, Inc.
January 23, 2008 October 24, 2008
Connectivity Preconditions for Session Description Protocol Media Connectivity Preconditions for Session Description Protocol Media
Streams Streams
draft-ietf-mmusic-connectivity-precon-04.txt draft-ietf-mmusic-connectivity-precon-05.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 39 skipping to change at page 1, line 39
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 July 26, 2008. This Internet-Draft will expire on April 27, 2009.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines a new connectivity precondition for the Session This document defines a new connectivity precondition for the Session
Description Protocol (SDP) precondition framework. A connectivity Description Protocol (SDP) precondition framework. A connectivity
precondition can be used to delay session establishment or precondition can be used to delay session establishment or
modification until media stream connectivity has been successfully modification until media stream connectivity has been successfully
verified. The method of verification may vary depending on the type verified. The method of verification may vary depending on the type
of transport used for the media. For unreliable datagram transports of transport used for the media. For unreliable datagram transports
such as UDP, verification involves probing the stream with data or such as UDP, verification involves probing the stream with data or
skipping to change at page 2, line 24 skipping to change at page 2, line 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Connectivity Precondition Definition . . . . . . . . . . . . . 3 3. Connectivity Precondition Definition . . . . . . . . . . . . . 3
3.1. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Operational Semantics . . . . . . . . . . . . . . . . . . 4 3.2. Operational Semantics . . . . . . . . . . . . . . . . . . 4
3.3. Status Type . . . . . . . . . . . . . . . . . . . . . . . 4 3.3. Status Type . . . . . . . . . . . . . . . . . . . . . . . 4
3.4. Direction Tag . . . . . . . . . . . . . . . . . . . . . . 5 3.4. Direction Tag . . . . . . . . . . . . . . . . . . . . . . 5
3.5. Precondition Strength . . . . . . . . . . . . . . . . . . 5 3.5. Precondition Strength . . . . . . . . . . . . . . . . . . 5
4. Verifying Connectivity . . . . . . . . . . . . . . . . . . . . 6 4. Verifying Connectivity . . . . . . . . . . . . . . . . . . . . 6
4.1. Media Stream to Dialog Correlation . . . . . . . . . . . . 6 4.1. Media Stream to Dialog Correlation . . . . . . . . . . . . 7
4.2. Explicit Connectivity Verification Mechanisms . . . . . . 7 4.2. Explicit Connectivity Verification Mechanisms . . . . . . 7
4.3. Verifying Connectivity for Connection-Oriented 4.3. Verifying Connectivity for Connection-Oriented
Transports . . . . . . . . . . . . . . . . . . . . . . . . 9 Transports . . . . . . . . . . . . . . . . . . . . . . . . 9
5. Connectivity and Other Precondition Types . . . . . . . . . . 9 5. Connectivity and Other Precondition Types . . . . . . . . . . 9
6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Changes since -03 . . . . . . . . . . . . . . . . . . . . 15 9.1. Changes since -03 . . . . . . . . . . . . . . . . . . . . 15
9.2. Changes since -02 . . . . . . . . . . . . . . . . . . . . 15 9.2. Changes since -02 . . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 16, line 48 skipping to change at page 16, line 48
RFC 5027, October 2007. RFC 5027, October 2007.
[I-D.ietf-avt-rtp-no-op] [I-D.ietf-avt-rtp-no-op]
Andreasen, F., "A No-Op Payload Format for RTP", Andreasen, F., "A No-Op Payload Format for RTP",
draft-ietf-avt-rtp-no-op-04 (work in progress), May 2007. draft-ietf-avt-rtp-no-op-04 (work in progress), May 2007.
[I-D.ietf-mmusic-ice] [I-D.ietf-mmusic-ice]
Rosenberg, J., "Interactive Connectivity Establishment Rosenberg, J., "Interactive Connectivity Establishment
(ICE): A Protocol for Network Address Translator (NAT) (ICE): A Protocol for Network Address Translator (NAT)
Traversal for Offer/Answer Protocols", Traversal for Offer/Answer Protocols",
draft-ietf-mmusic-ice-16 (work in progress), June 2007. draft-ietf-mmusic-ice-19 (work in progress), October 2007.
[I-D.ietf-mmusic-ice-tcp] [I-D.ietf-mmusic-ice-tcp]
Rosenberg, J., "TCP Candidates with Interactive Rosenberg, J., "TCP Candidates with Interactive
Connectivity Establishment (ICE", Connectivity Establishment (ICE)",
draft-ietf-mmusic-ice-tcp-03 (work in progress), draft-ietf-mmusic-ice-tcp-07 (work in progress),
March 2007. July 2008.
[I-D.ietf-behave-rfc3489bis] [I-D.ietf-behave-rfc3489bis]
Rosenberg, J., "Session Traversal Utilities for (NAT) Rosenberg, J., Mahy, R., Matthews, P., and D. Wing,
(STUN)", draft-ietf-behave-rfc3489bis-06 (work in "Session Traversal Utilities for (NAT) (STUN)",
progress), March 2007. draft-ietf-behave-rfc3489bis-18 (work in progress),
July 2008.
Authors' Addresses Authors' Addresses
Flemming Andreasen Flemming Andreasen
Cisco Systems, Inc. Cisco Systems, 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 44 skipping to change at line 779
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 9 change blocks. 
16 lines changed or deleted 13 lines changed or added

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