draft-ietf-bess-virtual-subnet-00.txt   draft-ietf-bess-virtual-subnet-01.txt 
Network Working Group X. Xu Network Working Group X. Xu
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Informational R. Raszuk Intended status: Informational R. Raszuk
Expires: December 3, 2015 Mirantis Inc. Expires: April 11, 2016 Mirantis Inc.
C. Jacquenet C. Jacquenet
Orange Orange
T. Boyes T. Boyes
Bloomberg LP Bloomberg LP
B. Fee B. Fee
Extreme Networks Extreme Networks
June 1, 2015 October 9, 2015
Virtual Subnet: A BGP/MPLS IP VPN-based Subnet Extension Solution Virtual Subnet: A BGP/MPLS IP VPN-based Subnet Extension Solution
draft-ietf-bess-virtual-subnet-00 draft-ietf-bess-virtual-subnet-01
Abstract Abstract
This document describes a BGP/MPLS IP VPN-based subnet extension This document describes a BGP/MPLS IP VPN-based subnet extension
solution referred to as Virtual Subnet, which can be used for solution referred to as Virtual Subnet, which can be used for
building Layer3 network virtualization overlays within and/or between building Layer3 network virtualization overlays within and/or between
data centers. data centers.
Status of This Memo Status of This Memo
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 3, 2015. This Internet-Draft will expire on April 11, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 8 skipping to change at page 5, line 8
2. Terminology 2. Terminology
This memo makes use of the terms defined in [RFC4364]. This memo makes use of the terms defined in [RFC4364].
3. Solution Description 3. Solution Description
3.1. Unicast 3.1. Unicast
3.1.1. Intra-subnet Unicast 3.1.1. Intra-subnet Unicast
+--------------------+ +--------------------+
+-----------------+ | | +-----------------+ +------------------+ | | +------------------+
|VPN_A:10.1.1.1/24| | | |VPN_A:10.1.1.1/24| |VPN_A:192.0.2.1/24| | | |VPN_A:192.0.2.1/24|
| \ | | | | / | | \ | | | | / |
| +------+ \++---+-+ +-+---++/ +------+ | | +------+ \ ++---+-+ +-+---++/ +------+ |
| |Host A+----+ PE-1 | | PE-2 +----+Host B| | | |Host A+-----+ PE-1 | | PE-2 +----+Host B| |
| +------+\ ++-+-+-+ +-+-+-++ /+------+ | | +------+\ ++-+-+-+ +-+-+-++ /+------+ |
| 10.1.1.2/24 | | | | | | 10.1.1.3/24 | | 192.0.2.2/24 | | | | | | 192.0.2.3/24 |
| | | | | | | | | | | | | | | |
| DC West | | | IP/MPLS Backbone | | | DC East | | DC West | | | IP/MPLS Backbone | | | DC East |
+-----------------+ | | | | +-----------------+ +------------------+ | | | | +------------------+
| +--------------------+ | | +--------------------+ |
| | | |
VRF_A : V VRF_A : V VRF_A : V VRF_A : V
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol|
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.1/32 |127.0.0.1| Direct | |10.1.1.1/32 |127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.2/32 |10.1.1.2 | Direct | |10.1.1.2/32 | PE-1 | IBGP | |192.0.2.2/32|192.0.2.2| Direct | |192.0.2.2/32| PE-1 | IBGP |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.3/32 | PE-2 | IBGP | |10.1.1.3/32 |10.1.1.3 | Direct | |192.0.2.3/32| PE-2 | IBGP | |192.0.2.3/32|192.0.2.3| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.0/24 |10.1.1.1 | Direct | |10.1.1.0/24 |10.1.1.1 | Direct | |192.0.2.0/24|192.0.2.1| Direct | |192.0.2.0/24|192.0.2.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
Figure 1: Intra-subnet Unicast Example Figure 1: Intra-subnet Unicast Example
As shown in Figure 1, two CE hosts (i.e., Hosts A and B) belonging to As shown in Figure 1, two CE hosts (i.e., Hosts A and B) belonging to
the same subnet (i.e., 10.1.1.0/24) are located at different data the same subnet (i.e., 192.0.2.0/24) are located at different data
centers (i.e., DC West and DC East) respectively. PE routers (i.e., centers (i.e., DC West and DC East) respectively. PE routers (i.e.,
PE-1 and PE-2) which are used for interconnecting these two data PE-1 and PE-2) which are used for interconnecting these two data
centers create host routes for their own local CE hosts respectively centers create host routes for their own local CE hosts respectively
and then advertise them via the BGP/MPLS IP VPN signaling. and then advertise them via the BGP/MPLS IP VPN signaling.
Meanwhile, ARP proxy is enabled on VRF attachment circuits of these Meanwhile, ARP proxy is enabled on VRF attachment circuits of these
PE routers. PE routers.
Now assume host A sends an ARP request for host B before Now assume host A sends an ARP request for host B before
communicating with host B. Upon receiving the ARP request, PE-1 communicating with host B. Upon receiving the ARP request, PE-1
acting as an ARP proxy returns its own MAC address as a response. acting as an ARP proxy returns its own MAC address as a response.
Host A then sends IP packets for host B to PE-1. PE-1 tunnels such Host A then sends IP packets for host B to PE-1. PE-1 tunnels such
packets towards PE-2 which in turn forwards them to host B. Thus, packets towards PE-2 which in turn forwards them to host B. Thus,
hosts A and B can communicate with each other as if they were located hosts A and B can communicate with each other as if they were located
within the same subnet. within the same subnet.
3.1.2. Inter-subnet Unicast 3.1.2. Inter-subnet Unicast
+--------------------+ +--------------------+
+-----------------+ | | +-----------------+ +------------------+ | | +------------------+
|VPN_A:10.1.1.1/24| | | |VPN_A:10.1.1.1/24| |VPN_A:192.0.2.1/24| | | |VPN_A:192.0.2.1/24|
| \ | | | | / | | \ | | | | / |
| +------+ \++---+-+ +-+---++/ +------+ | | +------+ \ ++---+-+ +-+---++/ +------+ |
| |Host A+------+ PE-1 | | PE-2 +-+----+Host B| | | |Host A+-------+ PE-1 | | PE-2 +-+----+Host B| |
| +------+\ ++-+-+-+ +-+-+-++ | /+------+ | | +------+\ ++-+-+-+ +-+-+-++ | /+------+ |
| 10.1.1.2/24 | | | | | | | 10.1.1.3/24 | | 192.0.2.2/24 | | | | | | | 192.0.2.3/24 |
| GW=10.1.1.4 | | | | | | | GW=10.1.1.4 | | GW=192.0.2.4 | | | | | | | GW=192.0.2.4 |
| | | | | | | | +------+ | | | | | | | | | +------+ |
| | | | | | | +----+ GW +--| | | | | | | | +----+ GW +-- |
| | | | | | | /+------+ | | | | | | | | /+------+ |
| | | | | | | 10.1.1.4/24 | | | | | | | | 192.0.2.4/24 |
| | | | | | | | | | | | | | | |
| DC West | | | IP/MPLS Backbone | | | DC East | | DC West | | | IP/MPLS Backbone | | | DC East |
+-----------------+ | | | | +-----------------+ +------------------+ | | | | +------------------+
| +--------------------+ | | +--------------------+ |
| | | |
VRF_A : V VRF_A : V VRF_A : V VRF_A : V
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol|
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.1/32 |127.0.0.1| Direct | |10.1.1.1/32 |127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.2/32 |10.1.1.2 | Direct | |10.1.1.2/32 | PE-1 | IBGP | |192.0.2.2/32|192.0.2.2| Direct | |192.0.2.2/32| PE-1 | IBGP |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.3/32 | PE-2 | IBGP | |10.1.1.3/32 |10.1.1.3 | Direct | |192.0.2.3/32| PE-2 | IBGP | |192.0.2.3/32|192.0.2.3| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.4/32 | PE-2 | IBGP | |10.1.1.4/32 |10.1.1.4 | Direct | |192.0.2.4/32| PE-2 | IBGP | |192.0.2.4/32|192.0.2.4| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.0/24 |10.1.1.1 | Direct | |10.1.1.0/24 |10.1.1.1 | Direct | |192.0.2.0/24|192.0.2.1| Direct | |192.0.2.0/24|192.0.2.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| 0.0.0.0/0 | PE-2 | IBGP | | 0.0.0.0/0 |10.1.1.4 | Static | | 0.0.0.0/0 | PE-2 | IBGP | | 0.0.0.0/0 |192.0.2.4| Static |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
Figure 2: Inter-subnet Unicast Example (1) Figure 2: Inter-subnet Unicast Example (1)
As shown in Figure 2, only one data center (i.e., DC East) is As shown in Figure 2, only one data center (i.e., DC East) is
deployed with a default gateway (i.e., GW). PE-2 which is connected deployed with a default gateway (i.e., GW). PE-2 which is connected
to GW would either be configured with or learn from GW a default to GW would either be configured with or learn from GW a default
route with next-hop being pointed to GW. Meanwhile, this route is route with next-hop being pointed to GW. Meanwhile, this route is
distributed to other PE routers (i.e., PE-1) as per normal [RFC4364] distributed to other PE routers (i.e., PE-1) as per normal [RFC4364]
operation. Assume host A sends an ARP request for its default operation. Assume host A sends an ARP request for its default
gateway (i.e., 10.1.1.4) prior to communicating with a destination gateway (i.e., 192.0.2.4) prior to communicating with a destination
host outside of its subnet. Upon receiving this ARP request, PE-1 host outside of its subnet. Upon receiving this ARP request, PE-1
acting as an ARP proxy returns its own MAC address as a response. acting as an ARP proxy returns its own MAC address as a response.
Host A then sends a packet for Host B to PE-1. PE-1 tunnels such Host A then sends a packet for Host B to PE-1. PE-1 tunnels such
packet towards PE-2 according to the default route learnt from PE-2, packet towards PE-2 according to the default route learnt from PE-2,
which in turn forwards that packet to GW. which in turn forwards that packet to GW.
+--------------------+ +--------------------+
+-----------------+ | | +-----------------+ +------------------+ | | +------------------+
|VPN_A:10.1.1.1/24| | | |VPN_A:10.1.1.1/24| |VPN_A:192.0.2.1/24| | | |VPN_A:192.0.2.1/24|
| \ | | | | / | | \ | | | | / |
| +------+ \++---+-+ +-+---++/ +------+ | | +------+ \ ++---+-+ +-+---++/ +------+ |
| |Host A+----+-+ PE-1 | | PE-2 +-+----+Host B| | | |Host A+----+--+ PE-1 | | PE-2 +-+----+Host B| |
| +------+\ | ++-+-+-+ +-+-+-++ | /+------+ | | +------+\ | ++-+-+-+ +-+-+-++ | /+------+ |
| 10.1.1.2/24 | | | | | | | | 10.1.1.3/24 | | 192.0.2.2/24 | | | | | | | | 192.0.2.3/24 |
| GW=10.1.1.4 | | | | | | | | GW=10.1.1.4 | | GW=192.0.2.4 | | | | | | | | GW=192.0.2.4 |
| +------+ | | | | | | | | +------+ | | +------+ | | | | | | | | +------+ |
|--+ GW-1 +----+ | | | | | | +----+ GW-2 +--| |--+ GW-1 +----+ | | | | | | +----+ GW-2 +-- |
| +------+\ | | | | | | /+------+ | | +------+\ | | | | | | /+------+ |
| 10.1.1.4/24 | | | | | | 10.1.1.4/24 | | 192.0.2.4/24 | | | | | | 192.0.2.4/24 |
| | | | | | | | | | | | | | | |
| DC West | | | IP/MPLS Backbone | | | DC East | | DC West | | | IP/MPLS Backbone | | | DC East |
+-----------------+ | | | | +-----------------+ +------------------+ | | | | +------------------+
| +--------------------+ | | +--------------------+ |
| | | |
VRF_A : V VRF_A : V VRF_A : V VRF_A : V
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol|
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.1/32 |127.0.0.1| Direct | |10.1.1.1/32 |127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.2/32 |10.1.1.2 | Direct | |10.1.1.2/32 | PE-1 | IBGP | |192.0.2.2/32|192.0.2.2| Direct | |192.0.2.2/32| PE-1 | IBGP |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.3/32 | PE-2 | IBGP | |10.1.1.3/32 |10.1.1.3 | Direct | |192.0.2.3/32| PE-2 | IBGP | |192.0.2.3/32|192.0.2.3| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.4/32 |10.1.1.4 | Direct | |10.1.1.4/32 |10.1.1.4 | Direct | |192.0.2.4/32|192.0.2.4| Direct | |192.0.2.4/32|192.0.2.4| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.0/24 |10.1.1.1 | Direct | |10.1.1.0/24 |10.1.1.1 | Direct | |192.0.2.0/24|192.0.2.1| Direct | |192.0.2.0/24|192.0.2.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| 0.0.0.0/0 |10.1.1.4 | Static | | 0.0.0.0/0 |10.1.1.4 | Static | | 0.0.0.0/0 |192.0.2.4| Static | | 0.0.0.0/0 |192.0.2.4| Static |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
Figure 3: Inter-subnet Unicast Example (2) Figure 3: Inter-subnet Unicast Example (2)
As shown in Figure 3, in the case where each data center is deployed As shown in Figure 3, in the case where each data center is deployed
with a default gateway, CE hosts will get ARP responses directly from with a default gateway, CE hosts will get ARP responses directly from
their local default gateways, rather than from their local PE routers their local default gateways, rather than from their local PE routers
when sending ARP requests for their default gateways. when sending ARP requests for their default gateways.
+------+ +------+
+------+ PE-3 +------+ +------+ PE-3 +------+
+-----------------+ | +------+ | +-----------------+ +------------------+ | +------+ | +------------------+
|VPN_A:10.1.1.1/24| | | |VPN_A:10.1.1.1/24| |VPN_A:192.0.2.1/24| | | |VPN_A:192.0.2.1/24|
| \ | | | | / | | \ | | | | / |
| +------+ \++---+-+ +-+---++/ +------+ | | +------+ \ ++---+-+ +-+---++/ +------+ |
| |Host A+------+ PE-1 | | PE-2 +------+Host B| | | |Host A+-------+ PE-1 | | PE-2 +------+Host B| |
| +------+\ ++-+-+-+ +-+-+-++ /+------+ | | +------+\ ++-+-+-+ +-+-+-++ /+------+ |
| 10.1.1.2/24 | | | | | | 10.1.1.3/24 | | 192.0.2.2/24 | | | | | | 192.0.2.3/24 |
| GW=10.1.1.1 | | | | | | GW=10.1.1.1 | | GW=192.0.2.1 | | | | | | GW=192.0.2.1 |
| | | | | | | | | | | | | | | |
| DC West | | | IP/MPLS Backbone | | | DC East | | DC West | | | IP/MPLS Backbone | | | DC East |
+-----------------+ | | | | +-----------------+ +------------------+ | | | | +------------------+
| +--------------------+ | | +--------------------+ |
| | | |
VRF_A : V VRF_A : V VRF_A : V VRF_A : V
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol| | Prefix | Nexthop |Protocol|
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.1/32 |127.0.0.1| Direct | |10.1.1.1/32 |127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct | |192.0.2.1/32|127.0.0.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.2/32 |10.1.1.2 | Direct | |10.1.1.2/32 | PE-1 | IBGP | |192.0.2.2/32|192.0.2.2| Direct | |192.0.2.2/32| PE-1 | IBGP |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.3/32 | PE-2 | IBGP | |10.1.1.3/32 |10.1.1.3 | Direct | |192.0.2.3/32| PE-2 | IBGP | |192.0.2.3/32|192.0.2.3| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
|10.1.1.0/24 |10.1.1.1 | Direct | |10.1.1.0/24 |10.1.1.1 | Direct | |192.0.2.0/24|192.0.2.1| Direct | |192.0.2.0/24|192.0.2.1| Direct |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
| 0.0.0.0/0 | PE-3 | IBGP | | 0.0.0.0/0 | PE-3 | IBGP | | 0.0.0.0/0 | PE-3 | IBGP | | 0.0.0.0/0 | PE-3 | IBGP |
+------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+ +------------+---------+--------+
Figure 4: Inter-subnet Unicast Example (3) Figure 4: Inter-subnet Unicast Example (3)
Alternatively, as shown in Figure 4, PE routers themselves could be Alternatively, as shown in Figure 4, PE routers themselves could be
directly configured as default gateways of their locally connected CE directly configured as default gateways of their locally connected CE
hosts as long as these PE routers have routes for outside networks. hosts as long as these PE routers have routes for outside networks.
3.2. Multicast 3.2. Multicast
skipping to change at page 12, line 38 skipping to change at page 12, line 38
This document doesn't introduce additional security risk to BGP/MPLS This document doesn't introduce additional security risk to BGP/MPLS
IP VPN, nor does it provide any additional security feature for BGP/ IP VPN, nor does it provide any additional security feature for BGP/
MPLS IP VPN. MPLS IP VPN.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC0925] Postel, J., "Multi-LAN address resolution", RFC 925, [RFC0925] Postel, J., "Multi-LAN address resolution", RFC 925,
October 1984. DOI 10.17487/RFC0925, October 1984,
<http://www.rfc-editor.org/info/rfc925>.
[RFC1027] Carl-Mitchell, S. and J. Quarterman, "Using ARP to [RFC1027] Carl-Mitchell, S. and J. Quarterman, "Using ARP to
implement transparent subnet gateways", RFC 1027, October implement transparent subnet gateways", RFC 1027,
1987. DOI 10.17487/RFC1027, October 1987,
<http://www.rfc-editor.org/info/rfc1027>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private
Networks (VPNs)", RFC 4364, February 2006. Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <http://www.rfc-editor.org/info/rfc4364>.
[RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery [RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery
Proxies (ND Proxy)", RFC 4389, April 2006. Proxies (ND Proxy)", RFC 4389, DOI 10.17487/RFC4389, April
2006, <http://www.rfc-editor.org/info/rfc4389>.
[RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
"BGP-MPLS IP Virtual Private Network (VPN) Extension for "BGP-MPLS IP Virtual Private Network (VPN) Extension for
IPv6 VPN", RFC 4659, September 2006. IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006,
<http://www.rfc-editor.org/info/rfc4659>.
[RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service [RFC4761] Kompella, K., Ed. and Y. Rekhter, Ed., "Virtual Private
(VPLS) Using BGP for Auto-Discovery and Signaling", RFC LAN Service (VPLS) Using BGP for Auto-Discovery and
4761, January 2007. Signaling", RFC 4761, DOI 10.17487/RFC4761, January 2007,
<http://www.rfc-editor.org/info/rfc4761>.
[RFC4762] Lasserre, M. and V. Kompella, "Virtual Private LAN Service [RFC4762] Lasserre, M., Ed. and V. Kompella, Ed., "Virtual Private
(VPLS) Using Label Distribution Protocol (LDP) Signaling", LAN Service (VPLS) Using Label Distribution Protocol (LDP)
RFC 4762, January 2007. Signaling", RFC 4762, DOI 10.17487/RFC4762, January 2007,
<http://www.rfc-editor.org/info/rfc4762>.
[RFC5798] Nadas, S., "Virtual Router Redundancy Protocol (VRRP) [RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP)
Version 3 for IPv4 and IPv6", RFC 5798, March 2010. Version 3 for IPv4 and IPv6", RFC 5798,
DOI 10.17487/RFC5798, March 2010,
<http://www.rfc-editor.org/info/rfc5798>.
[RFC6513] Rosen, E. and R. Aggarwal, "Multicast in MPLS/BGP IP [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
VPNs", RFC 6513, February 2012. BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <http://www.rfc-editor.org/info/rfc6513>.
8.2. Informative References 8.2. Informative References
[RFC6820] Narten, T., Karir, M., and I. Foo, "Address Resolution [RFC6820] Narten, T., Karir, M., and I. Foo, "Address Resolution
Problems in Large Data Center Networks", RFC 6820, January Problems in Large Data Center Networks", RFC 6820,
2013. DOI 10.17487/RFC6820, January 2013,
<http://www.rfc-editor.org/info/rfc6820>.
Authors' Addresses Authors' Addresses
Xiaohu Xu Xiaohu Xu
Huawei Huawei
Email: xuxiaohu@huawei.com Email: xuxiaohu@huawei.com
Robert Raszuk Robert Raszuk
Mirantis Inc. Mirantis Inc.
Email: robert@raszuk.net Email: robert@raszuk.net
Christian Jacquenet Christian Jacquenet
Orange Orange
Email: christian.jacquenet@orange.com Email: christian.jacquenet@orange.com
 End of changes. 42 change blocks. 
108 lines changed or deleted 120 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/