(Resending to ALTO mailing list solely, since it seems there was some problem
for having the mail there due to the number of recipients in the mail)
Thanks Med
(adding also in cc ALTO mailing list).
I have gone through the suggested changes producing a -01 version, yet open for
comments and discussion. I attach the txt file for your convenience (the diff
with the published one is easily generated with IETF authors tools).
I have also created a github space for the draft, here:
https://github.com/luismcontreras/alto-bgp-communities
Best regards
Luis
De: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
Enviado el: miércoles, 12 de abril de 2023 16:49
Para: Qin Wu <[email protected]<mailto:[email protected]>>; Jordi Ros Giralt
<[email protected]<mailto:[email protected]>>; Y. Richard Yang
<[email protected]<mailto:[email protected]>>; Jensen Zhang
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; Lachlan Keller
<[email protected]<mailto:[email protected]>>; LUIS MIGUEL
CONTRERAS MURILLO
<[email protected]<mailto:[email protected]>>;
Randriamasy, Sabine (Nokia - FR/Paris-Saclay)
<[email protected]<mailto:[email protected]>>;
maqiufang (A) <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; Motoyoshi Sekiya
(Fujitsu) <[email protected]<mailto:[email protected]>>;
Chongfeng Xie <[email protected]<mailto:[email protected]>>; Cheng
Zhou <[email protected]<mailto:[email protected]>>
Asunto: RE: Reminder ALTO interim meeting today at 10am EST (not 9am)
Hi all,
FWIW, some additional comments on the BGP communities proposal can be seen at
https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-contreras-alto-bgp-communities-00-rev%20Med.doc
Cheers,
Med
De : Qin Wu <[email protected]<mailto:[email protected]>>
Envoyé : mardi 11 avril 2023 17:21
À : Jordi Ros Giralt <[email protected]<mailto:[email protected]>>; Y.
Richard Yang <[email protected]<mailto:[email protected]>>; Jensen Zhang
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; Lachlan Keller
<[email protected]<mailto:[email protected]>>; LUIS MIGUEL
CONTRERAS MURILLO
<[email protected]<mailto:[email protected]>>;
Randriamasy, Sabine (Nokia - FR/Paris-Saclay)
<[email protected]<mailto:[email protected]>>;
maqiufang (A) <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; Motoyoshi Sekiya
(Fujitsu) <[email protected]<mailto:[email protected]>>;
Chongfeng Xie <[email protected]<mailto:[email protected]>>; Cheng
Zhou <[email protected]<mailto:[email protected]>>
Cc : BOUCADAIR Mohamed INNOV/NET
<[email protected]<mailto:[email protected]>>
Objet : RE: Reminder ALTO interim meeting today at 10am EST (not 9am)
Thank all for participanting the discussion of ALTO interim meeting.
For ALTO OAM and New transport, please keeping on engaging with directorate
reviewers who raised major issues and make sure all these major issues are
addressed and related discussion transparent to the ALTO list.
For the next interim meeting plan, we will discuss Deployment Catalyst.
Unfortunately we run out of time due to accident at the beginning of the
interim meeting.
I believe the following drafts will be good input to the discussion. I made
some of comments on these drafts,
Hope these remarks and comments help you understand the direction we suggested.
YANG Data Model for BGP-LS protocol
https://datatracker.ietf.org/doc/rfc7752/
https://datatracker.ietf.org/doc/rfc9085/
https://datatracker.ietf.org/doc/rfc9351/
https://datatracker.ietf.org/doc/rfc8571/
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sr-policy/
https://www.ietf.org/archive/id/draft-ietf-idr-bgp-ls-te-path-00.txt
Comment: Need to figure how this work is related to or decoupled from ALTO OAM
Extending ALTO by using BGP Communities
Comments:
How many BGP communities do we need to support?
e.g., Route Target Community, Route Origin Community
How BGP Communities can be encoded?
How BGP Communities are different from PID?
ALTO for Querying LMAP Results
https://www.ietf.org/archive/id/draft-xie-alto-lmap-00.txt
How Network Topology data collected using NETCONF/YANG can be translated into
ALTO Network Map, Cost Map, Endpoint Map?
https://www.ietf.org/archive/id/draft-hzx-alto-network-topo-00.txt
-Qin/Med
发件人: alto [mailto:[email protected]] 代表 Jordi Ros Giralt
发送时间: 2023年4月11日 19:31
收件人: [email protected]<mailto:[email protected]>
主题: [alto] Reminder ALTO interim meeting today at 10am EST (not 9am)
Hello ALTOers,
Just a reminder that we will be meeting today Tuesday at 10am EST for the ALTO
interim #3 meeting. The focus of this meeting is on "WGLC follow-up of
OAM/Transport I-Ds":
- Remote instructions:
https://meetings.conf.meetecho.com/interim/?short=a6c2968d-b9f9-4ea7-b856-c1ee2e64e0c7
- Agenda
https://datatracker.ietf.org/meeting/interim-2023-alto-02/materials/agenda-interim-2023-alto-02-alto-01-00
- Session materials:
https://datatracker.ietf.org/meeting/interim-2023-alto-02/session/alto
Note that at 9am EST we have our usual ALTO weekly meeting. However, today's
important meeting is the interim, held at 10am EST. So let me suggest that we
skip the 9am call so we can all focus on the 10am call. I will join the 9am
call in case anyone needs to be reminded about the 10am interim meeting.
Below you will also find the agendas for the forthcoming interim meetings as
proposed by the chairs:
* interim #2: WGLC follow-up of OAM/Transport I-Ds
* interim #3: Deployment Catalysts
• Reuse existing network resources to identify ALTO resources (e.g.,
BGP communities)
• Proposals to fix the integration complexity and integration with data
sources
* interim #4: OAM/Transport I-Ds
* interim #5: Deployment Catalysts
• Security/privacy isolation
Thanks,
Jordi on behalf of ALTO WG
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
________________________________
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede
contener información privilegiada o confidencial y es para uso exclusivo de la
persona o entidad de destino. Si no es usted. el destinatario indicado, queda
notificado de que la lectura, utilización, divulgación y/o copia sin
autorización puede estar prohibida en virtud de la legislación vigente. Si ha
recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente
por esta misma vía y proceda a su destrucción.
The information contained in this transmission is confidential and privileged
information intended only for the use of the individual or entity named above.
If the reader of this message is not the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this communication
is strictly prohibited. If you have received this transmission in error, do not
read it. Please immediately reply to the sender that you have received this
communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode
conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa
ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica
notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização
pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem
por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e
proceda a sua destruição
ALTO L. M. Contreras
Internet-Draft Telefonica
Intended status: Informational 25 April 2023
Expires: 27 October 2023
Extending ALTO by using BGP Communities
draft-contreras-alto-bgp-communities-01
Abstract
This memo introduces a proposal to extend ALTO by using BGP
Communities as PIDs. This proposal is meant to ease the integration
of ALTO in operational networks by leveraging existing resource
identifiers.
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 27 October 2023.
Copyright Notice
Copyright (c) 2023 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 (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 Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Contreras Expires 27 October 2023 [Page 1]
Internet-Draft Extending ALTO by using BGP Communities April 2023
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. BGP Communities Overview . . . . . . . . . . . . . . . . . . 2
3. Extending ALTO with BGP communities . . . . . . . . . . . . . 3
3.1. Usage of BGP Communities in ALTO . . . . . . . . . . . . 3
3.2. BGP Community representation in ALTO . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
7. Informative References . . . . . . . . . . . . . . . . . . . 4
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction
The Provider-defined Identifiers (PIDs) in the ALTO Protocol
[RFC7285] provide an indirect and network-agnostic way to aggregate a
set of network endpoints, that grouped creates a network map.
Network endpoints that share a common PID are expected to receive
similar treatment on the decisions assisted by ALTO.
With the same goal of grouping destinations, BGP Communities
[RFC1997] were introduced in the past to tag a grouping of
destinations so that the routing decision can also be based on the
identity of a group. As per [RFC1997], a community is a group of
destinations which share some common property.
Given that BGP communities are widely used in operational networks,
and for the sake of simplifying the integration of ALTO into these
networks, this document specifies an extension to [RFC7285] by
defining a new PID type based on the BGP community concept.
2. BGP Communities Overview
BGP Communities, as per [RFC1997], is a BGP attribute which is used
to group destinations.
Standard BGP Communities are represented as an integer number of
32-bit. It is typically written as the combination of two integer
numbers of 16-bit separated by colon. The first number is usually
the Autonomous System (AS) number, while the second one is determined
by the service provider according to some internal logic. In order
to support 4-octet ASNs, [RFC8092] specifies a BGP Large Communities
attribute. Another form of BGP communities is defined in the BGP
Extended Communities Attribute [RFC4360]. IP prefixes can be part of
distinct BGP Communities, with different purposes, typically for
influencing the traffic reaching the particular prefixes of a
community.
Contreras Expires 27 October 2023 [Page 2]
Internet-Draft Extending ALTO by using BGP Communities April 2023
The BGP Communities attribute is useful for applying policies of
applicability to a certain set of prefixes, grouped as a community
for some reason at the criteria of the service provider. For
instance, BGP Communities can be useful for indicating local
preference for a route to the receive to a set of IP prefixes in a
peering scenario.
The initial approach in the usage of BGP Communities in ALTO followed
in this document is to consider [RFC1997] and [RFC8092] as means of
identifying grouping of IP prefixes in networks with either 2-octet
or 4-octet ASNs.
3. Extending ALTO with BGP communities
Network operators use extensively BGP Communities as a mean of
grouping some destinations (i.e., IP prefixes) for different
purposes. Typically, they are used by administratively-defined
filters for applying policies, thus influencing the behavior of the
traffic towards the associated destinations.
On the other hand, the ALTO Protocol is based on IP prefixes. When
considering queries to IP prefixes, it could be the case that those
queries apply for IP addresses associated to the same topological
element. This is for instance the case of aggregations node in the
Network (such as BNG or PGW) which have associated a number of IP
prefixes (that can evolve along the time). The same response will be
obtained from an ALTO server for all the prefixes associated with
such a node since the topological information is essentially the
same.
For assisting an efficient usage of ALTO resources in this kind of
situations, the usage of BGP Communities simplifies the process by
reducing the number of queries to ALTO server, but also by smoothly
absorbing the modification of prefixes for a given aggregation node.
3.1. Usage of BGP Communities in ALTO
Some potential usages of BGP Communities in ALTO are envisaged:
* In situations where the BGP Community and an ALTO PID scope the
same grouping of prefixes, leveraging on BGP Communities
simplifies the operation by using an existing identifier for the
purpose of retrieving ALTO information.
* In situations where the purpose is to retrieve ALTO information
applicable to a superset of PIDs, a BGP Community can be defined
in order to group the prefixes of all those PIDs.
Contreras Expires 27 October 2023 [Page 3]
Internet-Draft Extending ALTO by using BGP Communities April 2023
* In situations where the purpose is to retrieve ALTO information
applicable to a subset of prefixes across multiple PIDs, a BGP
Community can be defined in order to group the subset of prefixes
of all those PIDs.
3.2. BGP Community representation in ALTO
To be done.
4. Security Considerations
To be provided.
5. IANA Considerations
To be provided.
6. Acknowledgements
The author thanks Med Boucadair for his review, comments and
suggestions to make this document and solution more complete.
7. Informative References
[RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities
Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996,
<https://www.rfc-editor.org/info/rfc1997>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
February 2006, <https://www.rfc-editor.org/info/rfc4360>.
[RFC7285] Alimi, R., Ed., Penno, R., Ed., Yang, Y., Ed., Kiesel, S.,
Previdi, S., Roome, W., Shalunov, S., and R. Woundy,
"Application-Layer Traffic Optimization (ALTO) Protocol",
RFC 7285, DOI 10.17487/RFC7285, September 2014,
<https://www.rfc-editor.org/info/rfc7285>.
[RFC8092] Heitz, J., Ed., Snijders, J., Ed., Patel, K., Bagdonas,
I., and N. Hilliard, "BGP Large Communities Attribute",
RFC 8092, DOI 10.17487/RFC8092, February 2017,
<https://www.rfc-editor.org/info/rfc8092>.
Author's Address
Contreras Expires 27 October 2023 [Page 4]
Internet-Draft Extending ALTO by using BGP Communities April 2023
Luis M. Contreras
Telefonica
Ronda de la Comunicacion, s/n
28050 Madrid
Spain
Email: [email protected]
URI: http://lmcontreras.com
Contreras Expires 27 October 2023 [Page 5]
_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto
