Network Service Header (NSH) Context Header Allocation (Network Security)
draft-wang-sfc-nsh-ns-allocation-03

Document Type Active Internet-Draft (individual)
Last updated 2017-06-28
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                                        E. Wang
Internet-Draft                                                  K. Leung
Intended status: Informational                                A. Ossipov
Expires: December 30, 2017                            Cisco Systems Inc.
                                                           June 28, 2017

    Network Service Header (NSH) Context Header Allocation (Network
                               Security)
                  draft-wang-sfc-nsh-ns-allocation-03

Abstract

   This document provides a recommended default allocation of the
   mandatory fixed context headers for a Network Service Header (NSH)
   relevant to Service Function Chaining (SFC) for network security
   Service Functions.  NSH is defined in [I-D.ietf-sfc-nsh].  This
   allocation is intended to support the use cased described in
   [I-D.wang-sfc-ns-use-cases].

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 December 30, 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

Wang, et al.            Expires December 30, 2017               [Page 1]
Internet-Draft  NSH Context Header Allocation (Security)       June 2017

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

1.  Introduction

   Service Function Chaining (SFC) provides a mechanism for network
   traffic to go through a set of Service Functions in sequence.
   Network Service Header (NSH) allows metadata to be shared between
   Service Functions along with the packets.  Such metadata is carried
   by either a fixed number of 32-bit context headers (MD-Type 1) or a
   variable number of TLVs (MD-Type 2), as defined in NSH
   [I-D.ietf-sfc-nsh].  This document provides a recommended default
   allocation of the fixed size context headers for network security
   Service Functions forming a Service Function Chain.  The allocation
   may also form a MD-Type 2 metadata TLV.  Supporting use cases for a
   metadata definition in this context are described in SFC-NS-Use-Cases
   [I-D.wang-sfc-ns-use-cases] . This document does not define any other
   variable TLVs.  It does not address the control plane mechanisms.

1.1.  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 RFC 2119 [RFC2119].

2.  Definition Of Terms
Show full document text