Generic Subtype for BGP Four-octet AS specific extended community
draft-dhrao-idr-4octet-extcomm-generic-subtype-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dhananjaya Rao , Prodosh Mohapatra , Jeffrey Haas | ||
| Last updated | 2008-10-21 | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
Maintaining the current best practices with communities, ISPs and enterprises that get assigned a 4-octet AS number may want the BGP UPDATE messages they receive from their customers or peers to include a 4-octet AS specific extended community. This document defines a new sub-type within the four-octet AS specific extended community to facilitate this practice.
Authors
Dhananjaya Rao
Prodosh Mohapatra
Jeffrey Haas
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)