[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Psudo WG Last Call for: http://www.ietf.org/internet-drafts/draft-ietf-ops-taddress-mib-02.txt




>>>>> Glenn Mansfield Keeni writes:

Glenn> Hi, The following are the comments on the taddress-mib-02
Glenn> draft.  some are cosmetic others require discussion:

Glenn> Page-4 Sec-3 para 1. s/following definitions/follwing/

I do not see how that improves much.

Glenn> Page-5 3.1.1 TransportAddressType appears for the first time
Glenn> Would it be better to move this section towards the end of the
Glenn> document or someplace after TransportAddressType is defined.

The concept of a transport address type is defined in section 3
enumeration 3 well before 3.1.1.

Glenn> Page-7 definition of transportDomainUdpIpv4z you have used the
Glenn> term "non-global" which is correct. But "private" may be better
Glenn> those are the terms that appear in RFC1597 (?)

non-global != private. See the following reference for details:

   [21]  Deering, S., Haberman, B., Jinmei, T., Nordmark, E., Onoe, A.
         and B. Zill, "IPv6 Scoped Address Architecture", draft-ietf-
         ipngwg-scoping-arch-03.txt, November 2001.

Glenn> Technical issues:

Glenn> There are provisions transportDomainUdpIpv4 (global +
Glenn> non-global) and transportDomainUdpIv4z (non-global) and
Glenn> similarly for TCP and v6. But, what about the global domain -
Glenn> for which the corresponding addresses *are* from the global
Glenn> pool ? I would think it is necessary.

I do not understand this comment. A global UDP address will use
transportDomainUdpIpv4.

Glenn> More important - this affects us and implementations on all
Glenn> dual (v4/v6) stack systems rightaway-

Glenn>      There is the need for the following transport domains:
Glenn> transportDomainUdpIpv4OrIpv6 and transportDomainTcpIpv4OrIpv6
Glenn> which will be used when the underlying IP transport (version)
Glenn> is either unknown or unspecified. (as far as the command
Glenn> generators are concerned, in the SNMP context).

Why? If you have a concrete address, then you know the concrete
domain. If you do not know a concrete value, you just use unknown(0)
or zeroDotZero in case you use OIDs. Perhaps I am missing the point.
Can you provide a concrete example?

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>