< draft-ietf-sfc-nsh-tlv-13.txt		draft-ietf-sfc-nsh-tlv-14.txt >
	SFC Yuehua. Wei, Ed.		SFC Yuehua. Wei, Ed.
	Internet-Draft ZTE Corporation		Internet-Draft ZTE Corporation
	Intended status: Standards Track U. Elzur		Intended status: Standards Track U. Elzur
	Expires: 30 July 2022 Intel		Expires: 1 October 2022 Intel
	S. Majee		S. Majee
	Individual contributor		Individual contributor
	C. Pignataro		C. Pignataro
	Cisco		Cisco
	D. Eastlake		D. Eastlake
	Futurewei Technologies		Futurewei Technologies
	26 January 2022		30 March 2022
	Network Service Header Metadata Type 2 Variable-Length Context Headers		Network Service Header Metadata Type 2 Variable-Length Context Headers
	draft-ietf-sfc-nsh-tlv-13		draft-ietf-sfc-nsh-tlv-14
	Abstract		Abstract
	Service Function Chaining (SFC) uses the Network Service Header (NSH)		Service Function Chaining (SFC) uses the Network Service Header (NSH)
	(RFC 8300) to steer and provide context Metadata (MD) with each		(RFC 8300) to steer and provide context Metadata (MD) with each
	packet. Such Metadata can be of various Types including MD Type 2		packet. Such Metadata can be of various Types including MD Type 2
	variable length context headers. This document specifies several		variable length context headers. This document specifies several
	such context headers that can be used within a service function path.		such context headers that can be used within a service function path.
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 41 ¶		skipping to change at page 1, line 41 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at https://datatracker.ietf.org/drafts/current/.		Drafts is at https://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on 30 July 2022.		This Internet-Draft will expire on 1 October 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2022 IETF Trust and the persons identified as the		Copyright (c) 2022 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 2, line 27 ¶		skipping to change at page 2, line 27 ¶
	2. Conventions used in this document . . . . . . . . . . . . . . 3		2. Conventions used in this document . . . . . . . . . . . . . . 3
	2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3		2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
	2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3		2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3
	3. NSH MD Type 2 format . . . . . . . . . . . . . . . . . . . . 3		3. NSH MD Type 2 format . . . . . . . . . . . . . . . . . . . . 3
	4. NSH MD Type 2 Context Headers . . . . . . . . . . . . . . . . 4		4. NSH MD Type 2 Context Headers . . . . . . . . . . . . . . . . 4
	4.1. Forwarding Context . . . . . . . . . . . . . . . . . . . 4		4.1. Forwarding Context . . . . . . . . . . . . . . . . . . . 4
	4.2. Tenant Identifier . . . . . . . . . . . . . . . . . . . . 6		4.2. Tenant Identifier . . . . . . . . . . . . . . . . . . . . 6
	4.3. Ingress Network Node Information . . . . . . . . . . . . 6		4.3. Ingress Network Node Information . . . . . . . . . . . . 6
	4.4. Ingress Network Source Interface . . . . . . . . . . . . 7		4.4. Ingress Network Source Interface . . . . . . . . . . . . 7
	4.5. Flow ID . . . . . . . . . . . . . . . . . . . . . . . . . 8		4.5. Flow ID . . . . . . . . . . . . . . . . . . . . . . . . . 8
	4.6. Source and/or Destination Groups . . . . . . . . . . . . 8		4.6. Source and/or Destination Groups . . . . . . . . . . . . 9
	4.7. Policy Identifier . . . . . . . . . . . . . . . . . . . . 9		4.7. Policy Identifier . . . . . . . . . . . . . . . . . . . . 9
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 10		5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
	6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10		6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10		7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
	7.1. MD Type 2 Context Types . . . . . . . . . . . . . . . . . 10		7.1. MD Type 2 Context Types . . . . . . . . . . . . . . . . . 10
	7.2. Forwarding Context Types . . . . . . . . . . . . . . . . 11		7.2. Forwarding Context Types . . . . . . . . . . . . . . . . 11
			7.3. Flow ID Context Types . . . . . . . . . . . . . . . . . . 12
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
	8.1. Normative References . . . . . . . . . . . . . . . . . . 12		8.1. Normative References . . . . . . . . . . . . . . . . . . 12
	8.2. Informative References . . . . . . . . . . . . . . . . . 12		8.2. Informative References . . . . . . . . . . . . . . . . . 13
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
	1. Introduction		1. Introduction
	The Network Service Header (NSH) [RFC8300] is the Service Function		The Network Service Header (NSH) [RFC8300] is the Service Function
	Chaining (SFC) encapsulation that supports the SFC architecture		Chaining (SFC) encapsulation that supports the SFC architecture
	[RFC7665]. As such, the NSH provides following key elements:		[RFC7665]. As such, the NSH provides following key elements:
	1. Service Function Path (SFP) identification.		1. Service Function Path (SFP) identification.
	skipping to change at page 5, line 41 ¶		skipping to change at page 5, line 41 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Session ID |		| Session ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 7: Forwarding Context - 5(Session ID)		Figure 7: Forwarding Context - 5(Session ID)
	where:		where:
	Context Type (CT) is four bits-long field that defines the length		Context Type (CT) is four bits-long field that defines the length
	and the interpretation of the Forwarding Context field. Please		and the interpretation of the Forwarding Context field. Please
	see the IANA Considerations in Section 7. This document defines		see the IANA Considerations in Section 7.2. This document defines
	these CT values:		these CT values:
	- 0x0 - 12 bits VLAN identifier [IEEE.802.1Q_2018]. See		- 0x0 - 12 bits VLAN identifier [IEEE.802.1Q_2018]. See
	Figure 3.		Figure 3.
	- 0x1 - 24 bits double tagging identifiers. A service VLAN tag		- 0x1 - 24 bits double tagging identifiers. A service VLAN tag
	followed by a customer VLAN tag [IEEE.802.1Q_2018]. The two		followed by a customer VLAN tag [IEEE.802.1Q_2018]. The two
	VLAN IDs are concatenated and appear in the same order that		VLAN IDs are concatenated and appear in the same order that
	they appeared in the payload. See Figure 4.		they appeared in the payload. See Figure 4.
	skipping to change at page 6, line 43 ¶		skipping to change at page 6, line 43 ¶
	Figure 8: Tenant Identifier List		Figure 8: Tenant Identifier List
	The fields are described as follows:		The fields are described as follows:
	Length: Indicates the length of the Tenant ID in octets (see		Length: Indicates the length of the Tenant ID in octets (see
	Section 2.5.1 of [RFC8300]).		Section 2.5.1 of [RFC8300]).
	Tenant ID: Represents an opaque value pointing to Orchestration		Tenant ID: Represents an opaque value pointing to Orchestration
	system-generated tenant identifier. The structure and semantics		system-generated tenant identifier. The structure and semantics
	of this field are deployment specific.		of this field are specific to the operator's deployment across its
			operational domain, and are specified and assigned by an
			orchestration function. The specifics of that orchestration-based
			assignment are outside the scope of this document.
	4.3. Ingress Network Node Information		4.3. Ingress Network Node Information
	This context header carries a Node ID of the ingress network node.		This context header carries a Node ID of the ingress network node.
	0 1 2 3		0 1 2 3
	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		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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Metadata Class = 0x0000 | Type = TBA3 |U| Length = var|		| Metadata Class = 0x0000 | Type = TBA3 |U| Length = var|
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 8, line 19 ¶		skipping to change at page 8, line 19 ¶
	Label as Flow ID, [RFC6790] defined an entropy label which is		Label as Flow ID, [RFC6790] defined an entropy label which is
	generated based on flow information in the MPLS network is another		generated based on flow information in the MPLS network is another
	example of Flow ID. Absence of this field, or a value of zero		example of Flow ID. Absence of this field, or a value of zero
	denotes that packets have not been labeled.		denotes that packets have not been labeled.
	0 1 2 3		0 1 2 3
	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		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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Metadata Class = 0x0000 | Type = TBA5 |U| Length = 4 |		| Metadata Class = 0x0000 | Type = TBA5 |U| Length = 4 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Flow ID |		|CT=0x0 | Reserved | IPv6 Flow ID |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 11: Flow ID		Figure 11: IPv6 Flow ID
			0 1 2 3
			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
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Metadata Class = 0x0000 | Type = TBA5 |U| Length = 4 |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			|CT=0x1 | Reserved | MPLS entropy label |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			Figure 12: MPLS entropy label
	The fields are described as follows:		The fields are described as follows:
	Length: Indicates the length of the Flow ID in octets (see		Length: Indicates the length of the Flow ID in octets (see
	Section 2.5.1 of [RFC8300]). For example, IPv6 Flow Label in		Section 2.5.1 of [RFC8300]). For example, IPv6 Flow Label in
	[RFC8200] is 20-bit long. An entropy label in the MPLS network in		[RFC8200] is 20-bit long. An entropy label in the MPLS network in
	[RFC6790] is also 20-bit long.		[RFC6790] is also 20-bit long.
	Flow ID: Represents an opaque value of the Flow ID. The Flow ID		Context Type (CT) is four bits-long field that defines the length
	is right justified (appears in the least significant bits of the		and the interpretation of the Flow ID field. Please see the IANA
	Flow ID word) and is padded on the left with bits which MUST be		Considerations in Section 7.3. This document defines these CT
	sent as zero and ignored on receipt.		values:
			- 0x0 - 20 bits IPv6 Flow Label in [RFC8200]. See Figure 11.
			- 0x1 - 20 bits entropy label in the MPLS network in [RFC6790].
			See Figure 12.
			Reserved bits in the context fields MUST be sent as zero and
			ignored on receipt.
	4.6. Source and/or Destination Groups		4.6. Source and/or Destination Groups
	Intent-based systems can use this data to express the logical		Intent-based systems can use this data to express the logical
	grouping of source and/or destination objects. [OpenStack] and		grouping of source and/or destination objects. [OpenStack] and
	[OpenDaylight] provide examples of such a system. Each is expressed		[OpenDaylight] provide examples of such a system. Each is expressed
	as a 32-bit opaque object.		as a 32-bit opaque object.
	0 1 2 3		0 1 2 3
	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		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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Metadata Class = 0x0000 | Type = TBA6 |U| Length=8 |		| Metadata Class = 0x0000 | Type = TBA6 |U| Length=8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Source Group |		| Source Group |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Dest Group |		| Dest Group |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 12: Source/Dest Groups		Figure 13: Source/Dest Groups
			If there is no group information specified for the source group or
			dest group field, the field MUST be sent as zero and ignored on
			receipt.
	4.7. Policy Identifier		4.7. Policy Identifier
	Traffic handling policies are often referred to by a system-generated		Traffic handling policies are often referred to by a system-generated
	identifier, which is then used by the devices to look up the policy's		identifier, which is then used by the devices to look up the policy's
	content locally. For example, this identifier could be an index to		content locally. For example, this identifier could be an index to
	an array, a lookup key, a database Id. The identifier allows		an array, a lookup key, a database Id. The identifier allows
	enforcement agents or services to look up the content of their part		enforcement agents or services to look up the content of their part
	of the policy.		of the policy.
	0 1 2 3		0 1 2 3
	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		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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Metadata Class = 0x0000 | Type = TBA7 |U| Length=var |		| Metadata Class = 0x0000 | Type = TBA7 |U| Length=var |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	~ Policy ID ~		~ Policy ID ~
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 13: Policy ID		Figure 14: Policy ID
	The fields are described as follows:		The fields are described as follows:
	Length: Indicates the length of the Policy ID in octets (see		Length: Indicates the length of the Policy ID in octets (see
	Section 2.5.1 of [RFC8300]).		Section 2.5.1 of [RFC8300]).
	Policy ID: Represents an opaque value of the Policy ID.		Policy ID: Represents an opaque value of the Policy ID.
	This policy identifier is a general policy ID, essentially a key to		This policy identifier is a general policy ID, essentially a key to
	allow Service Functions to know which policies to apply to packets.		allow Service Functions to know which policies to apply to packets.
	skipping to change at page 12, line 5 ¶		skipping to change at page 12, line 5 ¶
	+---------+-----------------------------------------+---------------+		+---------+-----------------------------------------+---------------+
	| 0x4 | 32-bit Session ID | This document |		| 0x4 | 32-bit Session ID | This document |
	+---------+-----------------------------------------+---------------+		+---------+-----------------------------------------+---------------+
	| 0x5-0xE | Unassigned | |		| 0x5-0xE | Unassigned | |
	+---------+-----------------------------------------+---------------+		+---------+-----------------------------------------+---------------+
	| 0xF | Reserved | This document |		| 0xF | Reserved | This document |
	+---------+-----------------------------------------+---------------+		+---------+-----------------------------------------+---------------+
	Table 2: Forwarding Context Types		Table 2: Forwarding Context Types
			7.3. Flow ID Context Types
			IANA is requested to create a new sub-registry for "Flow ID Context"
			context types at [IANA-NSH-MD2] as follows:
			The Registration Policy is IETF Review
			+=========+==============================+===============+
			| Value | Flow ID Context Header Types | Reference |
			+=========+==============================+===============+
			| 0x0 | 20-bit IPv6 Flow Label | This document |
			+---------+------------------------------+---------------+
			| 0x1 | 20-bit entropy label in the | This document |
			| | MPLS network | |
			+---------+------------------------------+---------------+
			| 0x2-0xE | Unassigned | |
			+---------+------------------------------+---------------+
			| 0xF | Reserved | This document |
			+---------+------------------------------+---------------+
			Table 3: Flow ID Context Types
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-sfc-nsh-integrity]		[I-D.ietf-sfc-nsh-integrity]
	Boucadair, M., Reddy, T., and D. Wing, "Integrity		Boucadair, M., Reddy, T., and D. Wing, "Integrity
	Protection for the Network Service Header (NSH) and		Protection for the Network Service Header (NSH) and
	Encryption of Sensitive Context Headers", Work in		Encryption of Sensitive Context Headers", Work in
	Progress, Internet-Draft, draft-ietf-sfc-nsh-integrity-09,		Progress, Internet-Draft, draft-ietf-sfc-nsh-integrity-09,
	20 September 2021, <https://www.ietf.org/archive/id/draft-		20 September 2021, <https://www.ietf.org/archive/id/draft-
End of changes. 15 change blocks.
	16 lines changed or deleted		64 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/