Service Function Chaining Metadata Type 1 and Type 2
draft-sarikaya-sfc-metadatat1t2-02

Document Type Active Internet-Draft (individual)
Last updated 2017-01-12
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)
Network Working Group                                        B. Sarikaya
Internet-Draft                                                    Huawei
Intended status: Informational                              M. Boucadair
Expires: July 16, 2017                                            Orange
                                                             D. von Hugo
                                         Telekom Innovation Laboratories
                                                        January 12, 2017

          Service Function Chaining Metadata Type 1 and Type 2
                 draft-sarikaya-sfc-metadatat1t2-02.txt

Abstract

   With the definition of service function chain data plane protocol
   there comes the need to define the context data needed in the service
   function chain use cases.  This document gives an account of all
   context data defined so far as Network Service Header metadata Type 1
   and Type 2 context headers.  Next, the document discusses the various
   options that can be taken in standardizing service function chain
   metadata.

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 16, 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

Sarikaya, et al.          Expires July 16, 2017                 [Page 1]
Internet-Draft              Metadata  in SFC                January 2017

   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.  Context Metadata Definitions  . . . . . . . . . . . . . . . .   3
   3.  Processing Metadata Type 1 and Type 2 . . . . . . . . . . . .   6
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Network Service Header (NSH) [I-D.ietf-sfc-nsh] is the Service
   Function Chaining (SFC) data plane protocol.  The SFC architecture is
   defined in [RFC7665].

   NSH has the function of carrying context data in the form of context
   header.  NSH metadata Type 1 is composed of a 4-byte base header,
   4-byte service path header.  It contains four mandatory Context
   Headers, 4-byte each which can be combined into one context header of
   16 octets in the latest version.  For additional metadata that needs
   to be carried, NSH metadata type 2 is defined.  Type 2 metadata is
   composed of a 4-byte base header carrying Type value of 0x02, 4-byte
   service path header followed by variable length context headers in
   the form of metadata class type-length-value or TLV.

   Optional variable length metadata definition includes 16-bit metadata
   class and 7-bit type fields.  It is an issue if such a long metadata
   class field is needed and whether the type field length should be
   increased.

   Many context headers were proposed by many documents.  In this
   document we survey existing drafts that propose new context metadata
   and then discuss different options that can be taken to standardize
   this work.

   The reader should be familiar with the terms defined in [RFC7665] and
   [I-D.ietf-sfc-nsh].

Sarikaya, et al.          Expires July 16, 2017                 [Page 2]
Show full document text