Network Service Header TLVs
draft-ietf-sfc-nsh-tlv-01
|
| Document |
Type |
|
Active Internet-Draft (sfc WG)
|
|
Last updated |
|
2019-12-16
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
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 P. Quinn
Expires: June 15, 2020 Cisco Systems, Inc.
U. Elzur
Intel
S. Majee
F5
December 13, 2019
Network Service Header TLVs
draft-ietf-sfc-nsh-tlv-01
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 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 June 15, 2020.
Copyright Notice
Copyright (c) 2019 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 June 15, 2020 [Page 1]
Internet-Draft Network Service Header TLVs December 2019
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. Requirements Language . . . . . . . . . . . . . . . . . . 3
3. NSH Type 2 Format . . . . . . . . . . . . . . . . . . . . . . 3
4. NSH Type 2 TLVs . . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Forwarding Context . . . . . . . . . . . . . . . . . . . 4
4.2. Tenant . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.3. Content Type . . . . . . . . . . . . . . . . . . . . . . 5
4.4. Ingress Network Information . . . . . . . . . . . . . . . 5
4.5. Flow ID . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.6. Source and/or Destination Groups . . . . . . . . . . . . 6
4.7. Universal Resource Identifier (URI) . . . . . . . . . . . 6
4.8. Policy Identifier (POLICY_ID) . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Network Service Header [RFC8300] 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.
Wei, et al. Expires June 15, 2020 [Page 2]
Internet-Draft Network Service Header TLVs December 2019
2. Conventions used in this document
2.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
Show full document text