Network Service Header Metadata Type 2 Variable-Length Context Headers
draft-ietf-sfc-nsh-tlv-03

Document Type Active Internet-Draft (sfc WG)
Last updated 2020-05-20
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized 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)
SFC                                                          Y. Wei, Ed.
Internet-Draft                                           ZTE Corporation
Intended status: Standards Track                                U. Elzur
Expires: November 21, 2020                                         Intel
                                                                S. Majee
                                                       Caber systems inc
                                                            May 20, 2020

 Network Service Header Metadata Type 2 Variable-Length Context Headers
                       draft-ietf-sfc-nsh-tlv-03

Abstract

   This draft describes Network Service Header (NSH) Metadata (MD) Type
   2 variable-length context headers 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 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 November 21, 2020.

Copyright Notice

   Copyright (c) 2020 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

Wei, et al.             Expires November 21, 2020               [Page 1]
Internet-Draft           NSH MD2 Context Headers                May 2020

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   3.  NSH MD Type 2 format  . . . . . . . . . . . . . . . . . . . .   3
   4.  NSH MD Type 2 Context Headers . . . . . . . . . . . . . . . .   4
     4.1.  Forwarding Context  . . . . . . . . . . . . . . . . . . .   4
     4.2.  Tenant Identifier . . . . . . . . . . . . . . . . . . . .   5
     4.3.  Content Type  . . . . . . . . . . . . . . . . . . . . . .   5
     4.4.  Ingress Network Node Information  . . . . . . . . . . . .   6
     4.5.  Ingress Network Source Interface  . . . . . . . . . . . .   6
     4.6.  Flow ID . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.7.  Source and/or Destination Groups  . . . . . . . . . . . .   7
     4.8.  Universal Resource Identifier . . . . . . . . . . . . . .   7
     4.9.  Policy Identifier (POLICY_ID) . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Forwarding Context Types  . . . . . . . . . . . . . . . .   9
     7.2.  Tenant Identifier Types . . . . . . . . . . . . . . . . .   9
     7.3.  Group Types . . . . . . . . . . . . . . . . . . . . . . .  10
     7.4.  URI Types . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   Network Service Header (NSH) [RFC8300] is the Service Function
   Chaining (SFC) encapsulation required to support the SFC
   architecture.  As such, NSH provides following key elements:

   1.  Service Function Path identification.

   2.  Indication of location within a Service Function Path.

   3.  Optional, per-packet metadata (fixed-length or variable).

   [RFC8300] further defines two metadata formats (MD Types): 1 and 2.
   MD Type 1 defines fixed length, 16 bytes-long metadata, whereas MD
   Type 2 defines a variable-length context format for metadata.  This

Wei, et al.             Expires November 21, 2020               [Page 2]
Internet-Draft           NSH MD2 Context Headers                May 2020
Show full document text