draft-ietf-bess-virtual-subnet-03.txt   draft-ietf-bess-virtual-subnet-04.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: May 12, 2016 Mirantis Inc. Expires: May 13, 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
November 9, 2015 November 10, 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-03 draft-ietf-bess-virtual-subnet-04
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 Layer 3 network virtualization overlays within and/or building Layer 3 network virtualization overlays within and/or
between data centers. between 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 May 12, 2016. This Internet-Draft will expire on May 13, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Solution Description . . . . . . . . . . . . . . . . . . . . 4 3. Solution Description . . . . . . . . . . . . . . . . . . . . 4
3.1. Unicast . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Unicast . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. Intra-subnet Unicast . . . . . . . . . . . . . . . . 4 3.1.1. Intra-subnet Unicast . . . . . . . . . . . . . . . . 4
3.1.2. Inter-subnet Unicast . . . . . . . . . . . . . . . . 5 3.1.2. Inter-subnet Unicast . . . . . . . . . . . . . . . . 5
3.2. Multicast . . . . . . . . . . . . . . . . . . . . . . . . 8 3.2. Multicast . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3. Host Discovery . . . . . . . . . . . . . . . . . . . . . 9 3.3. Host Discovery . . . . . . . . . . . . . . . . . . . . . 9
3.4. ARP/ND Proxy . . . . . . . . . . . . . . . . . . . . . . 9 3.4. ARP/ND Proxy . . . . . . . . . . . . . . . . . . . . . . 9
3.5. Host Mobility . . . . . . . . . . . . . . . . . . . . . . 9 3.5. Host Mobility . . . . . . . . . . . . . . . . . . . . . . 9
3.6. Forwarding Table Scalability on Data Center Switches . . 10 3.6. Forwarding Table Scalability on Data Center Switches . . 10
skipping to change at page 4, line 30 skipping to change at page 4, line 30
for data center interconnection, it actually could be used within for data center interconnection, it actually could be used within
data centers as well. data centers as well.
Note that the approach described in this document is not intended to Note that the approach described in this document is not intended to
achieve an exact emulation of Layer 2 connectivity and therefore it achieve an exact emulation of Layer 2 connectivity and therefore it
can only support a restricted Layer 2 connectivity service model with can only support a restricted Layer 2 connectivity service model with
limitations declared in Section 4. As for the discussion about in limitations declared in Section 4. As for the discussion about in
which environment this service model should be suitable, it's outside which environment this service model should be suitable, it's outside
the scope of this document. the scope of this document.
1.1. 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 RFC 2119 [RFC2119].
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
+--------------------+ +--------------------+
skipping to change at page 10, line 24 skipping to change at page 10, line 24
3.7. ARP/ND Cache Table Scalability on Default Gateways 3.7. ARP/ND Cache Table Scalability on Default Gateways
When default gateway functions are implemented on PE routers as shown When default gateway functions are implemented on PE routers as shown
in Figure 4, the ARP/ND cache table on each PE router only needs to in Figure 4, the ARP/ND cache table on each PE router only needs to
contain ARP/ND entries of local hosts As a result, the ARP/ND cache contain ARP/ND entries of local hosts As a result, the ARP/ND cache
table size would not grow as the number of data centers to be table size would not grow as the number of data centers to be
connected increases. connected increases.
3.8. ARP/ND and Unknown Uncast Flood Avoidance 3.8. ARP/ND and Unknown Uncast Flood Avoidance
In VS, the flooding domain associated with a given Virtual Subnet In a Virtual Subnet environment, the flooding domain associated with
that has been extended across multiple data centers, is partitioned a given Virtual Subnet that has been extended across multiple data
into segments and each segment is confined within a single data centers, is partitioned into segments and each segment is confined
center. Therefore, the performance impact on networks and servers within a single data center. Therefore, the performance impact on
imposed by the flooding of ARP/ND broadcast/multicast and unknown networks and servers imposed by the flooding of ARP/ND broadcast/
unicast traffic is alleviated. multicast and unknown unicast traffic is alleviated.
3.9. Path Optimization 3.9. Path Optimization
Take the scenario shown in Figure 4 as an example, to optimize the Take the scenario shown in Figure 4 as an example, to optimize the
forwarding path for the traffic between cloud users and cloud data forwarding path for the traffic between cloud users and cloud data
centers, PE routers located at cloud data centers (i.e., PE-1 and PE- centers, PE routers located at cloud data centers (i.e., PE-1 and PE-
2), which are also acting as default gateways, propagate host routes 2), which are also acting as default gateways, propagate host routes
for their own local hosts respectively to remote PE routers which are for their own local hosts respectively to remote PE routers which are
attached to cloud user sites (i.e., PE-3). As such, the traffic from attached to cloud user sites (i.e., PE-3). As such, the traffic from
cloud user sites to a given server on the Virtual Subnet which has cloud user sites to a given server on the Virtual Subnet which has
skipping to change at page 12, line 45 skipping to change at page 12, line 45
[RFC0925] Postel, J., "Multi-LAN address resolution", RFC 925, [RFC0925] Postel, J., "Multi-LAN address resolution", RFC 925,
DOI 10.17487/RFC0925, October 1984, DOI 10.17487/RFC0925, October 1984,
<http://www.rfc-editor.org/info/rfc925>. <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, implement transparent subnet gateways", RFC 1027,
DOI 10.17487/RFC1027, October 1987, DOI 10.17487/RFC1027, October 1987,
<http://www.rfc-editor.org/info/rfc1027>. <http://www.rfc-editor.org/info/rfc1027>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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, DOI 10.17487/RFC4364, February Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February
2006, <http://www.rfc-editor.org/info/rfc4364>. 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, DOI 10.17487/RFC4389, April Proxies (ND Proxy)", RFC 4389, DOI 10.17487/RFC4389, April
2006, <http://www.rfc-editor.org/info/rfc4389>. 2006, <http://www.rfc-editor.org/info/rfc4389>.
8.2. Informative References 8.2. Informative References
 End of changes. 8 change blocks. 
22 lines changed or deleted 10 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/