Skip to main content

Telechat Review of draft-ietf-netmod-rfc8022bis-08

Request Review of draft-ietf-netmod-rfc8022bis
Requested revision No specific revision (document currently at 11)
Type Telechat Review
Team Routing Area Directorate (rtgdir)
Deadline 2018-01-23
Requested 2018-01-05
Requested by Alvaro Retana
Authors Ladislav Lhotka , Acee Lindem , Yingzhen Qu
I-D last updated 2018-01-16
Completed reviews Yangdoctors Early review of -05 by Martin Björklund (diff)
Secdir Telechat review of -10 by Carl Wallace (diff)
Genart Telechat review of -06 by Francis Dupont (diff)
Opsdir Telechat review of -07 by Joe Clarke (diff)
Rtgdir Telechat review of -08 by He Jia (diff)
Assignment Reviewer He Jia
State Completed
Request Telechat review on draft-ietf-netmod-rfc8022bis by Routing Area Directorate Assigned
Reviewed revision 08 (document currently at 11)
Result Has nits
Completed 2018-01-16

I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see

Although these comments are primarily for the use of the Routing ADs, it would
be helpful if you could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft.

Document draft-ietf-netmod-rfc8022bis-08.txt
Reviewer: Jia He
Review Date: 17 January 2018
IETF LC End Date: 15 January 2018
Telechat date: 25 January 2018
Intended Status: Standards Track

This document provides an NMDA-compliant version of YANG data model for routing
management. It is very well written and ready for publication. But I happened
to see a small nit in Appendix D just before I finished my review, see below.


Major Issues:
No major issues found.

Minor Issues:
No minor issues found.

In Appendix D, the namespace of "ietf-ipv6-unicast-routing" is written as
"urn:ietf:params:xml:ns:yang:ietf-ipv6-unicast-routing-3". "-3" is not
meaningful and needs to be deleted.