BGP Large Communities Attribute
RFC 8092
|
| Document |
Type |
|
RFC - Proposed Standard
(February 2017; Errata)
|
|
Last updated |
|
2017-03-09
|
|
Replaces |
|
draft-heitz-idr-large-community
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
John Scudder
|
|
Shepherd write-up |
|
Show
(last changed 2016-11-22)
|
| IESG |
IESG state |
|
RFC 8092 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Alvaro Retana
|
|
Send notices to |
|
"John Scudder" <jgs@juniper.net>
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
RFC-Ed-Ack
|
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
Abstract
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.
Heitz, et al. Standards Track [Page 1]
RFC 8092 BGP Large Communities February 2017
Copyright Notice
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 review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
2. Requirements Language ...........................................3
3. BGP Large Communities Attribute .................................3
4. Aggregation .....................................................4
5. Canonical Representation ........................................4
6. Error Handling ..................................................5
7. Security Considerations .........................................5
8. IANA Considerations .............................................6
9. References ......................................................6
9.1. Normative References .......................................6
9.2. Informative References .....................................6
Acknowledgments ....................................................7
Contributors .......................................................7
Authors' Addresses .................................................8
1. Introduction
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.
Heitz, et al. Standards Track [Page 2]
RFC 8092 BGP Large Communities February 2017
A BGP Communities attribute is a variable-length attribute consisting
of a set of one or more four-octet values, each of which specify a
community [RFC1997]. Common use of the individual values of this
attribute type split this single 32-bit value into two 16-bit values.
The most significant word is interpreted as an Autonomous System
Number (ASN), and the least significant word is a locally defined
Show full document text