BANdwidth Aggregation for interNet Access (BANANA) ECN Operations for Bonding Tunnels
draft-leymann-banana-ecn-00

Document Type Active Internet-Draft (individual)
Last updated 2017-09-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
BANANA                                                        N. Leymann
INTERNET-DRAFT                                              C. Heidemann
Intended Category: Standards Track                   Deutsche Telekom AG
                                                                 J. Shen
                                                  China Telecom Co., Ltd
                                                                 L. Geng
                                                            China Mobile
                                                                 L. Chen
                                                                M. Zhang
                                                                 X. Geng
                                                                  Huawei
Expires: March 16, 2018                               September 12, 2017

           BANdwidth Aggregation for interNet Access (BANANA)
                   ECN Operations for Bonding Tunnels
                      draft-leymann-banana-ecn-00

Abstract

   This document specifies a Bonding Tunnel ECN Mechanism that uses
   Explicit Congestion Notification (ECN) in bonding tunnels to notify
   congestion of a tunnel so that the load-balancing strategy of the
   tunnel ingress can be adjusted accordingly. Attributes for the
   control protocol of BANANA are defined to support this mechanism.

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.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

 

N. Leymann, et al        Expires March 16, 2018                 [Page 1]
INTERNET DRAFT     ECN Operations for Bonding Tunnels September 12, 2017

Copyright and License Notice

   Copyright (c) 2017 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. 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2. ECN Features of IP-in-IP Bonding Tunnels  . . . . . . . . . . .  3
     2.1. ECN Features  . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2. ECN Features of IP-in-IP Tunnels  . . . . . . . . . . . . .  4
     2.3. Bonding Tunnel ECN Mechanism  . . . . . . . . . . . . . . .  5
   3. ECN Capability in Bonding Tunnels . . . . . . . . . . . . . . .  6
   4. Congestion Notification in Bonding Tunnels  . . . . . . . . . .  6
   5. Security Considerations . . . . . . . . . . . . . . . . . . . .  7
   6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  7
   7. References  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     7.1. Normative References  . . . . . . . . . . . . . . . . . . .  7
     7.2. Informative References  . . . . . . . . . . . . . . . . . .  7
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  8

 

N. Leymann, et al        Expires March 16, 2018                 [Page 2]
INTERNET DRAFT     ECN Operations for Bonding Tunnels September 12, 2017

1. Introduction

   Conventionally, ECN allows end-to-end notification of network
   congestion without dropping packets [RFC3168], and the sender reduces
   its transmission rate when it receives the congestion indication. ECN
   may be used between two ECN-enabled endpoints when the underlying
   network infrastructure also supports it. [RFC6040] redefines how the
   ECN field of the IP header should be constructed on entry to and exit
   from any IP-in-IP tunnel.

   This document, however, focuses on load-balancing adjustment between
Show full document text