Generic Subtype for BGP Four-octet AS specific extended community
draft-dhrao-idr-4octet-extcomm-generic-subtype-00

Document Type Expired Internet-Draft (individual)
Last updated 2008-10-21
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) 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)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-dhrao-idr-4octet-extcomm-generic-subtype-00.txt

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 (dhrao@cisco.com)
Prodosh Mohapatra (pmohapat@cisco.com)
Jeffrey Haas (jhaas@arbor.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)