TRILL Integrated Routing and Bridging Solution
draft-hao-trill-irb-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Hao Weiguo , Yizhou Li | ||
| Last updated | 2014-01-12 (Latest revision 2013-07-11) | ||
| Replaced by | draft-ietf-trill-irb, RFC 7956 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Currently, TRILL solution can only provide optimum unicast forwarding just for Layer2 traffic of intra-subnet forwarding, not for Layer3 traffic(inter-subnet forwarding). In this document, a TRILL Integrated Routing and Bridging (IRB) solution is introduced to provide optimum unicast forwarding not just for Layer 2 traffic (intra-subnet forwarding), but also for Layer 3 traffic (inter- subnet forwarding). In the TRILL IRB scenario, an edge RB MUST perform the bridging function for the End Systems that are on the same subnet and the IP routing for the End Systems that are on the different subnets of same tenant.ESADI extension can be used for synchronizing <MAC, IP> correspondence among edge RBridges. To reduce the number of ESADI session among edge RBridges, Management Data Label for ESADI is suggested to be used.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)