Hello,
I have been selected as the Routing Directorate QA reviewer for draft-ietf-ospf-routable-ip-address-00. The Routing Directorate QA reviews are intended to be a support to improve the quality of RTG Area documents as they pass through the IETF process. This is the QA review just after WG adoption. Summary This draft defines a useful extension to OSPF to allow routers in other areas to be able to associate reachable addresses with a router which supports a particular capability. I do not foresee any major hurdles in this document progressing to become an RFC. Comments It would be beneficial to explain why the routable address information only needs to be flooded with domain-scope (i.e. explain how routers in the area already have this information). I suspect the security folks will likely point to the dangers of advertising local node addresses domain wide - which may make it easier for a node in one area to be targeted from another area. The security section should anticipate this by referencing the various OSPF authentication RFCs as the means to protect this information. Major Issues No major issues found. Minor Issues The IANA Comsiderations section should refer to the OSPF Router Information (RI) TLVs Registry defined by [RFC4970]. Nits Abstract: Last sentence s/the OSPF/the term OSPF Introduction: First paragraph " propagated to another area, those routers in the latter area need..." The sentence should end after "area" and a new sentence begin with "Those". Introduction: Last sentence s/the OSPF/the term OSPF Section 3: penultimate sentence The phrase "within the body of the corresponding RI Opaque LSA" can be removed. It repeats the first sentence of the paragraph and does not match the equivalent text in Section 4.
_______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
