Hello authors,
I have a couple of comments. 1. A received Prefix Originator Sub-TLV that has an invalid length (not 4 or 16) or a Reachable Address containing an invalid IPv4 or IPv6 address (dependent on address family of the associated prefix) MUST be considered invalid and ignored. Additionally, reception of such Sub-TLV SHOULD be logged as an error (subject to rate-limiting). Shouldn’t that be “Router address”? 2. If the originating node is advertising an OSPFv2 Router Address TLV [RFC3630<https://tools.ietf.org/html/rfc3630>] or an OSPFv3 Router IPv6 Address TLV [RFC5329<https://tools.ietf.org/html/rfc5329>], then that value is set in the Router Address field of the Prefix Originator Sub-TLV. When the orignating node is not advertising such an Wang, et al. Expires January 1, 2021 [Page 5] ________________________________ Internet-Draft OSPF Prefix Originator Extensions June 2020 address, implementations MAY support mechanisms to determine a reachable address belonging to the originating node to set in the Router Address field. Such mechanisms are outside the scope of this document. Originating -> originating I assume that the “Router address” picked by a router could be one of the addresses advertised by it with “N-bit” (Node SID) set or some other reachable address which uniquely identifies the router. Regards, S. Baalajee On 15/10/20, 11:46 AM, "Lsr on behalf of Christian Hopps" <lsr-boun...@ietf.org on behalf of cho...@chopps.org> wrote: This begins a 2 week WG Last Call, ending after Oct 29th, 2020, for: https://datatracker.ietf.org/doc/draft-ietf-lsr-ospf-prefix-originator/ The following IPR has been filed https://datatracker.ietf.org/ipr/3448/ Authors, Please indicate to the list, your knowledge of any other IPR related to this work. Thanks, Chris.
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
