Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
Support adoption as a WG item. Willing to contribute text, reviews, etc. Brian On Wed, Jul 29, 2020 at 10:17 AM Christopher Morrow < christopher.mor...@gmail.com> wrote: > Howdy WG Folks! > There's been significant chatter on-list about: > draft-mcbride-grow-as-path-prepend-01 > > Abstract: > "AS_Path prepending provides a tool to manipulate the BGP AS_Path >attribute through prepending multiple entries of an AS. AS_Path >prepend is used to deprioritize a route or alternate path. By >prepending the local ASN multiple times, ASes can make advertised AS >paths appear artificially longer. Excessive AS_Path prepending has >caused routing issues in the internet. This document provides >guidance,to the internet community, with how best to utilize AS_Path >prepend in order to avoid negatively affecting the internet." > > This work seems directly in the GROW wheelhouse, and it appears folk > on-list agree. Let's decide with a WG Adoption call for this document > and see if we should continue this work officially/etc. > > Please give it a read, and comment on adoption ideals here-in. > > thanks! > -chris > co-chair-persona > > ___ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow > ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
needs work and what better place than a working group? randy ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Proposed updates to GROW charter
I understand that GROW is specific to Global Routing Operations at the current time. Is the intention of the new charter to address BGP as a protocol when explicitly dealing with routing state for standalone or inter-connected ... or is the scope expanded to include BGP as it is currently deployed to support non-routing and hybrid use cases? BGP is used for across multiple FOUs i.e Kompella, EVPN, FlowSpec, BGP-LS etc... Each of these present unique operational challenges. Will the charter address these and other FOUs BGP is used for? Thanks, Jim Uttaro -Original Message- From: GROW On Behalf Of Christopher Morrow Sent: Wednesday, July 29, 2020 5:17 PM To: Alvaro Retana Cc: ; grow@ietf.org grow@ietf.org ; Warren Kumari Subject: Re: [GROW] Proposed updates to GROW charter On Wed, Jul 29, 2020 at 8:54 PM Alvaro Retana wrote: > > Job: > > Hi! > > > Thanks for addressing my comments! > > > I have just a couple more things: > > - The use of "Internet networks" doesn't sound right...perhaps "Internet- > connected networks"? Looking at the rest of the charter, I assume that, Job an I had a concern (I think we both shared this concern) about limiting the problems/solutions/monitoring/etc to 'internet-connected'. I think that 'bgp' (or external routing protocols) are used on both 'internet connected' and 'all the other' IP networks, right? should the benefits GROW pushes for be limited to 'internet connected' ? (I agree the current wording could use some help, how do we capture the idea that any IP network that ends up using a bgp can benefit?) > for example, the operations of BGP in a non-Internet-connected network (a > data center, for example) is not within the scope of grow. Is that the > intent, or am I reading too much into it? i think we were hoping to cover both, actually. our wording choice wasn't great :) > - [nit] The last goal talks about "preventing malpractice in the global > routing system". I'm not sure documentation can stop someone from doing > the wrong thing -- especially if they want to. Maybe this goal can be > worded positively: Document best practices and recommendations to assist > in the proper operation of the global routing system. sounds ok to me :) > Thanks! > > Alvaro. > > > > On July 29, 2020 at 1:07:06 PM, Job Snijders > (j...@ntt.net(mailto:j...@ntt.net)) wrote: > > > Dear all, > > > > Below is a third revision of the charter proposal, we attempted to > > incorporate all the feedback received so far, specifically Alvaro's. > > > > Please let us know your feedback! > > > > Kind regards, > > > > Job & Chris > > > > -- > > > > Charter for Working Group > > == > > > > The purpose of GROW is to consider the operational problems associated > > with the Internet Protocol (IP) global routing systems, including but > > not limited to default-free zone routing table growth, effects of the > > interactions between interior and exterior routing protocols, the effect > > of address allocation policies, or practices on the global routing > > system. Where appropriate, GROW documents the operational aspects of > > measurement, monitoring, policy, routing system security, VPN > > infrastructures, or safe default behavior of IP routing protocol > > implementations and deployments. > > > > GROW will also advise various working groups, specifically IDR and > > SIDROPS, with respect to whether it is addressing the relevant > > operational and routing security requirements of Internet networks, > > and where appropriate, suggest course corrections. Finally, operational > > requirements developed in GROW can also be used by any working group > > chartered with standardizing a next generation inter-domain routing > > protocol. > > > > GOALS > > - > > > > * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) > > * Provide stewardship and maintenance for the Multi-Threaded Routing > > Toolkit (MRT) Routing Information Export Format > > * Document Best Current Practises for operations of the Internet global > > routing system. > > * Analyze aspects for supporting new applications, including extending > > existing routing protocols or creating new ones. This includes risk, > > interference, and application fit. > > * Document the operational aspects of securing the Internet routing > > system, and provide recommendations to other WGs. > > * Provide documentation to assist in preventing malpractice in the > > global routing system. > > > > Milestones > > -- > > > > 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG > > 2020 - "BMP Peer Up Message Namespace" to IESG > > 2020 - "Revision to Registration Procedures for Multiple BMP Registries" to > > IESG. > > 2021 - "Document negative consequences of de-aggregating received routes > > for traffic engineering purposes" - to IESG > > 2021 - "TLV support for BMP Route
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
I support adoption and also left a few comments in a separate thread. Best regards, Martijn From: GROW on behalf of Jakob Heitz (jheitz) Sent: 29 July 2020 23:27 To: Christopher Morrow ; grow-...@tools.ietf.org ; ; grow@ietf.org grow@ietf.org Subject: Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12) I support adoption. Already gave comments in a separate thread. Regards, Jakob. -Original Message- From: GROW On Behalf Of Christopher Morrow Sent: Wednesday, July 29, 2020 10:17 AM To: grow-...@tools.ietf.org; ; grow@ietf.org grow@ietf.org Subject: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12) Howdy WG Folks! There's been significant chatter on-list about: draft-mcbride-grow-as-path-prepend-01 Abstract: "AS_Path prepending provides a tool to manipulate the BGP AS_Path attribute through prepending multiple entries of an AS. AS_Path prepend is used to deprioritize a route or alternate path. By prepending the local ASN multiple times, ASes can make advertised AS paths appear artificially longer. Excessive AS_Path prepending has caused routing issues in the internet. This document provides guidance,to the internet community, with how best to utilize AS_Path prepend in order to avoid negatively affecting the internet." This work seems directly in the GROW wheelhouse, and it appears folk on-list agree. Let's decide with a WG Adoption call for this document and see if we should continue this work officially/etc. Please give it a read, and comment on adoption ideals here-in. thanks! -chris co-chair-persona ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Proposed updates to GROW charter
On July 29, 2020 at 5:17:04 PM, Christopher Morrow wrote: > On Wed, Jul 29, 2020 at 8:54 PM Alvaro Retana wrote: Chris: Hi! ... > > - The use of "Internet networks" doesn't sound right...perhaps "Internet- > > connected networks"? Looking at the rest of the charter, I assume that, > > Job an I had a concern (I think we both shared this concern) about limiting > the problems/solutions/monitoring/etc to 'internet-connected'. > I think that 'bgp' (or external routing protocols) are used on both > 'internet connected' and 'all the other' IP networks, right? > should the benefits GROW pushes for be limited to 'internet connected' ? > > (I agree the current wording could use some help, how do we capture > the idea that any IP network that ends up using a bgp can benefit?) > > > for example, the operations of BGP in a non-Internet-connected network (a > > data center, for example) is not within the scope of grow. Is that the > > intent, or am I reading too much into it? > > i think we were hoping to cover both, actually. our wording choice > wasn't great :) Personally, I think that benefiting all networks would be better. But then I think there's maybe some more words required to set the right scope. A couple of questions: - Does grow want to focus on "global routing" (which seems to imply Internet-connected) or on general routing operations? Or maybe operations of inter-domain routing protocols? - So far the focus has been on exterior routing, so mainly interacting with sidrops/idr makes sense. The first paragraph talks about "interactions between interior and exterior routing protocols"; should the operation of the IGPs also be in scope? All of them? I think that we could debate this forever. Assuming that the WG wants to keep the current focus, a simple change might be: OLD> GROW will also advise various working groups, specifically IDR and SIDROPS, with respect to whether it is addressing the relevant operational and routing security requirements of Internet networks, and where appropriate, suggest course corrections. NEW> GROW will also advise various working groups, mainly IDR and SIDROPS, with respect to whether it is addressing the relevant operational and routing security requirements of networks using inter-domain routing protocols, and where appropriate, suggest course corrections. At this point I'm just suggesting a color for the bike shed... Thanks! Alvaro. ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
I support adoption. Already gave comments in a separate thread. Regards, Jakob. -Original Message- From: GROW On Behalf Of Christopher Morrow Sent: Wednesday, July 29, 2020 10:17 AM To: grow-...@tools.ietf.org; ; grow@ietf.org grow@ietf.org Subject: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12) Howdy WG Folks! There's been significant chatter on-list about: draft-mcbride-grow-as-path-prepend-01 Abstract: "AS_Path prepending provides a tool to manipulate the BGP AS_Path attribute through prepending multiple entries of an AS. AS_Path prepend is used to deprioritize a route or alternate path. By prepending the local ASN multiple times, ASes can make advertised AS paths appear artificially longer. Excessive AS_Path prepending has caused routing issues in the internet. This document provides guidance,to the internet community, with how best to utilize AS_Path prepend in order to avoid negatively affecting the internet." This work seems directly in the GROW wheelhouse, and it appears folk on-list agree. Let's decide with a WG Adoption call for this document and see if we should continue this work officially/etc. Please give it a read, and comment on adoption ideals here-in. thanks! -chris co-chair-persona ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Proposed updates to GROW charter
On Wed, Jul 29, 2020 at 8:54 PM Alvaro Retana wrote: > > Job: > > Hi! > > > Thanks for addressing my comments! > > > I have just a couple more things: > > - The use of "Internet networks" doesn't sound right...perhaps "Internet- > connected networks"? Looking at the rest of the charter, I assume that, Job an I had a concern (I think we both shared this concern) about limiting the problems/solutions/monitoring/etc to 'internet-connected'. I think that 'bgp' (or external routing protocols) are used on both 'internet connected' and 'all the other' IP networks, right? should the benefits GROW pushes for be limited to 'internet connected' ? (I agree the current wording could use some help, how do we capture the idea that any IP network that ends up using a bgp can benefit?) > for example, the operations of BGP in a non-Internet-connected network (a > data center, for example) is not within the scope of grow. Is that the > intent, or am I reading too much into it? i think we were hoping to cover both, actually. our wording choice wasn't great :) > - [nit] The last goal talks about "preventing malpractice in the global > routing system". I'm not sure documentation can stop someone from doing > the wrong thing -- especially if they want to. Maybe this goal can be > worded positively: Document best practices and recommendations to assist > in the proper operation of the global routing system. sounds ok to me :) > Thanks! > > Alvaro. > > > > On July 29, 2020 at 1:07:06 PM, Job Snijders > (j...@ntt.net(mailto:j...@ntt.net)) wrote: > > > Dear all, > > > > Below is a third revision of the charter proposal, we attempted to > > incorporate all the feedback received so far, specifically Alvaro's. > > > > Please let us know your feedback! > > > > Kind regards, > > > > Job & Chris > > > > -- > > > > Charter for Working Group > > == > > > > The purpose of GROW is to consider the operational problems associated > > with the Internet Protocol (IP) global routing systems, including but > > not limited to default-free zone routing table growth, effects of the > > interactions between interior and exterior routing protocols, the effect > > of address allocation policies, or practices on the global routing > > system. Where appropriate, GROW documents the operational aspects of > > measurement, monitoring, policy, routing system security, VPN > > infrastructures, or safe default behavior of IP routing protocol > > implementations and deployments. > > > > GROW will also advise various working groups, specifically IDR and > > SIDROPS, with respect to whether it is addressing the relevant > > operational and routing security requirements of Internet networks, > > and where appropriate, suggest course corrections. Finally, operational > > requirements developed in GROW can also be used by any working group > > chartered with standardizing a next generation inter-domain routing > > protocol. > > > > GOALS > > - > > > > * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) > > * Provide stewardship and maintenance for the Multi-Threaded Routing > > Toolkit (MRT) Routing Information Export Format > > * Document Best Current Practises for operations of the Internet global > > routing system. > > * Analyze aspects for supporting new applications, including extending > > existing routing protocols or creating new ones. This includes risk, > > interference, and application fit. > > * Document the operational aspects of securing the Internet routing > > system, and provide recommendations to other WGs. > > * Provide documentation to assist in preventing malpractice in the > > global routing system. > > > > Milestones > > -- > > > > 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG > > 2020 - "BMP Peer Up Message Namespace" to IESG > > 2020 - "Revision to Registration Procedures for Multiple BMP Registries" to > > IESG. > > 2021 - "Document negative consequences of de-aggregating received routes > > for traffic engineering purposes" - to IESG > > 2021 - "TLV support for BMP Route Monitoring and Peer Down Messages" to > > IESG. > > 2021 - "A BCP on using IRR and RPKI data to improve filtering of BGP > > peering sessions" to IESG or via "Evolving Documents" > > > > > > ___ > > GROW mailing list > > GROW@ietf.org > > https://www.ietf.org/mailman/listinfo/grow ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Proposed updates to GROW charter
Job: Hi! Thanks for addressing my comments! I have just a couple more things: - The use of "Internet networks" doesn't sound right...perhaps "Internet- connected networks"? Looking at the rest of the charter, I assume that, for example, the operations of BGP in a non-Internet-connected network (a data center, for example) is not within the scope of grow. Is that the intent, or am I reading too much into it? - [nit] The last goal talks about "preventing malpractice in the global routing system". I'm not sure documentation can stop someone from doing the wrong thing -- especially if they want to. Maybe this goal can be worded positively: Document best practices and recommendations to assist in the proper operation of the global routing system. Thanks! Alvaro. On July 29, 2020 at 1:07:06 PM, Job Snijders (j...@ntt.net(mailto:j...@ntt.net)) wrote: > Dear all, > > Below is a third revision of the charter proposal, we attempted to > incorporate all the feedback received so far, specifically Alvaro's. > > Please let us know your feedback! > > Kind regards, > > Job & Chris > > -- > > Charter for Working Group > == > > The purpose of GROW is to consider the operational problems associated > with the Internet Protocol (IP) global routing systems, including but > not limited to default-free zone routing table growth, effects of the > interactions between interior and exterior routing protocols, the effect > of address allocation policies, or practices on the global routing > system. Where appropriate, GROW documents the operational aspects of > measurement, monitoring, policy, routing system security, VPN > infrastructures, or safe default behavior of IP routing protocol > implementations and deployments. > > GROW will also advise various working groups, specifically IDR and > SIDROPS, with respect to whether it is addressing the relevant > operational and routing security requirements of Internet networks, > and where appropriate, suggest course corrections. Finally, operational > requirements developed in GROW can also be used by any working group > chartered with standardizing a next generation inter-domain routing > protocol. > > GOALS > - > > * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) > * Provide stewardship and maintenance for the Multi-Threaded Routing > Toolkit (MRT) Routing Information Export Format > * Document Best Current Practises for operations of the Internet global > routing system. > * Analyze aspects for supporting new applications, including extending > existing routing protocols or creating new ones. This includes risk, > interference, and application fit. > * Document the operational aspects of securing the Internet routing > system, and provide recommendations to other WGs. > * Provide documentation to assist in preventing malpractice in the > global routing system. > > Milestones > -- > > 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG > 2020 - "BMP Peer Up Message Namespace" to IESG > 2020 - "Revision to Registration Procedures for Multiple BMP Registries" to > IESG. > 2021 - "Document negative consequences of de-aggregating received routes for > traffic engineering purposes" - to IESG > 2021 - "TLV support for BMP Route Monitoring and Peer Down Messages" to IESG. > 2021 - "A BCP on using IRR and RPKI data to improve filtering of BGP peering > sessions" to IESG or via "Evolving Documents" > > > ___ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
I support adoption too (no hats) On Wed, Jul 29, 2020 at 05:19:07PM +, Christopher Morrow wrote: > + the real slim-shady. > > On Wed, Jul 29, 2020 at 5:17 PM Christopher Morrow > wrote: > > > > Howdy WG Folks! > > There's been significant chatter on-list about: > > draft-mcbride-grow-as-path-prepend-01 > > > > Abstract: > > "AS_Path prepending provides a tool to manipulate the BGP AS_Path > >attribute through prepending multiple entries of an AS. AS_Path > >prepend is used to deprioritize a route or alternate path. By > >prepending the local ASN multiple times, ASes can make advertised AS > >paths appear artificially longer. Excessive AS_Path prepending has > >caused routing issues in the internet. This document provides > >guidance,to the internet community, with how best to utilize AS_Path > >prepend in order to avoid negatively affecting the internet." > > > > This work seems directly in the GROW wheelhouse, and it appears folk > > on-list agree. Let's decide with a WG Adoption call for this document > > and see if we should continue this work officially/etc. > > > > Please give it a read, and comment on adoption ideals here-in. > > > > thanks! > > -chris > > co-chair-persona ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
Christopher Morrow wrote on 29/07/2020 18:17: This work seems directly in the GROW wheelhouse, and it appears folk on-list agree. Let's decide with a WG Adoption call for this document and see if we should continue this work officially/etc. sounds good for adoption. Nick ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
Hi all, On 07/29, Christopher Morrow wrote: > Howdy WG Folks! > There's been significant chatter on-list about: > draft-mcbride-grow-as-path-prepend-01 > > Abstract: > "AS_Path prepending provides a tool to manipulate the BGP AS_Path >attribute through prepending multiple entries of an AS. AS_Path >prepend is used to deprioritize a route or alternate path. By >prepending the local ASN multiple times, ASes can make advertised AS >paths appear artificially longer. Excessive AS_Path prepending has >caused routing issues in the internet. This document provides >guidance,to the internet community, with how best to utilize AS_Path >prepend in order to avoid negatively affecting the internet." > > This work seems directly in the GROW wheelhouse, and it appears folk > on-list agree. Let's decide with a WG Adoption call for this document > and see if we should continue this work officially/etc. > Agreed. I support adoption. Cheers, Ben > Please give it a read, and comment on adoption ideals here-in. > > thanks! > -chris > co-chair-persona > > ___ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow signature.asc Description: PGP signature ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
Support Thx, r. On Wed, Jul 29, 2020 at 7:17 PM Christopher Morrow < christopher.mor...@gmail.com> wrote: > Howdy WG Folks! > There's been significant chatter on-list about: > draft-mcbride-grow-as-path-prepend-01 > > Abstract: > "AS_Path prepending provides a tool to manipulate the BGP AS_Path >attribute through prepending multiple entries of an AS. AS_Path >prepend is used to deprioritize a route or alternate path. By >prepending the local ASN multiple times, ASes can make advertised AS >paths appear artificially longer. Excessive AS_Path prepending has >caused routing issues in the internet. This document provides >guidance,to the internet community, with how best to utilize AS_Path >prepend in order to avoid negatively affecting the internet." > > This work seems directly in the GROW wheelhouse, and it appears folk > on-list agree. Let's decide with a WG Adoption call for this document > and see if we should continue this work officially/etc. > > Please give it a read, and comment on adoption ideals here-in. > > thanks! > -chris > co-chair-persona > > ___ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow > ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
+ the real slim-shady. On Wed, Jul 29, 2020 at 5:17 PM Christopher Morrow wrote: > > Howdy WG Folks! > There's been significant chatter on-list about: > draft-mcbride-grow-as-path-prepend-01 > > Abstract: > "AS_Path prepending provides a tool to manipulate the BGP AS_Path >attribute through prepending multiple entries of an AS. AS_Path >prepend is used to deprioritize a route or alternate path. By >prepending the local ASN multiple times, ASes can make advertised AS >paths appear artificially longer. Excessive AS_Path prepending has >caused routing issues in the internet. This document provides >guidance,to the internet community, with how best to utilize AS_Path >prepend in order to avoid negatively affecting the internet." > > This work seems directly in the GROW wheelhouse, and it appears folk > on-list agree. Let's decide with a WG Adoption call for this document > and see if we should continue this work officially/etc. > > Please give it a read, and comment on adoption ideals here-in. > > thanks! > -chris > co-chair-persona ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
[GROW] [WG ADOPTION]: draft-mcbride-grow-as-path-prepend-01 - ENDS 08/12/2020 (Aug 12)
Howdy WG Folks! There's been significant chatter on-list about: draft-mcbride-grow-as-path-prepend-01 Abstract: "AS_Path prepending provides a tool to manipulate the BGP AS_Path attribute through prepending multiple entries of an AS. AS_Path prepend is used to deprioritize a route or alternate path. By prepending the local ASN multiple times, ASes can make advertised AS paths appear artificially longer. Excessive AS_Path prepending has caused routing issues in the internet. This document provides guidance,to the internet community, with how best to utilize AS_Path prepend in order to avoid negatively affecting the internet." This work seems directly in the GROW wheelhouse, and it appears folk on-list agree. Let's decide with a WG Adoption call for this document and see if we should continue this work officially/etc. Please give it a read, and comment on adoption ideals here-in. thanks! -chris co-chair-persona ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Proposed updates to GROW charter
Dear all, Below is a third revision of the charter proposal, we attempted to incorporate all the feedback received so far, specifically Alvaro's. Please let us know your feedback! Kind regards, Job & Chris -- Charter for Working Group == The purpose of GROW is to consider the operational problems associated with the Internet Protocol (IP) global routing systems, including but not limited to default-free zone routing table growth, effects of the interactions between interior and exterior routing protocols, the effect of address allocation policies, or practices on the global routing system. Where appropriate, GROW documents the operational aspects of measurement, monitoring, policy, routing system security, VPN infrastructures, or safe default behavior of IP routing protocol implementations and deployments. GROW will also advise various working groups, specifically IDR and SIDROPS, with respect to whether it is addressing the relevant operational and routing security requirements of Internet networks, and where appropriate, suggest course corrections. Finally, operational requirements developed in GROW can also be used by any working group chartered with standardizing a next generation inter-domain routing protocol. GOALS - * Provide stewardship and maintenance for the BGP Monitoring Protocol (BMP) * Provide stewardship and maintenance for the Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format * Document Best Current Practises for operations of the Internet global routing system. * Analyze aspects for supporting new applications, including extending existing routing protocols or creating new ones. This includes risk, interference, and application fit. * Document the operational aspects of securing the Internet routing system, and provide recommendations to other WGs. * Provide documentation to assist in preventing malpractice in the global routing system. Milestones -- 2020 - "Support for Local RIB in BGP Monitoring Protocol (BMP)" to IESG 2020 - "BMP Peer Up Message Namespace" to IESG 2020 - "Revision to Registration Procedures for Multiple BMP Registries" to IESG. 2021 - "Document negative consequences of de-aggregating received routes for traffic engineering purposes" - to IESG 2021 - "TLV support for BMP Route Monitoring and Peer Down Messages" to IESG. 2021 - "A BCP on using IRR and RPKI data to improve filtering of BGP peering sessions" to IESG or via "Evolving Documents" ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
