< draft-ietf-detnet-architecture-12.txt   draft-ietf-detnet-architecture-13.txt >
DetNet N. Finn DetNet N. Finn
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track P. Thubert Intended status: Standards Track P. Thubert
Expires: September 10, 2019 Cisco Expires: November 7, 2019 Cisco
B. Varga B. Varga
J. Farkas J. Farkas
Ericsson Ericsson
March 9, 2019 May 6, 2019
Deterministic Networking Architecture Deterministic Networking Architecture
draft-ietf-detnet-architecture-12 draft-ietf-detnet-architecture-13
Abstract Abstract
This document provides the overall architecture for Deterministic This document provides the overall architecture for Deterministic
Networking (DetNet), which provides a capability to carry specified Networking (DetNet), which provides a capability to carry specified
unicast or multicast data flows for real-time applications with unicast or multicast data flows for real-time applications with
extremely low data loss rates and bounded latency within a network extremely low data loss rates and bounded latency within a network
domain. Techniques used include: 1) reserving data plane resources domain. Techniques used include: 1) reserving data plane resources
for individual (or aggregated) DetNet flows in some or all of the for individual (or aggregated) DetNet flows in some or all of the
intermediate nodes along the path of the flow; 2) providing explicit intermediate nodes along the path of the flow; 2) providing explicit
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 September 10, 2019. This Internet-Draft will expire on November 7, 2019.
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/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 3, line 20 skipping to change at page 3, line 20
4.7.1. Exporting flow identification . . . . . . . . . . . . 32 4.7.1. Exporting flow identification . . . . . . . . . . . . 32
4.7.2. Flow attribute mapping between layers . . . . . . . . 34 4.7.2. Flow attribute mapping between layers . . . . . . . . 34
4.7.3. Flow-ID mapping examples . . . . . . . . . . . . . . 35 4.7.3. Flow-ID mapping examples . . . . . . . . . . . . . . 35
4.8. Advertising resources, capabilities and adjacencies . . . 36 4.8. Advertising resources, capabilities and adjacencies . . . 36
4.9. Scaling to larger networks . . . . . . . . . . . . . . . 37 4.9. Scaling to larger networks . . . . . . . . . . . . . . . 37
4.10. Compatibility with Layer-2 . . . . . . . . . . . . . . . 37 4.10. Compatibility with Layer-2 . . . . . . . . . . . . . . . 37
5. Security Considerations . . . . . . . . . . . . . . . . . . . 37 5. Security Considerations . . . . . . . . . . . . . . . . . . . 37
6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 39 6. Privacy Considerations . . . . . . . . . . . . . . . . . . . 39
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 39
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
9. Informative References . . . . . . . . . . . . . . . . . . . 40 9. Informative References . . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44
1. Introduction 1. Introduction
This document provides the overall architecture for Deterministic This document provides the overall architecture for Deterministic
Networking (DetNet), which provides a capability for the delivery of Networking (DetNet), which provides a capability for the delivery of
data flows with extremely low packet loss rates and bounded end-to- data flows with extremely low packet loss rates and bounded end-to-
end delivery latency. DetNet is for networks that are under a single end delivery latency. DetNet is for networks that are under a single
administrative control or within a closed group of administrative administrative control or within a closed group of administrative
control; these include campus-wide networks and private WANs. DetNet control; these include campus-wide networks and private WANs. DetNet
skipping to change at page 17, line 15 skipping to change at page 17, line 15
The mechanisms to support these requirements are both data plane and The mechanisms to support these requirements are both data plane and
implementation specific. Data plane specific solutions will be implementation specific. Data plane specific solutions will be
specified in the relevant data plane solution document. There also specified in the relevant data plane solution document. There also
exist techniques, at present and/or in various stages of exist techniques, at present and/or in various stages of
standardization, that can support these fault mitigation tasks that standardization, that can support these fault mitigation tasks that
deliver a high probability that misbehaving systems will have zero deliver a high probability that misbehaving systems will have zero
impact on well-behaved DetNet flows, except of course, for the impact on well-behaved DetNet flows, except of course, for the
receiving interface(s) immediately downstream of the misbehaving receiving interface(s) immediately downstream of the misbehaving
device. Examples of such techniques include traffic policing and device. Examples of such techniques include traffic policing and
shaping functions (e.g., [RFC2475]) and separating flows into per- shaping functions (e.g., [RFC2475]) and separating flows into per-
flow rate-limited queues. flow rate-limited queues, and potentially apply active queue
management [RFC7567].
4. DetNet Architecture 4. DetNet Architecture
4.1. DetNet stack model 4.1. DetNet stack model
DetNet functionality (Section 3) is implemented in two adjacent sub- DetNet functionality (Section 3) is implemented in two adjacent sub-
layers in the protocol stack: the DetNet service sub-layer and the layers in the protocol stack: the DetNet service sub-layer and the
DetNet forwarding sub-layer. The DetNet service sub-layer provides DetNet forwarding sub-layer. The DetNet service sub-layer provides
DetNet service, e.g., service protection, to higher layers in the DetNet service, e.g., service protection, to higher layers in the
protocol stack and applications. The DetNet forwarding sub-layer protocol stack and applications. The DetNet forwarding sub-layer
skipping to change at page 39, line 24 skipping to change at page 39, line 24
requirements. The intent of this section is to provide a baseline requirements. The intent of this section is to provide a baseline
for security considerations which are common to all DetNet designs for security considerations which are common to all DetNet designs
and implementations, without burdening individual designs with and implementations, without burdening individual designs with
specifics of security infrastructure which may not be germane to the specifics of security infrastructure which may not be germane to the
given use case. Designers and implementers of DetNet systems are given use case. Designers and implementers of DetNet systems are
expected to take use case specific considerations into account in expected to take use case specific considerations into account in
their DetNet designs and implementations. their DetNet designs and implementations.
6. Privacy Considerations 6. Privacy Considerations
DetNet provides a Quality of Service (QoS), and as such, is not DetNet provides a Quality of Service (QoS), and the generic
expected to directly raise any new privacy considerations, the considerations for such mechanisms apply. In particular, such
generic considerations for such mechanisms apply. In particular, markings allow for an attacker to correlate flows or to select
such markings allow for an attacker to correlate flows or to select
particular types of flow for more detailed inspection. particular types of flow for more detailed inspection.
However, the requirement for every (or almost every) node along the However, the requirement for every (or almost every) node along the
path of a DetNet flow to identify DetNet flows may present an path of a DetNet flow to identify DetNet flows may present an
additional attack surface for privacy, should the DetNet paradigm be additional attack surface for privacy, should the DetNet paradigm be
found useful in broader environments. found useful in broader environments.
7. IANA Considerations 7. IANA Considerations
This document does not require an action from IANA. This document does not require an action from IANA.
skipping to change at page 40, line 22 skipping to change at page 40, line 16
Group", Group",
<https://datatracker.ietf.org/doc/charter-ietf-ccamp/>. <https://datatracker.ietf.org/doc/charter-ietf-ccamp/>.
[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-20 (work of IEEE 802.15.4", draft-ietf-6tisch-architecture-20 (work
in progress), March 2019. in progress), March 2019.
[I-D.ietf-detnet-dp-sol-ip] [I-D.ietf-detnet-dp-sol-ip]
Korhonen, J. and B. Varga, "DetNet IP Data Plane Korhonen, J. and B. Varga, "DetNet IP Data Plane
Encapsulation", draft-ietf-detnet-dp-sol-ip-01 (work in Encapsulation", draft-ietf-detnet-dp-sol-ip-02 (work in
progress), October 2018. progress), March 2019.
[I-D.ietf-detnet-dp-sol-mpls] [I-D.ietf-detnet-dp-sol-mpls]
Korhonen, J. and B. Varga, "DetNet MPLS Data Plane Korhonen, J. and B. Varga, "DetNet MPLS Data Plane
Encapsulation", draft-ietf-detnet-dp-sol-mpls-01 (work in Encapsulation", draft-ietf-detnet-dp-sol-mpls-02 (work in
progress), October 2018. progress), March 2019.
[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-09 (work Statement", draft-ietf-detnet-problem-statement-09 (work
in progress), December 2018. in progress), December 2018.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell,
J., Austad, H., Stanton, K., and N. Finn, "Deterministic J., Austad, H., Stanton, K., and N. Finn, "Deterministic
Networking (DetNet) Security Considerations", draft-ietf- Networking (DetNet) Security Considerations", draft-ietf-
skipping to change at page 43, line 41 skipping to change at page 43, line 36
Defined Networking (SDN): Layers and Architecture Defined Networking (SDN): Layers and Architecture
Terminology", RFC 7426, DOI 10.17487/RFC7426, January Terminology", RFC 7426, DOI 10.17487/RFC7426, January
2015, <https://www.rfc-editor.org/info/rfc7426>. 2015, <https://www.rfc-editor.org/info/rfc7426>.
[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>.
[RFC7567] Baker, F., Ed. and G. Fairhurst, Ed., "IETF
Recommendations Regarding Active Queue Management",
BCP 197, RFC 7567, DOI 10.17487/RFC7567, July 2015,
<https://www.rfc-editor.org/info/rfc7567>.
[RFC7813] Farkas, J., Ed., Bragg, N., Unbehagen, P., Parsons, G., [RFC7813] Farkas, J., Ed., Bragg, N., Unbehagen, P., Parsons, G.,
Ashwood-Smith, P., and C. Bowers, "IS-IS Path Control and Ashwood-Smith, P., and C. Bowers, "IS-IS Path Control and
Reservation", RFC 7813, DOI 10.17487/RFC7813, June 2016, Reservation", RFC 7813, DOI 10.17487/RFC7813, June 2016,
<https://www.rfc-editor.org/info/rfc7813>. <https://www.rfc-editor.org/info/rfc7813>.
[RFC8033] Pan, R., Natarajan, P., Baker, F., and G. White, [RFC8033] Pan, R., Natarajan, P., Baker, F., and G. White,
"Proportional Integral Controller Enhanced (PIE): A "Proportional Integral Controller Enhanced (PIE): A
Lightweight Control Scheme to Address the Bufferbloat Lightweight Control Scheme to Address the Bufferbloat
Problem", RFC 8033, DOI 10.17487/RFC8033, February 2017, Problem", RFC 8033, DOI 10.17487/RFC8033, February 2017,
<https://www.rfc-editor.org/info/rfc8033>. <https://www.rfc-editor.org/info/rfc8033>.
 End of changes. 10 change blocks. 
14 lines changed or deleted 19 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/