< draft-pthubert-raw-problem-statement-02.txt		draft-pthubert-raw-problem-statement-03.txt >
	RAW P. Thubert, Ed.		RAW P. Thubert, Ed.
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Informational G. Papadopoulos		Intended status: Informational G.Z. Papadopoulos
	Expires: April 5, 2020 IMT Atlantique		Expires: 10 April 2020 IMT Atlantique
	October 3, 2019		8 October 2019
	Reliable and Available Wireless Problem Statement		Reliable and Available Wireless Problem Statement
	draft-pthubert-raw-problem-statement-02		draft-pthubert-raw-problem-statement-03
	Abstract		Abstract
	Due to uncontrolled interferences, including the self-induced		Due to uncontrolled interferences, including the self-induced
	multipath fading, deterministic networking can only be approached on		multipath fading, deterministic networking can only be approached on
	wireless links. The radio conditions may change -way- faster than a		wireless links. The radio conditions may change -way- faster than a
	centralized routing can adapt and reprogram, in particular when the		centralized routing can adapt and reprogram, in particular when the
	controller is distant and connectivity is slow and limited. RAW		controller is distant and connectivity is slow and limited. RAW
	separates the routing time scale at which a complex path is		separates the routing time scale at which a complex path is
	recomputed from the forwarding time scale at which the forwarding		recomputed from the forwarding time scale at which the forwarding
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	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 April 5, 2020.		This Internet-Draft will expire on 10 April 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	(https://trustee.ietf.org/license-info) in effect on the date of		license-info) in effect on the date of publication of this document.
	publication of this document. Please review these documents		Please review these documents carefully, as they describe your rights
	carefully, as they describe your rights and restrictions with respect		and restrictions with respect to this document. Code Components
	to this document. Code Components extracted from this document must		extracted from this document must include Simplified BSD License text
	include Simplified BSD License text as described in Section 4.e of		as described in Section 4.e of the Trust Legal Provisions and are
	the Trust Legal Provisions and are provided without warranty as		provided without warranty as described in the Simplified BSD License.
	described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Use Cases and Requirements Served . . . . . . . . . . . . . . 4		2. Use Cases and Requirements Served . . . . . . . . . . . . . . 4
	3. Routing Scale vs. Forwarding Scale . . . . . . . . . . . . . 4		3. Routing Scale vs. Forwarding Scale . . . . . . . . . . . . . 4
	4. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 5		4. Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . 5
	5. Related Work at The IETF . . . . . . . . . . . . . . . . . . 6		5. Related Work at The IETF . . . . . . . . . . . . . . . . . . 5
	6. Functional Gaps . . . . . . . . . . . . . . . . . . . . . . . 6		6. Functional Gaps . . . . . . . . . . . . . . . . . . . . . . . 6
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
	7.1. Normative References . . . . . . . . . . . . . . . . . . 7		7.1. Normative References . . . . . . . . . . . . . . . . . . 7
	7.2. Informative References . . . . . . . . . . . . . . . . . 8		7.2. Informative References . . . . . . . . . . . . . . . . . 8
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
	1. Introduction		1. Introduction
	Bringing determinism in a packet network means eliminating the		Bringing determinism in a packet network means eliminating the
	statistical effects of multiplexing that result in probabilistic		statistical effects of multiplexing that result in probabilistic
	skipping to change at page 3, line 40 ¶		skipping to change at page 3, line 39 ¶
	transmissions is assumed. How the PHY is programmed to do so, and		transmissions is assumed. How the PHY is programmed to do so, and
	whether the radio is single-hop or meshed, are unknown at the IP		whether the radio is single-hop or meshed, are unknown at the IP
	layer and not part of the RAW abstraction.		layer and not part of the RAW abstraction.
	Still, in order to focus on real-worlds issues and assert the		Still, in order to focus on real-worlds issues and assert the
	feasibility of the proposed capabilities, RAW will focus on selected		feasibility of the proposed capabilities, RAW will focus on selected
	technologies that can be scheduled at the lower layers: IEEE Std.		technologies that can be scheduled at the lower layers: IEEE Std.
	802.15.4 timeslotted channel hopping (TSCH), 3GPP 5G ultra-reliable		802.15.4 timeslotted channel hopping (TSCH), 3GPP 5G ultra-reliable
	low latency communications (URLLC), IEEE 802.11ax/be where 802.11be		low latency communications (URLLC), IEEE 802.11ax/be where 802.11be
	is extreme high throughput (EHT), and L-band Digital Aeronautical		is extreme high throughput (EHT), and L-band Digital Aeronautical
	Communications System (LDACS). See [I-D.thubert-raw-technologies]		Communications System (LDACS). See [RAW-TECHNOS] for more.
	for more.
	The establishment of a path is not in-scope for RAW. It may be the		The establishment of a path is not in-scope for RAW. It may be the
	product of a centralized Controller Plane as described for DetNet.		product of a centralized Controller Plane as described for DetNet.
	As opposed to wired networks, the action of installing a path over a		As opposed to wired networks, the action of installing a path over a
	set of wireless links may be very slow relative to the speed at which		set of wireless links may be very slow relative to the speed at which
	the radio conditions vary, and it makes sense in the wireless case to		the radio conditions vary, and it makes sense in the wireless case to
	provide redundant forwarding solutions along a complex path and to		provide redundant forwarding solutions along a complex path and to
	leave it to the RAW Network Plane to select which of those forwarding		leave it to the RAW Network Plane to select which of those forwarding
	solutions are to be used for a given packet based on the current		solutions are to be used for a given packet based on the current
	conditions.		conditions.
	skipping to change at page 4, line 20 ¶		skipping to change at page 4, line 20 ¶
	Network plane protocol elements such as OAM and in-band control to		Network plane protocol elements such as OAM and in-band control to
	improve the RAW operation at the Service and at the forwarding sub-		improve the RAW operation at the Service and at the forwarding sub-
	layers, e.g., controlling whether to use packet replication, Hybrid		layers, e.g., controlling whether to use packet replication, Hybrid
	ARQ and coding, with a constraint to limit the use of redundancy when		ARQ and coding, with a constraint to limit the use of redundancy when
	it is really needed, e.g., when a spike of loss is observed. This is		it is really needed, e.g., when a spike of loss is observed. This is
	discussed in more details in Section 3 and the next sections.		discussed in more details in Section 3 and the next sections.
	2. Use Cases and Requirements Served		2. Use Cases and Requirements Served
	[RFC8578] presents a number of wireless use cases including Wireless		[RFC8578] presents a number of wireless use cases including Wireless
	for Industrial Applications. [I-D.bernardos-raw-use-cases] adds a		for Industrial Applications. [RAW-USE-CASES] adds a number of use
	number of use cases that demonstrate the need for RAW capabilities in		cases that demonstrate the need for RAW capabilities in Pro-Audio,
	Pro-Audio, gaming and robotics.		gaming and robotics.
	3. Routing Scale vs. Forwarding Scale		3. Routing Scale vs. Forwarding Scale
	RAW extends DetNet to focus on issues that are mostly a concern on		RAW extends DetNet to focus on issues that are mostly a concern on
	wireless links. See [I-D.ietf-detnet-architecture] for more on		wireless links. See [DetNet-ARCH] for more on DetNet. With DetNet,
	DetNet. With DetNet, the end-to-end routing can be centralized and		the end-to-end routing can be centralized and can reside outside the
	can reside outside the network. In wireless, and in particular in a		network. In wireless, and in particular in a wireless mesh, the path
	wireless mesh, the path to the controller that performs the route		to the controller that performs the route computation and maintenance
	computation and maintenance may be slow and expensive in terms of		may be slow and expensive in terms of critical resources such as air
	critical resources such as air time and energy.		time and energy.
	Reaching to the routing computation can be slow in regards to the		Reaching to the routing computation can be slow in regards to the
	speed of events that affect the forwarding operation at the radio		speed of events that affect the forwarding operation at the radio
	layer. Due to the cost and latency to perform a route computation,		layer. Due to the cost and latency to perform a route computation,
	routing is not expected to be sensitive/reactive to transient		routing is not expected to be sensitive/reactive to transient
	changes. The abstraction of a link at the routing level is expected		changes. The abstraction of a link at the routing level is expected
	to use statistical operational metrics that aggregate the behavior of		to use statistical operational metrics that aggregate the behavior of
	a link over long periods of time, and represent its availability as a		a link over long periods of time, and represent its availability as a
	shade of gray as opposed to either up or down.		shade of gray as opposed to either up or down.
	skipping to change at page 5, line 25 ¶		skipping to change at page 5, line 25 ¶
	to hours, but as a first approximation can ignore flapping. On the		to hours, but as a first approximation can ignore flapping. On the
	other hand, the RAW forwarding decision is made at packet speed, and		other hand, the RAW forwarding decision is made at packet speed, and
	uses information that must be pertinent at the present time for the		uses information that must be pertinent at the present time for the
	current transmission.		current transmission.
	4. Prerequisites		4. Prerequisites
	A prerequisite to the RAW work is that an end-to-end routing function		A prerequisite to the RAW work is that an end-to-end routing function
	computes a complex sub-topology along which forwarding can happen		computes a complex sub-topology along which forwarding can happen
	between a source and one or more destinations. For 6TiSCH, this is a		between a source and one or more destinations. For 6TiSCH, this is a
	Track. The concept of Track is specified in the		Track. The concept of Track is specified in the 6TiSCH Architecture
	[I-D.ietf-6tisch-architecture]. Tracks provide a high degree of		[6TiSCH-ARCH]. Tracks provide a high degree of redundancy and
	redundancy and diversity and enable DetNet PREOF, end-to-end network		diversity and enable DetNet PREOF, end-to-end network coding, and
	coding, and possibly radio-specific abstracted techniques such as		possibly radio-specific abstracted techniques such as ARQ,
	ARQ, overhearing, frequency diversity, time slotting, and possibly		overhearing, frequency diversity, time slotting, and possibly others.
	others.
	How the routing operation computes the Track is out of scope for RAW.		How the routing operation computes the Track is out of scope for RAW.
	The scope of the RAW operation is one Track, and the goal of the RAW		The scope of the RAW operation is one Track, and the goal of the RAW
	operation is to optimize the use of the Track at the forwarding		operation is to optimize the use of the Track at the forwarding
	timescale to maintain the expected service while optimizing the usage		timescale to maintain the expected service while optimizing the usage
	of constrained resources such as energy and spectrum.		of constrained resources such as energy and spectrum.
	Another prerequisite is that an IP link can be established over the		Another prerequisite is that an IP link can be established over the
	radio with some guarantees in terms of service reliability, e.g., it		radio with some guarantees in terms of service reliability, e.g., it
	can be relied upon to transmit a packet within a bounded latency and		can be relied upon to transmit a packet within a bounded latency and
	skipping to change at page 6, line 10 ¶		skipping to change at page 6, line 5 ¶
	return an abstract view of the state of the Link to help forwarding		return an abstract view of the state of the Link to help forwarding
	decision (think DLEP from MANET). In the layered approach, how the		decision (think DLEP from MANET). In the layered approach, how the
	radio manages its PHY layer is out of control and out of scope.		radio manages its PHY layer is out of control and out of scope.
	Whether it is single hop or meshed is also unknown and out of scope.		Whether it is single hop or meshed is also unknown and out of scope.
	5. Related Work at The IETF		5. Related Work at The IETF
	RAW intersects with protocols or practices in development at the IETF		RAW intersects with protocols or practices in development at the IETF
	as follows:		as follows:
	o The Dynamic Link Exchange Protocol [RFC8175] (DLEP) from [MANET]		* The Dynamic Link Exchange Protocol (DLEP) [RFC8175] from [MANET]
	can be leveraged at each hop to derive generic radio metrics		can be leveraged at each hop to derive generic radio metrics
	(e.g., based on LQI, RSSI, queueing delays and ETX) on individual		(e.g., based on LQI, RSSI, queueing delays and ETX) on individual
	hops		hops
	o Operations, Administration and Maintenance (OAM) work at [DetNet]		* Operations, Administration and Maintenance (OAM) work at [DetNet]
	such as [I-D.mirsky-detnet-ip-oam] for the case of the IP Data		such as [DetNet-IP-OAM] for the case of the IP Data Plane observes
	Plane observes the state of DetNet paths, typically MPLS and IPv6		the state of DetNet paths, typically MPLS and IPv6 pseudowires
	pseudowires [I-D.ietf-detnet-data-plane-framework], in the		[DetNet-DP-FW], in the direction of the traffic. RAW needs
	direction of the traffic. RAW needs feedback that flows on the		feedback that flows on the reverse path and gathers instantaneous
	reverse path and gathers instantaneous values from the radio		values from the radio receivers at each hop to inform back the
	receivers at each hop to inform back the source and replicating		source and replicating relays so they can make optimized
	relays so they can make optimized forwarding decisions. The work		forwarding decisions. The work named ICAN may be related as well.
	named ICAN may be related and may find a home at RAW.
	o [BFD] detect faults in the path between an ingress and an egress		* [BFD] detect faults in the path between an ingress and an egress
	forwarding engines, but is aware of the complexity of a path with		forwarding engines, but is unaware of the complexity of a path
	replication, and expects bidirectionality. BFD considers delivery		with replication, and expects bidirectionality. BFD considers
	as success whereas with RAW the bounded latency can be as		delivery as success whereas with RAW the bounded latency can be as
	important as the delivery itself.		important as the delivery itself.
	o [SPRING] and [BIER] define in-band signaling that influences the		* [SPRING] and [BIER] define in-band signaling that influences the
	routing when decided at the head-end on the path. There's already		routing when decided at the head-end on the path. There's already
	one RAW-related draft at BIER		one RAW-related draft at BIER [BIER-PREF] more may follow. RAW
	[I-D.thubert-bier-replication-elimination] more may follow. RAW
	will need new in-band signaling when the decision is distributed,		will need new in-band signaling when the decision is distributed,
	e.g., required chances of reliable delivery to destination within		e.g., required chances of reliable delivery to destination within
	latency. This signaling enables relays to tune retries and		latency. This signaling enables relays to tune retries and
	replication to be met.		replication to be met.
	o [CCAMP] defines protocol-independent metrics and parameters		* [CCAMP] defines protocol-independent metrics and parameters
	(measurement attributes) for describing links and paths that are		(measurement attributes) for describing links and paths that are
	required for routing and signaling in technology-specific		required for routing and signaling in technology-specific
	networks. RAW would be a source of requirements for CCAMP to		networks. RAW would be a source of requirements for CCAMP to
	define metrics that are significant to the focus radios.		define metrics that are significant to the focus radios.
	6. Functional Gaps		6. Functional Gaps
	Within a large routed topology, the routing operation builds a		Within a large routed topology, the routing operation builds a
	particular complex Track with one source and one or more		particular complex Track with one source and one or more
	destinations; within the Track, packets may follows different paths		destinations; within the Track, packets may follows different paths
	skipping to change at page 7, line 24 ¶		skipping to change at page 7, line 19 ¶
	specific knowledge of the state of the Track for the type of flow of		specific knowledge of the state of the Track for the type of flow of
	interest (e.g., for a QoS level of interest). To observe the whole		interest (e.g., for a QoS level of interest). To observe the whole
	Track in quasi real time, RAW will consider existing tools such as		Track in quasi real time, RAW will consider existing tools such as
	L2-triggers, DLEP, BFD and in-band and out-of-band OAM.		L2-triggers, DLEP, BFD and in-band and out-of-band OAM.
	One possible way of making the RAW forwarding decisions is to make		One possible way of making the RAW forwarding decisions is to make
	them all at the ingress and express them in-band in the packet, which		them all at the ingress and express them in-band in the packet, which
	requires new loose or strict Hop-by-hop signaling. To control the		requires new loose or strict Hop-by-hop signaling. To control the
	RAW forwarding operation along a Track for the individual packets,		RAW forwarding operation along a Track for the individual packets,
	RAW may leverage and extend known techniques such as DetNet tagging,		RAW may leverage and extend known techniques such as DetNet tagging,
	Segment Routing (SRv6) or BIER-TE such as done with		Segment Routing (SRv6) or BIER-TE such as done with [BIER-PREF].
	[I-D.thubert-bier-replication-elimination].
	An alternate way is to enable each forwarding node to make the RAW		An alternate way is to enable each forwarding node to make the RAW
	forwarding decisions for a packet on its own, based on its knowledge		forwarding decisions for a packet on its own, based on its knowledge
	of the expectation (timeliness and reliability) for that packet and a		of the expectation (timeliness and reliability) for that packet and a
	recent observation of the rest of the way across the possible paths		recent observation of the rest of the way across the possible paths
	within the Track. Information about the service should be placed in		within the Track. Information about the service should be placed in
	the packet and matched with the forwarding node's capabilities and		the packet and matched with the forwarding node's capabilities and
	policies.		policies.
	In either case, a per-flow state is installed in all intermediate		In either case, a per-flow state is installed in all intermediate
	nodes to recognize the flow and determine the forwarding policy to be		nodes to recognize the flow and determine the forwarding policy to be
	applied.		applied.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[I-D.bernardos-raw-use-cases]		[6TiSCH-ARCH]
	Papadopoulos, G., Thubert, P., Theoleyre, F., and C.
	Bernardos, "RAW use cases", draft-bernardos-raw-use-
	cases-00 (work in progress), July 2019.
	[I-D.ietf-6tisch-architecture]
	Thubert, P., "An Architecture for IPv6 over the TSCH mode		Thubert, P., "An Architecture for IPv6 over the TSCH mode
	of IEEE 802.15.4", draft-ietf-6tisch-architecture-26 (work		of IEEE 802.15.4", Work in Progress, Internet-Draft,
	in progress), August 2019.		draft-ietf-6tisch-architecture-26, 27 August 2019,
			<https://tools.ietf.org/html/draft-ietf-6tisch-
			architecture-26>.
	[I-D.ietf-detnet-architecture]		[DetNet-ARCH]
	Finn, N., Thubert, P., Varga, B., and J. Farkas,		Finn, N., Thubert, P., Varga, B., and J. Farkas,
	"Deterministic Networking Architecture", draft-ietf-		"Deterministic Networking Architecture", Work in Progress,
	detnet-architecture-13 (work in progress), May 2019.		Internet-Draft, draft-ietf-detnet-architecture-13, 6 May
			2019, <https://tools.ietf.org/html/draft-ietf-detnet-
			architecture-13>.
	[I-D.thubert-raw-technologies]		[RAW-TECHNOS]
	Thubert, P., Cavalcanti, D., Vilajosana, X., and C.		Thubert, P., Cavalcanti, D., Vilajosana, X., and C.
	Schmitt, "Reliable and Available Wireless Technologies",		Schmitt, "Reliable and Available Wireless Technologies",
	draft-thubert-raw-technologies-03 (work in progress), July		Work in Progress, Internet-Draft, draft-thubert-raw-
	2019.		technologies-03, 1 July 2019,
			<https://tools.ietf.org/html/draft-thubert-raw-
			technologies-03>.
			[RAW-USE-CASES]
			Papadopoulos, G., Thubert, P., Theoleyre, F., and C.
			Bernardos, "RAW use cases", Work in Progress, Internet-
			Draft, draft-bernardos-raw-use-cases-00, 5 July 2019,
			<https://tools.ietf.org/html/draft-bernardos-raw-use-
			cases-00>.
	[RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.		[RFC8175] Ratliff, S., Jury, S., Satterwhite, D., Taylor, R., and B.
	Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,		Berry, "Dynamic Link Exchange Protocol (DLEP)", RFC 8175,
	DOI 10.17487/RFC8175, June 2017,		DOI 10.17487/RFC8175, June 2017,
	<https://www.rfc-editor.org/info/rfc8175>.		<https://www.rfc-editor.org/info/rfc8175>.
	[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",		[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",
	RFC 8578, DOI 10.17487/RFC8578, May 2019,		RFC 8578, DOI 10.17487/RFC8578, May 2019,
	<https://www.rfc-editor.org/info/rfc8578>.		<https://www.rfc-editor.org/info/rfc8578>.
	7.2. Informative References		7.2. Informative References
	[BFD] IETF, "Bidirectional Forwarding Detection",		[BFD] IETF, "Bidirectional Forwarding Detection", October 2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-bfd/>.		<https://dataTracker.ietf.org/doc/charter-ietf-bfd/>.
	[BIER] IETF, "Bit Indexed Explicit Replication",		[BIER] IETF, "Bit Indexed Explicit Replication", October 2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-bier/>.		<https://dataTracker.ietf.org/doc/charter-ietf-bier/>.
	[CCAMP] IETF, "Common Control and Measurement Plane",		[BIER-PREF]
			Thubert, P., Eckert, T., Brodard, Z., and H. Jiang, "BIER-
			TE extensions for Packet Replication and Elimination
			Function (PREF) and OAM", Work in Progress, Internet-
			Draft, draft-thubert-bier-replication-elimination-03, 3
			March 2018,
			<https://tools.ietf.org/html/draft-thubert-bier-
			replication-elimination-03>.
			[CCAMP] IETF, "Common Control and Measurement Plane", October
			2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-ccamp/>.		<https://dataTracker.ietf.org/doc/charter-ietf-ccamp/>.
	[DetNet] IETF, "Deterministic Networking",		[DetNet] IETF, "Deterministic Networking", October 2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-detnet/>.		<https://dataTracker.ietf.org/doc/charter-ietf-detnet/>.
	[I-D.ietf-detnet-data-plane-framework]		[DetNet-DP-FW]
	Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,		Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A.,
	Bryant, S., and J. Korhonen, "DetNet Data Plane		Bryant, S., and J. Korhonen, "DetNet Data Plane
	Framework", draft-ietf-detnet-data-plane-framework-02		Framework", Work in Progress, Internet-Draft, draft-ietf-
	(work in progress), September 2019.		detnet-data-plane-framework-02, 13 September 2019,
			<https://tools.ietf.org/html/draft-ietf-detnet-data-plane-
			framework-02>.
	[I-D.mirsky-detnet-ip-oam]		[DetNet-IP-OAM]
	Mirsky, G. and M. Chen, "Operations, Administration and		Mirsky, G. and M. Chen, "Operations, Administration and
	Maintenance (OAM) for Deterministic Networks (DetNet) with		Maintenance (OAM) for Deterministic Networks (DetNet) with
	IP Data Plane", draft-mirsky-detnet-ip-oam-00 (work in		IP Data Plane", Work in Progress, Internet-Draft, draft-
	progress), July 2019.		mirsky-detnet-ip-oam-00, 8 July 2019,
			<https://tools.ietf.org/html/draft-mirsky-detnet-ip-oam-
	[I-D.thubert-bier-replication-elimination]		00>.
	Thubert, P., Eckert, T., Brodard, Z., and H. Jiang, "BIER-
	TE extensions for Packet Replication and Elimination
	Function (PREF) and OAM", draft-thubert-bier-replication-
	elimination-03 (work in progress), March 2018.
	[MANET] IETF, "Mobile Ad hoc Networking",		[MANET] IETF, "Mobile Ad hoc Networking", October 2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-manet/>.		<https://dataTracker.ietf.org/doc/charter-ietf-manet/>.
	[PCE] IETF, "Path Computation Element",		[SPRING] IETF, "Source Packet Routing in Networking", October 2019,
	<https://dataTracker.ietf.org/doc/charter-ietf-pce/>.
	[SPRING] IETF, "Source Packet Routing in Networking",
	<https://dataTracker.ietf.org/doc/charter-ietf-spring/>.		<https://dataTracker.ietf.org/doc/charter-ietf-spring/>.
	[TEAS] IETF, "Traffic Engineering Architecture and Signaling",
	<https://dataTracker.ietf.org/doc/charter-ietf-teas/>.
	Authors' Addresses		Authors' Addresses
	Pascal Thubert (editor)		Pascal Thubert (editor)
	Cisco Systems, Inc		Cisco Systems, Inc
	Building D		Building D, 45 Allee des Ormes - BP1200
	45 Allee des Ormes - BP1200		06254 MOUGINS - Sophia Antipolis
	MOUGINS - Sophia Antipolis 06254		France
	FRANCE
	Phone: +33 497 23 26 34		Phone: +33 497 23 26 34
	Email: pthubert@cisco.com		Email: pthubert@cisco.com
	Georgios Z. Papadopoulos		Georgios Z. Papadopoulos
	IMT Atlantique		IMT Atlantique
	Office B00 - 114A		Office B00 - 114A, 2 Rue de la Chataigneraie
	2 Rue de la Chataigneraie		35510 Cesson-Sevigne - Rennes
	Cesson-Sevigne - Rennes 35510		France
	FRANCE
	Phone: +33 299 12 70 04		Phone: +33 299 12 70 04
	Email: georgios.papadopoulos@imt-atlantique.fr		Email: georgios.papadopoulos@imt-atlantique.fr
End of changes. 36 change blocks.
	97 lines changed or deleted		100 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/