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

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

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-26 (latest revision 2012-03-25)
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-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. A few solutions have been proposed as in [1] in the recent past that have not looked at the PB-like functionality. These solutions have not dealt with the details as to how these services could be provided such that multiple TRILL sites can be inter-connected with issues like nick-name collisons for unicast and multicast being taken care of. It has been found that with extensions to BGP the problem statement which we will define below can be handled. Both control plane and data plane operations can be driven into the solution to make it seamlessly look at the entire set of TRILL sites as a single entity which then can be viewed as one single Layer 2 cloud. MAC moves across TRILL sites and within TRILL sites can be realized. This document / proposal envisions the use of BGP-MAC-VPN vrfs both at the IP cloud PE devices and at the peripheral PEs within a TRILL site providing Provider Backbone like functionality. We deal in depth with the control plane and data plane particulars for unicast and multicast with nick-name election being taken care of as part of the solution.

Authors

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)