BGP Large Communities Attribute (RFC8092)
Original Publication Date: 2017-Feb-01
Included in the Prior Art Database: 2017-Feb-17
Internet Society Requests For Comment (RFCs)
J. Heitz: AUTHOR [+6]
BGP [RFC4271] implementations typically support a routing policy language to control the distribution of routing information. Network operators attach BGP communities to routes to associate particular properties with these routes. These properties may include information such as the route origin location, or specification of a routing policy action to be taken, or one that has been taken, and is applied to all routes contained in a BGP Update Message where the Communities Attribute is included. Because BGP communities are optional transitive BGP attributes, BGP communities may be acted upon or otherwise used by routing policies in other Autonomous Systems (ASes) on the Internet.
Internet Engineering Task Force (IETF) J. Heitz, Ed. Request for Comments: 8092 Cisco Category: Standards Track J. Snijders, Ed. ISSN: 2070-1721 NTT K. Patel Arrcus I. Bagdonas Equinix N. Hilliard INEX February 2017
BGP Large Communities Attribute
This document describes the BGP Large Communities attribute, an extension to BGP-4. This attribute provides a mechanism to signal opaque information within separate namespaces to aid in routing management. The attribute is suitable for use with all Autonomous System Numbers (ASNs) including four-octet ASNs.
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 7841.
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/rfc8092.
al. Standards Track [Page 1]
RFC 8092 BGP Large Communities February 2017
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please rev...