BGP Well Known Large Community
draft-heitz-idr-wklc-01
IDR J. Heitz
Internet-Draft Cisco
Intended status: Standards Track K. Sriram
Expires: March 13, 2021 NIST
B. Dickson
J. Heasly
September 9, 2020
BGP Well Known Large Community
draft-heitz-idr-wklc-01
Abstract
A range of BGP Autonomous System Numbers is reserved to create a set
of BGP Well Known Large Communities.
Requirements Language
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 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 13, 2021.
Copyright Notice
Copyright (c) 2020 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
Heitz, et al. Expires March 13, 2021 [Page 1]
Internet-Draft Well Known Large Community September 2020
(https://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. Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Transitivity . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The Global Administrator field of the BGP Large community [RFC8092]
is an Autonomous System Number (ASN). To create a set of Well Known
Large Communities, a set of ASNs must be reserved for them, such that
a real ASN in the Global Administrator field cannot be mistaken for a
Well Known Large Community.
2. Encoding
Each BGP Well Known Large Community value is encoded as a 12-octet
quantity, as follows:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|1 1 1 1 0 1| T | WKLC ID | Data 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Data 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The fields are as shown below:
T - Transitivity field (2 bits). This is further
described below.
Heitz, et al. Expires March 13, 2021 [Page 2]
Internet-Draft Well Known Large Community September 2020
WKLC ID - Well Known Large Community Identifier (1 octet).
See IANA Considerations. If an experimental type
is used, then it MUST NOT be hard coded in the BGP
speaker software; it MUST be configurable.
Different experiments can then run in the same
network without having to coordinate identifier
assignment during the coding stage.
Data 1,2,3 - A 10 octet value specific to the WKLC. Data 1 is
Show full document text