NSH Context Header Allocation for Broadband
draft-ietf-sfc-nsh-broadband-allocation-01

Document Type Active Internet-Draft (sfc WG)
Last updated 2018-06-19
Replaces draft-napper-sfc-nsh-broadband-allocation
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Service Function Chaining                                      J. Napper
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                                S. Kumar
Expires: December 21, 2018                        Individual Contributor
                                                                P. Muley
                                                           W. Hendericks
                                                                   Nokia
                                                            M. Boucadair
                                                                  Orange
                                                           June 19, 2018

              NSH Context Header Allocation for Broadband
               draft-ietf-sfc-nsh-broadband-allocation-01

Abstract

   This document provides a recommended allocation of Network Service
   Header (NSH) context headers within the broadband service provider
   network context.  Both fixed and mobile deployments are considered.

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 https://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 December 21, 2018.

Napper, et al.          Expires December 21, 2018               [Page 1]
Internet-Draft      NSH Broadband Context Allocation           June 2018

Copyright Notice

   Copyright (c) 2018 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
   (https://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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Network Service Header (NSH) Context Headers: A Reminder  . .   3
   4.  Recommended Context Allocation For Broadband  . . . . . . . .   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  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Service Function Chaining (SFC) [RFC7665] provides a mechanism for
   network traffic to be steered through an ordered list of Service
   Functions (SFs).  Furthermore, SFC allows to share metadata among
   involved SFC data functional elements (classifiers and SFs).
   Particularly, the Network Service Header (NSH, [RFC8300]) provides
   support for carrying shared metadata either using a fixed context
   header or as optional TLVs.

   This document describes a recommended default allocation scheme for
   the fixed-length context header used for SFC within fixed and mobile
   broadband service provider networks.  Also, the document defines
   companion TLV types when MD Type 0x02 is used.  The use cases
   describing the need for metadata in these deployment contexts are
   described in [I-D.ietf-sfc-use-case-mobility].

Napper, et al.          Expires December 21, 2018               [Page 2]
Internet-Draft      NSH Broadband Context Allocation           June 2018

   This document does not address control plane considerations.  The
   reader may refer to [I-D.ietf-sfc-control-plane].
Show full document text