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

[Mike Daniele <daniele@zk3.dec.com>]

hi,

> 
> [ ... yet another late response ... ]
> 
> 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.

hi,

i can see the worth of defining "targets" with DNS names.

but it's not really a "transport-layer address", and there are certainly
implementation issues involved in supporting them.

(the SNMP TARGET MIB designers may have specifically used TDomain/TAddress
types because none of the then-existing ones required runtime resolution...)

so i tentatively agree with adding this. 

   TransportAddressDns ::= TEXTUAL-CONVENTION
       DISPLAY-HINT "1a"
       STATUS      current
       DESCRIPTION
           "Represents a dotted DNS domain name followed by a colon
            ':' (ASCII character 0x3A) and a port number in ASCII.
            The name SHOULD be fully qualified whenever possible.

>> i think we should remove "dotted".

>> i'd like to add something like
+++
	    Values of this TC are not directly useable as transport-layer 
            addressing information, and require runtime resolution.
	    As such, command-generator applications that use them in SetRequest 
	    operations must be prepared for command-responders to reject them.
---

            The DESCRIPTION clause of TransportAddress objects that may
            have TransportAddressDns values must fully describe how (and
            when) such names are to be resolved to IP addresses and vice
            versa.

            This textual convention SHOULD NOT be used directly in object
            definitions since it restricts addresses to a specific format.
            However, if it is used, it MAY be used either on its own or
            in conjunction with TransportAddressType or TransportDomain
            as a pair.

            When this textual convention is used as a syntax of an
            index object, there may be issues with the limit of 128
            sub-identifiers specified in SMIv2, STD 58. In this case,
            the OBJECT-TYPE declaration MUST include a 'SIZE' clause
            to limit the number of potential instance sub-identifiers."
       REFERENCE
           "Protocol Independent Interfaces (IEEE POSIX 1003.1g)"

>> cut/paste oops?  we have no REF clause for InetAddressDNS in RFC 3291.

       SYNTAX      OCTET STRING (SIZE (1..255))

   END

also, please change my email contact to md@world.std.com.

thx,
mike