Bitmask Route Target
draft-zzhang-idr-bitmask-route-target-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , Srihari R. Sangli , Jeffrey Haas | ||
| Last updated | 2021-01-13 (Latest revision 2020-07-12) | ||
| 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
This document specifies a new type of Route Target called Bitmask Route Target as a BGP Community Container. The key element of a Bitmask Route Target is a Bitmask. Two Bitmask Route Targets are considered equivalent for the purpose of controlling route propagation (via Route Target Constraints) and importation if the result of logical "AND" operation of the Bitmask of the two is non- zero.
Authors
Zhaohui (Jeffrey) Zhang
Srihari R. Sangli
Jeffrey Haas
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)