NSH Context Header Allocation -- Broadband
draft-napper-sfc-nsh-broadband-allocation-02

Document Type Active Internet-Draft (individual)
Last updated 2017-01-17
Replaces draft-napper-sfc-nsh-mobility-allocation
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Service Function Chaining                                      J. Napper
Internet-Draft                                                  S. Kumar
Intended status: Standards Track                     Cisco Systems, Inc.
Expires: July 20, 2017                                          P. Muley
                                                           W. Hendericks
                                                                   Nokia
                                                            M. Boucadair
                                                                  Orange
                                                        January 16, 2017

               NSH Context Header Allocation -- Broadband
              draft-napper-sfc-nsh-broadband-allocation-02

Abstract

   This document provides a recommended allocation of context headers
   for a Network Service Header (NSH) within the broadband service
   provider network context.  NSH is described in detail in
   [ietf-sfc-nsh].  This allocation is intended to support uses cases as
   defined in [ietf-sfc-use-case-mobility].

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

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 July 20, 2017.

Napper, et al.            Expires July 20, 2017                 [Page 1]
Internet-Draft      NSH Broadband Context Allocation        January 2017

Copyright 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definition Of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Network Service Header (NSH) Context Headers  . . . . . . . .   3
   4.  Recommended Context Allocation  . . . . . . . . . . . . . . .   4
     4.1.  MD Type 0x01 Allocation Specifics . . . . . . . . . . . .   4
     4.2.  MD Type 0x02 Allocation Specifics . . . . . . . . . . . .   6
   5.  Context Allocation and Control Plane Considerations . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Service function chaining provides a mechanism for network traffic to
   be steered through multiple service functions in a sequence.
   Metadata can be useful to service functions.  The Network Service
   Header (NSH) provides support for carrying shared metadata between
   service functions (and devices) either using 4 fixed-length 32-bit
   context headers or as optional TLVs as defined in [ietf-sfc-nsh].
   NSH is then encapsulated within an outer header for transport.

   This document provides a recommended default allocation scheme for
   the fixed-length context headers and for TLV types in the context of
   service chaining within fixed and mobile broadband service provider
   networks.  Supporting use cases describing the need for a metadata
Show full document text