draft-ietf-detnet-ip-over-mpls-02.txt   draft-ietf-detnet-ip-over-mpls-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
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
October 16, 2019 October 27, 2019
DetNet Data Plane: IP over MPLS DetNet Data Plane: IP over MPLS
draft-ietf-detnet-ip-over-mpls-02 draft-ietf-detnet-ip-over-mpls-03
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 39
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 5, line 13 skipping to change at page 5, line 13
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
An example use of DetNet IP over DetNet MPLS is presented here. An example use of DetNet IP over DetNet MPLS is presented here.
Figure 1 illustrated DetNet enabled End Systems (hosts), connected to Figure 1 illustrated DetNet enabled End Systems (hosts), connected to
DetNet (DN) enabled IP networks, operating over a DetNet aware MPLS DetNet (DN) enabled IP networks, operating over a DetNet aware MPLS
network. iUsing this figure we can have a case where the Relay nodes network. Using this figure we can have a case where the Relay nodes
act as T-PEs and sit at the boundary of the MPLS domain since the act as T-PEs and sit at the boundary of the MPLS domain since the
non-MPLS domain is DetNet aware. This case is very similar to the non-MPLS domain is DetNet aware. This case is very similar to the
DetNet MPLS Network figure 2 in [I-D.ietf-detnet-mpls]. However in DetNet MPLS Network figure 2 in [I-D.ietf-detnet-mpls]. However in
[I-D.ietf-detnet-mpls] figure 2 the T-PEs are located at the end [I-D.ietf-detnet-mpls] figure 2 the T-PEs are located at the end
syetem and MPLS spans the whole DetNet service. The primary system and MPLS spans the whole DetNet service. The primary
difference in this document is that the Relay nodes are at the edges difference in this document is that the Relay nodes are at the edges
of the MPLS domain and therefore function as T-PEs, and that iMPLS of the MPLS domain and therefore function as T-PEs, and that MPLS
service sub-layer functions are not provided over the DetNet IP service sub-layer functions are not provided over the DetNet IP
network. The transit node functions show above are identical to network. The transit node functions show above are identical to
those described in [I-D.ietf-detnet-mpls]. those described in [I-D.ietf-detnet-mpls].
Figure 2 illustrates how relay nodes can provide service protection Figure 2 illustrates how relay nodes can provide service protection
over an MPLS domain. In this case, CE1 and CE2 are IP DetNet end over an MPLS domain. In this case, CE1 and CE2 are IP DetNet end
systems which are interconnected via a MPLS domain such as described systems which are interconnected via a MPLS domain such as described
in [I-D.ietf-detnet-mpls]. Note that R1 and R3 sit at the edges of in [I-D.ietf-detnet-mpls]. Note that R1 and R3 sit at the edges of
an MPLS domain and therefore are similar to T-PEs, while R2 sits in an MPLS domain and therefore are similar to T-PEs, while R2 sits in
the middle of the domain and is therefore similar to an S-PE. the middle of the domain and is therefore similar to an S-PE.
skipping to change at page 6, line 30 skipping to change at page 6, line 30
| | | |
|<-------------- 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: DetNet IP Over DetNet MPLS Network
Figure 1 illustrates DetNet enabled End Systems (hosts), connected to Figure 1 illustrates DetNet enabled End Systems, connected to DetNet
DetNet (DN) enabled MPLS network. A similar situation occurs when (DN) enabled MPLS network. A similar situation occurs when end
end systems are are not DetNet aware. In this case, edge nodes sit systems are are not DetNet aware. In this case, edge nodes sit at
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
operation, particularly when distributed control plane protocols are operation, particularly when distributed control plane protocols are
used. used.
It is still possible to provided DetNet service protection for non- It is still possible to provided DetNet service protection for non-
DetNet aware end systems. case is basically the same as Figure 2, DetNet aware end systems. This case is basically the same as
with the exception that CE1 and CE2 are non-DetNet aware end systems Figure 2, with the exception that CE1 and CE2 are non-DetNet aware
and R1 and R3 become edge nodes. end systems and R1 and R3 become edge nodes.
4.2. DetNet IP over DetNet MPLS Encapsulation 4.2. DetNet IP over DetNet MPLS Encapsulation
The basic encapsulation approach is to treat a DetNet IP flow as an The basic encapsulation approach is to treat a DetNet IP flow as an
app-flow from the DetNet MPLS perspective. The corresponding example app-flow from the DetNet MPLS perspective. The corresponding example
DetNet Sub-Network format is shown in Figure 3. DetNet Sub-Network format is shown in Figure 3.
/-> +------+ +------+ +------+ ^ ^ /-> +------+ +------+ +------+ ^ ^
| | X | | X | | X |<- App-Flow : : | | X | | X | | X |<- App-Flow : :
| +------+ +------+ +------+ : : | +------+ +------+ +------+ : :
skipping to change at page 7, line 27 skipping to change at page 7, line 27
+------+ +------+ +------+ +------+ +------+ +------+
| IP | | IP |
+------+ +------+
| 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 the figure, "App-Flow" indicates the payload carried by the DetNet In Figure 3 "App-Flow" indicates the payload carried by the DetNet IP
IP data plane. "IP" and "NProto" indicate the fields described in data plane. "IP" and "NProto" indicate the fields described in
Section 7.1.1. IP Header Information and Section 7.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 in [I-D.ietf-detnet-ip], respectively.
"MPLS App-Flow" indicates that an individual DetNet IP flow is the "App-Flow for MPLS" indicates that an individual DetNet IP flow is
payload from the perspective of the DetNet MPLS data plane defined in the payload from the perspective of the DetNet MPLS data plane
[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 [I-D.ietf-detnet-mpls], the DetNet MPLS data plane uses a single
S-Label to support a single app flow. Section 7.1. DetNet IP Flow S-Label to support a single app flow. Section 5.1. DetNet IP Flow
Identification Procedures in [I-D.ietf-detnet-ip] states that a Identification Procedures in [I-D.ietf-detnet-ip] states that a
single DetNet flow is identified based on IP, and next level single DetNet flow is identified based on IP, and next level
protocol, header information. Section 7.4. Aggregation protocol, header information. Section 4.4. Aggregation
Considerations in [I-D.ietf-detnet-ip] defines that aggregation is Considerations in [I-D.ietf-detnet-ip] defines the ways in which
supported through the use of prefixes, wildcards, lists, and port aggregation is supported through the use of prefixes, wildcards,
ranges. Collectively, this results in the fairly straight forward lists, and port ranges. Collectively, this results in the fairly
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.
Mapping of IP to the MPLS Detnet is similar for IP Detnet flows and Mapping of IP to DetNet MPLS is similar for DetNet IP flows and IP
IP flows. The six-tuple of IP is mapped to the S-Label in both flows. The six-tuple of IP is mapped to the S-Label in both cases.
cases. The various fields may be mapped or ignored when going from The various fields may be mapped or ignored when going from IP to
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 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 Section 6.1. PRF MAY be supported at the MPLS level for DetNet IP
skipping to change at page 8, line 36 skipping to change at page 8, line 36
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 7.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 PEOF 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 an provisioned via configuration or the controller plane. When a DetNet
DetNet IP flow is sent over DetNet MPLS, a DetNet relay node MUST IP flow is sent over DetNet MPLS, a DetNet relay node MUST ensure
ensure that the provisioned DetNet IP traffic treatment is provided that the provisioned DetNet IP traffic treatment is provided at the
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.
Traffic treatment for DetNet IP flows received over the DetNet MPLS Traffic treatment for DetNet IP flows received over the DetNet MPLS
data plane MUST follow Section 7.3 DetNet IP Traffic Treatment data plane MUST follow Section 5.3 DetNet IP Traffic Treatment
Procedures in [I-D.ietf-detnet-ip]. Procedures in [I-D.ietf-detnet-ip].
6. Management and Control Information Summary 6. 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
support DetNet IP over DetNet MPLS at the MPLS ingress node: support DetNet IP over DetNet MPLS at the MPLS ingress node:
o Each MPLS App-Flow is identified using the IP flow identification o Each MPLS App-Flow is identified using the IP flow identification
information as defined in [I-D.ietf-detnet-ip]. The information information as defined in [I-D.ietf-detnet-ip]. The information
is summarized in Section 6 of that document, and includes all is summarized in Section 5.1 of that document, and includes all
wildcards, port ranges and ability to ignore specific IP fields. wildcards, port ranges and the ability to ignore specific IP
fields.
o The DetNet MPLS service that is to be used to send the matching IP o The DetNet MPLS service that is to be used to send the matching IP
traffic. Logically this is a pointer to the information provided traffic. This matching information is provided in
in [I-D.ietf-detnet-mpls] Section 5.1, and includes both service [I-D.ietf-detnet-mpls] Section 5.1, and includes both service and
and traffic delivery information. traffic delivery information.
The following summarizes the set of information that is needed to The following summarizes the set of information that is needed to
support DetNet IP over DetNet MPLS at the MPLS egress node: support DetNet IP over DetNet MPLS at the MPLS egress node:
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
 End of changes. 20 change blocks. 
42 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/