Diff: draft-ietf-detnet-use-cases-08.txt - draft-ietf-detnet-use-cases-09.txt

	draft-ietf-detnet-use-cases-08.txt	draft-ietf-detnet-use-cases-09.txt

	Internet Engineering Task Force E. Grossman, Ed.	Internet Engineering Task Force E. Grossman, Ed.
	Internet-Draft DOLBY	Internet-Draft DOLBY
	Intended status: Informational C. Gunther	Intended status: Informational C. Gunther

	Expires: September 8, 2016 HARMAN	Expires: September 22, 2016 HARMAN
	P. Thubert	P. Thubert
	P. Wetterwald	P. Wetterwald
	CISCO	CISCO
	J. Raymond	J. Raymond
	HYDRO-QUEBEC	HYDRO-QUEBEC
	J. Korhonen	J. Korhonen
	BROADCOM	BROADCOM
	Y. Kaneko	Y. Kaneko
	Toshiba	Toshiba
	S. Das	S. Das
	Applied Communication Sciences	Applied Communication Sciences
	Y. Zha	Y. Zha
	HUAWEI	HUAWEI
	B. Varga	B. Varga
	J. Farkas	J. Farkas
	Ericsson	Ericsson
	F. Goetz	F. Goetz
	J. Schmitt	J. Schmitt
	Siemens	Siemens

	March 7, 2016	March 21, 2016

	Deterministic Networking Use Cases	Deterministic Networking Use Cases

	draft-ietf-detnet-use-cases-08	draft-ietf-detnet-use-cases-09

	Abstract	Abstract

	This draft documents requirements in several diverse industries to	This draft documents requirements in several diverse industries to
	establish multi-hop paths for characterized flows with deterministic	establish multi-hop paths for characterized flows with deterministic
	properties. In this context deterministic implies that streams can	properties. In this context deterministic implies that streams can
	be established which provide guaranteed bandwidth and latency which	be established which provide guaranteed bandwidth and latency which
	can be established from either a Layer 2 or Layer 3 (IP) interface,	can be established from either a Layer 2 or Layer 3 (IP) interface,
	and which can co-exist on an IP network with best-effort traffic.	and which can co-exist on an IP network with best-effort traffic.


	skipping to change at page 2, line 20 ¶	skipping to change at page 2, line 20 ¶
	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 http://datatracker.ietf.org/drafts/current/.	Drafts is at http://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 September 8, 2016.	This Internet-Draft will expire on September 22, 2016.

	Copyright Notice	Copyright Notice

	Copyright (c) 2016 IETF Trust and the persons identified as the	Copyright (c) 2016 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
	(http://trustee.ietf.org/license-info) in effect on the date of	(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents	publication of this document. Please review these documents

	skipping to change at page 4, line 14 ¶	skipping to change at page 4, line 14 ¶

	5.2. Wireless Industrial Today . . . . . . . . . . . . . . . . 39	5.2. Wireless Industrial Today . . . . . . . . . . . . . . . . 39
	5.3. Wireless Industrial Future . . . . . . . . . . . . . . . 39	5.3. Wireless Industrial Future . . . . . . . . . . . . . . . 39
	5.3.1. Unified Wireless Network and Management . . . . . . . 39	5.3.1. Unified Wireless Network and Management . . . . . . . 39
	5.3.1.1. PCE and 6TiSCH ARQ Retries . . . . . . . . . . . 41	5.3.1.1. PCE and 6TiSCH ARQ Retries . . . . . . . . . . . 41
	5.3.2. Schedule Management by a PCE . . . . . . . . . . . . 42	5.3.2. Schedule Management by a PCE . . . . . . . . . . . . 42
	5.3.2.1. PCE Commands and 6TiSCH CoAP Requests . . . . . . 42	5.3.2.1. PCE Commands and 6TiSCH CoAP Requests . . . . . . 42
	5.3.2.2. 6TiSCH IP Interface . . . . . . . . . . . . . . . 43	5.3.2.2. 6TiSCH IP Interface . . . . . . . . . . . . . . . 43
	5.3.3. 6TiSCH Security Considerations . . . . . . . . . . . 43	5.3.3. 6TiSCH Security Considerations . . . . . . . . . . . 43
	5.4. Wireless Industrial Asks . . . . . . . . . . . . . . . . 44	5.4. Wireless Industrial Asks . . . . . . . . . . . . . . . . 44

	6. Cellular Radio Use Cases . . . . . . . . . . . . . . . . . . 44	6. Cellular Radio . . . . . . . . . . . . . . . . . . . . . . . 44
	6.1. Use Case Description . . . . . . . . . . . . . . . . . . 44	6.1. Use Case Description . . . . . . . . . . . . . . . . . . 44
	6.1.1. Network Architecture . . . . . . . . . . . . . . . . 44	6.1.1. Network Architecture . . . . . . . . . . . . . . . . 44
	6.1.2. Delay Constraints . . . . . . . . . . . . . . . . . . 45	6.1.2. Delay Constraints . . . . . . . . . . . . . . . . . . 45
	6.1.3. Time Synchronization Constraints . . . . . . . . . . 46	6.1.3. Time Synchronization Constraints . . . . . . . . . . 46
	6.1.4. Transport Loss Constraints . . . . . . . . . . . . . 48	6.1.4. Transport Loss Constraints . . . . . . . . . . . . . 48
	6.1.5. Security Considerations . . . . . . . . . . . . . . . 48	6.1.5. Security Considerations . . . . . . . . . . . . . . . 48
	6.2. Cellular Radio Networks Today . . . . . . . . . . . . . . 48	6.2. Cellular Radio Networks Today . . . . . . . . . . . . . . 48
	6.2.1. Fronthaul . . . . . . . . . . . . . . . . . . . . . . 48	6.2.1. Fronthaul . . . . . . . . . . . . . . . . . . . . . . 48
	6.2.2. Midhaul and Backhaul . . . . . . . . . . . . . . . . 49	6.2.2. Midhaul and Backhaul . . . . . . . . . . . . . . . . 49
	6.3. Cellular Radio Networks Future . . . . . . . . . . . . . 49	6.3. Cellular Radio Networks Future . . . . . . . . . . . . . 49

	skipping to change at page 44, line 17 ¶	skipping to change at page 44, line 17 ¶
	6TiSCH depends on DetNet to define:	6TiSCH depends on DetNet to define:

	o Configuration (state) and operations for deterministic paths	o Configuration (state) and operations for deterministic paths

	o End-to-end protocols for deterministic forwarding (tagging, IP)	o End-to-end protocols for deterministic forwarding (tagging, IP)

	o Protocol for packet replication and elimination	o Protocol for packet replication and elimination

	o Protocol for packet automatic retries (ARQ) (specific to wireless)	o Protocol for packet automatic retries (ARQ) (specific to wireless)


	6. Cellular Radio Use Cases	6. Cellular Radio

	6.1. Use Case Description	6.1. Use Case Description

	This use case describes the application of deterministic networking	This use case describes the application of deterministic networking
	in the context of cellular telecom transport networks. Important	in the context of cellular telecom transport networks. Important
	elements include time synchronization, clock distribution, and ways	elements include time synchronization, clock distribution, and ways
	of establishing time-sensitive streams for both Layer-2 and Layer-3	of establishing time-sensitive streams for both Layer-2 and Layer-3
	user plane traffic.	user plane traffic.

	6.1.1. Network Architecture	6.1.1. Network Architecture

	skipping to change at page 45, line 41 ¶	skipping to change at page 45, line 41 ¶
	processing uses most of it, allowing only a small fraction to be used	processing uses most of it, allowing only a small fraction to be used
	by the Fronthaul network (e.g. up to 250us one-way delay, though the	by the Fronthaul network (e.g. up to 250us one-way delay, though the
	existing spec ([NGMN-fronth]) supports delay only up to 100us). This	existing spec ([NGMN-fronth]) supports delay only up to 100us). This
	ultimately determines the distance the remote radio heads can be	ultimately determines the distance the remote radio heads can be
	located from the base stations (e.g., 100us equals roughly 20 km of	located from the base stations (e.g., 100us equals roughly 20 km of
	optical fiber-based transport). Allocation options of the available	optical fiber-based transport). Allocation options of the available
	time budget between processing and transport are under heavy	time budget between processing and transport are under heavy
	discussions in the mobile industry.	discussions in the mobile industry.

	For packet-based transport the allocated transport time (e.g. CPRI	For packet-based transport the allocated transport time (e.g. CPRI

	would allow for 100us delay [CPRI-transp]) is consumed by all nodes	would allow for 100us delay [CPRI]) is consumed by all nodes and
	and buffering between the remote radio head and the baseband	buffering between the remote radio head and the baseband processing
	processing unit, plus the distance-incurred delay.	unit, plus the distance-incurred delay.

	The baseband processing time and the available "delay budget" for the	The baseband processing time and the available "delay budget" for the
	fronthaul is likely to change in the forthcoming "5G" due to reduced	fronthaul is likely to change in the forthcoming "5G" due to reduced
	radio round trip times and other architectural and service	radio round trip times and other architectural and service
	requirements [NGMN].	requirements [NGMN].

	[METIS] documents the fundamental challenges as well as overall	[METIS] documents the fundamental challenges as well as overall
	technical goals of the future 5G mobile and wireless system as the	technical goals of the future 5G mobile and wireless system as the
	starting point. These future systems should support much higher data	starting point. These future systems should support much higher data
	volumes and rates and significantly lower end-to-end latency for 100x	volumes and rates and significantly lower end-to-end latency for 100x

	skipping to change at page 49, line 34 ¶	skipping to change at page 49, line 34 ¶
	synchronization capabilities as a part of the transport media.	synchronization capabilities as a part of the transport media.
	Alternatively other technologies such as Global Positioning System	Alternatively other technologies such as Global Positioning System
	(GPS) or Synchronous Ethernet (SyncE) are used [SyncE].	(GPS) or Synchronous Ethernet (SyncE) are used [SyncE].

	Both Ethernet and IP/MPLS [RFC3031] (and PseudoWires (PWE) [RFC3985]	Both Ethernet and IP/MPLS [RFC3031] (and PseudoWires (PWE) [RFC3985]
	for legacy transport support) have become popular tools to build and	for legacy transport support) have become popular tools to build and
	manage new all-IP Radio Access Networks (RANs)	manage new all-IP Radio Access Networks (RANs)
	[I-D.kh-spring-ip-ran-use-case]. Although various timing and	[I-D.kh-spring-ip-ran-use-case]. Although various timing and
	synchronization optimizations have already been proposed and	synchronization optimizations have already been proposed and
	implemented including 1588 PTP enhancements	implemented including 1588 PTP enhancements

	[I-D.ietf-tictoc-1588overmpls] and [I-D.mirsky-mpls-residence-time],	[I-D.ietf-tictoc-1588overmpls] and [I-D.ietf-mpls-residence-time],
	these solution are not necessarily sufficient for the forthcoming RAN	these solution are not necessarily sufficient for the forthcoming RAN
	architectures nor do they guarantee the more stringent time-	architectures nor do they guarantee the more stringent time-
	synchronization requirements such as [CPRI].	synchronization requirements such as [CPRI].

	There are also existing solutions for TDM over IP such as [RFC5087]	There are also existing solutions for TDM over IP such as [RFC5087]
	and [RFC4553], as well as TDM over Ethernet transports such as	and [RFC4553], as well as TDM over Ethernet transports such as
	[RFC5086].	[RFC5086].

	6.3. Cellular Radio Networks Future	6.3. Cellular Radio Networks Future


	skipping to change at page 60, line 45 ¶	skipping to change at page 60, line 45 ¶
	Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,	Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,
	"Terminology in IPv6 over the TSCH mode of IEEE	"Terminology in IPv6 over the TSCH mode of IEEE
	802.15.4e", draft-ietf-6tisch-terminology-06 (work in	802.15.4e", draft-ietf-6tisch-terminology-06 (work in
	progress), November 2015.	progress), November 2015.

	[I-D.ietf-ipv6-multilink-subnets]	[I-D.ietf-ipv6-multilink-subnets]
	Thaler, D. and C. Huitema, "Multi-link Subnet Support in	Thaler, D. and C. Huitema, "Multi-link Subnet Support in
	IPv6", draft-ietf-ipv6-multilink-subnets-00 (work in	IPv6", draft-ietf-ipv6-multilink-subnets-00 (work in
	progress), July 2002.	progress), July 2002.


		[I-D.ietf-mpls-residence-time]
		Mirsky, G., Ruffini, S., Gray, E., Drake, J., Bryant, S.,
		and S. Sasha, "Residence Time Measurement in MPLS
		network", draft-ietf-mpls-residence-time-06 (work in
		progress), March 2016.

	[I-D.ietf-roll-rpl-industrial-applicability]	[I-D.ietf-roll-rpl-industrial-applicability]
	Phinney, T., Thubert, P., and R. Assimiti, "RPL	Phinney, T., Thubert, P., and R. Assimiti, "RPL
	applicability in industrial networks", draft-ietf-roll-	applicability in industrial networks", draft-ietf-roll-
	rpl-industrial-applicability-02 (work in progress),	rpl-industrial-applicability-02 (work in progress),
	October 2013.	October 2013.

	[I-D.ietf-tictoc-1588overmpls]	[I-D.ietf-tictoc-1588overmpls]
	Davari, S., Oren, A., Bhatia, M., Roberts, P., and L.	Davari, S., Oren, A., Bhatia, M., Roberts, P., and L.
	Montini, "Transporting Timing messages over MPLS	Montini, "Transporting Timing messages over MPLS
	Networks", draft-ietf-tictoc-1588overmpls-07 (work in	Networks", draft-ietf-tictoc-1588overmpls-07 (work in
	progress), October 2015.	progress), October 2015.

	[I-D.kh-spring-ip-ran-use-case]	[I-D.kh-spring-ip-ran-use-case]
	Khasnabish, B., hu, f., and L. Contreras, "Segment Routing	Khasnabish, B., hu, f., and L. Contreras, "Segment Routing
	in IP RAN use case", draft-kh-spring-ip-ran-use-case-02	in IP RAN use case", draft-kh-spring-ip-ran-use-case-02
	(work in progress), November 2014.	(work in progress), November 2014.


	[I-D.mirsky-mpls-residence-time]
	Mirsky, G., Ruffini, S., Gray, E., Drake, J., Bryant, S.,
	and S. Vainshtein, "Residence Time Measurement in MPLS
	network", draft-mirsky-mpls-residence-time-07 (work in
	progress), July 2015.

	[I-D.svshah-tsvwg-deterministic-forwarding]	[I-D.svshah-tsvwg-deterministic-forwarding]
	Shah, S. and P. Thubert, "Deterministic Forwarding PHB",	Shah, S. and P. Thubert, "Deterministic Forwarding PHB",
	draft-svshah-tsvwg-deterministic-forwarding-04 (work in	draft-svshah-tsvwg-deterministic-forwarding-04 (work in
	progress), August 2015.	progress), August 2015.

	[I-D.thubert-6lowpan-backbone-router]	[I-D.thubert-6lowpan-backbone-router]
	Thubert, P., "6LoWPAN Backbone Router", draft-thubert-	Thubert, P., "6LoWPAN Backbone Router", draft-thubert-
	6lowpan-backbone-router-03 (work in progress), February	6lowpan-backbone-router-03 (work in progress), February
	2013.	2013.


End of changes. 10 change blocks.
	16 lines changed or deleted	16 lines changed or added
This html diff was produced by rfcdiff 1.44. The latest version is available from http://tools.ietf.org/tools/rfcdiff/