Moin, thank you for sharing the review. I just went through the points below and made corresponding changes to the document in -09, which I just uploaded.
Please find details below and the diff here: https://author-tools.ietf.org/iddiff?url1=draft-ietf-grow-bgpopsecupd-08&url2=draft-ietf-grow-bgpopsecupd-09&difftype=--html With best regards, Tobias > Major: > - Section 4.1: the second bullet is not great for a standards doc: > "All ASes left of the originating AS in the AS_PATH MUST be > authorized to > advertise the NLRI to the AS directly to their left,.." > > Suggest the following: > "Let AS_PATH = {AS1, AS2, …, ASn}, where AS1 is the neighbor that > sent the > UPDATE and ASn is the origin. For each k in 1..n−1, AS(k+1) > MUST/SHOULD be > authorized to export the NLRI to ASk according to their bilateral > routing > policy (e.g., provider–customer, peer, or lateral-peer)." Implemented a slightly adjusted version of this text to better align with the overall text flow. > Minor: > - Section 3.1 lists desired properties (prevent off-path injection, > interruption, etc.) but gives no references (e.g., GTSM/TTL-security, > TCP-AO, > BGP-MD5, CoPP/CP-policing, max-prefix). It would be helpful to > readers to have > the informative references or a short “Examples include …” Added text along these lines. > NITS: > Section 2 Scope: > - suggest expand DFZ: “...routers in the Default-Free Zone (DFZ)" Addressed. > Section 3.2: > - “External activity towards the management interface do not > interfere …” -> > “does not interfere …”. Addressed. > Ack: Acknowledgements list has Martin Pels twice; Addressed. -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M [email protected] Pronouns: he/him/his _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
