draft-ietf-detnet-use-cases-17.txt   draft-ietf-detnet-use-cases-18.txt 
Internet Engineering Task Force E. Grossman, Ed. Internet Engineering Task Force E. Grossman, Ed.
Internet-Draft DOLBY Internet-Draft DOLBY
Intended status: Informational June 26, 2018 Intended status: Informational September 17, 2018
Expires: December 28, 2018 Expires: March 21, 2019
Deterministic Networking Use Cases Deterministic Networking Use Cases
draft-ietf-detnet-use-cases-17 draft-ietf-detnet-use-cases-18
Abstract Abstract
This draft documents requirements in several diverse industries to This draft documents use cases 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 flows can be properties. In this context deterministic implies that flows can be
established which provide guaranteed bandwidth and latency which can established which provide guaranteed bandwidth and latency which can
be established from either a Layer 2 or Layer 3 (IP) interface, and 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. which can co-exist on an IP network with best-effort traffic.
Additional requirements include optional redundant paths, very high Additional use case properties include optional redundant paths, very
reliability paths, time synchronization, and clock distribution. high reliability paths, time synchronization, and clock distribution.
Industries considered include professional audio, electrical Industries considered include professional audio, electrical
utilities, building automation systems, wireless for industrial, utilities, building automation systems, wireless for industrial,
cellular radio, industrial machine-to-machine, mining, private cellular radio, industrial machine-to-machine, mining, private
blockchain, and network slicing. blockchain, and network slicing.
For each case, this document will identify the application, identify For each case, this document will identify the application, identify
representative solutions used today, and the improvements IETF DetNet representative solutions used today, and the improvements IETF DetNet
solutions may enable. solutions may enable.
Status of This Memo Status of This Memo
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 December 28, 2018. This Internet-Draft will expire on March 21, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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/license-info) in effect on the date of (https://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 2, line 35 skipping to change at page 2, line 35
2.1.1. Uninterrupted Stream Playback . . . . . . . . . . . . 7 2.1.1. Uninterrupted Stream Playback . . . . . . . . . . . . 7
2.1.2. Synchronized Stream Playback . . . . . . . . . . . . 7 2.1.2. Synchronized Stream Playback . . . . . . . . . . . . 7
2.1.3. Sound Reinforcement . . . . . . . . . . . . . . . . . 8 2.1.3. Sound Reinforcement . . . . . . . . . . . . . . . . . 8
2.1.4. Deterministic Time to Establish Streaming . . . . . . 8 2.1.4. Deterministic Time to Establish Streaming . . . . . . 8
2.1.5. Secure Transmission . . . . . . . . . . . . . . . . . 8 2.1.5. Secure Transmission . . . . . . . . . . . . . . . . . 8
2.1.5.1. Safety . . . . . . . . . . . . . . . . . . . . . 8 2.1.5.1. Safety . . . . . . . . . . . . . . . . . . . . . 8
2.2. Pro Audio Today . . . . . . . . . . . . . . . . . . . . . 9 2.2. Pro Audio Today . . . . . . . . . . . . . . . . . . . . . 9
2.3. Pro Audio Future . . . . . . . . . . . . . . . . . . . . 9 2.3. Pro Audio Future . . . . . . . . . . . . . . . . . . . . 9
2.3.1. Layer 3 Interconnecting Layer 2 Islands . . . . . . . 9 2.3.1. Layer 3 Interconnecting Layer 2 Islands . . . . . . . 9
2.3.2. High Reliability Stream Paths . . . . . . . . . . . . 9 2.3.2. High Reliability Stream Paths . . . . . . . . . . . . 9
2.3.3. Integration of Reserved Streams into IT Networks . . 9 2.3.3. Integration of Reserved Streams into IT Networks . . 10
2.3.4. Use of Unused Reservations by Best-Effort Traffic . . 10 2.3.4. Use of Unused Reservations by Best-Effort Traffic . . 10
2.3.5. Traffic Segregation . . . . . . . . . . . . . . . . . 10 2.3.5. Traffic Segregation . . . . . . . . . . . . . . . . . 10
2.3.5.1. Packet Forwarding Rules, VLANs and Subnets . . . 10 2.3.5.1. Packet Forwarding Rules, VLANs and Subnets . . . 11
2.3.5.2. Multicast Addressing (IPv4 and IPv6) . . . . . . 11 2.3.5.2. Multicast Addressing (IPv4 and IPv6) . . . . . . 11
2.3.6. Latency Optimization by a Central Controller . . . . 11 2.3.6. Latency Optimization by a Central Controller . . . . 11
2.3.7. Reduced Device Cost Due To Reduced Buffer Memory . . 11 2.3.7. Reduced Device Cost Due To Reduced Buffer Memory . . 11
2.4. Pro Audio Asks . . . . . . . . . . . . . . . . . . . . . 12 2.4. Pro Audio Asks . . . . . . . . . . . . . . . . . . . . . 12
3. Electrical Utilities . . . . . . . . . . . . . . . . . . . . 12 3. Electrical Utilities . . . . . . . . . . . . . . . . . . . . 12
3.1. Use Case Description . . . . . . . . . . . . . . . . . . 12 3.1. Use Case Description . . . . . . . . . . . . . . . . . . 12
3.1.1. Transmission Use Cases . . . . . . . . . . . . . . . 12 3.1.1. Transmission Use Cases . . . . . . . . . . . . . . . 12
3.1.1.1. Protection . . . . . . . . . . . . . . . . . . . 12 3.1.1.1. Protection . . . . . . . . . . . . . . . . . . . 13
3.1.1.2. Intra-Substation Process Bus Communications . . . 18 3.1.1.2. Intra-Substation Process Bus Communications . . . 18
3.1.1.3. Wide Area Monitoring and Control Systems . . . . 19 3.1.1.3. Wide Area Monitoring and Control Systems . . . . 19
3.1.1.4. IEC 61850 WAN engineering guidelines requirement 3.1.1.4. IEC 61850 WAN engineering guidelines requirement
classification . . . . . . . . . . . . . . . . . 20 classification . . . . . . . . . . . . . . . . . 20
3.1.2. Generation Use Case . . . . . . . . . . . . . . . . . 21 3.1.2. Generation Use Case . . . . . . . . . . . . . . . . . 21
3.1.2.1. Control of the Generated Power . . . . . . . . . 21 3.1.2.1. Control of the Generated Power . . . . . . . . . 21
3.1.2.2. Control of the Generation Infrastructure . . . . 22 3.1.2.2. Control of the Generation Infrastructure . . . . 22
3.1.3. Distribution use case . . . . . . . . . . . . . . . . 27 3.1.3. Distribution use case . . . . . . . . . . . . . . . . 27
3.1.3.1. Fault Location Isolation and Service Restoration 3.1.3.1. Fault Location Isolation and Service Restoration
(FLISR) . . . . . . . . . . . . . . . . . . . . . 27 (FLISR) . . . . . . . . . . . . . . . . . . . . . 27
skipping to change at page 5, line 38 skipping to change at page 5, line 38
14.2. Utility Telecom . . . . . . . . . . . . . . . . . . . . 78 14.2. Utility Telecom . . . . . . . . . . . . . . . . . . . . 78
14.3. Building Automation Systems . . . . . . . . . . . . . . 78 14.3. Building Automation Systems . . . . . . . . . . . . . . 78
14.4. Wireless for Industrial . . . . . . . . . . . . . . . . 78 14.4. Wireless for Industrial . . . . . . . . . . . . . . . . 78
14.5. Cellular Radio . . . . . . . . . . . . . . . . . . . . . 78 14.5. Cellular Radio . . . . . . . . . . . . . . . . . . . . . 78
14.6. Industrial M2M . . . . . . . . . . . . . . . . . . . . . 79 14.6. Industrial M2M . . . . . . . . . . . . . . . . . . . . . 79
14.7. Internet Applications and CoMP . . . . . . . . . . . . . 79 14.7. Internet Applications and CoMP . . . . . . . . . . . . . 79
14.8. Electrical Utilities . . . . . . . . . . . . . . . . . . 79 14.8. Electrical Utilities . . . . . . . . . . . . . . . . . . 79
14.9. Network Slicing . . . . . . . . . . . . . . . . . . . . 79 14.9. Network Slicing . . . . . . . . . . . . . . . . . . . . 79
14.10. Mining . . . . . . . . . . . . . . . . . . . . . . . . . 79 14.10. Mining . . . . . . . . . . . . . . . . . . . . . . . . . 79
14.11. Private Blockchain . . . . . . . . . . . . . . . . . . . 79 14.11. Private Blockchain . . . . . . . . . . . . . . . . . . . 79
15. Informative References . . . . . . . . . . . . . . . . . . . 79 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 79
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 90 16. Informative References . . . . . . . . . . . . . . . . . . . 79
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 86
1. Introduction 1. Introduction
This draft presents use cases from diverse industries which have in This draft presents use cases from diverse industries which have in
common a need for deterministic flows, but which also differ notably common a need for deterministic flows, but which also differ notably
in their network topologies and specific desired behavior. Together, in their network topologies and specific desired behavior. Together,
they provide broad industry context for DetNet and a yardstick they provide broad industry context for DetNet and a yardstick
against which proposed DetNet designs can be measured (to what extent against which proposed DetNet designs can be measured (to what extent
does a proposed design satisfy these various use cases?) does a proposed design satisfy these various use cases?)
skipping to change at page 8, line 32 skipping to change at page 8, line 33
Note that the 15ms latency bound includes all parts of the signal Note that the 15ms latency bound includes all parts of the signal
path, not just the network, so the network latency must be path, not just the network, so the network latency must be
significantly less than 15ms. significantly less than 15ms.
In some cases local performers must perform in synchrony with a In some cases local performers must perform in synchrony with a
remote broadcast. In such cases the latencies of the broadcast remote broadcast. In such cases the latencies of the broadcast
stream and the local performer must be adjusted to match each other, stream and the local performer must be adjusted to match each other,
with a worst case of one video frame (33ms for NTSC video). with a worst case of one video frame (33ms for NTSC video).
In cases where audio phase is a consideration, for example beam- In cases where audio phase is a consideration, for example beam-
forming using multiple speakers, latency requirements can be in the forming using multiple speakers, latency can be in the 10 microsecond
10 microsecond range (1 audio sample at 96kHz). range (1 audio sample at 96kHz).
2.1.4. Deterministic Time to Establish Streaming 2.1.4. Deterministic Time to Establish Streaming
Note: The WG has decided that guidelines for deterministic time to Note: The WG has decided that guidelines for deterministic time to
establish stream startup is not within scope of DetNet. If bounded establish stream startup is not within scope of DetNet. If bounded
timing of establishing or re-establish streams is required in a given timing of establishing or re-establish streams is required in a given
use case, it is up to the application/system to achieve this. (The use case, it is up to the application/system to achieve this. (The
supporting text from this section has been removed as of draft 12). supporting text from this section has been removed as of draft 12).
2.1.5. Secure Transmission 2.1.5. Secure Transmission
skipping to change at page 10, line 28 skipping to change at page 10, line 34
as file transfers. as file transfers.
This also addresses a concern of IT network administrators that are This also addresses a concern of IT network administrators that are
considering adding reserved bandwidth traffic to their networks that considering adding reserved bandwidth traffic to their networks that
("users will reserve large quantities of bandwidth and then never un- ("users will reserve large quantities of bandwidth and then never un-
reserve it even though they are not using it, and soon the network reserve it even though they are not using it, and soon the network
will have no bandwidth left"). will have no bandwidth left").
2.3.5. Traffic Segregation 2.3.5. Traffic Segregation
Note: It is still under WG discussion whether this topic will be
addressed by DetNet.
Sink devices may be low cost devices with limited processing power. Sink devices may be low cost devices with limited processing power.
In order to not overwhelm the CPUs in these devices it is important In order to not overwhelm the CPUs in these devices it is important
to limit the amount of traffic that these devices must process. to limit the amount of traffic that these devices must process.
As an example, consider the use of individual seat speakers in a As an example, consider the use of individual seat speakers in a
cinema. These speakers are typically required to be cost reduced cinema. These speakers are typically required to be cost reduced
since the quantities in a single theater can reach hundreds of seats. since the quantities in a single theater can reach hundreds of seats.
Discovery protocols alone in a one thousand seat theater can generate Discovery protocols alone in a one thousand seat theater can generate
enough broadcast traffic to overwhelm a low powered CPU. Thus an enough broadcast traffic to overwhelm a low powered CPU. Thus an
installation like this will benefit greatly from some type of traffic installation like this will benefit greatly from some type of traffic
segregation that can define groups of seats to reduce traffic within segregation that can define groups of seats to reduce traffic within
each group. All seats in the theater must still be able to each group. All seats in the theater must still be able to
communicate with a central controller. communicate with a central controller.
There are many techniques that can be used to support this There are many techniques that can be used to support this feature
requirement including (but not limited to) the following examples. including (but not limited to) the following examples.
2.3.5.1. Packet Forwarding Rules, VLANs and Subnets 2.3.5.1. Packet Forwarding Rules, VLANs and Subnets
Packet forwarding rules can be used to eliminate some extraneous Packet forwarding rules can be used to eliminate some extraneous
streaming traffic from reaching potentially low powered sink devices, streaming traffic from reaching potentially low powered sink devices,
however there may be other types of broadcast traffic that should be however there may be other types of broadcast traffic that should be
eliminated using other means for example VLANs or IP subnets. eliminated using other means for example VLANs or IP subnets.
2.3.5.2. Multicast Addressing (IPv4 and IPv6) 2.3.5.2. Multicast Addressing (IPv4 and IPv6)
skipping to change at page 11, line 23 skipping to change at page 11, line 28
important that a multicast MAC address is only associated with one important that a multicast MAC address is only associated with one
stream. This will prevent reservations from forwarding packets from stream. This will prevent reservations from forwarding packets from
one stream down a path that has no interested sinks simply because one stream down a path that has no interested sinks simply because
there is another stream on that same path that shares the same there is another stream on that same path that shares the same
multicast MAC address. multicast MAC address.
Since each multicast MAC Address can represent 32 different IPv4 Since each multicast MAC Address can represent 32 different IPv4
multicast addresses there must be a process put in place to make sure multicast addresses there must be a process put in place to make sure
this does not occur. Requiring use of IPv6 address can achieve this, this does not occur. Requiring use of IPv6 address can achieve this,
however due to their continued prevalence, solutions that are however due to their continued prevalence, solutions that are
effective for IPv4 installations are also required. effective for IPv4 installations are also desirable.
2.3.6. Latency Optimization by a Central Controller 2.3.6. Latency Optimization by a Central Controller
A central network controller might also perform optimizations based A central network controller might also perform optimizations based
on the individual path delays, for example sinks that are closer to on the individual path delays, for example sinks that are closer to
the source can inform the controller that they can accept greater the source can inform the controller that they can accept greater
latency since they will be buffering packets to match presentation latency since they will be buffering packets to match presentation
times of farther away sinks. The controller might then move a stream times of farther away sinks. The controller might then move a stream
reservation on a short path to a longer path in order to free up reservation on a short path to a longer path in order to free up
bandwidth for other critical streams on that short path. See slides bandwidth for other critical streams on that short path. See slides
skipping to change at page 55, line 47 skipping to change at page 55, line 47
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.ietf-mpls-residence-time], [I-D.ietf-tictoc-1588overmpls] and [RFC8169], these solution are not
these solution are not necessarily sufficient for the forthcoming RAN necessarily sufficient for the forthcoming RAN architectures nor do
architectures nor do they guarantee the more stringent time- they guarantee the more stringent time-synchronization requirements
synchronization requirements such as [CPRI]. such as [CPRI].
There are also existing solutions for TDM over IP such as [RFC4553], There are also existing solutions for TDM over IP such as [RFC4553],
[RFC5086], and [RFC5087], as well as TDM over Ethernet transports [RFC5086], and [RFC5087], as well as TDM over Ethernet transports
such as [MEF8]. such as [MEF8].
6.3. Cellular Radio Networks Future 6.3. Cellular Radio Networks Future
Future Cellular Radio Networks will be based on a mix of different Future Cellular Radio Networks will be based on a mix of different
xHaul networks (xHaul = front-, mid- and backhaul), and future xHaul networks (xHaul = front-, mid- and backhaul), and future
transport networks should be able to support all of them transport networks should be able to support all of them
skipping to change at page 79, line 41 skipping to change at page 79, line 41
14.10. Mining 14.10. Mining
This section was written by Diego Dujovne in conjunction with Xavier This section was written by Diego Dujovne in conjunction with Xavier
Vilasojana. Vilasojana.
14.11. Private Blockchain 14.11. Private Blockchain
This section was written by Daniel Huang. This section was written by Daniel Huang.
15. Informative References 15. IANA Considerations
[ACE] IETF, "Authentication and Authorization for Constrained This memo includes no requests from IANA.
Environments",
<https://datatracker.ietf.org/doc/charter-ietf-ace/>. 16. Informative References
[Ahm14] Ahmed, M. and R. Kim, "Communication network architectures [Ahm14] Ahmed, M. and R. Kim, "Communication network architectures
for smart-wind power farms.", Energies, p. 3900-3921. , for smart-wind power farms.", Energies, p. 3900-3921. ,
June 2014. June 2014.
[bacnetip] [bacnetip]
ASHRAE, "Annex J to ANSI/ASHRAE 135-1995 - BACnet/IP", ASHRAE, "Annex J to ANSI/ASHRAE 135-1995 - BACnet/IP",
January 1999. January 1999.
[CCAMP] IETF, "Common Control and Measurement Plane",
<https://datatracker.ietf.org/doc/charter-ietf-ccamp/>.
[CoMP] NGMN Alliance, "RAN EVOLUTION PROJECT COMP EVALUATION AND [CoMP] NGMN Alliance, "RAN EVOLUTION PROJECT COMP EVALUATION AND
ENHANCEMENT", NGMN Alliance NGMN_RANEV_D3_CoMP_Evaluation_ ENHANCEMENT", NGMN Alliance NGMN_RANEV_D3_CoMP_Evaluation_
and_Enhancement_v2.0, March 2015, and_Enhancement_v2.0, March 2015,
<https://www.ngmn.org/uploads/media/ <https://www.ngmn.org/uploads/media/
NGMN_RANEV_D3_CoMP_Evaluation_and_Enhancement_v2.0.pdf>. NGMN_RANEV_D3_CoMP_Evaluation_and_Enhancement_v2.0.pdf>.
[CONTENT_PROTECTION] [CONTENT_PROTECTION]
Olsen, D., "1722a Content Protection", 2012, Olsen, D., "1722a Content Protection", 2012,
<http://grouper.ieee.org/groups/1722/contributions/2012/ <http://grouper.ieee.org/groups/1722/contributions/2012/
avtp_dolsen_1722a_content_protection.pdf>. avtp_dolsen_1722a_content_protection.pdf>.
[CPRI] CPRI Cooperation, "Common Public Radio Interface (CPRI); [CPRI] CPRI Cooperation, "Common Public Radio Interface (CPRI);
Interface Specification", CPRI Specification V6.1, July Interface Specification", CPRI Specification V6.1, July
2014, <http://www.cpri.info/downloads/ 2014, <http://www.cpri.info/downloads/
CPRI_v_6_1_2014-07-01.pdf>. CPRI_v_6_1_2014-07-01.pdf>.
[CPRI-transp]
CPRI TWG, "CPRI requirements for Ethernet Fronthaul",
November 2015,
<http://www.ieee802.org/1/files/public/docs2015/
cm-CPRI-requirements-1115-v01.pdf>.
[DCI] Digital Cinema Initiatives, LLC, "DCI Specification, [DCI] Digital Cinema Initiatives, LLC, "DCI Specification,
Version 1.2", 2012, <http://www.dcimovies.com/>. Version 1.2", 2012, <http://www.dcimovies.com/>.
[DICE] IETF, "DTLS In Constrained Environments",
<https://datatracker.ietf.org/doc/charter-ietf-dice/>.
[EA12] Evans, P. and M. Annunziata, "Industrial Internet: Pushing
the Boundaries of Minds and Machines", November 2012.
[eCPRI] IEEE Standards Association, "Common Public Radio [eCPRI] IEEE Standards Association, "Common Public Radio
Interface, "Common Public Radio Interface: eCPRI Interface Interface, "Common Public Radio Interface: eCPRI Interface
Specification V1.0", 2017, <http://www.cpri.info/>. Specification V1.0", 2017, <http://www.cpri.info/>.
[ESPN_DC2] [ESPN_DC2]
Daley, D., "ESPN's DC2 Scales AVB Large", 2014, Daley, D., "ESPN's DC2 Scales AVB Large", 2014,
<http://sportsvideo.org/main/blog/2014/06/ <http://sportsvideo.org/main/blog/2014/06/
espns-dc2-scales-avb-large>. espns-dc2-scales-avb-large>.
[flnet] Japan Electrical Manufacturers Association, "JEMA 1479 - [flnet] Japan Electrical Manufacturers Association, "JEMA 1479 -
English Edition", September 2012. English Edition", September 2012.
[Fronthaul] [Fronthaul]
Chen, D. and T. Mustala, "Ethernet Fronthaul Chen, D. and T. Mustala, "Ethernet Fronthaul
Considerations", IEEE 1904.3, February 2015, Considerations", IEEE 1904.3, February 2015,
<http://www.ieee1904.org/3/meeting_archive/2015/02/ <http://www.ieee1904.org/3/meeting_archive/2015/02/
tf3_1502_che n_1a.pdf>. tf3_1502_che n_1a.pdf>.
[HART] www.hartcomm.org, "Highway Addressable remote Transducer,
a group of specifications for industrial process and
control devices administered by the HART Foundation".
[I-D.ietf-6tisch-6top-interface] [I-D.ietf-6tisch-6top-interface]
Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer
(6top) Interface", draft-ietf-6tisch-6top-interface-04 (6top) Interface", draft-ietf-6tisch-6top-interface-04
(work in progress), July 2015. (work in progress), July 2015.
[I-D.ietf-6tisch-architecture] [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-14 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-14 (work
in progress), April 2018. in progress), April 2018.
[I-D.ietf-6tisch-coap] [I-D.ietf-6tisch-coap]
Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and Sudhaakar, R. and P. Zand, "6TiSCH Resource Management and
Interaction using CoAP", draft-ietf-6tisch-coap-03 (work Interaction using CoAP", draft-ietf-6tisch-coap-03 (work
in progress), March 2015. in progress), March 2015.
[I-D.ietf-6tisch-terminology]
Palattella, M., Thubert, P., Watteyne, T., and Q. Wang,
"Terms Used in IPv6 over the TSCH mode of IEEE 802.15.4e",
draft-ietf-6tisch-terminology-10 (work in progress), March
2018.
[I-D.ietf-detnet-architecture] [I-D.ietf-detnet-architecture]
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", draft-ietf-
detnet-architecture-05 (work in progress), May 2018. detnet-architecture-07 (work in progress), August 2018.
[I-D.ietf-detnet-problem-statement] [I-D.ietf-detnet-problem-statement]
Finn, N. and P. Thubert, "Deterministic Networking Problem Finn, N. and P. Thubert, "Deterministic Networking Problem
Statement", draft-ietf-detnet-problem-statement-05 (work Statement", draft-ietf-detnet-problem-statement-06 (work
in progress), June 2018. in progress), July 2018.
[I-D.ietf-ipv6-multilink-subnets]
Thaler, D. and C. Huitema, "Multi-link Subnet Support in
IPv6", draft-ietf-ipv6-multilink-subnets-00 (work in
progress), July 2002.
[I-D.ietf-mpls-residence-time]
Mirsky, G., Ruffini, S., Gray, E., Drake, J., Bryant, S.,
and S. Vainshtein, "Residence Time Measurement in MPLS
network", draft-ietf-mpls-residence-time-15 (work in
progress), March 2017.
[I-D.ietf-roll-rpl-industrial-applicability]
Phinney, T., Thubert, P., and R. Assimiti, "RPL
applicability in industrial networks", draft-ietf-roll-
rpl-industrial-applicability-02 (work in progress),
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.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]
Thubert, P., "6LoWPAN Backbone Router", draft-thubert-
6lowpan-backbone-router-03 (work in progress), February
2013.
[I-D.wang-6tisch-6top-sublayer] [I-D.wang-6tisch-6top-sublayer]
Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer Wang, Q. and X. Vilajosana, "6TiSCH Operation Sublayer
(6top)", draft-wang-6tisch-6top-sublayer-04 (work in (6top)", draft-wang-6tisch-6top-sublayer-04 (work in
progress), November 2015. progress), November 2015.
[IEC-60870-5-104] [IEC-60870-5-104]
International Electrotechnical Commission, "International International Electrotechnical Commission, "International
Standard IEC 60870-5-104: Network access for IEC Standard IEC 60870-5-104: Network access for IEC
60870-5-101 using standard transport profiles", June 2006. 60870-5-101 using standard transport profiles", June 2006.
[IEC61400] [IEC61400]
"International standard 61400-25: Communications for "International standard 61400-25: Communications for
monitoring and control of wind power plants", June 2013. monitoring and control of wind power plants", June 2013.
[IEC61850-90-12]
TC57 WG10, IEC., "IEC 61850-90-12 TR: Communication
networks and systems for power utility automation - Part
90-12: Wide area network engineering guidelines", 2015.
[IEC62439-3:2012]
TC65, IEC., "IEC 62439-3: Industrial communication
networks - High availability automation networks - Part 3:
Parallel Redundancy Protocol (PRP) and High-availability
Seamless Redundancy (HSR)", 2012.
[IEEE1588] [IEEE1588]
IEEE, "IEEE Standard for a Precision Clock Synchronization IEEE, "IEEE Standard for a Precision Clock Synchronization
Protocol for Networked Measurement and Control Systems", Protocol for Networked Measurement and Control Systems",
IEEE Std 1588-2008, 2008, IEEE Std 1588-2008, 2008,
<http://standards.ieee.org/findstds/ <http://standards.ieee.org/findstds/
standard/1588-2008.html>. standard/1588-2008.html>.
[IEEE1646] [IEEE1646]
"Communication Delivery Time Performance Requirements for "Communication Delivery Time Performance Requirements for
Electric Power Substation Automation", IEEE Standard Electric Power Substation Automation", IEEE Standard
skipping to change at page 84, line 28 skipping to change at page 83, line 28
<http://standards.ieee.org/getIEEE802/ <http://standards.ieee.org/getIEEE802/
download/802.1AS-2011.pdf>. download/802.1AS-2011.pdf>.
[IEEE8021CM] [IEEE8021CM]
Farkas, J., "Time-Sensitive Networking for Fronthaul", Farkas, J., "Time-Sensitive Networking for Fronthaul",
Unapproved PAR, PAR for a New IEEE Standard; Unapproved PAR, PAR for a New IEEE Standard;
IEEE P802.1CM, April 2015, IEEE P802.1CM, April 2015,
<http://www.ieee802.org/1/files/public/docs2015/ <http://www.ieee802.org/1/files/public/docs2015/
new-P802-1CM-dr aft-PAR-0515-v02.pdf>. new-P802-1CM-dr aft-PAR-0515-v02.pdf>.
[IEEE8021TSN]
IEEE 802.1, "The charter of the TG is to provide the
specifications that will allow time-synchronized low
latency streaming services through 802 networks.", 2016,
<http://www.ieee802.org/1/pages/tsn.html>.
[IETFDetNet]
IETF, "Charter for IETF DetNet Working Group", 2015,
<https://datatracker.ietf.org/wg/detnet/charter/>.
[ISA100] ISA/ANSI, "ISA100, Wireless Systems for Automation", [ISA100] ISA/ANSI, "ISA100, Wireless Systems for Automation",
<https://www.isa.org/isa100/>. <https://www.isa.org/isa100/>.
[ISA100.11a]
ISA/ANSI, "Wireless Systems for Industrial Automation:
Process Control and Related Applications - ISA100.11a-2011
- IEC 62734", 2011, <http://www.isa.org/Community/
SP100WirelessSystemsforAutomation>.
[ISO7240-16]
ISO, "ISO 7240-16:2007 Fire detection and alarm systems --
Part 16: Sound system control and indicating equipment",
2007, <http://www.iso.org/iso/
catalogue_detail.htm?csnumber=42978>.
[knx] KNX Association, "ISO/IEC 14543-3 - KNX", November 2006. [knx] KNX Association, "ISO/IEC 14543-3 - KNX", November 2006.
[lontalk] ECHELON, "LonTalk(R) Protocol Specification Version 3.0", [lontalk] ECHELON, "LonTalk(R) Protocol Specification Version 3.0",
1994. 1994.
[LTE-Latency]
Johnston, S., "LTE Latency: How does it compare to other
technologies", March 2014,
<http://opensignal.com/blog/2014/03/10/
lte-latency-how-does-it-compare-to-other-technologies>.
[MEF22.1.1] [MEF22.1.1]
MEF, "Mobile Backhaul Phase 2 Amendment 1 -- Small Cells", MEF, "Mobile Backhaul Phase 2 Amendment 1 -- Small Cells",
MEF 22.1.1, July 2014, MEF 22.1.1, July 2014,
<http://www.mef.net/Assets/Technical_Specifications/PDF/ <http://www.mef.net/Assets/Technical_Specifications/PDF/
MEF_22.1.1.pdf>. MEF_22.1.1.pdf>.
[MEF8] MEF, "Implementation Agreement for the Emulation of PDH [MEF8] MEF, "Implementation Agreement for the Emulation of PDH
Circuits over Metro Ethernet Networks", MEF 8, October Circuits over Metro Ethernet Networks", MEF 8, October
2004, 2004,
<https://www.mef.net/Assets/Technical_Specifications/PDF/ <https://www.mef.net/Assets/Technical_Specifications/PDF/
skipping to change at page 85, line 39 skipping to change at page 84, line 11
wireless system", ICT-317669-METIS/D1.1 ICT- wireless system", ICT-317669-METIS/D1.1 ICT-
317669-METIS/D1.1, April 2013, <https://www.metis2020.com/ 317669-METIS/D1.1, April 2013, <https://www.metis2020.com/
wp-content/uploads/deliverables/METIS_D1.1_v1.pdf>. wp-content/uploads/deliverables/METIS_D1.1_v1.pdf>.
[modbus] Modbus Organization, "MODBUS APPLICATION PROTOCOL [modbus] Modbus Organization, "MODBUS APPLICATION PROTOCOL
SPECIFICATION V1.1b", December 2006. SPECIFICATION V1.1b", December 2006.
[MODBUS] Modbus Organization, Inc., "MODBUS Application Protocol [MODBUS] Modbus Organization, Inc., "MODBUS Application Protocol
Specification", Apr 2012. Specification", Apr 2012.
[net5G] Ericsson, "5G Radio Access, Challenges for 2020 and
Beyond", Ericsson white paper wp-5g, June 2013,
<http://www.ericsson.com/res/docs/whitepapers/wp-5g.pdf>.
[NGMN] NGMN Alliance, "5G White Paper", NGMN 5G White Paper v1.0, [NGMN] NGMN Alliance, "5G White Paper", NGMN 5G White Paper v1.0,
February 2015, <https://www.ngmn.org/uploads/media/ February 2015, <https://www.ngmn.org/uploads/media/
NGMN_5G_White_Paper_V1_0.pdf>. NGMN_5G_White_Paper_V1_0.pdf>.
[NGMN-fronth] [NGMN-fronth]
NGMN Alliance, "Fronthaul Requirements for C-RAN", March NGMN Alliance, "Fronthaul Requirements for C-RAN", March
2015, <https://www.ngmn.org/uploads/media/ 2015, <https://www.ngmn.org/uploads/media/
NGMN_RANEV_D1_C-RAN_Fronthaul_Requirements_v1.0.pdf>. NGMN_RANEV_D1_C-RAN_Fronthaul_Requirements_v1.0.pdf>.
[OPCXML] OPC Foundation, "OPC XML-Data Access Specification", Dec [OPCXML] OPC Foundation, "OPC XML-Data Access Specification", Dec
2004. 2004.
[PCE] IETF, "Path Computation Element", [PCE] IETF, "Path Computation Element",
<https://datatracker.ietf.org/doc/charter-ietf-pce/>. <https://datatracker.ietf.org/doc/charter-ietf-pce/>.
[profibus] [profibus]
IEC, "IEC 61158 Type 3 - Profibus DP", January 2001. IEC, "IEC 61158 Type 3 - Profibus DP", January 2001.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <https://www.rfc-editor.org/info/rfc2460>.
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black,
"Definition of the Differentiated Services Field (DS
Field) in the IPv4 and IPv6 Headers", RFC 2474,
DOI 10.17487/RFC2474, December 1998,
<https://www.rfc-editor.org/info/rfc2474>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, Label Switching Architecture", RFC 3031,
DOI 10.17487/RFC3031, January 2001, DOI 10.17487/RFC3031, January 2001,
<https://www.rfc-editor.org/info/rfc3031>. <https://www.rfc-editor.org/info/rfc3031>.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<https://www.rfc-editor.org/info/rfc3209>.
[RFC3393] Demichelis, C. and P. Chimento, "IP Packet Delay Variation
Metric for IP Performance Metrics (IPPM)", RFC 3393,
DOI 10.17487/RFC3393, November 2002,
<https://www.rfc-editor.org/info/rfc3393>.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
DOI 10.17487/RFC3411, December 2002, DOI 10.17487/RFC3411, December 2002,
<https://www.rfc-editor.org/info/rfc3411>. <https://www.rfc-editor.org/info/rfc3411>.
[RFC3444] Pras, A. and J. Schoenwaelder, "On the Difference between
Information Models and Data Models", RFC 3444,
DOI 10.17487/RFC3444, January 2003,
<https://www.rfc-editor.org/info/rfc3444>.
[RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)",
RFC 3972, DOI 10.17487/RFC3972, March 2005,
<https://www.rfc-editor.org/info/rfc3972>.
[RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation [RFC3985] Bryant, S., Ed. and P. Pate, Ed., "Pseudo Wire Emulation
Edge-to-Edge (PWE3) Architecture", RFC 3985, Edge-to-Edge (PWE3) Architecture", RFC 3985,
DOI 10.17487/RFC3985, March 2005, DOI 10.17487/RFC3985, March 2005,
<https://www.rfc-editor.org/info/rfc3985>. <https://www.rfc-editor.org/info/rfc3985>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC4553] Vainshtein, A., Ed. and YJ. Stein, Ed., "Structure- [RFC4553] Vainshtein, A., Ed. and YJ. Stein, Ed., "Structure-
Agnostic Time Division Multiplexing (TDM) over Packet Agnostic Time Division Multiplexing (TDM) over Packet
(SAToP)", RFC 4553, DOI 10.17487/RFC4553, June 2006, (SAToP)", RFC 4553, DOI 10.17487/RFC4553, June 2006,
<https://www.rfc-editor.org/info/rfc4553>. <https://www.rfc-editor.org/info/rfc4553>.
[RFC4903] Thaler, D., "Multi-Link Subnet Issues", RFC 4903,
DOI 10.17487/RFC4903, June 2007,
<https://www.rfc-editor.org/info/rfc4903>.
[RFC4919] Kushalnagar, N., Montenegro, G., and C. Schumacher, "IPv6
over Low-Power Wireless Personal Area Networks (6LoWPANs):
Overview, Assumptions, Problem Statement, and Goals",
RFC 4919, DOI 10.17487/RFC4919, August 2007,
<https://www.rfc-editor.org/info/rfc4919>.
[RFC5086] Vainshtein, A., Ed., Sasson, I., Metz, E., Frost, T., and [RFC5086] Vainshtein, A., Ed., Sasson, I., Metz, E., Frost, T., and
P. Pate, "Structure-Aware Time Division Multiplexed (TDM) P. Pate, "Structure-Aware Time Division Multiplexed (TDM)
Circuit Emulation Service over Packet Switched Network Circuit Emulation Service over Packet Switched Network
(CESoPSN)", RFC 5086, DOI 10.17487/RFC5086, December 2007, (CESoPSN)", RFC 5086, DOI 10.17487/RFC5086, December 2007,
<https://www.rfc-editor.org/info/rfc5086>. <https://www.rfc-editor.org/info/rfc5086>.
[RFC5087] Stein, Y(J)., Shashoua, R., Insler, R., and M. Anavi, [RFC5087] Stein, Y(J)., Shashoua, R., Insler, R., and M. Anavi,
"Time Division Multiplexing over IP (TDMoIP)", RFC 5087, "Time Division Multiplexing over IP (TDMoIP)", RFC 5087,
DOI 10.17487/RFC5087, December 2007, DOI 10.17487/RFC5087, December 2007,
<https://www.rfc-editor.org/info/rfc5087>. <https://www.rfc-editor.org/info/rfc5087>.
[RFC6282] Hui, J., Ed. and P. Thubert, "Compression Format for IPv6
Datagrams over IEEE 802.15.4-Based Networks", RFC 6282,
DOI 10.17487/RFC6282, September 2011,
<https://www.rfc-editor.org/info/rfc6282>.
[RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J., [RFC6550] Winter, T., Ed., Thubert, P., Ed., Brandt, A., Hui, J.,
Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur, Kelsey, R., Levis, P., Pister, K., Struik, R., Vasseur,
JP., and R. Alexander, "RPL: IPv6 Routing Protocol for JP., and R. Alexander, "RPL: IPv6 Routing Protocol for
Low-Power and Lossy Networks", RFC 6550, Low-Power and Lossy Networks", RFC 6550,
DOI 10.17487/RFC6550, March 2012, DOI 10.17487/RFC6550, March 2012,
<https://www.rfc-editor.org/info/rfc6550>. <https://www.rfc-editor.org/info/rfc6550>.
[RFC6551] Vasseur, JP., Ed., Kim, M., Ed., Pister, K., Dejean, N., [RFC6551] Vasseur, JP., Ed., Kim, M., Ed., Pister, K., Dejean, N.,
and D. Barthel, "Routing Metrics Used for Path Calculation and D. Barthel, "Routing Metrics Used for Path Calculation
in Low-Power and Lossy Networks", RFC 6551, in Low-Power and Lossy Networks", RFC 6551,
DOI 10.17487/RFC6551, March 2012, DOI 10.17487/RFC6551, March 2012,
<https://www.rfc-editor.org/info/rfc6551>. <https://www.rfc-editor.org/info/rfc6551>.
[RFC6775] Shelby, Z., Ed., Chakrabarti, S., Nordmark, E., and C.
Bormann, "Neighbor Discovery Optimization for IPv6 over
Low-Power Wireless Personal Area Networks (6LoWPANs)",
RFC 6775, DOI 10.17487/RFC6775, November 2012,
<https://www.rfc-editor.org/info/rfc6775>.
[RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using [RFC7554] Watteyne, T., Ed., Palattella, M., and L. Grieco, "Using
IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the IEEE 802.15.4e Time-Slotted Channel Hopping (TSCH) in the
Internet of Things (IoT): Problem Statement", RFC 7554, Internet of Things (IoT): Problem Statement", RFC 7554,
DOI 10.17487/RFC7554, May 2015, DOI 10.17487/RFC7554, May 2015,
<https://www.rfc-editor.org/info/rfc7554>. <https://www.rfc-editor.org/info/rfc7554>.
[RFC8169] Mirsky, G., Ruffini, S., Gray, E., Drake, J., Bryant, S.,
and A. Vainshtein, "Residence Time Measurement in MPLS
Networks", RFC 8169, DOI 10.17487/RFC8169, May 2017,
<https://www.rfc-editor.org/info/rfc8169>.
[Spe09] Sperotto, A., Sadre, R., Vliet, F., and A. Pras, "A First [Spe09] Sperotto, A., Sadre, R., Vliet, F., and A. Pras, "A First
Look into SCADA Network Traffic", IP Operations and Look into SCADA Network Traffic", IP Operations and
Management, p. 518-521. , June 2009. Management, p. 518-521. , June 2009.
[SRP_LATENCY] [SRP_LATENCY]
Gunther, C., "Specifying SRP Latency", 2014, Gunther, C., "Specifying SRP Latency", 2014,
<http://www.ieee802.org/1/files/public/docs2014/ <http://www.ieee802.org/1/files/public/docs2014/
cc-cgunther-acceptable-latency-0314-v01.pdf>. cc-cgunther-acceptable-latency-0314-v01.pdf>.
[STUDIO_IP]
Mace, G., "IP Networked Studio Infrastructure for
Synchronized & Real-Time Multimedia Transmissions", 2007,
<http://www.ieee802.org/1/files/public/docs2047/
avb-mace-ip-networked-studio-infrastructure-0107.pdf>.
[SyncE] ITU-T, "G.8261 : Timing and synchronization aspects in [SyncE] ITU-T, "G.8261 : Timing and synchronization aspects in
packet networks", Recommendation G.8261, August 2013, packet networks", Recommendation G.8261, August 2013,
<http://www.itu.int/rec/T-REC-G.8261>. <http://www.itu.int/rec/T-REC-G.8261>.
[TEAS] IETF, "Traffic Engineering Architecture and Signaling",
<https://datatracker.ietf.org/doc/charter-ietf-teas/>.
[TR38801] IEEE Standards Association, "3GPP TR 38.801, Technical [TR38801] IEEE Standards Association, "3GPP TR 38.801, Technical
Specification Group Radio Access Network; Study on new Specification Group Radio Access Network; Study on new
radio access technology: Radio access architecture and radio access technology: Radio access architecture and
interfaces (Release 14)", 2017, interfaces (Release 14)", 2017,
<https://portal.3gpp.org/desktopmodules/Specifications/ <https://portal.3gpp.org/desktopmodules/Specifications/
SpecificationDetails.aspx?specificationId=3056>. SpecificationDetails.aspx?specificationId=3056>.
[TS23401] 3GPP, "General Packet Radio Service (GPRS) enhancements [TS23401] 3GPP, "General Packet Radio Service (GPRS) enhancements
for Evolved Universal Terrestrial Radio Access Network for Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access", 3GPP TS 23.401 10.10.0, March 2013. (E-UTRAN) access", 3GPP TS 23.401 10.10.0, March 2013.
skipping to change at page 89, line 40 skipping to change at page 86, line 40
[TS36300] 3GPP, "Evolved Universal Terrestrial Radio Access (E-UTRA) [TS36300] 3GPP, "Evolved Universal Terrestrial Radio Access (E-UTRA)
and Evolved Universal Terrestrial Radio Access Network and Evolved Universal Terrestrial Radio Access Network
(E-UTRAN); Overall description; Stage 2", 3GPP TS 36.300 (E-UTRAN); Overall description; Stage 2", 3GPP TS 36.300
10.11.0, September 2013. 10.11.0, September 2013.
[TSNTG] IEEE Standards Association, "IEEE 802.1 Time-Sensitive [TSNTG] IEEE Standards Association, "IEEE 802.1 Time-Sensitive
Networks Task Group", 2013, Networks Task Group", 2013,
<http://www.IEEE802.org/1/pages/avbridges.html>. <http://www.IEEE802.org/1/pages/avbridges.html>.
[UHD-video]
Holub, P., "Ultra-High Definition Videos and Their
Applications over the Network", The 7th International
Symposium on VICTORIES Project PetrHolub_presentation,
October 2014, <http://www.aist-
victories.org/jp/7th_sympo_ws/PetrHolub_presentation.pdf>.
[WirelessHART] [WirelessHART]
www.hartcomm.org, "Industrial Communication Networks - www.hartcomm.org, "Industrial Communication Networks -
Wireless Communication Network and Communication Profiles Wireless Communication Network and Communication Profiles
- WirelessHART - IEC 62591", 2010. - WirelessHART - IEC 62591", 2010.
Author's Address Author's Address
Ethan Grossman (editor) Ethan Grossman (editor)
Dolby Laboratories, Inc. Dolby Laboratories, Inc.
1275 Market Street 1275 Market Street
San Francisco, CA 94103 San Francisco, CA 94103
USA USA
Phone: +1 415 645 4726 Phone: +1 415 645 4726
Email: ethan.grossman@dolby.com Email: ethan.grossman@dolby.com
URI: http://www.dolby.com URI: http://www.dolby.com
 End of changes. 41 change blocks. 
197 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/