LSP-Ping Mechanisms for EVPN and PBB-EVPN
draft-jain-bess-evpn-lsp-ping-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
BESS Workgroup P. Jain
Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track S. Boutros
Expires: May 25, 2017 VmWare, Inc.
S. Salam
Cisco Systems, Inc.
November 21, 2016
LSP-Ping Mechanisms for EVPN and PBB-EVPN
draft-jain-bess-evpn-lsp-ping-04
Abstract
LSP-Ping is a widely deployed Operation, Administration, and
Maintenance (OAM) mechanism in MPLS networks. This document
describes mechanisms for detecting data-plane failures using LSP Ping
in MPLS based EVPN and PBB-EVPN 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 http://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 May 25, 2017.
Copyright Notice
Copyright (c) 2016 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
Jain, et al. Expires May 25, 2017 [Page 1]
Internet-Draft MPLS OAM for EVPN November 2016
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Specification of Requirements . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Proposed Target FEC Stack Sub-TLVs . . . . . . . . . . . . . 3
4.1. EVPN MAC Sub-TLV . . . . . . . . . . . . . . . . . . . . 4
4.2. EVPN Inclusive Multicast Sub-TLV . . . . . . . . . . . . 4
4.3. EVPN Auto-Discovery Sub-TLV . . . . . . . . . . . . . . . 6
4.4. EVPN IP Prefix Sub-TLV . . . . . . . . . . . . . . . . . 6
5. Encapsulation of OAM Ping Packets . . . . . . . . . . . . . . 7
6. Operations . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Unicast Data-plane connectivity checks . . . . . . . . . 7
6.2. Inclusive Multicast Data-plane Connectivity Checks . . . 9
6.2.1. Ingress Replication . . . . . . . . . . . . . . . . . 9
6.2.2. Using P2MP P-tree . . . . . . . . . . . . . . . . . . 10
6.2.3. Controlling Echo Responses when using P2MP P-tree . . 11
6.3. EVPN Aliasing Data-plane connectivity check . . . . . . . 11
6.4. EVPN IP Prefix (RT-5) Data-plane connectivity check . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
[RFC7432] describes MPLS based Ethernet VPN (EVPN) technology. An
EVPN comprises CE(s) connected to PE(s). The PEs provide layer 2
EVPN among the CE(s) over the MPLS core infrastructure. In EVPN
networks, PEs advertise the MAC addresses learned from the locally
connected CE(s), along with MPLS Label, to remote PE(s) in the
control plane using multi-protocol BGP. EVPN enables multi-homing of
CE(s) connected to multiple PEs and load balancing of traffic to and
from multi-homed CE(s).
[RFC7623] describes the use of Provider Backbone Bridging [802.1ah]
Show full document text