Hello, I see the following proposal, which I reckon references to de-aggregation oopsies by so-called "route optimizers":
Jul 2020 - “Document negative consequences of de-aggregating received routes for traffic engineering purposes” - to IESG And that reminds me of something - what about the inverse where the originating ISP is overdoing their traffic engineering by selectively announcing de-aggregated routes alongside an overarching supernet? It's not a huge problem from a routing security perspective, but this is a major challenge in routing traffic locally outside well-established markets, especially when the ISP in question backhauls some (but not all) of their upstream providers over very long submarine paths. Best regards, Martijn Schmidt ________________________________ From: GROW <[email protected]> on behalf of Paolo Lucente <[email protected]> Sent: 02 November 2019 08:49:02 To: Nick Hilliard <[email protected]>; Job Snijders <[email protected]> Cc: <[email protected]> <[email protected]>; [email protected] [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: [GROW] Proposed updates to GROW charter Dears, Please add Multi-threaded Routing Toolkit (MRT). Paolo > On 31 Oct 2019, at 16:55, Nick Hilliard <[email protected]> wrote: > > Job Snijders wrote on 29/10/2019 00:10: >> My hope is that the proposed update aligns our description with our >> activities. > > It does, but it also aligns with lots of other things. Too generic is not a > good thing. > > That said, GROW fulfils an important niche at IETF, not just for producing > its own RFCs, but also acting as a reference point for other WGs. So it > badly needs not to be closed down (randy, take note). > > I've re-worked your proposal. Please feel free to add / remove / modify / > ignore / throw in volcano as you see fit. > > * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) > * Develop and document Best Current Practises for operations in the Internet > routing system. > * Develop and document the operational aspects of securing the Internet > routing system including management of filtering and routing leaks. > * Analyse, document and provide best practice characteristics of running BGP > at large scale > * Provide analysis, feedback and assistance for other IETF working groups > when their subject matter impacts on the global Internet routing ecosystem.. > > Nick > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
