datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Connecting Disparate TRILL-based Data Center/PBB/Campus sites using BGP
draft-balaji-l2vpn-trill-over-ip-multi-level-03

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-08-23 (latest revision 2013-02-19)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-balaji-l2vpn-trill-over-ip-multi-level

Abstract

There is a need to connect (a) TRILL based data centers or (b) TRILL based networks which provide Provider Backbone like functionalities or (c) Campus TRILL based networks over the WAN using one or more ISPs that provide regular IP+GRE or IP+MPLS transport. Some of the solutions proposed as in [DRAFT-EVPN] have not dealt with the scalable methods in their details as to how these services could be provided such that multiple TRILL sites can be inter-connected with issues like nick-name collisions for unicast and multicast being taken care of. It has been found that with extensions to BGP and a scalable method on Provider edge devices the problem statement which we will define below can be handled. Specifically the division of the nick-name into site-id and Rbridge-ID is one that can limit the number of sites that can be interconnected and the number of Rbridges within each such site that can be provisioned. The draft proposed herein deals / overcomes these issues by not limiting the number of sites and Rbridges within a TRILL site interconnect. Only the maximum space for a nick-name which happens to be 16 bits is the actual limit. MAC moves across TRILL sites and within TRILL sites can also be realized. This document / proposal envisions the use of BGP-MAC- VPN vrfs at the ISP cloud PE devices. We deal in depth with the control plane and data plane particulars for unicast and multicast in this scheme. Additionally Provider Backbone like functionality is also covered.

Authors

Radia Perlman <radia@alum.mit.edu>
Bhargav Bhikkaji <bhargav_bhikkaji@dell.com>
Balaji Venkataswami <balaji_venkat_venkat@dell.com>
Ramasubramani Mahadevan <ramasubramani_mahade@dell.com>
Shivakumar Sundaram <shivakumar_sundaram@dell.com>
Narayana Swamy <narayana_perumal@dell.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)