Re: <draft-ops-taddress-mib-01.txt>

[Alan Luchuk <luchuk@snmp.com>]

Hello,

Regarding <draft-ops-taddress-mib-01.txt>:

Overall it looks reasonable to me.  I noticed only a few, mostly insign-
ificant, typographical errors, and one typographical error that I thought
might affect the technical content of the draft.  Also, I appreciate the
"Section 5, Examples" section of the document that adds clarity.


-  In the Abstract:

   I believe "commonly used" should include a hyphen, that is, 
   "commonly-used".  I believe this is a multi-word adjective 
   like "well-known".

-  In Section 1, Introduction:

   The text reads:  "Typical examples are MIBs for application protocols
   that can run over several different transports".  I suggest changing
   "run over" to "operate over" or "communicate over".  When I first saw
   the text "run over", I thought of "run over" as in "The car ran over
   the dog".

-  In Section 3, Overview, first paragraph:

   I believe "transport layer" should include a hyphen, that is, 
   "transport-layer".  I believe this is a multi-word adjective 
   like "well-known".

-  In the MIB itself, MIB object "transportDomainLocal", I believe that
   "well known" should have a hyphen; that is "well-known".

-  In the MIB itself, MIB object "transportAddress".  The second sentence
   of the first paragraph reads:

   The TransportAddressType or TransportDomain object which defines the
   format of the TransportAddress value MUST be registered before the 
   object(s) which use the TransportAddress textual convention.

   My question:  Where should these be registered?

-  In the MIB itself, MIB object "TransportAddressIPv4".  I believe the
   first sentence of the DESCRIPTION should include text about the global
   nature of the address.  That is, change:

   "Represents a TCP-over-IPv4 or a UDP-over-IPv4 transport address:"

   to:

   "Represents a TCP-over-IPv4 or a UDP-over-IPv4 transport address
   for global IPv4 addresses:"


****IMPORTANT****

-  In the MIB itself, MIB object "TransportAddressIPv4z".  I believe the
   text reads "for scoped IPv6 addresses:" should read "for scoped IPv4
   addresses".   Note the change from IPv6 to IPv4.  

   I believe this is the only typo that might affect the technical content
   of the draft.


I am not qualified to comment in any way about the non-IP transport domains.

I hope these comments are useful and timely.

Regards,
--Alan 

 ------------------------------------------------------------------------------
 Alan Luchuk               SNMP Research, Inc.          Voice:  +1 865 573 1434
 Senior Software Engineer  3001 Kimberlin Heights Road  FAX:    +1 865 573 9197
 luchuk@snmp.com           Knoxville, TN  37920-9716    http://www.snmp.com/
 ------------------------------------------------------------------------------