Explicit Congestion Notification (ECN) and Congestion Feedback Using the Network Service Header (NSH)
draft-eastlake-sfc-nsh-ecn-support-02

Document Type Active Internet-Draft (individual)
Last updated 2018-10-21
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)
INTERNET-DRAFT                                           Donald Eastlake
Intended status: Proposed Standard                                Huawei
                                                             Bob Briscoe
                                                             Independent
                                                            Andrew Malis
                                                                  Huawei
Expires: April 20, 2019                                 October 21, 2018

     Explicit Congestion Notification (ECN) and Congestion Feedback
                 Using the Network Service Header (NSH)
              <draft-eastlake-sfc-nsh-ecn-support-02.txt>

Abstract

   Explicit congestion notification (ECN) allows a forwarding element to
   notify downstream devices of the onset of congestion without having
   to drop packets. Coupled with a means to feed back information about
   congestion to upstream nodes, this can improve network efficiency
   through better congestion control, frequently without packet drops.
   This document specifies ECN and congestion feedback support through
   use of the Network Service Header (NSH, RFC 8300) and IP Flow
   Information Export (IPFIX, draft-ietf-tsvwg-tunnel-congestion-
   feedback).

Status of This Memo

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

   Distribution of this document is unlimited. Comments should be sent
   to the SFC Working Group mailing list <sfc@ietf.org> or to the
   authors.

   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.

D. Eastlake, B. Briscoe, & A. Malis                             [Page 1]
INTERNET-DRAFT                             NSH ECN & Congestion Feedback

Table of Contents

      1. Introduction............................................3
      1.1 NSH Background.........................................3
      1.2 ECN Background.........................................5
      1.3 Tunnel Congestion Feedback Background..................5
      1.4 Conventions Used in This Document......................6

      2. The NSH ECN Field.......................................8

      3. ECN Support in the NSH.................................10
      3.1 At The Ingress........................................11
      3.2 At Transit Nodes......................................11
      3.2.1 At NSH Transit Nodes................................12
      3.2.2 At an SF/Proxy......................................12
      3.2.3 At Other Forwarding Nodes...........................13
      3.3 At Exit/Egress........................................13
      3.4 Conservation of Packets...............................14

      4. Tunnel Congestion Feedback Support.....................15

      5. IANA Considerations....................................16
      6. Security Considerations................................17

      7. Acknowledgements.......................................17

      Normative References......................................18
      Informative References....................................19

      Authors' Addresses........................................20

D. Eastlake, B. Briscoe, & A. Malis                             [Page 2]
INTERNET-DRAFT                             NSH ECN & Congestion Feedback

1. Introduction

   Explicit congestion notification (ECN [RFC3168]) allows a forwarding
   element to notify downstream devices of the onset of congestion
   without having to drop packets. Coupled with a means to feed back
   information about congestion to upstream nodes, this can improve
   network efficiency through better congestion control, frequently
   without packet drops. This document specifies ECN and congestion
   feedback support through use of the Network Service Header (NSH
   [RFC8300]) and IP Flow Information Export (IPFIX
   [TunnelCongFeedback]).

   This section provides background information on NSH, ECN, congestion
   feedback, and terminology used in this document.

1.1 NSH Background

   The Service Function Chaining (SFC [RFC7665]) architecture calls for
   the encapsulation of traffic within a service function chaining
   domain with a Network Service Header (NSH [RFC8300]) added by the
   "Classifier" (ingress node) on entry to the domain and the NSH being
Show full document text