Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
Oops! time passed... this looks to have finished successfully, could the authors please submit a new version (catch all the comments you care to) with the new proper naming as well? thanks! On Fri, Nov 6, 2015 at 7:42 AM, Rick Casarez wrote: > Support. > > --- > Cheers, Rick > > Experiences not things. > > On Wed, Nov 4, 2015 at 10:38 PM, Colin Petrie wrote: >> >> On 05/11/15 10:20, Jon Mitchell wrote: >> > Nit for author - any reason why such short abbreviation for ADDPATH (AP) >> > in section 4/5 subtypes while unicast/multicast spelled out - would it >> > be more readable as ADDPATH? >> >> I was using the 'AS4' abbreviation that is already in place as a >> suggestion. >> >> Spelling it out fully (like unicast/multicast) would really result in >> '_ADDITIONAL_PATH' - ADDPATH is still an abbreviation >> >> But yes I think you're right, ADDPATH makes it more readable, and is a >> reasonable compromise between the very short and the very long versions. >> It also seems to be the current abbreviated term used by most people. >> I'll change it in the next revision. >> >> > Feel free to ignore if implementations are >> > already in place/use. >> >> The current implementations that are being worked on are still at the >> point where this is fairly easy to change at this stage, I think. >> >> Thanks for the feedback. >> >> Colin >> >> ___ >> 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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
Support. --- Cheers, Rick Experiences not things. On Wed, Nov 4, 2015 at 10:38 PM, Colin Petrie wrote: > On 05/11/15 10:20, Jon Mitchell wrote: > > Nit for author - any reason why such short abbreviation for ADDPATH (AP) > > in section 4/5 subtypes while unicast/multicast spelled out - would it > > be more readable as ADDPATH? > > I was using the 'AS4' abbreviation that is already in place as a > suggestion. > > Spelling it out fully (like unicast/multicast) would really result in > '_ADDITIONAL_PATH' - ADDPATH is still an abbreviation > > But yes I think you're right, ADDPATH makes it more readable, and is a > reasonable compromise between the very short and the very long versions. > It also seems to be the current abbreviated term used by most people. > I'll change it in the next revision. > > > Feel free to ignore if implementations are > > already in place/use. > > The current implementations that are being worked on are still at the > point where this is fairly easy to change at this stage, I think. > > Thanks for the feedback. > > Colin > > ___ > 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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
On 05/11/15 10:20, Jon Mitchell wrote: > Nit for author - any reason why such short abbreviation for ADDPATH (AP) > in section 4/5 subtypes while unicast/multicast spelled out - would it > be more readable as ADDPATH? I was using the 'AS4' abbreviation that is already in place as a suggestion. Spelling it out fully (like unicast/multicast) would really result in '_ADDITIONAL_PATH' - ADDPATH is still an abbreviation But yes I think you're right, ADDPATH makes it more readable, and is a reasonable compromise between the very short and the very long versions. It also seems to be the current abbreviated term used by most people. I'll change it in the next revision. > Feel free to ignore if implementations are > already in place/use. The current implementations that are being worked on are still at the point where this is fairly easy to change at this stage, I think. Thanks for the feedback. Colin ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
On 02/11/15 17:48 +1100, Christopher Morrow wrote: > Please consider this the start of a 3 week Adoption call for the noted > draft who's abstract is: >"This document updates the Multi-threaded Routing Toolkit (MRT) export >format for Border Gateway Protocol (BGP) routing information by >extending it to support the Advertisement of Multiple Paths in BGP >extensions." > > Please read/comment/advise by: > 11/23/2015 - Nov 23 2015 Support for adoption. Nit for author - any reason why such short abbreviation for ADDPATH (AP) in section 4/5 subtypes while unicast/multicast spelled out - would it be more readable as ADDPATH? Feel free to ignore if implementations are already in place/use. Thanks, Jon ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
Support On Nov 3, 2015 7:45 PM, "Thomas King" wrote: > Hi all, > > I support this draft as Add-Path is important as well as MRT is. > > Best regards, > Thomas > > > On 2 Nov 2015, at 15:48, Christopher Morrow < > christopher.mor...@gmail.com> wrote: > > > > Howdy WG folks, > > > > Please consider this the start of a 3 week Adoption call for the noted > > draft who's abstract is: > > "This document updates the Multi-threaded Routing Toolkit (MRT) export > > format for Border Gateway Protocol (BGP) routing information by > > extending it to support the Advertisement of Multiple Paths in BGP > > extensions." > > > > Please read/comment/advise by: > > 11/23/2015 - Nov 23 2015 > > > > thanks! > > -chris > > grow-co-chair > > > > ___ > > 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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
Hi all, I support this draft as Add-Path is important as well as MRT is. Best regards, Thomas > On 2 Nov 2015, at 15:48, Christopher Morrow > wrote: > > Howdy WG folks, > > Please consider this the start of a 3 week Adoption call for the noted > draft who's abstract is: > "This document updates the Multi-threaded Routing Toolkit (MRT) export > format for Border Gateway Protocol (BGP) routing information by > extending it to support the Advertisement of Multiple Paths in BGP > extensions." > > Please read/comment/advise by: > 11/23/2015 - Nov 23 2015 > > thanks! > -chris > grow-co-chair > > ___ > GROW mailing list > GROW@ietf.org > https://www.ietf.org/mailman/listinfo/grow smime.p7s Description: S/MIME cryptographic signature ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
On 11/3/15 7:12 AM, Susan Hares wrote: > Multiple paths are a fact of life in many BGP deployments. Please accept > and publish soon. +1 > Sue Hares > > -Original Message- > From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of heasley > Sent: Monday, November 02, 2015 11:25 AM > To: Jeffrey Haas > Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org; > grow-...@tools.ietf.org > Subject: Re: [GROW] Working Group Adoption Call: > draft-petrie-grow-mrt-add-paths > > Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas: >>> Please consider this the start of a 3 week Adoption call for the >>> noted draft who's abstract is: >>> "This document updates the Multi-threaded Routing Toolkit (MRT) export >>> format for Border Gateway Protocol (BGP) routing information by >>> extending it to support the Advertisement of Multiple Paths in BGP >>> extensions." >> >> IMO, this one is a no-brainer. I encourage adoption, swift editing and > then ship as an RFC. > > Agree with Jeff. > > ___ > 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 > signature.asc Description: OpenPGP digital signature ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
Multiple paths are a fact of life in many BGP deployments. Please accept and publish soon. Sue Hares -Original Message- From: GROW [mailto:grow-boun...@ietf.org] On Behalf Of heasley Sent: Monday, November 02, 2015 11:25 AM To: Jeffrey Haas Cc: grow-cha...@ietf.org; grow@ietf.org grow@ietf.org; grow-...@tools.ietf.org Subject: Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas: > > Please consider this the start of a 3 week Adoption call for the > > noted draft who's abstract is: > > "This document updates the Multi-threaded Routing Toolkit (MRT) export > > format for Border Gateway Protocol (BGP) routing information by > > extending it to support the Advertisement of Multiple Paths in BGP > > extensions." > > IMO, this one is a no-brainer. I encourage adoption, swift editing and then ship as an RFC. Agree with Jeff. ___ 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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
Mon, Nov 02, 2015 at 05:27:15PM +0900, Jeffrey Haas: > > Please consider this the start of a 3 week Adoption call for the noted > > draft who's abstract is: > > "This document updates the Multi-threaded Routing Toolkit (MRT) export > > format for Border Gateway Protocol (BGP) routing information by > > extending it to support the Advertisement of Multiple Paths in BGP > > extensions." > > IMO, this one is a no-brainer. I encourage adoption, swift editing and then > ship as an RFC. Agree with Jeff. ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
Re: [GROW] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
I support the adoption of this draft. Thomas http://exa.net.uk/about/contact-us On 2 Nov 2015, at 6:48, Christopher Morrow wrote: > Howdy WG folks, > > Please consider this the start of a 3 week Adoption call for the noted > draft who's abstract is: > "This document updates the Multi-threaded Routing Toolkit (MRT) export > format for Border Gateway Protocol (BGP) routing information by > extending it to support the Advertisement of Multiple Paths in BGP > extensions." > > Please read/comment/advise by: > 11/23/2015 - Nov 23 2015 > > thanks! > -chris > grow-co-chair > > ___ > 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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
> On Nov 2, 2015, at 3:48 PM, Christopher Morrow > wrote: > > Howdy WG folks, > > Please consider this the start of a 3 week Adoption call for the noted > draft who's abstract is: > "This document updates the Multi-threaded Routing Toolkit (MRT) export > format for Border Gateway Protocol (BGP) routing information by > extending it to support the Advertisement of Multiple Paths in BGP > extensions." IMO, this one is a no-brainer. I encourage adoption, swift editing and then ship as an RFC. -- Jeff > > Please read/comment/advise by: > 11/23/2015 - Nov 23 2015 > > thanks! > -chris > grow-co-chair > > ___ > 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] Working Group Adoption Call: draft-petrie-grow-mrt-add-paths
I support adoption of this draft. Job ___ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
