draft-ietf-detnet-ip-over-mpls-08.txt   draft-ietf-detnet-ip-over-mpls-09.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 14, 2021 D. Fedyk Expires: April 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 10, 2020 October 11, 2020
DetNet Data Plane: IP over MPLS DetNet Data Plane: IP over MPLS
draft-ietf-detnet-ip-over-mpls-08 draft-ietf-detnet-ip-over-mpls-09
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 14, 2021. This Internet-Draft will expire on April 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 21 skipping to change at page 2, line 21
2.1. Terms Used In This Document . . . . . . . . . . . . . . . 2 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 . . . . . . . . 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 . 9
6. Management and Control Information Summary . . . . . . . . . 9 6. Management and Control Information Summary . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative references . . . . . . . . . . . . . . . . . . 11 11.1. Normative references . . . . . . . . . . . . . . . . . . 11
11.2. Informative references . . . . . . . . . . . . . . . . . 12 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 a capability for the a network to DetNet flows. DetNet provides a capability for the
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
The main differences of mapping IP to DetNet MPLS (compared to plain
MPLS) are that (1) there is a mandatory flow identification to make
the forwarding decision (i.e., forwarding is not based on FEC), (2)
the d-CW (DetNet Control Word) is mandatory for the MPLS
encapsulation and (3) during forwarding over the DetNet MPLS network
DetNet flow specific treatment is needed.
5.1. DetNet IP over DetNet MPLS Flow Identification and Aggregation 5.1. DetNet IP over DetNet MPLS Flow Identification and Aggregation
Procedures 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].
PRF MAY be supported at the MPLS level for DetNet IP flows sent over PRF MAY be supported at the MPLS level for DetNet IP flows sent over
an DetNet MPLS network. Aggregation MAY be supported as defined in an DetNet MPLS network. Aggregation MAY be supported as defined in
[I-D.ietf-detnet-mpls] Section 4.4. Aggregation considerations in [I-D.ietf-detnet-mpls] Section 4.4. Aggregation considerations in
skipping to change at page 8, line 36 skipping to change at page 8, line 43
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 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. packet flows received via DetNet MPLS data plane as DetNet IP flows
Note that such configuration MAY include support from PREOF on the via configuration. Note that such configuration MAY include support
incoming DetNet MPLS flow. from PREOF on the incoming DetNet MPLS flow.
Note: using Layer-4 (L4) transport protocols e.g., for multipath are 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 out of scope of this document both for a single flow and aggregate
flows. 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
skipping to change at page 11, line 39 skipping to change at page 11, line 46
data-plane-framework-06 (work in progress), May 2020. 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-12 (work in progress), September 2020.
[I-D.ietf-detnet-security] [I-D.ietf-detnet-security]
Mizrahi, T. and E. Grossman, "Deterministic Networking Grossman, E., Mizrahi, T., and A. Hacker, "Deterministic
(DetNet) Security Considerations", draft-ietf-detnet- Networking (DetNet) Security Considerations", draft-ietf-
security-11 (work in progress), August 2020. detnet-security-12 (work in progress), October 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>.
 End of changes. 11 change blocks. 
14 lines changed or deleted 21 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/