[Isis-wg] Minor comments on draft-ietf-isis-wg-mib-13.txt

[Jonathan Harrison <[e-mail]>]

Hi,

We've got a number of minor suggested clarifications and typo fixes to the
MIB, itemized below.  Hopefully, these won't be too controversial!

Please let me know what you think.

Thanks,
Jon
-------------------------------------------
Jon Harrison
Network Protocols Group
Data Connection Ltd
Tel:	[phone]                 
Fax:	[phone]
Email:	[e-mail]    
Web:	http://www.dataconnection.com


SUGGESTED FIXES
===============

 - The MIB defines the type WideMetric for 24 bit values and the type
FullMetric for 32 bit values.  The syntax for FullMetric should be "SYNTAX
Unsigned32" rather than "SYNTAX Unsigned32 (0..16777215)".

 - The second sentence of the description of isisSysMaxAge should read "This
should be at least 300 seconds greater than isisSysMaxLSPGenInt."
 
 - isisSysInstance and isisSysLevelIndex are used in notifications, and so
the MIB compiler we use gives warnings because these objects have MAX-ACCESS
not-accessible.  Should these objects have MAX-ACCESS read-only (or
accessible-for-notify) instead?

 - Both isisCircPassiveCircuit and isisCircLevelCSNPInterval have an empty
REFERENCE "{}".  The reference for isisCircPassiveCircuit should be removed.
The reference for isisCircLevelCSNPInterval should be {ISIS.aoi
completeSNPInterval (8)}.

 - isisISAdjIndex - the description should read "This value is automatically
assigned by the system when the adjacency is created."

 - The references sometimes refer to level 1 objects, sometimes level 2
object (for example, l1DefaultMetric and l2DesignatedIntermediateSystem).
It would be more consistent to just refer to L1 objects, if possible.

 - The description for isisISAdjAreaAddrIndex should read "This provides a
simple way to walk the table."

 - The description of isisLSPSummaryEntry description has a typo - should be
"Each entry describes an LSP currently stored in the system."

 - In the LSP table description change "tupples" to "tuples".

 - To make the capitalization consistent, the description of isisLSPTLVType
should read "The type of this TLV".

 - The description of isisCircExtendedCircID could be clarified as follows
"The value to be used as the extended circuit ID in 3Way handshake.  This
value is only used if isisCirc3WayEnabled is true, and must be unique across
all circuits on this IS."

 - The description of the isisNotificationTable should read "Objects seen in
the most recent notification from this instance of the IS-IS protocol."

 - isisPduOriginatingBufferSize - The description should read "Holds the
size of isisSysOrigLSPBuffSize advertised by the peer in the
originatingLSPBufferSize TLV."

 - To make it (even more!) obvious that the minimum LSP generation interval
should be less than the maximum interval, modify the description of
isisSysMaxLSPGenInt as follows "The value must be greater than any value
configured for isisSysLevelMinLSPGenInt, and should be at least 300 seconds
less than isisSysMaxAge."  Similarly, add to the description of
isisSysLevelMinLSPGenInt "The value must be less than isisSysMaxLSPGenInt." 

 - isisSysTable description has a missing 's'.  Should be "The set of
instances of the Integrated IS-IS protocol existing on the system."

 - Add "This object follows the resettingTimer behavior." to the description
of the isisCircLevelCSNPInterval.

 - For consistency, isisISAdjIPAddressType and isisISAdjIPAddress should be
named isisISAdjIPAddrType and isisISAdjIPAddrAddress.

 - isisCircInitFails refers to "ISIS.aoi  initialisationFailures", which
counts specific adjacency initialization failures due to having no version
or area address in common.  The MIB should spell this out.  For example,
"The number of times initialization of an adjacency on this circuit has
failed due to the peer having either no version or no area address in common
with the local system."

 - Finally, isisCircLevelID.  I'd like to clarify whether this object is
only used for point to point circuits (as suggested by the reference to
ptPtCircuitID), or whether this field can be given a sensible value for a
LAN (since the CircuitID syntax doesn't give an option to return a zero
length OCTET STRING).

If the field does take a value on a LAN (with the disadvantage of making the
meaning of the field less clear), then the following text could be used.

"On a point to point circuit with a fully initialized adjacency to a peer
IS, the value of this object is the circuit ID negotiated during adjacency
initialization.  In all other cases, the value is the concatenation of the
local system ID and the one byte isisCircLevelIDOctet for this circuit.
This is the value that would be proposed for the circuit ID on a point to
point circuit, or for the LAN ID should this node be chosen as the LAN
Designated IS."

Or if the field is purely for use as the ptPtCircuitID, I suggest we change
the Circuit ID syntax to "OCTET STRING (SIZE(0|7))", and change the
description as follows:

"On a point to point circuit with a fully initialized adjacency to a peer
IS, the value of this object is the circuit ID negotiated during adjacency
initialization.  On a point to point circuit without such an adjacency, the
value is the concatenation of the local system ID and the one byte
isisCircLevelIDOctet for this circuit i.e. the value that would be proposed
for the circuit ID.

On other circuit types, the value returned is the zero length OCTET STRING."




_______________________________________________
Isis-wg mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/isis-wg