DetNet Data Plane: MPLS over UDP/IP
draft-ietf-detnet-mpls-over-udp-ip-07
DetNet B. Varga, Ed.
Internet-Draft J. Farkas
Intended status: Standards Track Ericsson
Expires: April 14, 2021 L. Berger
LabN Consulting, L.L.C.
A. Malis
Malis Consulting
S. Bryant
Futurewei Technologies
October 11, 2020
DetNet Data Plane: MPLS over UDP/IP
draft-ietf-detnet-mpls-over-udp-ip-07
Abstract
This document specifies the MPLS Deterministic Networking data plane
operation and encapsulation over an IP network. The approach is
modeled on the operation of MPLS and over UDP/IP packet switched
networks.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 14, 2021.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Varga, et al. Expires April 14, 2021 [Page 1]
Internet-Draft DetNet MPLS over UDP/IP October 2020
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Terms Used in This Document . . . . . . . . . . . . . . . 3
2.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
2.3. Requirements Language . . . . . . . . . . . . . . . . . . 4
3. DetNet MPLS Operation over DetNet
IP PSNs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. DetNet Data Plane Procedures . . . . . . . . . . . . . . . . 5
5. Management and Control Information Summary . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Deterministic Networking (DetNet) is a service that can be offered by
a network to DetNet flows. DetNet provides these flows extremely low
packet loss rates and assured maximum end-to-end delivery latency.
General background and concepts of DetNet can be found in [RFC8655].
To carry DetNet MPLS flows with full functionality at the DetNet
layer over an IP network, the following components are required
(these are a subset of the requirements for MPLS encapsulation listed
in [I-D.ietf-detnet-mpls]):
1. A method for identifying DetNet flows to the processing element.
2. A method for carrying the DetNet sequence number.
3. A method for distinguishing DetNet OAM packets from DetNet data
packets.
4. A method for carrying queuing and forwarding indication.
Varga, et al. Expires April 14, 2021 [Page 2]
Internet-Draft DetNet MPLS over UDP/IP October 2020
These requirements are satisfied by the DetNet over MPLS
Encapsulation described in [I-D.ietf-detnet-mpls] and they are partly
satisfied (i.e., IP flows can be identified however no DetNet
Show full document text