draft-ietf-detnet-ip-over-mpls-07.txt   draft-ietf-detnet-ip-over-mpls-08.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: March 5, 2021 D. Fedyk Expires: March 14, 2021 D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
J. Korhonen J. Korhonen
September 1, 2020 September 10, 2020
DetNet Data Plane: IP over MPLS DetNet Data Plane: IP over MPLS
draft-ietf-detnet-ip-over-mpls-07 draft-ietf-detnet-ip-over-mpls-08
Abstract Abstract
This document specifies the Deterministic Networking data plane when This document specifies the Deterministic Networking data plane when
encapsulating IP over an MPLS packet switched network. encapsulating IP over an 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 36 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 March 5, 2021. This Internet-Draft will expire on March 14, 2021.
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
skipping to change at page 2, line 26 skipping to change at page 2, line 26
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 . . . . . . . . 6
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 a capability for the
packet loss rates and assured maximum end-to-end delivery latency. delivery of data flows with extremely low packet loss rates and
General background and concepts of DetNet can be found in the DetNet bounded end-to-end delivery latency. General background and concepts
Architecture [RFC8655]. of DetNet can be found in the DetNet Architecture [RFC8655].
This document specifies use of the IP DetNet encapsulation over an This document specifies use of the IP DetNet encapsulation over an
MPLS network. It maps the IP data plane encapsulation described in MPLS network. It maps the IP data plane encapsulation described in
[I-D.ietf-detnet-ip] to the DetNet MPLS data plane defined in [I-D.ietf-detnet-ip] to the DetNet MPLS data plane defined in
[I-D.ietf-detnet-mpls]. [I-D.ietf-detnet-mpls].
2. Terminology 2. Terminology
2.1. Terms Used In This Document 2.1. Terms Used In This Document
skipping to change at page 3, line 26 skipping to change at page 3, line 26
d-CW DetNet Control Word. 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.
LSP Label-switched path. LSP Label-switched path.
MPLS Multiprotocol Label Switching. MPLS Multiprotocol Label Switching.
PE Provider Edge.
PEF Packet Elimination Function. PEF Packet Elimination Function.
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.
PW Pseudowire. PW Pseudowire.
S-Label DetNet "service" label. S-Label DetNet "service" label.
S-PE Switching Provider Edge.
T-PE Terminating Provider Edge. 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",
skipping to change at page 8, line 40 skipping to change at page 8, line 40
IP flow, without examination of IP headers. Alternatively, packets IP flow, without examination of IP headers. Alternatively, packets
received via the DetNet MPLS data plane MAY follow the normal DetNet received via the DetNet MPLS data plane MAY follow the normal DetNet
IP flow identification procedures defined in [I-D.ietf-detnet-ip] IP flow identification procedures defined in [I-D.ietf-detnet-ip]
Section 5.1. Section 5.1.
An implementation MUST support the provisioning for handling any An implementation MUST support the provisioning for handling any
received DetNet MPLS data plane as DetNet IP flows via configuration. received DetNet MPLS data plane as DetNet IP flows via configuration.
Note that such configuration MAY include support from PREOF on the Note that such configuration MAY include support from PREOF on the
incoming DetNet MPLS flow. incoming DetNet MPLS flow.
Note: using Layer-4 (L4) transport protocols e.g., for multipath are
out of scope of this document both for a single flow and aggregate
flows.
5.2. DetNet IP over DetNet MPLS Traffic Treatment Procedures 5.2. DetNet IP over DetNet MPLS Traffic Treatment Procedures
The traffic treatment required for a particular DetNet IP flow is The traffic treatment required for a particular DetNet IP flow is
provisioned via configuration or the controller plane. When a DetNet provisioned via configuration or the controller plane. When a DetNet
IP flow is sent over DetNet MPLS, a DetNet relay node MUST ensure IP flow is sent over DetNet MPLS, a DetNet relay node MUST ensure
that the provisioned DetNet IP traffic treatment is provided at the that the provisioned DetNet IP traffic treatment is provided at the
forwarding sub-layer as described in [I-D.ietf-detnet-mpls] forwarding sub-layer as described in [I-D.ietf-detnet-mpls]
Section 5.2. Note that the PRF function MAY be utilized when sending Section 5.2. Note that the PRF function MAY be utilized when sending
IP over MPLS. IP over MPLS.
skipping to change at page 9, line 34 skipping to change at page 9, line 38
o S-Label values that are carrying MPLS over IP encapsulated o S-Label values that are carrying MPLS over IP encapsulated
traffic. traffic.
o For each S-Label, how the received traffic is to be handled. The o For each S-Label, how the received traffic is to be handled. The
traffic may be processed according as any other DetNet IP traffic traffic may be processed according as any other DetNet IP traffic
as defined in this document or in [I-D.ietf-detnet-ip], or the as defined in this document or in [I-D.ietf-detnet-ip], or the
traffic may be directly treated as an MPLS App-flow for additional traffic may be directly treated as an MPLS App-flow for additional
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 provide the traffic treatment to meet each flow's
each flow's service requirements. This applies for aggregated and service requirements. This applies for aggregated and individual
individual flows. flows.
7. Security Considerations 7. Security Considerations
General security considerations for DetNet are described in detail in General security considerations for DetNet are described in detail in
[I-D.ietf-detnet-security]. DetNet MPLS and DetNet IP security [I-D.ietf-detnet-security]. DetNet MPLS and DetNet IP security
considerations equally apply to this document and are described in considerations equally apply to this document and are described in
[I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip]. [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 protect the support of specific quality of service aspects of DetNet,
primarily to deliver data flows with extremely low packet loss rates which are primarily to deliver data flows with extremely low packet
and bounded end-to-end delivery latency. loss rates and bounded end-to-end delivery latency.
The primary considerations for the data plane are to maintain The primary considerations for the data plane are 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
example, encryption may be used, such as that provided by IPSec example, encryption may be used, such as that provided by IPSec
[RFC4301] for IP flows and/or by an underlying sub-net using MACSec [RFC4301] for IP flows and/or by an underlying sub-net using MACSec
[IEEE802.1AE-2018] for IP over Ethernet (Layer-2) flows. [IEEE802.1AE-2018] for IP over Ethernet (Layer-2) flows.
From a data plane perspective this document does not add or modify From a data plane perspective this document does not add or modify
skipping to change at page 11, line 20 skipping to change at page 11, line 26
Malis Consulting Malis Consulting
Email: agmalis@gmail.com 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-data-plane-framework]
Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
data-plane-framework-06 (work in progress), May 2020.
[I-D.ietf-detnet-ip] [I-D.ietf-detnet-ip]
Varga, B., Farkas, J., Berger, L., Fedyk, D., and S. Varga, B., Farkas, J., Berger, L., Fedyk, D., and S.
Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-07 Bryant, "DetNet Data Plane: IP", draft-ietf-detnet-ip-07
(work in progress), July 2020. (work in progress), July 2020.
[I-D.ietf-detnet-mpls] [I-D.ietf-detnet-mpls]
Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S., Varga, B., Farkas, J., Berger, L., Malis, A., Bryant, S.,
and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf- and J. Korhonen, "DetNet Data Plane: MPLS", draft-ietf-
detnet-mpls-11 (work in progress), August 2020. detnet-mpls-11 (work in progress), August 2020.
[I-D.ietf-detnet-security]
Mizrahi, T. and E. Grossman, "Deterministic Networking
(DetNet) Security Considerations", draft-ietf-detnet-
security-11 (work in progress), August 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]
Varga, B., Farkas, J., Berger, L., Malis, A., and S.
Bryant, "DetNet Data Plane Framework", draft-ietf-detnet-
data-plane-framework-06 (work in progress), May 2020.
[I-D.ietf-detnet-security]
Mizrahi, T. and E. Grossman, "Deterministic Networking
(DetNet) Security Considerations", draft-ietf-detnet-
security-11 (work in progress), August 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>.
Authors' Addresses Authors' Addresses
 End of changes. 17 change blocks. 
33 lines changed or deleted 33 lines changed or added

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