idnits 2.17.1 draft-contreras-alto-bgp-communities-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 13, 2020) is 1383 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 ALTO WG LM. Contreras 3 Internet-Draft Telefonica 4 Intended status: Informational July 13, 2020 5 Expires: January 14, 2021 7 Extending ALTO by using BGP Communities 8 draft-contreras-alto-bgp-communities-00 10 Abstract 12 This memo introduces the proposal of extending ALTO by using BGP 13 Communities as PIDs. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on January 14, 2021. 32 Copyright Notice 34 Copyright (c) 2020 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (https://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. BGP Communities . . . . . . . . . . . . . . . . . . . . . . . 2 51 3. Extending ALTO with BGP communities . . . . . . . . . . . . . 3 52 4. BGP Community representation in ALTO . . . . . . . . . . . . 3 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 54 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 The Provider-defined Identifiers (PIDs) in the ALTO protocol 61 [RFC7285] provide an indirect and network-agnostic way to specify an 62 aggregation of network endpoints, that grouped creates a network map. 63 Network end-points sharing a common PID are expected to receive 64 similar treatment on the decisions assisted by ALTO. 66 With the same idea of grouping of destinations, the concept of BGP 67 Communities [RFC1997] was developed to apply a common routing 68 decision to a number of destinations based on the identity of a 69 group. Since BGP communities are widely configured in real 70 operational networks, this document propose an extension to [RFC7285] 71 by defining a new type of PID based on the BGP community concept. 73 2. BGP Communities 75 A BGP Community is a BGP attribute which is used to group 76 destinations 78 The BGP Communities are represented as an integer number of 32 bit. 79 It is typically written as the combination of two integer numbers of 80 16 bit separated by colon. The first number is usually the 81 Autonomous System (AS) number, while the second one is determined by 82 the service provider according to some internal logic. 84 The IP prefixes can be part of distinct BGP Communities, with 85 different purposes, typically for influencing the traffic reaching 86 the particular prefizes of a community. 88 The BGP Community attribute is useful for applying polcies of 89 applicability to a certain set of prefixes, grouped as a community 90 for some reason at the criteria of the service provider. 92 3. Extending ALTO with BGP communities 94 Network operators use extensively BGP Communities as a mean of 95 putting together some destinations (i.e., IP prefixes) for different 96 purposes Traditionally they are used by administratively-defined 97 filters for applying policies, thus Influencing the behavior of the 98 traffic towards the associated destinations. 100 On the other hand, the ALTO protocol based on IP prefixes. When 101 cosnidering queries to IP prefixes, it could be the case that those 102 queries apply for IP addresses associated to the same topological 103 element. This is for instance the case of aggregations node in the 104 Network (such as BNG or PGW for example) which have associated a 105 number of IP prefixes (that can evolve along the time). The same 106 response will be obtained from ALTO server for all the prefixes 107 associated with such a node since the topological information is 108 essentially the same. 110 For assisting on an efficient usage of ALTO resources in this kind of 111 situations, the usage of BGP Communities can simplify the process by 112 reducing the number of queries to ALTO server, but also by smoothly 113 absorbing the modification of prefixes for a given aggregation node. 115 4. BGP Community representation in ALTO 117 To be done. 119 5. Security Considerations 121 To be done. 123 6. IANA Considerations 125 This draft does not include any IANA considerations 127 7. References 129 [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities 130 Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, 131 . 133 [RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S., 134 Previdi, S., Roome, W., Shalunov, S., and R. Woundy, 135 "Application-Layer Traffic Optimization (ALTO) Protocol", 136 RFC 7285, DOI 10.17487/RFC7285, September 2014, 137 . 139 Author's Address 141 Luis M. Contreras 142 Telefonica 143 Ronda de la Comunicacion, s/n 144 Sur-3 building, 3rd floor 145 Madrid 28050 146 Spain 148 Email: luismiguel.contrerasmurillo@telefonica.com 149 URI: http://lmcontreras.com/