RBridge VLAN Mapping
draft-perlman-trill-rbridge-vlan-mapping-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Donald E. Eastlake 3rd , Dinesh G. Dutt, Radia Perlman | ||
| Last updated | 2009-03-11 (Latest revision 2008-10-27) | ||
| Replaced by | draft-ietf-trill-rbridge-vlan-mapping | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-trill-rbridge-vlan-mapping | |
| 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
Some bridge products perform a feature known as "VLAN mapping", in which a bridge translates a data frame's VLAN ID from one VLAN to another when it forwards a frame from one port to another. This feature facilitates scenarios such as combining two bridged LANs with overlapping VLAN IDs into one bridged LAN without merging two communities just because they have been given the same VLAN ID in the original two clouds. This document describes how RBridges can achieve the same functionality.
Authors
Donald E. Eastlake 3rd
Dinesh G. Dutt
Radia Perlman
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)