Liaison from IEEE 802.1 - Deterministic Networking
Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
|From Contact||Glenn Parsons|
|To Contacts||The IETF Chair <email@example.com>|
|Cc||The IESG <firstname.lastname@example.org>
Eric Gray <Eric.Gray@Ericsson.com>
At 8:00 PM on Wednesday, July 23, at IETF90 in Toronto, there will be a side meeting (aka Bar BOF — see RFC6771) on the subject of Deterministic Networking in the Quebec room. IEEE 802.1 wishes to encourage your cooperation and/or participation. Over the past few years, the IEEE 802 Audio Video Bridging Task Group and it successor, the Time-Sensitive Networking TG, have released standards that define: 1. Protocols for the reservation, by end stations, of Layer 2 network resources for critical flows; 2. Specific data plane mechanisms for a Layer 2 network to guarantee 0 congestion loss, and consequently, a known finite end-to-end latency, for those reserved flows; and 3. Plug-and-play distribution of the Precision Time Protocol (IEEE 1588 PTP) over bridged, routed, or mixed networks. These standards were originally targeted for the transport of raw audio and video streams. The successful deployment of multi-vendor networks employing these standards has triggered interest from new market segments, including industrial, vehicular, and other real-time systems. As a consequence, the IEEE 802.1 Time-Sensitive Networking Task Group has number of projects in progress to expand the first-round capabilities. This success has also made clear that the users of these capabilities have networking needs that transcend the limitations imposed by networks that operate at only Layer 2. The following elements are essential to expand the current Time-Sensitive Networking TG’s standards into “Deterministic Networking”: A. Deterministic Networking has to be a QoS feature of standard networks, not a set of point features around which one could write an Application. B. The networks of interest contain a mixture of bridges and routers. The QoS features have to be supported regardless of Layer 2 / Layer 3 boundaries. The control protocols must be visible to both routers and bridges; every box along the path must reserve resources. C. The host making the reservations must not care whether the first box to which it is connected is a bridge or a router, or what suite of protocols is used by the network to support its reservations. A number of members of IEEE 802.1 believe that the models for information propagation used by the Path Computation Element, RSVP, RSVP-TE, PCEP, and/or segment routing are a superset of that used by the existing and planned work by the 802.1 TSN WG, and offer a model for a combined Layer 2 / Layer 3, IEEE / IETF, effort. We hope that the Deterministic Networking side meeting can be used by the participants to test the waters, and see whether there is interest in working on the above problems. -- Glenn Parsons - Chair, IEEE 802.1 email@example.com +1-613-963-8141