Thank you for the comments Dan

On 9/11/12 5:59 AM, Romascanu, Dan (Dan) wrote:
Hi,

There are a few issues that need to be corrected and clarified before
submitting this document to the IESG. There may be more, but I did not
have the time to perform a full MIB Doctor review, this is what I found
at a first pass reading of the document.

- Runing smilint indicates a number of problems - most derive from the
fact that indices of many table are of the SYNTAX of Integer32 with no
range restriction

thanks - fixed. (added ranges)

- LispAddressType TC is defined as a four-tuple with several variants -
how can it have 0 as its lower size?

thanks - fixed.

- Having a REFERENCE clause that says "[LISP]" is not useful. People may
use the MIB module but not the RFC, and even if they know what the
reference is just one high level reference is useless. To be useful to
implementers REFERENCE clauses of specific objects must point to the
exact paragraphs that define the origin of the MIB definition in the
LIPS RFC

thanks - fixed. added pertinent references w/ sections.

- Some of the Integer objects have obviously a range, but this is not
specified - for example lispMapCacheLocatorRlocPriority or
lispMapCacheLocatorRlocWeight

thanks - fixed. added ranges.

- The indexation of lispIidToVrfTable seems broken - if the value of
VPNIdOrZero is zero because a VPN ID could not be determined, how are to
rows in such situation distinguished?

thanks - fixed. added index.

- There is no discontinuity indicator for the (many) counter objects in
the MIB module. See section 4.6.1.2 in RFC 4181 for some advice on this
issue

thanks - fixing...

- IANA Considerations - IANA must allocate a branch under mib-2 for this
MIB module (marked xxx in the MIB module)

thanks - yes, we had this on the "to do" list. will get this going.


Regards,

Dan

cheers
gregg

--
--------------------------------------------------------------------
 .:|:.:|:.  | gregg schudel (ccie#9591) LISP technical mrkting engr
   cisco    | mobile: +1 571 332 2222   email: [email protected]
--------------------------------------------------------------------
cisco corporate legal statement:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
--------------------------------------------------------------------
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp

Reply via email to