Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP
draft-ietf-tsvwg-ecn-encap-guidelines-09

Document Type Active Internet-Draft (tsvwg WG)
Last updated 2017-07-20
Replaces draft-briscoe-tsvwg-ecn-encap-guidelines
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Jan 2018 - Submit 'Guidelines f... )
Document shepherd David Black
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "David Black" <david.black@dell.com>
Transport Area Working Group                                  B. Briscoe
Internet-Draft                                Simula Research Laboratory
Updates: 3819 (if approved)                            J. Kaippallimalil
Intended status: Best Current Practice                            Huawei
Expires: January 21, 2018                                      P. Thaler
                                                    Broadcom Corporation
                                                           July 20, 2017

    Guidelines for Adding Congestion Notification to Protocols that
                             Encapsulate IP
                draft-ietf-tsvwg-ecn-encap-guidelines-09

Abstract

   The purpose of this document is to guide the design of congestion
   notification in any lower layer or tunnelling protocol that
   encapsulates IP.  The aim is for explicit congestion signals to
   propagate consistently from lower layer protocols into IP.  Then the
   IP internetwork layer can act as a portability layer to carry
   congestion notification from non-IP-aware congested nodes up to the
   transport layer (L4).  Following these guidelines should assure
   interworking between new lower layer congestion notification
   mechanisms, whether specified by the IETF or other standards bodies.

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 January 21, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Briscoe, et al.         Expires January 21, 2018                [Page 1]
Internet-Draft        ECN Encapsulation Guidelines             July 2017

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Guidelines in All Cases . . . . . . . . . . . . . . . . . . .   7
   4.  Modes of Operation  . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Feed-Forward-and-Up Mode  . . . . . . . . . . . . . . . .   8
     4.2.  Feed-Up-and-Forward Mode  . . . . . . . . . . . . . . . .  10
     4.3.  Feed-Backward Mode  . . . . . . . . . . . . . . . . . . .  11
     4.4.  Null Mode . . . . . . . . . . . . . . . . . . . . . . . .  13
   5.  Feed-Forward-and-Up Mode: Guidelines for Adding Congestion
       Notification  . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  IP-in-IP Tunnels with Shim Headers  . . . . . . . . . . .  14
     5.2.  Wire Protocol Design: Indication of ECN Support . . . . .  15
     5.3.  Encapsulation Guidelines  . . . . . . . . . . . . . . . .  17
     5.4.  Decapsulation Guidelines  . . . . . . . . . . . . . . . .  19
     5.5.  Sequences of Similar Tunnels or Subnets . . . . . . . . .  20
     5.6.  Reframing and Congestion Markings . . . . . . . . . . . .  21
   6.  Feed-Up-and-Forward Mode: Guidelines for Adding Congestion
       Notification  . . . . . . . . . . . . . . . . . . . . . . . .  21
   7.  Feed-Backward Mode: Guidelines for Adding Congestion
       Notification  . . . . . . . . . . . . . . . . . . . . . . . .  23
   8.  IANA Considerations (to be removed by RFC Editor) . . . . . .  24
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  24
   10. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . .  24
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  25
   12. Comments Solicited  . . . . . . . . . . . . . . . . . . . . .  25
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  25
     13.2.  Informative References . . . . . . . . . . . . . . . . .  26
   Appendix A.  Outstanding Document Issues  . . . . . . . . . . . .  31
Show full document text