Network Service Header (NSH) MD Type 1: Context Header Allocation (Data Center)
draft-ietf-sfc-nsh-dc-allocation-00

Document Type Active Internet-Draft (sfc WG)
Last updated 2018-02-12
Replaces draft-guichard-sfc-nsh-dc-allocation
Stream IETF
Intended RFC status (None)
Formats plain text 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. Guichard
Internet-Draft                                                    Huawei
Intended status: Informational                                  M. Smith
Expires: August 16, 2018                                        S. Kumar
                                                     Cisco Systems, Inc.
                                                                S. Majee
                                                             F5 Networks
                                                              P. Agarwal
                                                                Broadcom
                                                               K. Glavin
                                                                Riverbed
                                                               Y. Laribi
                                                                  Citrix
                                                              T. Mizrahi
                                                                 Marvell
                                                       February 12, 2018

Network Service Header (NSH) MD Type 1: Context Header Allocation (Data
                                Center)
                  draft-ietf-sfc-nsh-dc-allocation-00

Abstract

   This document provides a recommended default allocation for the
   Network Service Header (NSH) MD Type 1 fixed length context header
   when NSH is used for Service Function Chaining within a data center.

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 August 16, 2018.

Guichard, et al.         Expires August 16, 2018                [Page 1]
Internet-Draft    NSH Context Allocation (Data Center)     February 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.  Definition Of Terms . . . . . . . . . . . . . . . . . . . . .   3
   3.  Recommended Data Center MD Type 1 Fixed Length Context
       Allocation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Data Center Allocation Specifics  . . . . . . . . . . . .   3
   4.  Context Allocation and Control Plane Considerations . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Network Service Header (NSH) [RFC8300] provides a mechanism to carry
   shared metadata between network devices and service functions, and
   between service functions.  When MD Type 1 is used, such metadata is
   carried within a fixed length (16-bytes) context header.

   This document provides a recommended default allocation of the MD
   Type 1 context header for Service Function Chaining [RFC7665] within
   a data center.  The context header may be used to support use cases
   such as those described in [I-D.ietf-sfc-dc-use-cases].

   The goal of this document is to provide a reference allocation that
   may be used with or without a control plane.  It also serves as a
   guide to implementers and network operators.

Guichard, et al.         Expires August 16, 2018                [Page 2]
Internet-Draft    NSH Context Allocation (Data Center)     February 2018

2.  Definition Of Terms
Show full document text