And, this was because the Large community authors – wanted it as just a number.

Individuals even said, there would be no use for well-known large BGP 
communities.

Sue

From: Jeffrey Haas <[email protected]>
Sent: Friday, June 7, 2024 5:24 PM
To: Robert Raszuk <[email protected]>
Cc: Job Snijders <[email protected]>; David Farmer 
<[email protected]>; [email protected]
Subject: [GROW]Re: I-D Action: draft-ietf-grow-ixp-ext-comms-00.txt

There is no such thing as a well known large bgp community. Jeff  ‌  ‌  ‌  ‌  ‌ 
 ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  
‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌ 
 ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌  ‌
External ([email protected]<mailto:[email protected]>)
  Report This 
Email<https://protection.inkyphishfence.com/report?id=bmV0b3JnMTA1ODY5MTIvc2hhcmVzQG5kemguY29tLzI4MTFiNzZmMjNmZWMwZTBhZGIzNjVlMzlkZDM3Yzg5LzE3MTc3OTU0NjMuMTI=#key=de5a2d80c9582815787a5df9fee0dc36>
  
FAQ<https://www.godaddy.com/help/report-email-with-advanced-email-security-40813>
  GoDaddy Advanced Email Security, Powered by 
INKY<https://www.inky.com/protection-by-inky>

There is no such thing as a well known large bgp community.


Jeff


On Jun 7, 2024, at 15:51, Robert Raszuk 
<[email protected]<mailto:[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 
<[email protected]<mailto:[email protected]>> wrote:
Thanks David, we will incorporate this in the next revision

On Fri, 7 Jun 2024 at 21:15, David Farmer 
<[email protected]<mailto:[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]<mailto:[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/<https://shared.outlook.inky.com/link?domain=datatracker.ietf.org&t=h.eJwVjk0OgyAYBa9iWBcQqCKuvArCh1h_MICpadO7V7aTeZP3RWdcUV8hn_ORekqtzjpHbRaIZIbsSIgTtcFQG7XLuCA8xfDG83VguDI2YdsSRY8KLaWzQ74XrG66VjFOk9cR0rDbjye3SXnH2Chbx4UDU0Ot7SjaBoSyVkjTKcokk1I1z1YQxksVSvXltU7D4aIpfwq2N97Pdf39AUdkPIA.MEUCIQD2wg69pW7vBVOCiVVz6iV_4wFKi2zCPKrd76RXAqPtOAIgeLcbb_8m0i-ZvjXnd-X1IE75I23zs4FtJdyQWMNNYVE>

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-grow-ixp-ext-comms-00<https://shared.outlook.inky.com/link?domain=datatracker.ietf.org&t=h.eJwVjssOgyAUBX_FsC4CUkVc-SsIF7E-A9fUtOm_V7aTOZPzJWdcSFeQgHikjjFn0GA0doZYToC-3OPI3G5ZwHVhLhqPNHM6xv1Np-ugcCG1-7omyjl5FGTOuQ3wHgpet40WFUvBREj95j6hvF1WtUIMqvGV9GA5cOMG2dQgtXNS2VYzoYRSun42shRVrkKuvoIxqT98tPlWxu7G27ksvz8b-D7C.MEYCIQDmernls7g0_RxxLuXFmRXQnLVCM8ysNbCdSV1Hf9fBmwIhAJ4zn01CrF1doFoMO-fMTz0E6ERxdRivAmJuZnz_fS5N>

Internet-Drafts are also available by rsync at:
rsync.ietf.org<https://shared.outlook.inky.com/link?domain=rsync.ietf.org&t=h.eJw1jUEOwiAUBa_SsDbQDwKlq16FwkfUShugi2q8u2Xh8s0k8z5kzwsZOxJr3UbGcjmSo3esga75Ri4deTabsJ4TejkoA5yVaDOWKfl3pG59MT4AzFoFLgK6HnvrZ6EkCuO90G4wDDRobeRVCQq8VbFVH9HaMm0hu_-ZP3Hal-X7A8mULNk.MEQCIHrZacaRUBB3GjPmp_X7o6Rb-iHXJrpt3ibi3xmrQzsEAiBLECO9B2OXdwsQ7YfEu_fM56VdgK4dEqbhMne77i9iiw>::internet-drafts


_______________________________________________
GROW mailing list -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to [email protected]<mailto:[email protected]>


--
===============================================
David Farmer               Email:[email protected]<mailto:email%[email protected]>
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave 
SE<https://shared.outlook.inky.com/link?domain=www.google.com&t=h.eJwdzMEOgiAYAOBXaRy62EQgRd1adegJWg9A8AsWggPMVevdy67f4XujKVjUrpBJaYwtxvM859p7bSGXfsCDGCOOIII0mFJSZxfXPyDEPj2z4wOy82kPLoXnTg-it-vopyBhp9Fmhe5L6yD5oElR1lVDKI5GBIgHp17m39OakCuvOso6kAUUQl1ZVQJrlGJc1g0mnHDelNuK5YQuKyzrzQgRD2MXZP7bF1Y_dpO1ny8ni0FZ.MEQCIFTX9gJv92ZPcOKqt2aTxmsnVa9pqO_XHRdQjg_rMYJnAiAn_0xuVUF51LoD_z6YUjBy8TVWTtFeGWxZWriZr9SXhQ>
        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================
_______________________________________________
GROW mailing list -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________
GROW mailing list -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________
GROW mailing list -- [email protected]<mailto:[email protected]>
To unsubscribe send an email to [email protected]<mailto:[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]

Reply via email to