MVPN and MSDP SA Interoperation
draft-ietf-bess-mvpn-msdp-sa-interoperation-00
BESS Z. Zhang
Internet-Draft L. Giuliano
Updates: 6514 (if approved) Juniper Networks
Intended status: Standards Track March 22, 2018
Expires: September 23, 2018
MVPN and MSDP SA Interoperation
draft-ietf-bess-mvpn-msdp-sa-interoperation-00
Abstract
This document specifies the procedures for interoperation between
MVPN Source Active routes and customer MSDP Source Active routes,
which is useful for MVPN provider networks offering services to
customers with an existing MSDP infrastructure. Without the
procedures described in this document, VPN-specific MSDP sessions are
required among the PEs that are customer MSDP peers.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC2119.
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 September 23, 2018.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
Zhang & Giuliano Expires September 23, 2018 [Page 1]
Internet-Draft mvpn-sa-msdp March 2018
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. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. MVPN RPT-SPT Mode . . . . . . . . . . . . . . . . . . . . 4
3. Specification . . . . . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Terminologies
Familiarity with MVPN and MSDP protocols and procedures is assumed.
Some terminologies are listed below for convenience.
o ASM: Any source multicast.
o SPT: Source-specific Shortest-path Tree.
o C-S: A multicast source address, identifying a multicast source
located at a VPN customer site.
o C-G: A multicast group address used by a VPN customer.
o C-RP: A multicast Rendezvous Point for a VPN customer.
o EC: Extended Community.
2. Introduction
Section "14. Supporting PIM-SM without Inter-Site Shared C-Trees" of
[RFC6514] specifies the procedures for MVPN PEs to discover (C-S,C-G)
via MVPN Source Active A-D routes and then send (C-S,C-G) C-multicast
routes towards the ingress PEs, to establish SPTs for customer ASM
flows for which they have downstream receivers. (C-*,C-G)
Zhang & Giuliano Expires September 23, 2018 [Page 2]
Internet-Draft mvpn-sa-msdp March 2018
C-multicast routes are not sent among the PEs so inter-site shared
C-Trees are not used and the method is generally referred to as "spt-
only" mode.
With this mode, the MVPN Source Active routes are functionally
similar to MSDP Source-Active messages [RFC3618]. One or more of the
PEs, say PE1, either act as a C-RP and learn of (C-S,C-G) via PIM
Register messages, or have MSDP sessions with some MSDP peers and
learn (C-S,C-G) via MSDP SA messages. In either case, PE1 will then
originate MVPN SA routes for other PEs to learn the (C-S,C-G).
[RFC6514] only specifies that a PE receiving the MVPN SA routes, say
Show full document text