BGP Extensions for Enhanced VPN Auto Discovery
draft-zhuang-bess-enhanced-vpn-auto-discovery-06
INTERNET-DRAFT S. Zhuang
Intended status: Proposed Standard Z. Li
Huawei Technologies
D. Eastlake
Futurewei Technologies
L. Yong
Independent
Expires: January 12, 2021 July 13, 2020
BGP Extensions for Enhanced VPN Auto Discovery
draft-zhuang-bess-enhanced-vpn-auto-discovery-06.txt
Abstract
A variety of VPN technologies have been widely deployed to bear
different services. As new applications develop, a requirement has
been proposed for auto-discovery of Layer 3 Virtual Private Networks
(L3VPN) and enhanced auto-discovery requirements for other VPN
technologies that already have basic auto-discovery mechanisms.
This document identifies some possible applications of these auto-
discovery requirements and defines a new BGP NLRI, called the BGP-
VPN-INSTANCE NLRI, to satisfy the requirement for auto-discovery of
BGP VPN instances. It also defines a new type of extended community,
called the Import Route Target, which can be applied to auto-
discovery mechanisms of multiple VPN technologies.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Distribution of this document is unlimited. Comments should be sent
to the authors or the BESS working group mailing list: bess@ietf.org.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Zhuang, et al [Page 1]
INTERNET-DRAFT BGP Extensions For VPN AD
Table of Contents
1. Introduction............................................3
2. Terminologies...........................................4
3. Requirements of VPN Auto-Discovery......................5
3.1 Centralized Traffic Optimization.......................5
3.2 Label/Segment Allocation for VPN Instance..............5
4. IRT Extended Community..................................6
5. BGP Extensions for L3VPN Auto-Discovery.................7
5.1 BGP-VPN-INSTANCE SAFI..................................7
5.2 BGP-VPN-INSTANCE NLRI..................................8
5.2.1 VPN Membership A-D Route.............................8
5.3 Procedures............................................9
6. IANA Considerations....................................10
6.1 BGP Extended Communities..............................10
6.2 Subsequent Address Family Identifier..................10
7. Security Considerations................................11
Contributors..............................................11
Acknowledgements..........................................11
Normative References......................................12
Informative References....................................13
Authors' Addresses........................................14
Zhuang, et al [Page 2]
INTERNET-DRAFT BGP Extensions For VPN AD
1. Introduction
A variety of VPN technologies have been widely deployed to bear
different services. As new applications develop, a requirement has
been proposed for auto-discovery of Layer 3 Virtual Private Networks
(L3VPN) [RFC4364] and enhanced auto-discovery requirements for other
VPN technologies which already have basic auto-discovery mechanisms.
This document identifies some possible applications of these auto-
discovery requirements and defines a new BGP NLRI [RFC4271], called
the BGP-VPN-INSTANCE NLRI, to satisfy the requirement of auto-
discovery of BGP VPN instance. It also defines a new type of extended
community, called the Import Route Target (IRT), which can be applied
to auto-discovery mechanisms of multiple VPN technologies.
Zhuang, et al [Page 3]
Show full document text