Deprecation of AS_SET and AS_CONFED_SET in BGP
draft-kumari-deprecate-as-set-confed-set-12
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Warren "Ace" Kumari , Kotikalapudi Sriram | ||
Last updated | 2019-01-03 (Latest revision 2018-07-02) | ||
Replaced by | draft-ietf-idr-deprecate-as-set-confed-set, draft-ietf-idr-deprecate-as-set-confed-set | ||
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
RFC 6472 (i.e., BCP 172) recommends not using AS_SET and AS_CONFED_SET in BGP. This document updates RFC 4271 and proscribes the use of the AS_SET and AS_CONFED_SET types of the AS_PATH in BGPv4. This is done to simplify the design and implementation of BGP and to make the semantics of the originator of a route more clear. This will also simplify the design, implementation, and deployment of ongoing work in the Secure Inter-Domain Routing Working Group.
Authors
Warren "Ace" Kumari
Kotikalapudi Sriram
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)