Autonomous System Confederations for BGP

Traina, P.; McPherson, Danny; Scudder, John

doi:10.17487/rfc5065

Cited by 46 publications

(10 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To prevent the possible propagation of Confederation-related path segments outside of a Confederation, the path segment types AS_CONFED_SEQUENCE and AS_CONFED_SET [RFC5065] are declared invalid for the AS4_PATH attribute and MUST NOT be included in the AS4_PATH attribute of an UPDATE message.…”

Section: Protocol Extensionsmentioning

confidence: 99%

“…In order to construct the AS path information, it is necessary to first calculate the number of AS numbers in the AS_PATH and AS4_PATH attributes using the method specified in Section 9.1.2.2 of [RFC4271] and in [RFC5065] for route selection.…”

Section: Processing Received Updatesmentioning

confidence: 99%

“…In addition, the path segment types AS_CONFED_SEQUENCE and AS_CONFED_SET [RFC5065] MUST NOT be carried in the AS4_PATH attribute of an UPDATE message. A NEW BGP speaker that receives these path segment types in the AS4_PATH attribute of an UPDATE message from an OLD BGP speaker MUST discard these path segments, adjust the relevant attribute fields accordingly, and continue processing the UPDATE message.…”

Section: Error Handlingmentioning

confidence: 99%

See 2 more Smart Citations

BGP Support for Four-Octet Autonomous System (AS) Number Space

Vohra¹,

Chen²

2012

View full text Add to dashboard Cite

The Autonomous System number is encoded as a two-octet entity in the base BGP specification. This document describes extensions to BGP to carry the Autonomous System numbers as four-octet entities. This document obsoletes RFC 4893 and updates RFC 4271. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6793.

show abstract

Section: Protocol Extensionsmentioning

confidence: 99%

Section: Processing Received Updatesmentioning

confidence: 99%

Section: Error Handlingmentioning

confidence: 99%

See 1 more Smart Citation

BGP Support for Four-Octet Autonomous System (AS) Number Space

Vohra¹,

Chen²

2012

View full text Add to dashboard Cite

show abstract

“…The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [7] o Easy Transition It must be possible to transition from a full-mesh configuration without the need to change either topology or AS. This is an unfortunate management overhead of the technique proposed in [3].…”

Section: Specification Of Requirementsmentioning

confidence: 99%

“…This scaling problem has been well documented, and a number of proposals have been made to alleviate this [2,3]. This document represents another alternative in alleviating the need for a "full mesh" and is known as "route reflection".…”

Section: Introductionmentioning

confidence: 99%

BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)

Chandra¹,

Chen²,

Bates³

2006

View full text Add to dashboard Cite

show abstract

BGP Migrations

2010

Network Mergers and Migrations

View full text Add to dashboard Cite

Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners. The publisher is not associated with any product or vendor mentioned in this book. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold on the understanding that the publisher is not engaged in rendering professional services. If professional advice or other expert assistance is required, the services of a competent professional should be sought.

show abstract

Autonomous System Confederations for BGP

Cited by 46 publications

References 7 publications

BGP Support for Four-Octet Autonomous System (AS) Number Space

BGP Support for Four-Octet Autonomous System (AS) Number Space

BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)

BGP Migrations

Contact Info

Product

Resources

About