draft-ietf-grow-large-communities-usage-06.txt   draft-ietf-grow-large-communities-usage-07.txt 
Global Routing Operations J. Snijders Global Routing Operations J. Snijders
Internet-Draft J. Heasley Internet-Draft J. Heasley
Intended status: Informational NTT Intended status: Informational NTT
Expires: October 16, 2017 M. Schmidt Expires: October 21, 2017 M. Schmidt
i3D.net i3D.net
April 14, 2017 April 19, 2017
Use of BGP Large Communities Use of BGP Large Communities
draft-ietf-grow-large-communities-usage-06 draft-ietf-grow-large-communities-usage-07
Abstract Abstract
Examples and inspiration for operators to use BGP Large Communities. This document presents examples and inspiration for operator's
application of BGP Large Communities. Based on operational
experience with BGP Communties, this document suggests logical
categories of BGP Large Communities and demonstrates an orderly
manner of organizing community values within them to achieve typical
goals in routing policy. Any operator can consider using the
concepts presented as the basis for their own BGP Large Communities
repertoire.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 16, 2017. This Internet-Draft will expire on October 21, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Design Overview . . . . . . . . . . . . . . . . . . . . . 2 2. The Design Overview . . . . . . . . . . . . . . . . . . . . . 3
2.1. Informational Communities . . . . . . . . . . . . . . . . 4 2.1. Informational Communities . . . . . . . . . . . . . . . . 4
2.2. Action Communities . . . . . . . . . . . . . . . . . . . 4 2.2. Action Communities . . . . . . . . . . . . . . . . . . . 4
3. Examples of Informational Communities . . . . . . . . . . . . 5 3. Examples of Informational Communities . . . . . . . . . . . . 5
3.1. Location . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1. Location . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1.1. An ISO 3166-1 Numeric Function . . . . . . . . . . . 5 3.1.1. An ISO 3166-1 Numeric Function . . . . . . . . . . . 5
3.1.2. An UN M.49 Region Function . . . . . . . . . . . . . 5 3.1.2. An UN M.49 Region Function . . . . . . . . . . . . . 5
3.2. Relation Function . . . . . . . . . . . . . . . . . . . . 6 3.2. Relation Function . . . . . . . . . . . . . . . . . . . . 6
3.3. Combining Informational Communities . . . . . . . . . . . 6 3.3. Combining Informational Communities . . . . . . . . . . . 6
4. Examples of Action Communities . . . . . . . . . . . . . . . 7 4. Examples of Action Communities . . . . . . . . . . . . . . . 7
4.1. Selective NO_EXPORT . . . . . . . . . . . . . . . . . . . 7 4.1. Selective NO_EXPORT . . . . . . . . . . . . . . . . . . . 7
skipping to change at page 2, line 31 skipping to change at page 2, line 36
4.2. Selective AS_PATH Prepending . . . . . . . . . . . . . . 8 4.2. Selective AS_PATH Prepending . . . . . . . . . . . . . . 8
4.2.1. ASN Based Selective AS_PATH Prepending . . . . . . . 8 4.2.1. ASN Based Selective AS_PATH Prepending . . . . . . . 8
4.2.2. Location Based Selective AS_PATH Prepending . . . . . 9 4.2.2. Location Based Selective AS_PATH Prepending . . . . . 9
4.3. Manipulation of the LOCAL_PREF Attribute . . . . . . . . 9 4.3. Manipulation of the LOCAL_PREF Attribute . . . . . . . . 9
4.3.1. Global Manipulation of LOCAL_PREF . . . . . . . . . . 10 4.3.1. Global Manipulation of LOCAL_PREF . . . . . . . . . . 10
4.3.2. Region Based Manipulation of LOCAL_PREF . . . . . . . 10 4.3.2. Region Based Manipulation of LOCAL_PREF . . . . . . . 10
4.3.3. Note of Caution for LOCAL_PREF Functions . . . . . . 11 4.3.3. Note of Caution for LOCAL_PREF Functions . . . . . . 11
4.4. Route Server Prefix Distribution Control . . . . . . . . 11 4.4. Route Server Prefix Distribution Control . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 13 8.2. Informative References . . . . . . . . . . . . . . . . . 13
8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13 8.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
BGP Large Communities [RFC8092] provide a mechanism to signal opaque BGP Large Communities [RFC8092] provide a mechanism to signal opaque
information between Autonomous Systems (ASs). In very much the same information between Autonomous Systems (ASs). In very much the same
way that [RFC1998] provides a concrete real-world application for way that [RFC1998] provides a concrete real-world application for
[RFC1997] communities, this document presents examples of how [RFC1997] communities, this document presents examples of how
operators might utilize BGP Large Communities to achieve various operators might utilize BGP Large Communities to achieve various
goals. This document draws on the experience of operator communities goals. This document draws on the experience of operator communities
skipping to change at page 12, line 9 skipping to change at page 12, line 9
adaption of "ASN Based Selective NO_EXPORT" (Section 4.1.1). adaption of "ASN Based Selective NO_EXPORT" (Section 4.1.1).
An example BGP Large Communities policy which enables client- An example BGP Large Communities policy which enables client-
controlled prefix distribution for a route server operating as AS controlled prefix distribution for a route server operating as AS
64497, is outlined as follows: 64497, is outlined as follows:
+-------------------+-----------------------------------------------+ +-------------------+-----------------------------------------------+
| BGP Large | Description | | BGP Large | Description |
| Community | | | Community | |
+-------------------+-----------------------------------------------+ +-------------------+-----------------------------------------------+
| 64497:0:peer-as | Explicitly prevent announcement of route to | | 64497:13:peer-as | Explicitly prevent announcement of route to |
| | peer-as | | | peer-as |
| 64497:1:peer-as | Explicitly announce route to peer-as | | 64497:14:peer-as | Explicitly announce route to peer-as |
| 64497:0:0 | Do not announce route to any peers by default | | 64497:13:0 | Do not announce route to any peers by default |
| 64497:1:0 | Announce route to all peers by default | | 64497:14:0 | Announce route to all peers by default |
+-------------------+-----------------------------------------------+ +-------------------+-----------------------------------------------+
Table 12: Action: Route Server Prefix Distribution Control Table 12: Action: Route Server Prefix Distribution Control
Multiple BGP Large Community values can be used together to implement Multiple BGP Large Community values can be used together to implement
fine-grained route distribution control. For example, route server fine-grained route distribution control. For example, route server
client AS 64500 might wish to use a route server for interconnecting client AS 64500 might wish to use a route server for interconnecting
to all other clients except AS 64510. In this case, they would label to all other clients except AS 64510. In this case, they would label
all their outbound routes to the route server with 64497:1:0 (to all their outbound routes to the route server with 64497:14:0 (to
announce to all clients by default) and 64497:1:64510 (to prevent announce to all clients by default) and 64497:13:64510 (to prevent
announcement to AS 64510). announcement to AS 64510).
Alternatively, route server client AS 64501 may have a selective Alternatively, route server client AS 64501 may have a selective
routing policy and may wish to interconnect with only AS 64505 and AS routing policy and may wish to interconnect with only AS 64505 and AS
64506. This could be implemented by announcing routes labeled with 64506. This could be implemented by announcing routes labeled with
64497:0:0 (blocking all distribution by default) and 64497:1:64505, 64497:13:0 (blocking all distribution by default) and 64497:14:64505,
64497:1:64506 to instruct the route server to force announcement to 64497:14:64506 to instruct the route server to force announcement to
those two ASNs. those two ASNs.
5. Security Considerations 5. Security Considerations
Operators should note the recommendations in Section 11 of BGP Operators should note the recommendations in Section 11 of BGP
Operations and Security [RFC7454]. Operations and Security [RFC7454] and handle BGP Large Communities
with their ASN in the Global Administrator field similarly.
In particular and in the same respect as BGP Communities [RFC1997],
operators should be congnizant that any Large Community can be
carried in a BGP UPDATE. Operators should recognize that BGP
neighbors, particularly customers and customers of customers, may
utilize communities defined by other BGP neighbors of the operator.
They may wish to send routes with action communities and receive
routes with informational communities to or from these other
neighbors and it is beneficial to all to permit this.
6. IANA Considerations 6. IANA Considerations
None. None.
7. Acknowledgments 7. Acknowledgments
The authors would like to gratefully acknowledge the insightful The authors would like to gratefully acknowledge the insightful
comments, contributions, critique and support from Adam Chappell, comments, contributions, critique and support from Adam Chappell,
Jonathan Stewart, Greg Hankins, Nick Hilliard, Will Hargrave, Randy Jonathan Stewart, Greg Hankins, Nick Hilliard, Will Hargrave, Randy
Bush, Shawn Morris and Jay Borkenhagen. Bush, Shawn Morris, Jay Borkenhagen and Stewart Bryant.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,
<http://www.rfc-editor.org/info/rfc1997>. <http://www.rfc-editor.org/info/rfc1997>.
[RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations [RFC7454] Durand, J., Pepelnjak, I., and G. Doering, "BGP Operations
 End of changes. 14 change blocks. 
18 lines changed or deleted 35 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/