draft-ietf-mmusic-media-loopback-10.txt   draft-ietf-mmusic-media-loopback-11.txt 
Internet Draft K. Hedayat Internet Draft K. Hedayat
Expires: August 18, 2009 Brix Networks Expires: March 7, 2010 EXFO
N. Venna N. Venna
Brix Networks EXFO
P. Jones P. Jones
Cisco Systems, Inc. Cisco Systems, Inc.
A. Roychowdhury A. Roychowdhury
Hughes Systique Corp. Hughes Systique Corp.
C. SivaChelvan C. SivaChelvan
Cisco Systems, Inc. Cisco Systems, Inc.
N. Stratton N. Stratton
BlinkMind, Inc. BlinkMind, Inc.
February 18, 2009 October 7, 2009
An Extension to the Session Description Protocol (SDP) for Media An Extension to the Session Description Protocol (SDP) for Media
Loopback Loopback
draft-ietf-mmusic-media-loopback-10 draft-ietf-mmusic-media-loopback-11
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
skipping to change at page 2, line 15 skipping to change at page 2, line 15
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the BSD License.
Abstract Abstract
The wide deployment of Voice over IP (VoIP), Real-time Text and The wide deployment of Voice over IP (VoIP), Real-time Text and
Video over IP services has introduced new challenges in managing Video over IP services has introduced new challenges in managing
and maintaining voice/real-time Text/video quality, reliability, and maintaining voice/real-time Text/video quality, reliability,
and overall performance. In particular, media delivery is an area and overall performance. In particular, media delivery is an area
that needs attention. One method of meeting these challenges is that needs attention. One method of meeting these challenges is
monitoring the media delivery performance by looping media back to monitoring the media delivery performance by looping media back to
the transmitter. This is typically referred to as "active the transmitter. This is typically referred to as "active
skipping to change at page 2, line 49 skipping to change at page 3, line 5
Table of Contents Table of Contents
1. Introduction .................................................. 3 1. Introduction .................................................. 3
2. Terminology ................................................... 4 2. Terminology ................................................... 4
3. Offering Entity Behavior ...................................... 4 3. Offering Entity Behavior ...................................... 4
4. Answering Entity Behavior ..................................... 4 4. Answering Entity Behavior ..................................... 4
5. SDP Constructs Syntax ......................................... 5 5. SDP Constructs Syntax ......................................... 5
5.1 Loopback Type Attribute ................................... 5 5.1 Loopback Type Attribute ................................... 5
5.2 Loopback Mode Attribute ................................... 6 5.2 Loopback Mode Attribute ................................... 6
5.3 Generating the Offer for Loopback Session ................. 7 5.3 Generating the Offer for Loopback Session ................. 7
5.4 Generating the Answer for Loopback Session 5.4 Generating the Answer for Loopback Session ................ 8
5.5 Offerer Processing of the Answer ......................... 10 5.5 Offerer Processing of the Answer ......................... 10
5.6 Modifying the Session .................................... 10 5.6 Modifying the Session .................................... 10
6. RTP Requirements ............................................. 10 6. RTP Requirements ............................................. 10
7. Payload formats for Packet loopback .......................... 11 7. Payload formats for Packet loopback .......................... 11
7.1 Encapsulated Payload format .............................. 11 7.1 Encapsulated Payload format .............................. 11
7.2 Direct loopback RTP payload format ....................... 13 7.2 Direct loopback RTP payload format ....................... 13
8. RTCP Requirements ............................................ 15 8. RTCP Requirements ............................................ 15
9. Congestion Control ........................................... 15 9. Congestion Control ........................................... 15
10. Examples .................................................... 15 10. Examples .................................................... 15
10.1 Offer for specific media loopback type .................. 15 10.1 Offer for specific media loopback type .................. 15
skipping to change at page 3, line 31 skipping to change at page 3, line 34
13. IANA Considerations ......................................... 20 13. IANA Considerations ......................................... 20
13.1 SDP Attributes .......................................... 20 13.1 SDP Attributes .......................................... 20
13.2 MIME Types .............................................. 21 13.2 MIME Types .............................................. 21
14. Acknowledgements ............................................ 30 14. Acknowledgements ............................................ 30
15. Normative References ........................................ 30 15. Normative References ........................................ 30
1. Introduction 1. Introduction
The overall quality, reliability, and performance of VoIP, The overall quality, reliability, and performance of VoIP,
Real-time Text and Video over IP services rely on the performance Real-time Text and Video over IP services rely on the performance
and quality of the media path. In order to assure the quality of
the delivered media there is a need to monitor the performance of the delivered media there is a need to monitor the performance of
the media transport. One method of monitoring and managing the the media transport. One method of monitoring and managing the
overall quality of VoIP, Real-time Text and Video over IP Services overall quality of VoIP, Real-time Text and Video over IP Services
is through monitoring the quality of the media in an active is through monitoring the quality of the media in an active
session. This type of "active monitoring" of services is a method session. This type of "active monitoring" of services is a method
of pro-actively managing the performance and quality of VoIP based
services. services.
The goal of active monitoring is to measure the media quality of a The goal of active monitoring is to measure the media quality of a
VoIP, Real-time Text or Video over IP session. A way to achieve VoIP, Real-time Text or Video over IP session. A way to achieve
this goal is to request an endpoint to loop media back to the other this goal is to request an endpoint to loop media back to the other
endpoint and to provide media statistics (e.g., RTCP and RTCP XR endpoint and to provide media statistics (e.g., RTCP and RTCP XR
information). Another method involves deployment of special information). Another method involves deployment of special
endpoints that always loop incoming media back for sessions. endpoints that always loop incoming media back for sessions.
Although the latter method has been used and is functional, it does Although the latter method has been used and is functional, it does
not scale to support large networks and introduces new network not scale to support large networks and introduces new network
skipping to change at page 20, line 43 skipping to change at page 20, line 43
rtp-start-loopback MAY be implemented in complete implementations rtp-start-loopback MAY be implemented in complete implementations
of this draft. of this draft.
13. IANA Considerations 13. IANA Considerations
13.1 SDP Attributes 13.1 SDP Attributes
This document defines three new media-level SDP attributes. IANA This document defines three new media-level SDP attributes. IANA
has registered the following attributes: has registered the following attributes:
Contact name: Kaynam Hedayat <khedayat@brixnet.com>. Contact name: Kaynam Hedayat
<kaynam.hedayat@exfo.com>.
Attribute name: "loopback". Attribute name: "loopback".
Type of attribute: Media level.
Type of attribute: Media level.
Subject to charset: No. Subject to charset: No.
Purpose of attribute: The 'loopback' attribute is used to Purpose of attribute: The 'loopback' attribute is used to
indicate the type of media loopback. indicate the type of media loopback.
Allowed attribute values: The parameters to 'loopback' may be Allowed attribute values: The parameters to 'loopback' may be
one or more of "rtp-pkt-loopback," one or more of "rtp-pkt-loopback,"
"rtp-media-loopback," and "rtp-media-loopback," and
"rtp-start-loopback". See section 5 "rtp-start-loopback". See section 5
of this document for syntax. of this document for syntax.
Contact name: Kaynam Hedayat <khedayat@brixnet.com>. Contact name: Kaynam Hedayat
<kaynam.hedayat@exfo.com>.
Attribute name: "loopback-source". Attribute name: "loopback-source".
Type of attribute: Media level. Type of attribute: Media level.
Subject to charset: No. Subject to charset: No.
Purpose of attribute: The 'loopback-source' attribute Purpose of attribute: The 'loopback-source' attribute
specifies that the sender is the media specifies that the sender is the media
source and expects the receiver to act source and expects the receiver to act
as a loopback-mirror. as a loopback-mirror.
Allowed attribute values: The parameter to 'loopback-source' is Allowed attribute values: The parameter to 'loopback-source' is
a media format ("<fmt>") description a media format ("<fmt>") description
as defined in RFC 4566 Section 5.14. as defined in RFC 4566 Section 5.14.
Contact name: Kaynam Hedayat <khedayat@brixnet.com>. Contact name: Kaynam Hedayat
<kaynam.hedayat@exfo.com>.
Attribute name: "loopback-mirror". Attribute name: "loopback-mirror".
Type of attribute: Media level. Type of attribute: Media level.
Subject to charset: No. Subject to charset: No.
Purpose of attribute: The 'loopback-mirror' attribute Purpose of attribute: The 'loopback-mirror' attribute
specifies that the receiver will specifies that the receiver will
mirror (echo) all received media back mirror (echo) all received media back
to the sender of the RTP stream. to the sender of the RTP stream.
Allowed attribute values: The parameter to 'loopback-mirror' is Allowed attribute values: The parameter to 'loopback-mirror' is
a media format ("<fmt>") description a media format ("<fmt>") description
as defined in RFC 4566 Section 5.14. as defined in RFC 4566 Section 5.14.
skipping to change at page 22, line 31 skipping to change at page 22, line 34
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
skipping to change at page 23, line 38 skipping to change at page 23, line 43
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
skipping to change at page 24, line 43 skipping to change at page 24, line 46
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working Change controller: IETF Audio/Video Transport working
group delegated from the IESG. group delegated from the IESG.
13.2.4 application/encaprtp 13.2.4 application/encaprtp
To: ietf-types@iana.org To: ietf-types@iana.org
Subject: Registration of media type Subject: Registration of media type
skipping to change at page 25, line 49 skipping to change at page 26, line 4
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
Change controller: IETF Audio/Video Transport working Change controller: IETF Audio/Video Transport working
group delegated from the IESG. group delegated from the IESG.
skipping to change at page 26, line 49 skipping to change at page 27, line 4
Published specification: This MIME type is described fully Published specification: This MIME type is described fully
within this document. within this document.
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
skipping to change at page 28, line 4 skipping to change at page 28, line 8
Published specification: This MIME type is described fully Published specification: This MIME type is described fully
within this document. within this document.
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
skipping to change at page 29, line 15 skipping to change at page 29, line 17
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
skipping to change at page 30, line 20 skipping to change at page 30, line 23
Applications which use this media type: Applications wishing Applications which use this media type: Applications wishing
to monitor and ensure the quality of transport to the to monitor and ensure the quality of transport to the
edge of a given VoIP, Real-Time Text or Video Over IP edge of a given VoIP, Real-Time Text or Video Over IP
Service. Service.
Additional information: none Additional information: none
Person & email address to contact for further information: Person & email address to contact for further information:
Kaynam Hedayat Kaynam Hedayat
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: This media type depends on RTP Restrictions on usage: This media type depends on RTP
framing, and hence is only defined for transfer via framing, and hence is only defined for transfer via
RTP. Transfer within other framing protocols is not RTP. Transfer within other framing protocols is not
defined at this time. defined at this time.
Author: Author:
Kaynam Hedayat. Kaynam Hedayat.
skipping to change at page 31, line 41 skipping to change at page 31, line 44
[RFC4566] Handley, M., Jacobson, V., Perkins, C., "SDP: Session [RFC4566] Handley, M., Jacobson, V., Perkins, C., "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
Authors' Addresses Authors' Addresses
Kaynam Hedayat Kaynam Hedayat
Brix Networks EXFO
285 Mill Road 285 Mill Road
Chelmsford, MA 01824 Chelmsford, MA 01824
US US
Phone: +1 978 367 5611 Phone: +1 978 367 5611
EMail: khedayat@brixnet.com EMail: kaynam.hedayat@exfo.com
URI: http://www.brixnet.com/ URI: http://www.exfo.com/
Nagarjuna Venna Nagarjuna Venna
Brix Networks EXFO
285 Mill Road 285 Mill Road
Chelmsford, MA 01824 Chelmsford, MA 01824
US US
Phone: +1 978 367 5703 Phone: +1 978 367 5703
EMail: nvenna@brixnet.com EMail: nagarjuna.venna@exfo.com
URI: http://www.brixnet.com/ URI: http://www.exfo.com/
Paul E. Jones Paul E. Jones
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Rd. 7025 Kit Creek Rd.
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
US US
Phone: +1 919 392 6948 Phone: +1 919 392 6948
EMail: paulej@packetizer.com EMail: paulej@packetizer.com
URI: http://www.cisco.com/ URI: http://www.cisco.com/
 End of changes. 31 change blocks. 
29 lines changed or deleted 36 lines changed or added

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