draft-ietf-detnet-ip-over-mpls-05.txt   draft-ietf-detnet-ip-over-mpls-06.txt 
DetNet B. Varga, Ed. DetNet B. Varga, Ed.
Internet-Draft Ericsson Internet-Draft Ericsson
Intended status: Standards Track L. Berger Intended status: Standards Track L. Berger
Expires: August 6, 2020 D. Fedyk Expires: November 7, 2020 D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
A. Malis
Independent
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
J. Korhonen J. Korhonen
February 3, 2020 May 6, 2020
DetNet Data Plane: IP over MPLS DetNet Data Plane: IP over MPLS
draft-ietf-detnet-ip-over-mpls-05 draft-ietf-detnet-ip-over-mpls-06
Abstract Abstract
This document specifies the Deterministic Networking data plane when This document specifies the Deterministic Networking data plane when
operating in an IP over MPLS packet switched network. operating in an IP over MPLS packet switched network.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 38 skipping to change at page 1, line 36
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 August 6, 2020. This Internet-Draft will expire on November 7, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are 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. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Terms Used In This Document . . . . . . . . . . . . . . . 3 2.1. Terms Used In This Document . . . . . . . . . . . . . . . 2
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 4 3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 4
4. IP over DetNet MPLS . . . . . . . . . . . . . . . . . . . . . 5 4. IP over DetNet MPLS . . . . . . . . . . . . . . . . . . . . . 5
4.1. IP Over DetNet MPLS Data Plane Scenarios . . . . . . . . 5 4.1. IP Over DetNet MPLS Data Plane Scenarios . . . . . . . . 5
4.2. DetNet IP over DetNet MPLS Encapsulation . . . . . . . . 6 4.2. DetNet IP over DetNet MPLS Encapsulation . . . . . . . . 7
5. IP over DetNet MPLS Procedures . . . . . . . . . . . . . . . 8 5. IP over DetNet MPLS Procedures . . . . . . . . . . . . . . . 8
5.1. DetNet IP over DetNet MPLS Flow Identification 5.1. DetNet IP over DetNet MPLS Flow Identification
and Aggregation Procedures . . . . . . . . . . . . . . . 8 and Aggregation Procedures . . . . . . . . . . . . . . . 8
5.2. DetNet IP over DetNet MPLS Traffic Treatment Procedures . 8 5.2. DetNet IP over DetNet MPLS Traffic Treatment Procedures . 8
6. Management and Control Information Summary . . . . . . . . . 9 6. Management and Control Information Summary . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative references . . . . . . . . . . . . . . . . . . 11 11.1. Normative references . . . . . . . . . . . . . . . . . . 11
11.2. Informative references . . . . . . . . . . . . . . . . . 11 11.2. Informative references . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
Deterministic Networking (DetNet) is a service that can be offered by Deterministic Networking (DetNet) is a service that can be offered by
a network to DetNet flows. DetNet provides these flows extremely low a network to DetNet flows. DetNet provides these flows extremely low
packet loss rates and assured maximum end-to-end delivery latency. packet loss rates and assured maximum end-to-end delivery latency.
General background and concepts of DetNet can be found in the DetNet General background and concepts of DetNet can be found in the DetNet
Architecture [RFC8655]. Architecture [RFC8655].
skipping to change at page 3, line 19 skipping to change at page 3, line 16
be familiar with these documents and their terminology. be familiar with these documents and their terminology.
2.2. Abbreviations 2.2. Abbreviations
This document uses the abbreviations defined in the DetNet This document uses the abbreviations defined in the DetNet
architecture [RFC8655] and [I-D.ietf-detnet-data-plane-framework]. architecture [RFC8655] and [I-D.ietf-detnet-data-plane-framework].
This document uses the following abbreviations: This document uses the following abbreviations:
CE Customer Edge equipment. CE Customer Edge equipment.
d-CW DetNet Control Word.
DetNet Deterministic Networking. DetNet Deterministic Networking.
DF DetNet Flow. DF DetNet Flow.
DN DetNet. DN DetNet.
L2 Layer-2. L2 Layer-2.
L3 Layer-3. L3 Layer-3.
skipping to change at page 3, line 47 skipping to change at page 3, line 46
PRF Packet Replication Function. PRF Packet Replication Function.
PREOF Packet Replication, Elimination and Ordering Functions. PREOF Packet Replication, Elimination and Ordering Functions.
POF Packet Ordering Function. POF Packet Ordering Function.
PSN Packet Switched Network. PSN Packet Switched Network.
PW Pseudowire. PW Pseudowire.
S-Label DetNet "service" label.
T-PE Terminating Provider Edge.
TE Traffic Engineering. TE Traffic Engineering.
TSN Time-Sensitive Networking, TSN is a Task Group of the TSN Time-Sensitive Networking, TSN is a Task Group of the
IEEE 802.1 Working Group. IEEE 802.1 Working Group.
2.3. Requirements Language 2.3. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
skipping to change at page 4, line 50 skipping to change at page 5, line 24
|Forwarding| |Fwd| |Fwd| |Forwarding| |Fwd| |Fwd| |Forwarding| |Forwarding| |Fwd| |Fwd| |Forwarding| |Fwd| |Fwd| |Forwarding|
+-------.--+ +-.-+ +-.-+ +----.---.-+ +-.-+ +-.-+ +---.------+ +-------.--+ +-.-+ +-.-+ +----.---.-+ +-.-+ +-.-+ +---.------+
: Link : / ,-----. \ : Link : / ,-----. \ : Link : / ,-----. \ : Link : / ,-----. \
+........+ +-[ Sub ]-+ +......+ +-[ Sub ]-+ +........+ +-[ Sub ]-+ +......+ +-[ Sub ]-+
[Network] [Network] [Network] [Network]
`-----' `-----' `-----' `-----'
|<---- DetNet MPLS ---->| |<---- DetNet MPLS ---->|
|<--------------------- DetNet IP ------------------>| |<--------------------- DetNet IP ------------------>|
Figure 1: DetNet IP Over DetNet MPLS Network Figure 1: Architecture: DetNet IP Over DetNet MPLS Network
4. IP over DetNet MPLS 4. IP over DetNet MPLS
This section defines how IP encapsulated flows are carried over a This section defines how IP encapsulated flows are carried over a
DetNet MPLS data plane as defined in [I-D.ietf-detnet-mpls]. Since DetNet MPLS data plane as defined in [I-D.ietf-detnet-mpls]. Since
both Non-DetNet and DetNet IP packet are identical on the wire, this both Non-DetNet and DetNet IP packet are identical on the wire, this
section is applicable to any node that supports IP over DetNet MPLS, section is applicable to any node that supports IP over DetNet MPLS,
and this section refers to both cases as DetNet IP over DetNet MPLS. and this section refers to both cases as DetNet IP over DetNet MPLS.
4.1. IP Over DetNet MPLS Data Plane Scenarios 4.1. IP Over DetNet MPLS Data Plane Scenarios
skipping to change at page 6, line 28 skipping to change at page 6, line 35
| | | |
|<-DN IP-> <-------- DetNet MPLS ---------------> <-DN IP->| |<-DN IP-> <-------- DetNet MPLS ---------------> <-DN IP->|
| | | |
|<-------------- End to End DetNet Service --------------->| |<-------------- End to End DetNet Service --------------->|
-------------------------- Data Flow -------------------------> -------------------------- Data Flow ------------------------->
X = Service protection (PRF, PREOF, PEF/POF) X = Service protection (PRF, PREOF, PEF/POF)
DFx = DetNet member flow x over a TE LSP DFx = DetNet member flow x over a TE LSP
Figure 2: DetNet IP Over DetNet MPLS Network Figure 2: Service Protection Over DetNet MPLS Network for DetNet IP
Figure 1 illustrates DetNet enabled End Systems, connected to DetNet Figure 1 illustrates DetNet enabled End Systems, connected to DetNet
(DN) enabled MPLS network. A similar situation occurs when end (DN) enabled MPLS network. A similar situation occurs when end
systems are are not DetNet aware. In this case, edge nodes sit at systems are are not DetNet aware. In this case, edge nodes sit at
the boundary of the MPLS domain since it is also a DetNet domain the boundary of the MPLS domain since it is also a DetNet domain
boundary. The edge nodes provide DetNet service proxies for the end boundary. The edge nodes provide DetNet service proxies for the end
applications by initiating and terminating DetNet service for the applications by initiating and terminating DetNet service for the
application's IP flows. While the node types differ, there is application's IP flows. While the node types differ, there is
essentially no difference in data plane processing between relay and essentially no difference in data plane processing between relay and
edges. There are likely to be differences in controller plane edges. There are likely to be differences in controller plane
skipping to change at page 7, line 29 skipping to change at page 7, line 35
+------+ +------+
| L2 | | L2 |
+------+ +------+
(1) DetNet IP Flow (or simply IP flow) (1) DetNet IP Flow (or simply IP flow)
(2) DetNet MPLS Flow (2) DetNet MPLS Flow
Figure 3: Example DetNet IP over MPLS Sub-Network Formats Figure 3: Example DetNet IP over MPLS Sub-Network Formats
In Figure 3 "App-Flow" indicates the payload carried by the DetNet IP In Figure 3 "App-Flow" indicates the payload carried by the DetNet IP
data plane. "IP" and "NProto" indicate the fields described in data plane. "IP" and "NProto" indicate the fields described in
Section 5.1.1. IP Header Information and Section 5.1.2. Other Section 5.1.1. (IP Header Information) and Section 5.1.2. (Other
Protocol Header Information in [I-D.ietf-detnet-ip], respectively. Protocol Header Information) of [I-D.ietf-detnet-ip], respectively.
"App-Flow for MPLS" indicates that an individual DetNet IP flow is "App-Flow for MPLS" indicates that an individual DetNet IP flow is
the payload from the perspective of the DetNet MPLS data plane the payload from the perspective of the DetNet MPLS data plane
defined in [I-D.ietf-detnet-mpls]. defined in [I-D.ietf-detnet-mpls].
Per [I-D.ietf-detnet-mpls], the DetNet MPLS data plane uses a single Per Section 5.1 of [I-D.ietf-detnet-mpls], the DetNet MPLS data plane
S-Label to support a single app flow. Section 5.1. DetNet IP Flow uses a single S-Label to support a single app flow. DetNet IP Flow
Identification Procedures in [I-D.ietf-detnet-ip] states that a Identification Procedures in Section 4.4 of [I-D.ietf-detnet-ip]
single DetNet flow is identified based on IP, and next level states that a single DetNet flow is identified based on IP, and next
protocol, header information. Section 4.4. Aggregation level protocol, header information. Section 4.4. (Aggregation
Considerations in [I-D.ietf-detnet-ip] defines the ways in which Considerations) of [I-D.ietf-detnet-ip] defines the ways in which
aggregation is supported through the use of prefixes, wildcards, aggregation is supported through the use of prefixes, wildcards,
lists, and port ranges. Collectively, this results in the fairly lists, and port ranges. Collectively, this results in the fairly
straightforward procedures defined in this section. straightforward procedures defined in this section.
As shown in Figure 2, DetNet relay nodes are responsible for the As shown in Figure 2, DetNet relay nodes are responsible for the
mapping of a DetNet flow, at the service sub-layer, from the IP to mapping of a DetNet flow, at the service sub-layer, from the IP to
MPLS DetNet data planes and back again. Their related DetNet IP over MPLS DetNet data planes and back again. Their related DetNet IP over
DetNet MPLS data plane operation is comprised of two sets of DetNet MPLS data plane operation is comprised of two sets of
procedures: the mapping of flow identifiers, and ensuring proper procedures: the mapping of flow identifiers, and ensuring proper
traffic treatment. traffic treatment.
skipping to change at page 9, line 41 skipping to change at page 9, line 48
processing according to [I-D.ietf-detnet-mpls]. processing according to [I-D.ietf-detnet-mpls].
It is the responsibility of the DetNet controller plane to properly It is the responsibility of the DetNet controller plane to properly
provision both flow identification information and the flow specific provision both flow identification information and the flow specific
resources needed to provided the traffic treatment needed to meet resources needed to provided the traffic treatment needed to meet
each flow's service requirements. This applies for aggregated and each flow's service requirements. This applies for aggregated and
individual flows. individual flows.
7. Security Considerations 7. Security Considerations
This draft does not have additional security considerations. Generals security considerations for DetNet are described in detail
Security considerations for DetNet are described in detail in in [I-D.ietf-detnet-security]. DetNet MPLS and DetNet IP security
[I-D.ietf-detnet-security]. General security considerations are considerations equally apply to this document and are described in
described in [RFC8655]. MPLS and IP specific considerations are [I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip].
described in [I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip].
Security aspects which are unique to DetNet are those whose aim is to Security aspects which are unique to DetNet are those whose aim is to
provide the specific quality of service aspects of DetNet, which are provide the specific quality of service aspects of DetNet, which are
primarily to deliver data flows with extremely low packet loss rates primarily to deliver data flows with extremely low packet loss rates
and bounded end-to-end delivery latency. and bounded end-to-end delivery latency.
The primary considerations for the data plane is to maintain The primary considerations for the data plane is to maintain
integrity of data and delivery of the associated DetNet service integrity of data and delivery of the associated DetNet service
traversing the DetNet network. Application flows can be protected traversing the DetNet network. Application flows can be protected
through whatever means is provided by the underlying technology. For through whatever means is provided by the underlying technology. For
skipping to change at page 10, line 48 skipping to change at page 11, line 7
9. Acknowledgements 9. Acknowledgements
The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson, The authors wish to thank Pat Thaler, Norman Finn, Loa Anderson,
David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David David Black, Rodney Cummings, Ethan Grossman, Tal Mizrahi, David
Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J. Mozes, Craig Gunther, George Swallow, Yuanlong Jiang and Carlos J.
Bernardos for their various contributions to this work. Bernardos for their various contributions to this work.
10. Contributors 10. Contributors
RFC7322 limits the number of authors listed on the front page of a
draft to a maximum of 5. The editor wishes to thank and acknowledge
the follow authors for contributing text to this draft.
Janos Farkas
Ericsson
Email: janos.farkas@ericsson.com
Andrew G. Malis
Malis Consulting
Email: agmalis@gmail.com
Janos Farkas contributed substantially to the content of this Janos Farkas contributed substantially to the content of this
document. document.
11. References 11. References
11.1. Normative references 11.1. Normative references
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
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: IP", and S. Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-
draft-ietf-detnet-ip-04 (work in progress), November 2019. ip-05 (work in progress), February 2020.
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
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: MPLS", Bryant, S., and J. Korhonen, "DetNet Data Plane: MPLS",
draft-ietf-detnet-mpls-04 (work in progress), November draft-ietf-detnet-mpls-05 (work in progress), February
2019. 2020.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas, [RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655, "Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019, DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>. <https://www.rfc-editor.org/info/rfc8655>.
11.2. Informative references 11.2. Informative references
[I-D.ietf-detnet-data-plane-framework] [I-D.ietf-detnet-data-plane-framework]
Varga, B., Farkas, J., Berger, L., Fedyk, D., Malis, A., Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, S., and J. Korhonen, "DetNet Data Plane Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
Framework", draft-ietf-detnet-data-plane-framework-03 data-plane-framework-04 (work in progress), February 2020.
(work in progress), October 2019.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T., Grossman, E., Hacker, A., Das, S., Dowdell, Mizrahi, T. and E. Grossman, "Deterministic Networking
J., Austad, H., and N. Finn, "Deterministic Networking
(DetNet) Security Considerations", draft-ietf-detnet- (DetNet) Security Considerations", draft-ietf-detnet-
security-07 (work in progress), January 2020. security-09 (work in progress), March 2020.
[IEEE802.1AE-2018] [IEEE802.1AE-2018]
IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC IEEE Standards Association, "IEEE Std 802.1AE-2018 MAC
Security (MACsec)", 2018, Security (MACsec)", 2018,
<https://ieeexplore.ieee.org/document/8585421>. <https://ieeexplore.ieee.org/document/8585421>.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the [RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, Internet Protocol", RFC 4301, DOI 10.17487/RFC4301,
December 2005, <https://www.rfc-editor.org/info/rfc4301>. December 2005, <https://www.rfc-editor.org/info/rfc4301>.
skipping to change at page 12, line 29 skipping to change at page 12, line 46
Lou Berger Lou Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: lberger@labn.net Email: lberger@labn.net
Don Fedyk Don Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Email: dfedyk@labn.net Email: dfedyk@labn.net
Andrew G. Malis
Independent
Email: agmalis@gmail.com
Stewart Bryant Stewart Bryant
Futurewei Technologies Futurewei Technologies
Email: stewart.bryant@gmail.com Email: stewart.bryant@gmail.com
Jouni Korhonen Jouni Korhonen
Email: jouni.nospam@gmail.com Email: jouni.nospam@gmail.com
 End of changes. 24 change blocks. 
42 lines changed or deleted 49 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/