Generic Subtype for BGP Four-octet AS specific extended community
draft-ietf-idr-as4octet-extcomm-generic-subtype-05

The information below is for an old version of the document
Document Type Expired Internet-Draft (idr WG)
Last updated 2012-09-12 (latest revision 2012-03-11)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-idr-as4octet-extcomm-generic-subtype-05.txt

Abstract

Maintaining the current best practices with communities, ISPs and enterprises that are 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 BGP 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@pfrc.org)

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