--- 1/draft-ietf-mmusic-media-loopback-10.txt 2009-10-09 00:12:41.000000000 +0200 +++ 2/draft-ietf-mmusic-media-loopback-11.txt 2009-10-09 00:12:41.000000000 +0200 @@ -1,28 +1,28 @@ Internet Draft K. Hedayat - Expires: August 18, 2009 Brix Networks + Expires: March 7, 2010 EXFO N. Venna - Brix Networks + EXFO P. Jones Cisco Systems, Inc. A. Roychowdhury Hughes Systique Corp. C. SivaChelvan Cisco Systems, Inc. N. Stratton BlinkMind, Inc. - February 18, 2009 + October 7, 2009 An Extension to the Session Description Protocol (SDP) for Media Loopback - draft-ietf-mmusic-media-loopback-10 + draft-ietf-mmusic-media-loopback-11 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -44,21 +44,24 @@ Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents 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 The wide deployment of Voice over IP (VoIP), Real-time Text and Video over IP services has introduced new challenges in managing and maintaining voice/real-time Text/video quality, reliability, and overall performance. In particular, media delivery is an area that needs attention. One method of meeting these challenges is monitoring the media delivery performance by looping media back to the transmitter. This is typically referred to as "active @@ -78,21 +81,21 @@ Table of Contents 1. Introduction .................................................. 3 2. Terminology ................................................... 4 3. Offering Entity Behavior ...................................... 4 4. Answering Entity Behavior ..................................... 4 5. SDP Constructs Syntax ......................................... 5 5.1 Loopback Type Attribute ................................... 5 5.2 Loopback Mode Attribute ................................... 6 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.6 Modifying the Session .................................... 10 6. RTP Requirements ............................................. 10 7. Payload formats for Packet loopback .......................... 11 7.1 Encapsulated Payload format .............................. 11 7.2 Direct loopback RTP payload format ....................... 13 8. RTCP Requirements ............................................ 15 9. Congestion Control ........................................... 15 10. Examples .................................................... 15 10.1 Offer for specific media loopback type .................. 15 @@ -107,27 +110,27 @@ 13. IANA Considerations ......................................... 20 13.1 SDP Attributes .......................................... 20 13.2 MIME Types .............................................. 21 14. Acknowledgements ............................................ 30 15. Normative References ........................................ 30 1. Introduction The overall quality, reliability, and performance of VoIP, 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 media transport. One method of monitoring and managing the overall quality of VoIP, Real-time Text and Video over IP Services is through monitoring the quality of the media in an active session. This type of "active monitoring" of services is a method - + of pro-actively managing the performance and quality of VoIP based services. 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 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 information). Another method involves deployment of special endpoints that always loop incoming media back for sessions. Although the latter method has been used and is functional, it does not scale to support large networks and introduces new network @@ -880,46 +883,49 @@ rtp-start-loopback MAY be implemented in complete implementations of this draft. 13. IANA Considerations 13.1 SDP Attributes This document defines three new media-level SDP attributes. IANA has registered the following attributes: - Contact name: Kaynam Hedayat . + Contact name: Kaynam Hedayat + . Attribute name: "loopback". - Type of attribute: Media level. + Type of attribute: Media level. Subject to charset: No. Purpose of attribute: The 'loopback' attribute is used to indicate the type of media loopback. Allowed attribute values: The parameters to 'loopback' may be one or more of "rtp-pkt-loopback," "rtp-media-loopback," and "rtp-start-loopback". See section 5 of this document for syntax. - Contact name: Kaynam Hedayat . + Contact name: Kaynam Hedayat + . Attribute name: "loopback-source". Type of attribute: Media level. Subject to charset: No. Purpose of attribute: The 'loopback-source' attribute specifies that the sender is the media source and expects the receiver to act as a loopback-mirror. Allowed attribute values: The parameter to 'loopback-source' is a media format ("") description as defined in RFC 4566 Section 5.14. - Contact name: Kaynam Hedayat . + Contact name: Kaynam Hedayat + . Attribute name: "loopback-mirror". Type of attribute: Media level. Subject to charset: No. Purpose of attribute: The 'loopback-mirror' attribute specifies that the receiver will mirror (echo) all received media back to the sender of the RTP stream. Allowed attribute values: The parameter to 'loopback-mirror' is a media format ("") description as defined in RFC 4566 Section 5.14. @@ -959,21 +964,21 @@ Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. @@ -1011,21 +1017,21 @@ Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. @@ -1064,31 +1070,30 @@ Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: - Kaynam Hedayat. Change controller: IETF Audio/Video Transport working group delegated from the IESG. 13.2.4 application/encaprtp To: ietf-types@iana.org Subject: Registration of media type @@ -1119,23 +1124,24 @@ Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON + Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. Change controller: IETF Audio/Video Transport working group delegated from the IESG. @@ -1167,25 +1173,24 @@ Published specification: This MIME type is described fully within this document. Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none - Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. @@ -1220,24 +1225,25 @@ Published specification: This MIME type is described fully within this document. Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none + Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. @@ -1276,21 +1281,21 @@ Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. @@ -1330,21 +1335,21 @@ Applications which use this media type: Applications wishing to monitor and ensure the quality of transport to the edge of a given VoIP, Real-Time Text or Video Over IP Service. Additional information: none Person & email address to contact for further information: Kaynam Hedayat - EMail: khedayat@brixnet.com + EMail: kaynam.hedayat@exfo.com Intended usage: COMMON Restrictions on usage: This media type depends on RTP framing, and hence is only defined for transfer via RTP. Transfer within other framing protocols is not defined at this time. Author: Kaynam Hedayat. @@ -1394,37 +1400,38 @@ [RFC4566] Handley, M., Jacobson, V., Perkins, C., "SDP: Session Description Protocol", RFC 4566, July 2006. [RFC4855] Casner, S., "Media Type Registration of RTP Payload Formats", RFC 4855, February 2007. Authors' Addresses Kaynam Hedayat - Brix Networks + EXFO 285 Mill Road Chelmsford, MA 01824 US + Phone: +1 978 367 5611 - EMail: khedayat@brixnet.com - URI: http://www.brixnet.com/ + EMail: kaynam.hedayat@exfo.com + URI: http://www.exfo.com/ Nagarjuna Venna - Brix Networks + EXFO 285 Mill Road Chelmsford, MA 01824 US Phone: +1 978 367 5703 - EMail: nvenna@brixnet.com - URI: http://www.brixnet.com/ + EMail: nagarjuna.venna@exfo.com + URI: http://www.exfo.com/ Paul E. Jones Cisco Systems, Inc. 7025 Kit Creek Rd. Research Triangle Park, NC 27709 US Phone: +1 919 392 6948 EMail: paulej@packetizer.com URI: http://www.cisco.com/