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

[Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>]

[ ... yet another late response ... ]

>>>>> Glenn Mansfield Keeni writes:

[...]

Glenn> There are several points here - 1. Users and/or applications
Glenn> may not have a concrete address. They may have a DNS name-
Glenn> which may translate into one or more IPv4 or IPv6
Glenn> addresses. [InetAddressType = 16] In this case using "unknown"
Glenn> is not an accurate rendering of facts. - it is known that the
Glenn> address belongs to the {Udp|Tcp}Ip space, and that its value
Glenn> may be found from the DNS and that if found the address will
Glenn> belong to either the IPv4 or the IPv6 address space.

[...]

Glenn> Using the SNMP-TARGET-MIB as an example, I would prefer to
Glenn> assign a set of security parameters to host A.somedomain.com
Glenn> and specify that the address belongs to the TCP over IP domain
Glenn> of addresses (V4 and V6).

To address your requirements, I have added support for DNS names,
similar to what is in RFC 3291. For configuration purposes, it indeed
makes sense to be able to configure a target as noc.exmaple.net:162.
Of course, this requires to define when and how the resolution of the
name to an address takes place.

/js

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