< draft-ietf-detnet-mpls-oam-04.txt		draft-ietf-detnet-mpls-oam-05.txt >
	DetNet Working Group G. Mirsky		DetNet Working Group G. Mirsky
	Internet-Draft Ericsson		Internet-Draft Ericsson
	Intended status: Standards Track M. Chen		Intended status: Standards Track M. Chen
	Expires: 23 March 2022 Huawei		Expires: 21 April 2022 Huawei
	19 September 2021		18 October 2021
	Operations, Administration and Maintenance (OAM) for Deterministic		Operations, Administration and Maintenance (OAM) for Deterministic
	Networks (DetNet) with MPLS Data Plane		Networks (DetNet) with MPLS Data Plane
	draft-ietf-detnet-mpls-oam-04		draft-ietf-detnet-mpls-oam-05
	Abstract		Abstract
	This document defines format and use principals of the Deterministic		This document defines format and use principals of the Deterministic
	Network (DetNet) service Associated Channel (ACH) over a DetNet		Network (DetNet) service Associated Channel (ACH) over a DetNet
	network with the MPLS data plane. The DetNet service ACH can be used		network with the MPLS data plane. The DetNet service ACH can be used
	to carry test packets of active Operations, Administration, and		to carry test packets of active Operations, Administration, and
	Maintenance protocols that are used to detect DetNet failures and		Maintenance protocols that are used to detect DetNet failures and
	measure performance metrics.		measure performance metrics.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	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 23 March 2022.		This Internet-Draft will expire on 21 April 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 22 ¶		skipping to change at page 2, line 22 ¶
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Conventions used in this document . . . . . . . . . . . . . . 3		2. Conventions used in this document . . . . . . . . . . . . . . 3
	2.1. Terminology and Acronyms . . . . . . . . . . . . . . . . 3		2.1. Terminology and Acronyms . . . . . . . . . . . . . . . . 3
	2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 4		2.2. Keywords . . . . . . . . . . . . . . . . . . . . . . . . 4
	3. Active OAM for DetNet Networks with MPLS Data Plane . . . . . 4		3. Active OAM for DetNet Networks with MPLS Data Plane . . . . . 4
	3.1. DetNet Active OAM Encapsulation . . . . . . . . . . . . . 5		3.1. DetNet Active OAM Encapsulation . . . . . . . . . . . . . 5
	3.2. DetNet Replication, Elimination, and Ordering Sub-functions		3.2. DetNet Packet Replication, Elimination, and Ordering
	Interaction with Active OAM . . . . . . . . . . . . . . . 7		Functions Interaction with Active OAM . . . . . . . . . . 7
	4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 7		4. Use of Hybrid OAM in DetNet . . . . . . . . . . . . . . . . . 7
	5. OAM Interworking Models . . . . . . . . . . . . . . . . . . . 8		5. OAM Interworking Models . . . . . . . . . . . . . . . . . . . 7
	5.1. OAM of DetNet MPLS Interworking with OAM of TSN . . . . . 8		5.1. OAM of DetNet MPLS Interworking with OAM of TSN . . . . . 8
	5.2. OAM of DetNet MPLS Interworking with OAM of DetNet IP . . 9		5.2. OAM of DetNet MPLS Interworking with OAM of DetNet IP . . 9
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 9		7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
	8. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 9		8. Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . 9
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
	9.1. Normative References . . . . . . . . . . . . . . . . . . 9		9.1. Normative References . . . . . . . . . . . . . . . . . . 9
	9.2. Informational References . . . . . . . . . . . . . . . . 10		9.2. Informational References . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
	1. Introduction		1. Introduction
	[RFC8655] introduces and explains Deterministic Networks (DetNet)		[RFC8655] introduces and explains Deterministic Networks (DetNet)
	architecture and how the Packet Replication and Elimination function		architecture and how the Packet Replication, Elimination, and
	(PREF) can be used to ensure low packet drop ratio in DetNet domain.		Ordering functions (PREOF) can be used to ensure low packet drop
			ratio in DetNet domain.
	Operations, Administration and Maintenance (OAM) protocols are used		Operations, Administration and Maintenance (OAM) protocols are used
	to detect, localize defects in the network, and monitor network		to detect, localize defects in the network, and monitor network
	performance. Some OAM functions, e.g., failure detection, work in		performance. Some OAM functions, e.g., failure detection, work in
	the network proactively, while others, e.g., defect localization,		the network proactively, while others, e.g., defect localization,
	usually performed on-demand. These tasks achieved by a combination		usually performed on-demand. These tasks achieved by a combination
	of active and hybrid, as defined in [RFC7799], OAM methods.		of active and hybrid, as defined in [RFC7799], OAM methods.
	Also, this document defines format and use principals of the DetNet		Also, this document defines format and use principals of the DetNet
	service Associated Channel over a DetNet network with the MPLS data		service Associated Channel over a DetNet network with the MPLS data
	skipping to change at page 3, line 29 ¶		skipping to change at page 3, line 29 ¶
	d-CW DetNet Control Word		d-CW DetNet Control Word
	DNH DetNet Header		DNH DetNet Header
	GAL Generic Associated Channel Label		GAL Generic Associated Channel Label
	G-ACh Generic Associated Channel		G-ACh Generic Associated Channel
	OAM: Operations, Administration and Maintenance		OAM: Operations, Administration and Maintenance
	PREF Packet Replication and Elimination Function		PREOF Packet Replication, Elimination, and Ordering Functions
	POF Packet Ordering Function
	PW Pseudowire		PW Pseudowire
	RDI Remote Defect Indication		RDI Remote Defect Indication
	E2E End-to-end		E2E End-to-end
	CFM Connectivity Fault Management		CFM Connectivity Fault Management
	BFD Bidirectional Forwarding Detection		BFD Bidirectional Forwarding Detection
	skipping to change at page 4, line 11 ¶		skipping to change at page 4, line 11 ¶
	that implement also the DetNet service sub-layer functions. An		that implement also the DetNet service sub-layer functions. An
	S-Label is also used to identify a DetNet flow at DetNet service sub-		S-Label is also used to identify a DetNet flow at DetNet service sub-
	layer.		layer.
	Underlay Network or Underlay Layer: The network that provides		Underlay Network or Underlay Layer: The network that provides
	connectivity between the DetNet nodes. MPLS network providing LSP		connectivity between the DetNet nodes. MPLS network providing LSP
	connectivity between DetNet nodes is an example of the underlay		connectivity between DetNet nodes is an example of the underlay
	layer.		layer.
	DetNet Node - a node that is an actor in the DetNet domain. DetNet		DetNet Node - a node that is an actor in the DetNet domain. DetNet
	domain edge node and node that performs PREF within the domain are		domain edge node and node that performs PREOF within the domain are
	examples of DetNet node.		examples of DetNet node.
	2.2. Keywords		2.2. Keywords
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in BCP
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	skipping to change at page 5, line 5 ¶		skipping to change at page 5, line 5 ¶
	displayed in Figure 1.		displayed in Figure 1.
	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
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	|0 0 0 0| Sequence Number |		|0 0 0 0| Sequence Number |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: DetNet Control Word Format		Figure 1: DetNet Control Word Format
	PREF in the DetNet domain composed by a combination of nodes that		PREOF in the DetNet domain composed by a combination of nodes that
	perform replication and elimination sub-functions. The elimination		perform replication and elimination functions. The elimination
	sub-function always uses the S-Label and packet sequencing		function always uses the S-Label and packet sequencing information,
	information, e.g., the value in the Sequence Number field of DetNet		e.g., the value in the Sequence Number field of DetNet CW (d-CW).
	CW (d-CW). The replication sub-function uses the S-Label information		The replication sub-function uses the S-Label information only. For
	only. For data packets Figure 2 presents an example of PREF in		data packets Figure 2 presents an example of PREOF in DetNet domain.
	DetNet domain.
	1111 11111111 111111 112212 112212 132213		1111 11111111 111111 112212 112212 132213
	CE1----EN1--------R1-------R2-------R3--------EN2----CE2		CE1----EN1--------R1-------R2-------R3--------EN2----CE2
	\2 22222/ 3 /		\2 22222/ 3 /
	\2222222 /----+ 3 /		\2222222 /----+ 3 /
	+------R4------------------------+		+------R4------------------------+
	333333333333333333333333		333333333333333333333333
	Figure 2: DetNet Data Plane Based on PW		Figure 2: DetNet Data Plane Based on PW
	3.1. DetNet Active OAM Encapsulation		3.1. DetNet Active OAM Encapsulation
	DetNet OAM, like PW OAM, uses PW Associated Channel Header defined in		DetNet OAM, like PW OAM, uses PW Associated Channel Header defined in
	[RFC4385]. Figure 3 displays the encapsulation of a DetNet MPLS		[RFC4385]. Figure 3 displays the encapsulation of a DetNet MPLS
	[RFC8964] active OAM packet.		[RFC8964] active OAM packet.
	+---------------------------------+		+---------------------------------+
	| |		| |
	| DetNet App-Flow |		| DetNet OAM Packet |
	| Payload Packet |
	| |		| |
	+---------------------------------+ <--\		+---------------------------------+ <--\
	| DetNet Associated Channel Header| |		| DetNet Associated Channel Header| |
	+---------------------------------+ +--> DetNet active OAM		+---------------------------------+ +--> DetNet active OAM
	| S-Label | | MPLS encapsulation		| S-Label | | MPLS encapsulation
	+---------------------------------+ |		+---------------------------------+ |
	| [ F-Label(s) ] | |		| [ F-Label(s) ] | |
	+---------------------------------+ <--/		+---------------------------------+ <--/
	| Data-Link |		| Data-Link |
	+---------------------------------+		+---------------------------------+
	| Physical |		| Physical |
	+---------------------------------+		+---------------------------------+
	Figure 3: DetNet Active OAM Packet Encapsulation in MPLS Data Plane		Figure 3: DetNet Active OAM Packet Encapsulation in MPLS Data Plane
	Figure 4 displays encapsulation of a test packet of an active DetNet		Figure 4 displays encapsulation of a test packet of an active DetNet
	OAM protocol in case of MPLS-over-UDP/IP [RFC9025].		OAM protocol in case of MPLS-over-UDP/IP [RFC9025].
	+---------------------------------+		+---------------------------------+
	| |		| |
	| DetNet App-Flow |		| DetNet OAM Packet |
	| Payload Packet |
	| |		| |
	+---------------------------------+ <--\		+---------------------------------+ <--\
	| DetNet Associated Channel Header| |		| DetNet Associated Channel Header| |
	+---------------------------------+ +--> DetNet active OAM		+---------------------------------+ +--> DetNet active OAM
	| S-Label | | MPLS encapsulation		| S-Label | | MPLS encapsulation
	+---------------------------------+ |		+---------------------------------+ |
	| [ F-label(s) ] | |		| [ F-label(s) ] | |
	+---------------------------------+ <--+		+---------------------------------+ <--+
	| UDP Header | |		| UDP Header | |
	+---------------------------------+ +--> DetNet data plane		+---------------------------------+ +--> DetNet data plane
	skipping to change at page 7, line 7 ¶		skipping to change at page 7, line 7 ¶
	Bits 0..3 MUST be 0b0001. This value of the first nibble allows		Bits 0..3 MUST be 0b0001. This value of the first nibble allows
	the packet to be distinguished from an IP packet [RFC4928] and a		the packet to be distinguished from an IP packet [RFC4928] and a
	DetNet data packet [RFC8964].		DetNet data packet [RFC8964].
	Version: this is the version number of the d-ACH. This		Version: this is the version number of the d-ACH. This
	specification defines version 0.		specification defines version 0.
	Sequence Number: this is unsigned eight bits-long field. The		Sequence Number: this is unsigned eight bits-long field. The
	originating DetNet node MUST set the value of the Sequence Number		originating DetNet node MUST set the value of the Sequence Number
	field to a non-zero before packet being transmitted. The		field before packet being transmitted. The originating node MUST
	originating node MUST monotonically increase the value of the		monotonically increase the value of the Sequence Number field for
	Sequence Number field for the every next active OAM packet.		the every next active OAM packet.
	Channel Type: the value of DetNet Associated Channel Type is one		Channel Type: the value of DetNet Associated Channel Type is one
	of values defined in the IANA PW Associated Channel Type registry.		of values defined in the IANA PW Associated Channel Type registry.
	The DetNet flow, according to [RFC8964], is identified by the S-label		The DetNet flow, according to [RFC8964], is identified by the S-label
	that MUST be at the bottom of the stack. Active OAM packet MUST have		that MUST be at the bottom of the stack. Active OAM packet MUST have
	d-ACH immediately following the S-label.		d-ACH immediately following the S-label.
	3.2. DetNet Replication, Elimination, and Ordering Sub-functions		3.2. DetNet Packet Replication, Elimination, and Ordering Functions
	Interaction with Active OAM		Interaction with Active OAM
	At the DetNet service layer, special functions MAY be applied to the		At the DetNet service sub-layer, special functions MAY be applied to
	particular DetNet flow - PREF to potentially lower packet loss,		the particular DetNet flow, PREOF, to potentially lower packet loss,
	improve the probability of on-time packet delivery and Packet		improve the probability of on-time packet delivery and ensure in-
	Ordering Function (POF) to ensure in-order packet delivery. As data		order packet delivery. PREOF rely on sequencing information in the
	and the active OAM packets have the same Flow ID, S-label, sub-		DetNet service sub-layer. For a DetNet active OAM packet, 28 MSBs of
	functions that rely on sequencing information in the DetNet service		the d-ACH MUST be used as the source of the sequencing information by
	layer MUST process 28 MSBs of the d-ACH as the source of the		PREOF.
	sequencing information for the OAM packet.
	4. Use of Hybrid OAM in DetNet		4. Use of Hybrid OAM in DetNet
	Hybrid OAM methods are used in performance monitoring and defined in		Hybrid OAM methods are used in performance monitoring and defined in
	[RFC7799] as:		[RFC7799] as:
	Hybrid Methods are Methods of Measurement that use a combination		Hybrid Methods are Methods of Measurement that use a combination
	of Active Methods and Passive Methods.		of Active Methods and Passive Methods.
	A hybrid measurement method may produce metrics as close to passive,		A hybrid measurement method may produce metrics as close to passive,
End of changes. 14 change blocks.
	36 lines changed or deleted		31 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/