Naming the Protocol specified RFC 8029
draft-andersson-mpls-rfc8029-lsp-ping-naming-01
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Loa Andersson , Mach Chen , Carlos Pignataro | ||
| Last updated | 2024-11-20 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-andersson-mpls-rfc8029-lsp-ping-naming-01
MPLS WG L. Andersson
Internet-Draft Bronze Dragon Consulting
Updates: 8029 (if approved) M. Chen
Intended status: Informational Huawei Technologies
Expires: 24 May 2025 C. Pignataro
Blue Fern Consulting
20 November 2024
Naming the Protocol specified RFC 8029
draft-andersson-mpls-rfc8029-lsp-ping-naming-01
Abstract
RFC 8029 specifies the key MPLS Operation, Administration, and
Maintenance protocol, sometimes referred to MPLS Label Switched Path
(LSP) Ping, or MPLS LSP Ping.
Howerver, the actual name of the protocol have never been explicitly
specified or documented. This document corrects that omission.
This document updates RFC 8029.
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 24 May 2025.
Copyright Notice
Copyright (c) 2024 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.
Andersson, et al. Expires 24 May 2025 [Page 1]
Internet-Draft LSP Ping Naming November 2024
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 Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Protocol Name . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3
5.1. Normative References . . . . . . . . . . . . . . . . . . 3
5.2. Informative References . . . . . . . . . . . . . . . . . 3
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3
1. Background
RFC 8029 [RFC8029] specifies the basis for the main MPLS Operation,
Administration, and Maintenance (OAM) protocol. The title of the
RFCs is "Detecting Multiprotocol Label Switching (MPLS) Data-Plane
Failures".
The title correctly captures what the protocol does, but not what the
protocol is called.
RFC 8029 defines two modes for the protocol it specifies, Ping and
Traceroute respectively.
RFC 8611 [RFC8611] talks about "MPLS Ping" and "MPLS Ping and
Traceroute" interchangeably, when referring to RFC 8029.
The MPLS Working Group Charter (https://datatracker.ietf.org/doc/
charter-ietf-mpls/ (https://datatracker.ietf.org/doc/charter-ietf-
mpls/)) talks about "LSP Ping" as one of the MPLS key protocols.
Other working groups, e.g. PALS, and BESS have documents citing RFC
8029. However, the name(s) used to reference RFC 8029 are not
consistent.
2. Protocol Name
The following paragraph is now added to Section 1.1 "Conventions" in
RFC 8029 as the second paragraph.
The protocol defined in this RFC 80929 [RFC8029] is called "MPLS
Label Switched Path (LSP) Ping and Traceroute", AKA MPLS LSP Ping.
Andersson, et al. Expires 24 May 2025 [Page 2]
Internet-Draft LSP Ping Naming November 2024
Whenever a document refers to either "MPLS Label Switched Path Ping
and Traceroute", "MPLS LSP Ping" or "LSP Ping" they refer to the
protocol specified in RFC 8029 [RFC8029]. When there is a specific
text refering to lsp ping or traceroute, they refer to modes of
operation.
3. IANA Considerations
This document does not make any IANA requests.
Note to the RFC Editor: Please remove this section before
publication.
4. Security Considerations
This document names the protocol that is specified in RFC 8029, and
thus does not introduce an new security risks.
5. References
5.1. Normative References
[RFC8029] Kompella, K., Swallow, G., Pignataro, C., Ed., Kumar, N.,
Aldrin, S., and M. Chen, "Detecting Multiprotocol Label
Switched (MPLS) Data-Plane Failures", RFC 8029,
DOI 10.17487/RFC8029, March 2017,
<https://www.rfc-editor.org/rfc/rfc8029>.
5.2. Informative References
[RFC8611] Akiya, N., Swallow, G., Litkowski, S., Decraene, B.,
Drake, J., and M. Chen, "Label Switched Path (LSP) Ping
and Traceroute Multipath Support for Link Aggregation
Group (LAG) Interfaces", RFC 8611, DOI 10.17487/RFC8611,
June 2019, <https://www.rfc-editor.org/rfc/rfc8611>.
Authors' Addresses
Loa Andersson
Bronze Dragon Consulting
Email: loa@pi.nu
Mach Chen
Huawei Technologies
Email: mach.chen@huawei.com
Andersson, et al. Expires 24 May 2025 [Page 3]
Internet-Draft LSP Ping Naming November 2024
Carlos Pignataro
Blue Fern Consulting
Email: cpignata@gmail.com
Andersson, et al. Expires 24 May 2025 [Page 4]