Skip to main content

Last Call Review of draft-ietf-lisp-mib-08
review-ietf-lisp-mib-08-genart-lc-garcia-2013-01-17-00

Request Review of draft-ietf-lisp-mib
Requested revision No specific revision (document currently at 13)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2013-01-21
Requested 2013-01-10
Authors Gregg Schudel , Amit Jain , Victor Moreno
I-D last updated 2013-01-17
Completed reviews Genart Last Call review of -08 by Miguel Angel García (diff)
Genart Telechat review of -11 by Suresh Krishnan (diff)
Secdir Last Call review of -08 by Warren "Ace" Kumari (diff)
Assignment Reviewer Miguel Angel García
State Completed
Request Last Call review on draft-ietf-lisp-mib by General Area Review Team (Gen-ART) Assigned
Reviewed revision 08 (document currently at 13)
Result Ready
Completed 2013-01-17
review-ietf-lisp-mib-08-genart-lc-garcia-2013-01-17-00
Resending, now expanding some addresses that were giving trouble.

On 15/01/2013 15:44, Miguel A. Garcia wrote:



I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft. For background on Gen-ART, please see the FAQ at
<

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other comments you may receive.

Document: draft-ietf-lisp-mib-08
Reviewer: Miguel Garcia <Miguel.A.Garcia at ericsson.com>
Review Date: 2013-01-15
IETF LC End Date: 2013-01-21
IESG Telechat date:

Summary: The document is ready for publication as an experimental RFC.

Major issues: none

Minor issues: none

Nits/editorial comments:

- I have not reviewed Section 7, because I won't be able to make
technical comments, and it is quite extensive.

- The IANA considerations section could be slightly clear. It should
contain the request to IANA to allocate a value to the lispMib object
identifier, rather than be hidden in an Editor's note that is to be
removed prior to publication. Additionally, it is not clear which
subregistry IANA has to use to allocate a value. The draft refers to the
"mib-2", but I guess the formal name of the subregistry is "SMI Network
Management MGMT Codes". This subregistry should be explicitly named.
Furthermore, the registration is missing how IANA should populate the
"Name" and "Description" of the entry that IANA should give to this MIB.

/Miguel




--
Miguel A. Garcia
+34-91-339-3608
Ericsson Spain