Network Service Header (NSH) Explicit Congestion Notification (ECN) Support
draft-eastlake-sfc-nsh-ecn-support-00

Document Type Active Internet-Draft (individual)
Last updated 2018-03-05
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
Expires: September 4, 2018                                 March 5, 2018

                      Network Service Header (NSH)
             Explicit Congestion Notification (ECN) Support
              <draft-eastlake-sfc-nsh-ecn-support-00.txt>

Abstract

   Explicit congestion notification (ECN) allows a forwarding element to
   notify downstream devices of the onset of congestion without having
   to drop packets. This can improve network efficiency through better
   congestion control without packet drops. This document specifies ECN
   support within Service Function Chaining (SFC) domains through use of
   the Network Service Header (NSH).

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

   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                                        [Page 1]
INTERNET-DRAFT                                           NSH ECN Support

Table of Contents

      1. Introduction............................................3
      1.1 Conventions used in this document......................4

      2. The NSH ECN Field.......................................5

      3. ECN Support.............................................7
      3.1 At Classifier..........................................7
      3.2 At SFFs and SFs........................................7
      3.3 At Exit................................................7

      4. IANA Considerations.....................................8
      5. Security Considerations.................................9

      6. Acknowledgements........................................9

      Normative References......................................10
      Informative References....................................10

      Authors' Addresses........................................11

D. Eastlake & B. Briscoe                                        [Page 2]
INTERNET-DRAFT                                           NSH ECN Support

1. Introduction

   The Network Service Header (NSH [RFC8300]) is used to control the
   propagation of packets through a Service Function Chaining (SFC
   [RFC7665]) domain as discussed below. The SFC architecture calls for
   the encapsulation of traffic inside a service function chaining
   domain with an NSH being added by the "Classifier" on entry to the
   domain and the NSH being removed on exit from the domain. Thus the
   NSH is a natural place to note congestion within the SFC domain,
   avoiding possible confusion due, for example, to changes in the outer
   transport header in different parts of the SFC domain.

                  |
                  v
             +----------+
          . .|Classifier|. . . . . . . . . . . . . .
          .  +----------+                          .
          .       |          +----+                .
          .       |        --+ SF |     Service    .
          .       |       /  +----+     Function   .
          .       v    ---              Chaining   .
          .    +-----+/       +----+    domain     .
          .    | SFF |--------+ SF |               .
          .    +-----+\       +----+               .
          .       |    ---                         .
          .       |       \  +----+                .
          .       |        --+ SF |                .
          .       v          +----+                .
          .    +-----+                 +----+      .
          .    | SFF |-----------------+ SF |      .
          .    +-----+                 +----+      .
          .       |          +----+                .
          .       |        --+ SF |                .
          .       |       /  +----+                .
          .       v    ---                         .
          .    +-----+/       +----+               .
          .    | SFF |--------+ SF |               .
Show full document text