Doesn't RFC 8195 already cover much of that? https://datatracker.ietf.org/doc/rfc8195/
Thanks On Fri, Jun 7, 2024 at 5:04 PM Robert Raszuk <[email protected]> wrote: > > Maybe it is out of scope. Or perhaps scope is just too narrow. > > Anyhow ... > > Imagine I an IXP client advertising a prefix to RS which I want to be > distributed only to some client's ASNs. > > So how do I signal such policy using Large Communities keeping in mind > that such prefix is an IPv6 prefix ? > > Using extended communities this is easily achievable using IPv6 Address > Specific Extended Community (value 25): Hint: RFC5701. > > Regards, > Robert > > > On Fri, Jun 7, 2024 at 11:35 PM Job Snijders <[email protected]> wrote: > >> It seems out of scope to me >> >> On Fri, 7 Jun 2024 at 23:30, Robert Raszuk <[email protected]> wrote: >> >>> Jeff, >>> >>> True. But we there is clear opportunity to define those scoped for IXP >>> use case. >>> >>> This is BCP so IMO good place to encourage using common encoding for >>> most common needs. >>> >>> Thx, >>> R. >>> >>> On Fri, Jun 7, 2024 at 11:23 PM Jeffrey Haas <[email protected]> wrote: >>> >>>> There is no such thing as a well known large bgp community. >>>> >>>> >>>> Jeff >>>> >>>> On Jun 7, 2024, at 15:51, Robert Raszuk <[email protected]> wrote: >>>> >>>> >>>> Hi Job/WG, >>>> >>>> Reading the document I have a feeling/suggestion that perhaps this is a >>>> very good time now to define few IXP focused well known Large Communities >>>> such that most often signalled policies between RS and their clients are >>>> well defined and not random among IXPs. >>>> >>>> That may also in fact encourage faster migration to LCs from Extended >>>> Commuities. >>>> >>>> Thx a lot, >>>> Robert >>>> >>>> >>>> On Fri, Jun 7, 2024 at 9:39 PM Job Snijders <job= >>>> [email protected]> wrote: >>>> >>>>> Thanks David, we will incorporate this in the next revision >>>>> >>>>> On Fri, 7 Jun 2024 at 21:15, David Farmer <farmer= >>>>> [email protected]> wrote: >>>>> >>>>>> I reviewed the draft; >>>>>> >>>>>> The Abstract and Introduction says, "It includes guidance for >>>>>> both the Internet Service Provider side peering with Route Servers and >>>>>> IXPs >>>>>> operating Route Servers." >>>>>> >>>>>> However, the document no longer calls for any direct actions by ISPs. >>>>>> Obviously, the actions recommended for IXPs will impact the ISPs using >>>>>> IXPs. However, the statements above imply direct actions by ISPs in >>>>>> addition to IXPs, not indirect impacts on ISPs from IXP actions. >>>>>> >>>>>> You should probably rephrase the above statements to refer to >>>>>> indirect impacts on ISPs unless you expect ISPs to take other direct >>>>>> actions, and if you do, those other actions need to be more clearly >>>>>> stated. >>>>>> >>>>>> Thanks. >>>>>> >>>>>> On Wed, Jun 5, 2024 at 11:09 AM <[email protected]> wrote: >>>>>> >>>>>>> Internet-Draft draft-ietf-grow-ixp-ext-comms-00.txt is now >>>>>>> available. It is a >>>>>>> work item of the Global Routing Operations (GROW) WG of the IETF. >>>>>>> >>>>>>> Title: Recommendation to avoid use of BGP Extended Communities >>>>>>> at Internet Exchange Route Servers >>>>>>> Authors: Job Snijders >>>>>>> Stavros Konstantaras >>>>>>> Mo Shivji >>>>>>> Name: draft-ietf-grow-ixp-ext-comms-00.txt >>>>>>> Pages: 5 >>>>>>> Dates: 2024-06-04 >>>>>>> >>>>>>> Abstract: >>>>>>> >>>>>>> This document outlines a recommendation to the Internet >>>>>>> operational >>>>>>> community to avoid the use of BGP Extended Communities at Internet >>>>>>> Exchange Point (IXP) Route Servers. It includes guidance for both >>>>>>> the Internet Service Provider side peering with Route Servers and >>>>>>> IXPs operating Route Servers. This recommendation aims to help >>>>>>> the >>>>>>> global Internet routing system's performance and help protect >>>>>>> Route >>>>>>> Server participants against misconfigurations. >>>>>>> >>>>>>> The IETF datatracker status page for this Internet-Draft is: >>>>>>> https://datatracker.ietf.org/doc/draft-ietf-grow-ixp-ext-comms/ >>>>>>> >>>>>>> There is also an HTMLized version available at: >>>>>>> >>>>>>> https://datatracker.ietf.org/doc/html/draft-ietf-grow-ixp-ext-comms-00 >>>>>>> >>>>>>> Internet-Drafts are also available by rsync at: >>>>>>> rsync.ietf.org::internet-drafts >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> GROW mailing list -- [email protected] >>>>>>> To unsubscribe send an email to [email protected] >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> =============================================== >>>>>> David Farmer Email:[email protected] >>>>>> Networking & Telecommunication Services >>>>>> Office of Information Technology >>>>>> University of Minnesota >>>>>> 2218 University Ave SE >>>>>> <https://www.google.com/maps/search/2218+University+Ave+SE?entry=gmail&source=g> >>>>>> Phone: 612-626-0815 >>>>>> Minneapolis, MN 55414-3029 Cell: 612-812-9952 >>>>>> =============================================== >>>>>> _______________________________________________ >>>>>> GROW mailing list -- [email protected] >>>>>> To unsubscribe send an email to [email protected] >>>>>> >>>>> _______________________________________________ >>>>> GROW mailing list -- [email protected] >>>>> To unsubscribe send an email to [email protected] >>>>> >>>> _______________________________________________ >>>> GROW mailing list -- [email protected] >>>> To unsubscribe send an email to [email protected] >>>> >>>> -- =============================================== David Farmer Email:[email protected] Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
