Sign in
Version 5.13.0, 2015-03-25
Report a bug

Interconnecting multiple TRILL sites deploying Traffic Engineering

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. A copy of the expired Internet-Draft can be found here:


This document specifies the control plane procedures to support Traffic Engineering (TE) across TRILL sites where such sites are interconnected using [1] with the help of a Layer 3 core running IP+GRE or IP+MPLS. Traffic Engineering permits usage of a set of links that possess a certain characteristic like specified bandwidth, cost or even MTU. This draft aims at addressing how unicast frames travelling from one TRILL site to another across a Layer 3 core that supports IP+GRE and/or IP+MPLS can make use of the TE calculated paths in the sending site as well as the receiving site where such TE paths are pre-computed in both sites and need a mechanism to inter- link them together.


Balaji Venkataswami <>
Bhargav Bhikkaji <>
Narayana Swamy <>

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