Tagging Customer Bridge Domains in VPLS
draft-zhang-l2vpn-vpls-bd-tagging-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-02-12 (latest revision 2014-08-11) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-zhang-l2vpn-vpls-bd-tagging-02.txt
Abstract
This document proposes to use Customer VLAN ID as an identifier for traffic isolation in Virtual Private LAN Service (VPLS). In this way, multiple bridge domains of customers can share a single VPLS instance while their traffic are separated. With this proposal, Service Providers can be relieved from the heavy provisioning overhead of large number of pseudowires in the environment where a mass of bridge domains need be connected.
Authors
Mingui Zhang
(zhangmingui@huawei.com)
Liang Xia
(frank.xialiang@huawei.com)
Jie Hu
(hujie@ctbri.com.cn)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)