Hello Jeff, Sorry for the (extremely) late reply.
Le sam. 4 nov. 2023 à 10:41, Jeffrey Haas <[email protected]> a écrit : > On Tue, Oct 24, 2023 at 01:34:17PM +0200, Job Snijders wrote: > > The authors of draft-francois-grow-bmp-loc-peer asked whether GROW > > working group could consider adoption of the internet-draft. > > > > This message is a request to the group for feedback on whether this > > internet-draft should be adopted. > > I think the work should be adopted. > > Further comments for the authors on this version: > > - The address selector is sufficient for ipv4, ipv6, but not ipv6 > link-local > addresses. > That's a good point. We could add an "Address Type" field in the TLV, IPv4, IPv6, and "IPv6 Link-Local" which would allow to define an interface id or interface name bound with that ipv6 address. To keep the footprint as low as possible we'd prefer an interface id "à la" SNMP but if this is not flexible enough a string for the interface name could work too. > - The authors should consider what, if anything, should be done about BGP > routes learned from non-BGP live speakers; e.g. APIs or static > configuration. > In 2.1 we specify that self-originated routes are advertised with a zero value Peer Address in the TLV. To the best of our knowledge, API and statically configured routes would fall under that category. Are we missing something? Do you mean something different than this by "APIs or static"? > - Probably a general comment on the TLV procedures over-all, the error > handling for cases of conflicting information from the TLVs needs to be > addressed. For example, what if NLRI index 5 is present both in a group > and individually and conflicting state is expressed. > We'll happily let the authors of draft-ietf-grow-bmp-tlv reply to this :) We'll align with whatever they decide if there are any changes to make on our side. Regards, > > -- Jeff > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow >
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
