Note: This ballot was opened for revision 24 and is now closed.
Per the Gen-ART review, I think 2.3 may be a little clearer if it were to say "The field 'version' is used to indicate the OSPF LSA version and is mandatory." I did not review this entire document but I'm balloting based on the Gen-ART review.
Thank you for addressing my DISCUSSes and COMMENTs.
Thank you for addressing my Discuss and Comment points!
* Section 2.7 Why are the neighbor configuration and operational state under different subtrees here? I thought one of the goals of NMDA was to avoid this. * Section 2.9 Is there a reason why the clear operation for neighbors is defined using an RPC operation instead of simply an action under the relevant interface? * Meta comment NMDA is misspelt as NDMA in several places throughout the document including the abstract and the introduction. Suggest a global search and replace. Editorial ======== * Under ospfv2-lsa-option s/Baes idenity/Base identity/
Just two quick questions about references: - Is there no reference for mtu-ignore (see section 2.4)? If not, can you further describe what exactly would be disabled? - Also is there no reference for OSPF Non-Stop Routing (NSR) (see section 2.4)...? And one more comment: In the interface-common-config part (p76 and p77) you provide example or default values for various intervals and delays. Where does those values come from? Would it be possible to provide a reference/RFC that specifies actual default values? Especially when you specify something normatively ("The value MUST be greater than 'hello-interval'.") it would be good to provide a reference! Do any specification maybe also specify min and max value? If so, you should mention them here as well! If not would it make sense to recommend min and max values? If possible I would strongly support to describe min and max values as well!
I support Roman's and Ben's DISCUSSes.