draft-ietf-detnet-mpls-02.txt   draft-ietf-detnet-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: MPLS DetNet Data Plane: MPLS
draft-ietf-detnet-mpls-02 draft-ietf-detnet-mpls-03
Abstract Abstract
This document specifies the Deterministic Networking data plane when This document specifies the Deterministic Networking data plane when
operating over an MPLS Packet Switched Networks. operating over an MPLS Packet Switched Networks.
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 2, line 41 skipping to change at page 2, line 41
4.5.1. Edge Node Processing . . . . . . . . . . . . . . . . 19 4.5.1. Edge Node Processing . . . . . . . . . . . . . . . . 19
4.5.2. Relay Node Processing . . . . . . . . . . . . . . . . 19 4.5.2. Relay Node Processing . . . . . . . . . . . . . . . . 19
4.6. Forwarding Sub-Layer Considerations . . . . . . . . . . . 20 4.6. Forwarding Sub-Layer Considerations . . . . . . . . . . . 20
4.6.1. Class of Service . . . . . . . . . . . . . . . . . . 20 4.6.1. Class of Service . . . . . . . . . . . . . . . . . . 20
4.6.2. Quality of Service . . . . . . . . . . . . . . . . . 20 4.6.2. Quality of Service . . . . . . . . . . . . . . . . . 20
5. Management and Control Information Summary . . . . . . . . . 21 5. Management and Control Information Summary . . . . . . . . . 21
5.1. Service Sub-Layer Information Summary . . . . . . . . . . 21 5.1. Service Sub-Layer Information Summary . . . . . . . . . . 21
5.1.1. Service Aggregation Information Summary . . . . . . . 22 5.1.1. Service Aggregation Information Summary . . . . . . . 22
5.2. Forwarding Sub-Layer Information Summary . . . . . . . . 23 5.2. Forwarding Sub-Layer Information Summary . . . . . . . . 23
6. Security Considerations . . . . . . . . . . . . . . . . . . . 24 6. Security Considerations . . . . . . . . . . . . . . . . . . . 24
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 25
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 25
9.1. Normative References . . . . . . . . . . . . . . . . . . 25 9.1. Normative References . . . . . . . . . . . . . . . . . . 25
9.2. Informative References . . . . . . . . . . . . . . . . . 26 9.2. Informative References . . . . . . . . . . . . . . . . . 27
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29
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 General background and concepts of DetNet can be found in
[I-D.ietf-detnet-architecture]. [I-D.ietf-detnet-architecture].
skipping to change at page 22, line 20 skipping to change at page 22, line 20
values included 0, 16 and 28 bits. 0 bits cannot be used when PRF values included 0, 16 and 28 bits. 0 bits cannot be used when PRF
is configured for the service. is configured for the service.
o The S-Label for the service. o The S-Label for the service.
o If PRF is to be provided for the service. o If PRF is to be provided for the service.
o The forwarding sub-layer information associated with the output of o The forwarding sub-layer information associated with the output of
the service sub-layer. Note that when the PRF function is the service sub-layer. Note that when the PRF function is
provisioned, this information is per DetNet member flow. provisioned, this information is per DetNet member flow.
Logically this is a pointer to details provided below for Logically the forwarding sub-layer information is a pointer to
transmission of Detnet flows at the forwarding sub-layer. further details of transmission of Detnet flows at the forwarding
sub-layer.
The following summarizes the information that is needed on service The following summarizes the information that is needed on service
sub-layer aware nodes that receives DetNet MPLS traffic, on a per sub-layer aware nodes that receives DetNet MPLS traffic, on a per
service basis: service basis:
o The forwarding sub-layer information associated with the input of o The forwarding sub-layer information associated with the input of
the service sub-layer. Note that when the PEF function is the service sub-layer. Note that when the PEF function is
provisioned, this information is per DetNet member flow. provisioned, this information is per DetNet member flow.
Logically this is a pointer to details provided below related to Logically the forwarding sub-layer information is a pointer to
the reception of Detnet flows at the forwarding sub-layer or further details of the reception of Detnet flows at the forwarding
A-Label. sub-layer or A-Label.
o The S-Label for the received service. o The S-Label for the received service.
o If PEF or POF is to be provided for the service. o If PEF or POF is to be provided for the service.
o The sequence number length to be used for the service. Valid o The sequence number length to be used for the service. Valid
values included 0, 16 and 28 bits. 0 bits cannot be used when PEF values included 0, 16 and 28 bits. 0 bits cannot be used when PEF
or POF are configured for the service. or POF are configured for the service.
5.1.1. Service Aggregation Information Summary 5.1.1. Service Aggregation Information Summary
 End of changes. 8 change blocks. 
11 lines changed or deleted 12 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/