Thank you for the comments Martin, very helpful. I'll try to get an update out by end of week which incorporates your feedback along with Alejandro's.
mike -----Original Message----- From: GROW <[email protected]> On Behalf Of Martin Pels Sent: Tuesday, January 9, 2024 1:00 AM To: [email protected] Subject: Re: [GROW] I-D Action: draft-ietf-grow-as-path-prepending-09.txt Hi, Some comments ------------- Section 3.1 and 4: As has been mentioned before on this list, I think using the term "route leak" in this scenario is confusing. Something like "suboptimal" or "unintended" routing would be a better fit. 3.2 and 3.3: These do not appear to be separate problems, but rather two examples of the same problem (a malicious, shorter route being preferred over a legitimate, prepended route). 7: This only mentions the sending side. There is also security advice to be given to the accepting side (see section 3.5 and 3.6). Something like "Accepting routes with extremely long AS_PATHs may cause increased memory usage and possibly router crashes." A reference to ASPA may also be useful in this section, since this could help mitigate the effects of the route leaks described in 3.2 and 3.3. Text nits --------- Abstract: AS_Path attribute -> AS_PATH attribute multiple entries of an AS -> multiple entries of an ASN This document provides guidance with -> This document provides guidance for 1: the AS_PATH attribute which -> the AS_PATH attribute, which 2: today including -> today, including 4: more then 1 -> more than 1 Kind regards, Martin _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
