Label Switched Path (LSP) Ping for Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6
RFC 6829
| Document | Type |
RFC - Proposed Standard
(January 2013; No errata)
Obsoleted by RFC 8029
Updates RFC 4379
|
|
|---|---|---|---|
| Authors | Mach Chen , Ping Pan , Carlos Pignataro , Rajiv Asati | ||
| Last updated | 2018-12-20 | ||
| Replaces | draft-chen-mpls-ipv6-pw-lsp-ping | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6829 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Adrian Farrel | ||
| IESG note | Loa Andersson (loa.andersson@ericsson.com) is the document shepherd. | ||
| Send notices to | (None) | ||
Internet Engineering Task Force (IETF) M. Chen
Request for Comments: 6829 Huawei Technologies Co., Ltd
Updates: 4379 P. Pan
Category: Standards Track Infinera
ISSN: 2070-1721 C. Pignataro
R. Asati
Cisco
January 2013
Label Switched Path (LSP) Ping for
Pseudowire Forwarding Equivalence Classes (FECs) Advertised over IPv6
Abstract
The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)
Ping and traceroute mechanisms are commonly used to detect and
isolate data-plane failures in all MPLS LSPs, including LSPs used for
each direction of an MPLS Pseudowire (PW). However, the LSP Ping and
traceroute elements used for PWs are not specified for IPv6 address
usage.
This document extends the PW LSP Ping and traceroute mechanisms so
they can be used with PWs that are set up and maintained using IPv6
LDP sessions. This document updates RFC 4379.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6829.
Chen, et al. Standards Track [Page 1]
RFC 6829 PW LSP Ping for IPv6 January 2013
Copyright Notice
Copyright (c) 2013 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
(http://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Pseudowire IPv4 Target FEC Stack Sub-TLVs . . . . . . . . . . . 3
3. Pseudowire IPv6 Target FEC Stack Sub-TLVs . . . . . . . . . . . 4
3.1. FEC 128 Pseudowire . . . . . . . . . . . . . . . . . . . . 4
3.2. FEC 129 Pseudowire . . . . . . . . . . . . . . . . . . . . 5
4. Summary of Changes . . . . . . . . . . . . . . . . . . . . . . 6
5. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . . 7
1. Introduction
Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Ping
and traceroute are defined in [RFC4379]. These mechanisms can be
used to detect data-plane failures in all MPLS LSPs, including
Pseudowires (PWs). However, the PW LSP Ping and traceroute elements
are not specified for IPv6 address usage.
Specifically, the PW Forwarding Equivalence Class (FEC) sub-TLVs for
the Target FEC Stack in the LSP Ping and traceroute mechanism are
defined only for IPv4 Provider Edge (PE) routers and are not
applicable for the case where PEs use IPv6 addresses. Three PW-
related Target FEC sub-TLVs are currently defined (FEC 128
Pseudowire-Deprecated, FEC 128 Pseudowire-Current, and FEC 129
Pseudowire, see Sections 3.2.8 through 3.2.10 of [RFC4379]). These
sub-TLVs contain the source and destination addresses of the LDP
session, and currently only an IPv4 LDP session is covered. Despite
Chen, et al. Standards Track [Page 2]
RFC 6829 PW LSP Ping for IPv6 January 2013
the fact that the PE IP address family is not explicit in the sub-TLV
definition, this can be inferred indirectly by examining the lengths
of the Sender's/Remote PE Address fields or calculating the length of
Show full document text