Skip to main content

Deprecation of AS_SET and AS_CONFED_SET in BGP
draft-kumari-deprecate-as-set-confed-set-14

Document Type Replaced Internet-Draft (candidate for idr WG)
Expired & archived
Authors Warren "Ace" Kumari , Kotikalapudi Sriram
Last updated 2019-08-16 (Latest revision 2019-08-05)
Replaced by draft-ietf-idr-deprecate-as-set-confed-set
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Call For Adoption By WG Issued
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-idr-deprecate-as-set-confed-set
Consensus boilerplate Unknown
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

BCP 172 (i.e., RFC 6472) recommends not using AS_SET and AS_CONFED_SET in Border Gateway Protocol (BGP). This document updates RFC 4271 and proscribes the use of the AS_SET and AS_CONFED_SET types of path segments in the AS_PATH. This is done to simplify the design and implementation of BGP and to make the semantics of the originator of a route clearer. This will also simplify the design, implementation, and deployment of various BGP security mechanisms.

Authors

Warren "Ace" Kumari
Kotikalapudi Sriram

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