[GROW]Re: I-D Action: draft-ietf-grow-as-path-prepending-09.txt

[Michael McBride]

Hi Job, wg,

Once again ready for wglc. To better future proof the draft, we softened the 5 
prepend recommendation from:

   *  There is no need to prepend more than 5 ASs.  The following
      diagram, from the previously referenced AS Path Prepending
      analysis from 2019, shows that 90% of AS path lengths are 5 ASNs
      or fewer in length.

To:


   *  As can be seen from the following diagram (reproduced from

      [Excessive_AS_Path_Prepending]), prepending more than 5 times

      rarely provides any benefit.  Note that routing patterns may

      change over time and may be different in various parts of the

      internet.  A looking glass, as provided by many Internet Service

      Providers, can be used to get a better understanding of as-path

      length of an IP address prefix of interest.

mike


From: GROW <grow-boun...@ietf.org> On Behalf Of Michael McBride
Sent: Tuesday, April 9, 2024 2:04 AM
To: Job Snijders <j...@fastly.com>
Cc: grow@ietf.org
Subject: Re: [GROW] I-D Action: draft-ietf-grow-as-path-prepending-09.txt

Hi Job,

Please let us know if there is anything needed to help progress this draft.

Thanks,
mike


From: GROW <grow-boun...@ietf.org<mailto:grow-boun...@ietf.org>> On Behalf Of 
Michael McBride
Sent: Wednesday, February 7, 2024 11:20 PM
To: David Farmer <far...@umn.edu<mailto:far...@umn.edu>>
Cc: grow@ietf.org<mailto:grow@ietf.org>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-as-path-prepending-09.txt

Really appreciate the comments David, very helpful.

I incorporated all of your additional suggestions (added sentence to security 
section, created informational references section, moved links to informational 
section).

Back to you Job.

Thank you.
mike


From: David Farmer <far...@umn.edu<mailto:far...@umn.edu>>
Sent: Wednesday, February 7, 2024 7:21 AM
To: Michael McBride 
<michael.mcbr...@futurewei.com<mailto:michael.mcbr...@futurewei.com>>
Cc: grow@ietf.org<mailto:grow@ietf.org>; Job Snijders 
<j...@fastly.com<mailto:j...@fastly.com>>
Subject: Re: [GROW] I-D Action: draft-ietf-grow-as-path-prepending-09.txt

Also, the links to the articles "Geoff Huston's Path Prepending in BGP" and 
"Excessive AS Path Prepending" should be informational references instead of 
embedded links.

Thanks

On Wed, Feb 7, 2024 at 9:13 AM David Farmer 
<far...@umn.edu<mailto:far...@umn.edu>> wrote:
Speaking of informational references, all the references are normative. That 
doesn't seem correct. The references to RFC 5398, RFC 5738, and RFC 8195 seem 
to be informational references, in my opinion.

Thanks

On Wed, Feb 7, 2024 at 9:03 AM David Farmer 
<far...@umn.edu<mailto:far...@umn.edu>> wrote:


On Wed, Feb 7, 2024 at 7:54 AM Job Snijders 
<j...@fastly.com<mailto:j...@fastly.com>> wrote:
On Tue, Feb 06, 2024 at 09:11:12PM -0600, David Farmer wrote:
> If you keep it as updating RFC 7454, I believe you need to say it does
> so in the abstract. Also, somewhere in the document, probably in the
> introduction, you need to explain how it updates RFC 7454, that is how
> this document relates to RFC 7454.

Thanks David, that's how I understand the process too.

If the contents of draft-ietf-grow-as-path-prepending actually update
7454 (which currently doesn't seem the case), the working group has to
think about how that aligns with the 'big update' of 7454 happening in
https://datatracker.ietf.org/doc/draft-ietf-grow-bgpopsecupd/


Job, thanks for the pointer to the update of 7454. Given that it already 
includes references to this document, that will ensure readers of it know about 
this document. Which is the purpose of including the Updates metadata header.

I guess my final thought on the subject is whether there should be an 
informational reference to RFC 7454, maybe in the security considerations 
section.

Here is a suggestion: Add a new final paragraph to the security considerations 
section;

For a more comprehensive discussion of BGP Operations and Security, see 
[RFC7454].

Do with it what you will.

Thanks.


--
===============================================
David Farmer               Email:far...@umn.edu<mailto:email%3afar...@umn.edu>
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
===============================================


--
===============================================
David Farmer               Email:far...@umn.edu<mailto:email%3afar...@umn.edu>
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
===============================================


--
===============================================
David Farmer               Email:far...@umn.edu<mailto:email%3afar...@umn.edu>
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 -- grow@ietf.org
To unsubscribe send an email to grow-le...@ietf.org