| MPLS Working Group | G. Mirsky |
| Internet-Draft | ZTE Corp. |
| Intended status: Standards Track | October 18, 2018 |
| Expires: April 21, 2019 |
Operations, Administration, and Maintenance for MPLS-SR over IP
draft-mirsky-mpls-oam-mpls-sr-ip-01
Segment routing uses source routing paradigm to traffic engineering by specifying segments a packet traverses through the network. MPLS Segment Routing applies that paradigm to an MPLS data plane-based networks. SR-MPLS over IP uses MPLS label stack as a source routing instruction set and uses IP encapsulation/tunneling such as MPLS-in- UDP as defined in RFC 7510 to realize a source routing mechanism across MPLS, IPv4, and IPv6 data planes. This document describes Operations, Administration, and Maintenance operations in SR-MPLS over IP environment.
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 21, 2019.
Copyright (c) 2018 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 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.
Segment routing [RFC8402] uses source routing paradigm to traffic engineering by specifying segments a packet traverses through the network. MPLS Segment Routing (SR-MPLS) [I-D.ietf-spring-segment-routing-mpls] applies that paradigm to an MPLS data plane-based networks. SR-MPLS over IP uses MPLS label stack as a source routing instruction set and uses IP encapsulation/tunneling such as MPLS-in- UDP as defined in [RFC7510] to realize a source routing mechanism across MPLS, IPv4, and IPv6 data planes. This document describes Operations, Administration, and Maintenance (OAM) operations in SR-MPLS over IP environment.
MPLS: Multiprotocol Label Switching
LSP: Label Switched Path
BFD: Bidirectional Forwarding Detection
SR Segment Routing
SR-MPLS Segment Routing in MPLS data plane
FEC: Forwarding Equivalence Class
G-ACh: Generic Associated Channel
ACH: Associated Channel Header
GAL: G-ACh Label
OAM Operations, Administration, and Maintenance
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
OAM operations support Fault Management and Performance Monitoring components of FCAPS framework for network management. To achieve its objectives, Fault Management OAM includes proactive and on-demand protocols to provide constant monitoring of the network to detect the failure in combination with on-demand tools to efficiently localize and characterize the defect. Performance Monitoring OAM protocols support measurement of packet loss and packet delay that enables calculation of performance metrics, e.g., packet loss ration, inter-packet delay variation, that are useful in monitoring the quality of service in the network, detect and quantify the service degradation.
Fault management OAM toolset includes protocols to perform on-demand failure detection and localization as well as proactively monitor path continuity. An example of the former is echo request/reply, e.g., Label Switched Path (LSP) Ping [RFC8029]. An example of the latter - Bidirectional Forwarding Detection (BFD) over MPLS LSP [RFC5884]. For SR-MPLS environment applicability and use of these OAM tools defined in [RFC8287] and [I-D.mirsky-spring-bfd] respectively. Both LSP Ping and BFD can be used either with IP/UDP encapsulation or in Generic Associated Channel (G-ACh) [RFC5586]. The use of IP/UDP encapsulation is well-understood and has been defined in [RFC8029]: [I-D.mirsky-mpls-p2mp-bfd] with its Value field containing one of the routable IP addresses of the sender.
Using the sender's routable address enables the receiver to send an echo reply or BFD control packets over the IP network. In some environments, the overhead of extra IP/UDP encapsulations may be considered as overburden and make to use more compact G-ACh encapsulation instead. In such a case, the OAM control packet MUST be immediately followed by the IP Address TLV
Performance monitoring in SR-MPLS over IP may be performed using mechanisms defined in [RFC6374].
This document does not introduce new security aspects but inherits all security considerations from [RFC8287], [RFC8029], [RFC5884], [I-D.mirsky-spring-bfd].
TBD.
TBD