Network Service Header (NSH)
RFC 8300
| Document | Type |
RFC - Proposed Standard
(January 2018; No errata)
Was draft-ietf-sfc-nsh (sfc WG)
|
|
|---|---|---|---|
| Last updated | 2018-01-12 | ||
| Replaces | draft-quinn-sfc-nsh | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Joel Halpern | ||
| Shepherd write-up | Show (last changed 2017-07-26) | ||
| IESG | IESG state | RFC 8300 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alia Atlas | ||
| Send notices to | "Joel M. Halpern" <jmh@joelhalpern.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) P. Quinn, Ed.
Request for Comments: 8300 Cisco
Category: Standards Track U. Elzur, Ed.
ISSN: 2070-1721 Intel
C. Pignataro, Ed.
Cisco
January 2018
Network Service Header (NSH)
Abstract
This document describes a Network Service Header (NSH) imposed on
packets or frames to realize Service Function Paths (SFPs). The NSH
also provides a mechanism for metadata exchange along the
instantiated service paths. The NSH is the Service Function Chaining
(SFC) encapsulation required to support the SFC architecture (defined
in RFC 7665).
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8300.
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.
Quinn, et al. Standards Track [Page 1]
RFC 8300 Network Service Header (NSH) January 2018
Table of Contents
1. Introduction ....................................................3
1.1. Applicability ..............................................4
1.2. Requirements Language ......................................4
1.3. Definition of Terms ........................................4
1.4. Problem Space ..............................................6
1.5. NSH-Based Service Chaining .................................6
2. Network Service Header ..........................................7
2.1. Network Service Header Format ..............................7
2.2. NSH Base Header ............................................8
2.3. Service Path Header .......................................11
2.4. NSH MD Type 1 .............................................12
2.5. NSH MD Type 2 .............................................13
2.5.1. Optional Variable-Length Metadata ..................13
3. NSH Actions ....................................................15
4. NSH Transport Encapsulation ....................................16
5. Fragmentation Considerations ...................................17
6. Service Path Forwarding with NSH ...............................18
6.1. SFFs and Overlay Selection ................................18
6.2. Mapping the NSH to Network Topology .......................21
6.3. Service Plane Visibility ..................................21
6.4. Service Graphs ............................................22
7. Policy Enforcement with NSH ....................................22
7.1. NSH Metadata and Policy Enforcement .......................22
7.2. Updating/Augmenting Metadata ..............................24
7.3. Service Path Identifier and Metadata ......................25
8. Security Considerations ........................................26
8.1. NSH Security Considerations from Operators' Environments ..27
8.2. NSH Security Considerations from the SFC Architecture .....28
8.2.1. Integrity ..........................................29
8.2.2. Confidentiality ....................................31
9. IANA Considerations ............................................32
9.1. NSH Parameters ............................................32
9.1.1. NSH Base Header Bits ...............................32
9.1.2. NSH Version ........................................32
9.1.3. NSH MD Types .......................................33
9.1.4. NSH MD Class .......................................33
Show full document text