draft-ietf-detnet-ip-over-mpls-04.txt   draft-ietf-detnet-ip-over-mpls-05.txt 
DetNet B. Varga, Ed. DetNet B. Varga, Ed.
Internet-Draft J. Farkas Internet-Draft Ericsson
Intended status: Standards Track Ericsson Intended status: Standards Track L. Berger
Expires: May 24, 2020 L. Berger Expires: August 6, 2020 D. Fedyk
D. Fedyk
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
A. Malis A. Malis
Independent Independent
S. Bryant S. Bryant
Futurewei Technologies Futurewei Technologies
J. Korhonen J. Korhonen
November 21, 2019 February 3, 2020
DetNet Data Plane: IP over MPLS DetNet Data Plane: IP over MPLS
draft-ietf-detnet-ip-over-mpls-04 draft-ietf-detnet-ip-over-mpls-05
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 39 skipping to change at page 1, line 38
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 May 24, 2020. This Internet-Draft will expire on August 6, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 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 . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3 2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 3 2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 4 3. DetNet IP Data Plane Overview . . . . . . . . . . . . . . . . 4
4. IP over DetNet MPLS . . . . . . . . . . . . . . . . . . . . . 4 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 . . . . . . . . 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
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. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10
10.1. Normative references . . . . . . . . . . . . . . . . . . 10 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.2. Informative references . . . . . . . . . . . . . . . . . 11 11.1. Normative references . . . . . . . . . . . . . . . . . . 11
11.2. Informative references . . . . . . . . . . . . . . . . . 11
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 35 skipping to change at page 3, line 35
L2 Layer-2. L2 Layer-2.
L3 Layer-3. L3 Layer-3.
LSP Label-switched path. LSP Label-switched path.
MPLS Multiprotocol Label Switching. MPLS Multiprotocol Label Switching.
PE Provider Edge. PE Provider Edge.
PREOF Packet Replication, Ordering and Elimination Function. PEF Packet Elimination Function.
PRF Packet Replication Function.
PREOF Packet Replication, Elimination and Ordering Functions.
POF Packet Ordering Function.
PSN Packet Switched Network. PSN Packet Switched Network.
PW Pseudowire. PW Pseudowire.
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.
skipping to change at page 8, line 12 skipping to change at page 8, line 12
procedures: the mapping of flow identifiers, and ensuring proper procedures: the mapping of flow identifiers, and ensuring proper
traffic treatment. traffic treatment.
Mapping of IP to DetNet MPLS is similar for DetNet IP flows and IP Mapping of IP to DetNet MPLS is similar for DetNet IP flows and IP
flows. The six-tuple of IP is mapped to the S-Label in both cases. flows. The six-tuple of IP is mapped to the S-Label in both cases.
The various fields may be mapped or ignored when going from IP to The various fields may be mapped or ignored when going from IP to
MPLS. MPLS.
5. IP over DetNet MPLS Procedures 5. IP over DetNet MPLS Procedures
5.1. DetNet IP over DetNet MPLS Flow Identification Procedures 5.1. DetNet IP over DetNet MPLS Flow Identification and Aggregation
Procedures
A DetNet relay node (ingress T-PE) that sends a DetNet IP flow over a A DetNet relay node (ingress T-PE) that sends a DetNet IP flow over a
DetNet MPLS network MUST map a DetNet IP flow, as identified in DetNet MPLS network MUST map a DetNet IP flow, as identified in
[I-D.ietf-detnet-ip] into a single MPLS DetNet flow and MUST process [I-D.ietf-detnet-ip] into a single MPLS DetNet flow and MUST process
it in accordance to the procedures defined in [I-D.ietf-detnet-mpls] it in accordance to the procedures defined in [I-D.ietf-detnet-mpls].
Section 6.1. PRF MAY be supported at the MPLS level for DetNet IP PRF MAY be supported at the MPLS level for DetNet IP flows sent over
flows sent over an DetNet MPLS network. Aggregation MAY be supported an DetNet MPLS network. Aggregation MAY be supported as defined in
as defined in [I-D.ietf-detnet-mpls] Section 5.4. Aggregation [I-D.ietf-detnet-mpls] Section 4.4. Aggregation considerations in
considerations in [I-D.ietf-detnet-ip] MAY be used to identify an [I-D.ietf-detnet-ip] MAY be used to identify an individual DetNet IP
individual DetNet IP flow. The provisioning of the mapping of DetNet flow. The provisioning of the mapping of DetNet IP flows to DetNet
IP flows to DetNet MPLS flows MUST be supported via configuration, MPLS flows MUST be supported via configuration, e.g., via the
e.g., via the controller plane. controller plane.
A DetNet relay node (egress T-PE) MAY be provisioned to handle A DetNet relay node (egress T-PE) MAY be provisioned to handle
packets received via the DetNet MPLS data plane as DetNet IP flows. packets received via the DetNet MPLS data plane as DetNet IP flows.
A single incoming DetNet MPLS flow MAY be treated as a single DetNet A single incoming DetNet MPLS flow MAY be treated as a single DetNet
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 7.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.
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
skipping to change at page 10, line 46 skipping to change at page 10, line 46
This document makes no IANA requests. This document makes no IANA requests.
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. References 10. Contributors
10.1. Normative references Janos Farkas contributed substantially to the content of this
document.
11. 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", Bryant, S., and J. Korhonen, "DetNet Data Plane: IP",
draft-ietf-detnet-ip-03 (work in progress), October 2019. draft-ietf-detnet-ip-04 (work in progress), November 2019.
[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-03 (work in progress), October draft-ietf-detnet-mpls-04 (work in progress), November
2019. 2019.
[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>.
10.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., Fedyk, D., Malis, A.,
Bryant, S., and J. Korhonen, "DetNet Data Plane Bryant, S., and J. Korhonen, "DetNet Data Plane
Framework", draft-ietf-detnet-data-plane-framework-03 Framework", draft-ietf-detnet-data-plane-framework-03
(work in progress), October 2019. (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., Grossman, E., Hacker, A., Das, S., Dowdell,
J., Austad, H., and N. Finn, "Deterministic Networking J., Austad, H., and N. Finn, "Deterministic Networking
(DetNet) Security Considerations", draft-ietf-detnet- (DetNet) Security Considerations", draft-ietf-detnet-
security-06 (work in progress), November 2019. security-07 (work in progress), January 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
Balazs Varga (editor) Balazs Varga (editor)
Ericsson Ericsson
Magyar Tudosok krt. 11. Magyar Tudosok krt. 11.
Budapest 1117 Budapest 1117
Hungary Hungary
Email: balazs.a.varga@ericsson.com Email: balazs.a.varga@ericsson.com
Janos Farkas
Ericsson
Magyar Tudosok krt. 11.
Budapest 1117
Hungary
Email: janos.farkas@ericsson.com
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
 End of changes. 20 change blocks. 
39 lines changed or deleted 43 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/