Network Service Header TLVs
draft-quinn-sfc-nsh-tlv-04

Document Type Active Internet-Draft (individual)
Last updated 2017-10-18
Replaces draft-quinn-nsh-tlv
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                                           P. Quinn
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                                U. Elzur
Expires: April 21, 2018                                            Intel
                                                                S. Majee
                                                                      F5
                                                        October 18, 2017

                      Network Service Header TLVs
                     draft-quinn-sfc-nsh-tlv-04.txt

Abstract

   This draft describes Network Service Header (NSH) MD-Type 2 metadata
   TLVs that can be used within a service function path.

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 April 21, 2018.

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.

Quinn, et al.            Expires April 21, 2018                 [Page 1]
Internet-Draft         Network Service Header TLVs          October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  NSH Type 2 Format . . . . . . . . . . . . . . . . . . . . . .   2
   3.  NSH Type 2 TLVs . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Network Service Header [NSH] is the SFC encapsulation protocol used
   to create Service Function Chains.  As such, NSH provides two key
   elements:

   1.  Service Function Path identification

   2.  Metadata

   NSH further defines two metadata formats (MD Types): 1 and 2.  MD
   Type 1 defines fixed length, 16 byte metadata, whereas MD Type 2
   defines a variable-length TLV format for metadata.  This draft
   defines some common TLVs for use with NSH MD Type 2.

   This draft does not address metadata usage, updating/chaining of
   metadata or other SFP functions.  Those topics are described in NSH.

2.  NSH Type 2 Format

   A NSH is composed of a 4-byte Base Header, a 4-byte Service Path
   Header and Context Headers.  The Base Header identifies the MD-Type
   in use:

       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Ver|O|C|R|R|R|R|R|R|   Length  |    MD Type    | Next Protocol |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                         Figure 1: NSH Base Header

   Please refer to NSH [NSH] for a detailed header description.

Quinn, et al.            Expires April 21, 2018                 [Page 2]
Internet-Draft         Network Service Header TLVs          October 2017

   When the base header specifies MD Type= 0x2, zero or more Variable
   Length Context Headers MAY be added, immediately following the
   Service Path Header.  Therefore, Length = 0x2, indicates that only
   the Base Header followed by the Service Path Header are present.  The
   number, indicated in the length field, of optional Variable Length
Show full document text