draft-ietf-detnet-mpls-over-udp-ip-02.txt   draft-ietf-detnet-mpls-over-udp-ip-03.txt 
DetNet B. Varga, Ed. DetNet B. Varga, Ed.
Internet-Draft J. Farkas Internet-Draft J. Farkas
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: April 18, 2020 L. Berger Expires: April 29, 2020 L. Berger
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
October 16, 2019 October 27, 2019
DetNet Data Plane: MPLS over UDP/IP DetNet Data Plane: MPLS over UDP/IP
draft-ietf-detnet-mpls-over-udp-ip-02 draft-ietf-detnet-mpls-over-udp-ip-03
Abstract Abstract
This document specifies the MPLS Deterministic Networking data plane This document specifies the MPLS Deterministic Networking data plane
operation and encapsulation over an IP network. The approach is operation and encapsulation over an IP network. The approach is
modeled on the operation of MPLS and over UDP/IP packet switched modeled on the operation of MPLS and over UDP/IP packet switched
networks. networks.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 April 18, 2020. This Internet-Draft will expire on April 29, 2020.
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 2, line 33 skipping to change at page 2, line 33
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
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 with a 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 General background and concepts of DetNet can be found in [RFC8655].
[I-D.ietf-detnet-architecture].
This document specifies use of the MPLS DetNet encapsulation over an This document specifies use of the MPLS DetNet encapsulation over an
IP network. The approach is modeled on the operation of MPLS over an IP network. The approach is modeled on the operation of MPLS over an
IP Packet Switched Network (PSN) [RFC7510]. It maps the MPLS data IP Packet Switched Network (PSN) [RFC7510]. It maps the MPLS data
plane encapsulation described in [I-D.ietf-detnet-mpls] to the DetNet plane encapsulation described in [I-D.ietf-detnet-mpls] to the DetNet
IP data plane defined in [I-D.ietf-detnet-ip]. IP data plane defined in [I-D.ietf-detnet-ip].
To carry DetNet flows with full functionality at the DetNet layer To carry DetNet MPLS flows with full functionality at the DetNet
over an IP network, the following components are required (these are layer over an IP network, the following components are required
a subset of the requirements for MPLS encapsulation listed in (these are a subset of the requirements for MPLS encapsulation listed
[I-D.ietf-detnet-mpls]): in [I-D.ietf-detnet-mpls]):
1. A method of identifying the DetNet flow group to the processing 1. A method for identifying DetNet flows to the processing element.
element.
2. A method of carrying the DetNet sequence number. 2. A method for carrying the DetNet sequence number.
3. A method of distinguishing DetNet OAM packets from DetNet data 3. A method for distinguishing DetNet OAM packets from DetNet data
packets. packets.
4. A method of carrying queuing and forwarding indication. 4. A method for carrying queuing and forwarding indication.
These requirements are satisfied by the DetNet over MPLS These requirements are satisfied by the DetNet over MPLS
Encapsulation described in [I-D.ietf-detnet-mpls] and they are partly Encapsulation described in [I-D.ietf-detnet-mpls] and they are partly
satisfied by the DetNet IP data plane defined in [I-D.ietf-detnet-ip] satisfied by the DetNet IP data plane defined in [I-D.ietf-detnet-ip]
2. Terminology 2. Terminology
2.1. Terms Used in This Document 2.1. Terms Used in This Document
This document uses the terminology established in the DetNet This document uses the terminology established in the DetNet
architecture [I-D.ietf-detnet-architecture], and the reader is architecture [RFC8655], and the reader is assumed to be familiar with
assumed to be familiar with that document and its terminology. that document and its terminology.
2.2. Abbreviations 2.2. Abbreviations
The following abbreviations are used in this document: The following abbreviations are used in this document:
d-CW A DetNet Control Word (d-CW) is used for sequencing and d-CW A DetNet Control Word (d-CW) is used for sequencing and
identifying duplicate packets of a DetNet flow at the identifying duplicate packets of a DetNet flow at the
DetNet service sub-layer. DetNet service sub-layer.
DetNet Deterministic Networking. DetNet Deterministic Networking.
skipping to change at page 3, line 51 skipping to change at page 3, line 49
routers. routers.
MPLS Multiprotocol Label Switching. MPLS Multiprotocol Label Switching.
OAM Operations, Administration, and Maintenance. OAM Operations, Administration, and Maintenance.
PEF Packet Elimination Function. PEF Packet Elimination Function.
POF Packet Ordering Function. POF Packet Ordering Function.
PREOF Packet Replication, Elimination and Ordering Functions.
PRF Packet Replication Function. PRF Packet Replication Function.
PSN Packet Switched Network. PSN Packet Switched Network.
S-Label A DetNet "service" label that is used between DetNet S-Label A DetNet "service" label that is used between DetNet
nodes that implement also the DetNet service sub-layer nodes that also implement the DetNet service sub-layer
functions. An S-Label is also used to identify a functions. An S-Label is also used to identify a
DetNet flow at DetNet service sub-layer. DetNet flow at DetNet service sub-layer.
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
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
skipping to change at page 5, line 28 skipping to change at page 5, line 28
+---------------------------------+ +--> DetNet data plane +---------------------------------+ +--> DetNet data plane
| IP Header | | IP encapsulation | IP Header | | IP encapsulation
+---------------------------------+ <--/ +---------------------------------+ <--/
| Data-Link | | Data-Link |
+---------------------------------+ +---------------------------------+
| Physical | | Physical |
+---------------------------------+ +---------------------------------+
Figure 1: UDP/IP Encapsulation of DetNet MPLS Figure 1: UDP/IP Encapsulation of DetNet MPLS
d-CW, S-Labels and zero or more F-Labels are used as defined in S-Labels, d-CW and zero or more F-Labels are used as defined in
[I-D.ietf-detnet-mpls] and are not modified by this document. In [I-D.ietf-detnet-mpls] and are not modified by this document. In
case of aggregates the A-Label is treated as an S-Label and it too is case of aggregates the A-Label is treated as an S-Label and it too is
not modified. not modified.
4. DetNet Data Plane Procedures 4. DetNet Data Plane Procedures
To support outgoing DetNet MPLS over UDP/IP encapsulation, an To support outgoing DetNet MPLS over UDP/IP encapsulation, an
implementation MUST support the provisioning of UDP and IP header implementation MUST support the provisioning of UDP and IP header
information in addition or in place of F-Label(s). Note, when PRF is information in addition or in place of F-Label(s). Note, when PRF is
performed at the MPLS service sub-layer, there will be multiple performed at the MPLS service sub-layer, there will be multiple
member flows, and each member flow will require the provisioning of member flows, and each member flow will require the provisioning of
their own UDP and IP header information. The headers for each their own UDP and IP header information. The headers for each
outgoing packet MUST be formatted on the configuration information outgoing packet MUST be formatted according to the configuration
and as defined in [RFC7510], with one exception. Note that the UDP information and as defined in [RFC7510], with one exception. Note
Source Port value MUST be set to uniquely identify the DetNet flow. that the UDP Source Port value MUST be set to uniquely identify the
The packet MUST then be handed as a DetNet IP packet, per DetNet flow. The packet MUST then be handed as a DetNet IP packet,
[I-D.ietf-detnet-ip]. This includes QoS related traffic treatment. per [I-D.ietf-detnet-ip]. This includes QoS related traffic
treatment.
To support receive processing an implementation MUST also support the To support receive processing an implementation MUST also support the
provisioning of received UDP and IP header information. The provisioning of received UDP and IP header information. The
provisioned information MUST be used to identify incoming app-flows provisioned information MUST be used to identify incoming app-flows
based on the combination of S-Label and incoming encapsulation header based on the combination of S-Label and incoming encapsulation header
information. Normal receive processing as defined in information. Normal receive processing as defined in
[I-D.ietf-detnet-mpls], including PEF and POF, can then take place. [I-D.ietf-detnet-mpls], including PEF and POF, can then take place.
5. Management and Control Information Summary 5. Management and Control Information Summary
The following summarizes the set of information that is needed to The following summarizes the set of information that is needed to
configure DetNet MPLS over UDP/IP: configure DetNet MPLS over UDP/IP:
o Label information (S-label or F-label) to be mapped to UDP/IP o Label information (S-label or F-label) to be mapped to UDP/IP
flow. Note that a single S-Label can map to multiple sets of UPD/ flow. Note that a single S-Label can map to multiple sets of UPD/
IP information when PREOF is used. IP information when PREOF is used.
o IPv4 and IPv6 source address field. o IPv4 or IPv6 source address field.
o IPv4 and IPv6 destination address field. o IPv4 or IPv6 destination address field.
o IPv4 Type of Service and IPv6 Traffic Class Fields. o IPv4 Type of Service or IPv6 Traffic Class Fields.
o UDP Source Port. o UDP Source Port.
o UDP Destination Port. o UDP Destination Port.
This information MUST be provisioned per DetNet flow via This information MUST be provisioned per DetNet flow via
configuration, e.g., via the controller or management plane. configuration, e.g., via the controller or management plane.
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.
6. Security Considerations 6. Security Considerations
The security considerations of DetNet in general are discussed in The security considerations of DetNet in general are discussed in
[I-D.ietf-detnet-architecture] and [I-D.ietf-detnet-security]. MPLS [RFC8655] and [I-D.ietf-detnet-security]. MPLS and IP specific
and IP specific security considerations are described in security considerations are described in [I-D.ietf-detnet-mpls] and
[I-D.ietf-detnet-mpls] and [I-D.ietf-detnet-ip]. This draft does not [I-D.ietf-detnet-ip]. This draft does not have additional security
have additional security considerations. considerations.
7. IANA Considerations 7. IANA Considerations
This document makes no IANA requests. This document makes no IANA requests.
8. Acknowledgements 8. 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.
skipping to change at page 7, line 41 skipping to change at page 7, line 41
[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>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-6man-segment-routing-header] [I-D.ietf-6man-segment-routing-header]
Filsfils, C., Dukes, D., Previdi, S., Leddy, J., Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,
Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment
Routing Header (SRH)", draft-ietf-6man-segment-routing- Routing Header (SRH)", draft-ietf-6man-segment-routing-
header-24 (work in progress), October 2019. header-26 (work in progress), October 2019.
[I-D.ietf-detnet-architecture]
Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", draft-ietf-
detnet-architecture-13 (work in progress), May 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., 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-
detnet-security-05 (work in progress), August 2019. detnet-security-05 (work in progress), August 2019.
[RFC8655] Finn, N., Thubert, P., Varga, B., and J. Farkas,
"Deterministic Networking Architecture", RFC 8655,
DOI 10.17487/RFC8655, October 2019,
<https://www.rfc-editor.org/info/rfc8655>.
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
 End of changes. 22 change blocks. 
38 lines changed or deleted 39 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/