Multicast in L3VPNs Signaled by EVPN SAFI
draft-zzhang-bess-mcast-in-evpn-signaled-l3vpn-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-07-08
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
htmlized
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 Z. Zhang
Internet-Draft W. Lin
Intended status: Standards Track Juniper Networks
Expires: January 9, 2020 J. Rabadan
Nokia
July 8, 2019
Multicast in L3VPNs Signaled by EVPN SAFI
draft-zzhang-bess-mcast-in-evpn-signaled-l3vpn-00
Abstract
[ietf-bess-evpn-prefix-advertisement] specifies an EVPN SAFI Type-5
route that can be used to signal L3VPNs. This document specifies
procedures for multicast in such an L3VPN.
Requirements Language
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.
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 January 9, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Zhang, et al. Expires January 9, 2020 [Page 1]
Internet-Draft mvpn-with-evpn-safi July 2019
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.
Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Optimized Inter-Subnet Multicast for EVPN . . . . . . . . 3
2.2. Using [RFC6514] Procedures . . . . . . . . . . . . . . . 4
2.3. Adapted [RFC6514] Procedures . . . . . . . . . . . . . . 4
3. Specifications . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Normative References . . . . . . . . . . . . . . . . . . 5
5.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Terminology
It is expected that audience is familiar with EVPN and MVPN concepts
and terminologies. For convenience, the following terms are briefly
explained.
o PMSI: P-Multicast Service Interface - a conceptual interface for a
PE to send customer multicast traffic to all or some PEs in the
same VPN.
o I-PMSI: Inclusive PMSI - to all PEs in the same VPN.
o S-PMSI: Selective PMSI - to some of the PEs in the same VPN.
o Leaf A-D routes: For explicit leaf tracking purpose. Triggered by
S-PMSI A-D routes and targeted at triggering route's originator.
o IMET A-D route: Inclusive Multicast Ethernet Tag A-D route. The
EVPN equivalent of MVPN Intra-AS I-PMSI A-D route.
o SMET A-D route: Selective Multicast Ethernet Tag A-D route. The
EVPN equivalent of MVPN Leaf A-D route but unsolicited and
untargeted.
Zhang, et al. Expires January 9, 2020 [Page 2]
Internet-Draft mvpn-with-evpn-safi July 2019
2. Introduction
Traditionally, an L3VPN is signaled with BGP "MPLS-labeled VPN
address" SAFI and uses MPLS as provider tunnel as specified in
[RFC4364>]. Multicast support in such an L3VPN is specified in
[RFC6513] and [RFC6514].
[ietf-bess-evpn-prefix-advertisement] specifies another way of
signaling L3VPN via EVPN SAFI Type-5 routes for two reasons:
Show full document text