Explicit Congestion Notification (ECN) for RTP over UDP
draft-ietf-avtcore-ecn-for-rtp-07

The information below is for an old version of the document
Document Type Active Internet-Draft (avtcore WG)
Last updated 2012-04-12 (latest revision 2012-03-30)
Replaces draft-ietf-avt-ecn-for-rtp
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Other - see Comment Log
Consensus Unknown
Document shepherd Roni Even
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs a YES. Needs 7 more YES or NO OBJECTION positions to pass.
Responsible AD Robert Sparks
IESG note Roni Even (even.roni@huawei.com) is the document shepherd.
Send notices to avtcore-chairs@tools.ietf.org, draft-ietf-avtcore-ecn-for-rtp@tools.ietf.org
Network Working Group                                      M. Westerlund
Internet-Draft                                              I. Johansson
Intended status: Standards Track                                Ericsson
Expires: October 1, 2012                                      C. Perkins
                                                   University of Glasgow
                                                             P. O'Hanlon
                                                    University of Oxford
                                                             K. Carlberg
                                                                     G11
                                                          March 30, 2012

        Explicit Congestion Notification (ECN) for RTP over UDP
                   draft-ietf-avtcore-ecn-for-rtp-07

Abstract

   This memo specifies how Explicit Congestion Notification (ECN) can be
   used with the Real-time Transport Protocol (RTP) running over UDP,
   using RTP Control Protocol (RTCP) as a feedback mechanism.  It
   defines a new RTCP Extended Report (XR) block for periodic ECN
   feedback, a new RTCP transport feedback message for timely reporting
   of congestion events, and a Session Traversal Utilities for NAT
   (STUN) extension used in the optional initialization method using
   Interactive Connectivity Establishment (ICE).  Signalling and
   procedures for negotiation of capabilities and initialization methods
   are also defined.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 1, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Westerlund, et al.       Expires October 1, 2012                [Page 1]
Internet-Draft           ECN for RTP over UDP/IP              March 2012

   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.  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 Simplified BSD License.

Westerlund, et al.       Expires October 1, 2012                [Page 2]
Internet-Draft           ECN for RTP over UDP/IP              March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Conventions, Definitions and Acronyms  . . . . . . . . . . . .  5
   3.  Discussion, Requirements, and Design Rationale . . . . . . . .  6
     3.1.  Requirements . . . . . . . . . . . . . . . . . . . . . . .  7
     3.2.  Applicability  . . . . . . . . . . . . . . . . . . . . . .  8
     3.3.  Interoperability . . . . . . . . . . . . . . . . . . . . . 12
   4.  Overview of Use of ECN with RTP/UDP/IP . . . . . . . . . . . . 13
   5.  RTCP Extensions for ECN feedback . . . . . . . . . . . . . . . 16
     5.1.  RTP/AVPF Transport Layer ECN Feedback packet . . . . . . . 16
     5.2.  RTCP XR Report block for ECN summary information . . . . . 19
   6.  SDP Signalling Extensions for ECN  . . . . . . . . . . . . . . 21
     6.1.  Signalling ECN Capability using SDP  . . . . . . . . . . . 21
     6.2.  RTCP ECN Feedback SDP Parameter  . . . . . . . . . . . . . 25
     6.3.  XR Block ECN SDP Parameter . . . . . . . . . . . . . . . . 25
     6.4.  ICE Parameter to Signal ECN Capability . . . . . . . . . . 26
   7.  Use of ECN with RTP/UDP/IP . . . . . . . . . . . . . . . . . . 26
     7.1.  Negotiation of ECN Capability  . . . . . . . . . . . . . . 26
     7.2.  Initiation of ECN Use in an RTP Session  . . . . . . . . . 27
     7.3.  Ongoing Use of ECN Within an RTP Session . . . . . . . . . 34
     7.4.  Detecting Failures . . . . . . . . . . . . . . . . . . . . 37
   8.  Processing ECN in RTP Translators and Mixers . . . . . . . . . 41
     8.1.  Transport Translators  . . . . . . . . . . . . . . . . . . 41
Show full document text