[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-ops-endpoint-mib-04.txt
- To: mibs@ops.ietf.org
- Subject: Re: draft-ops-endpoint-mib-04.txt
- From: Keith McCloghrie <kzm@cisco.com>
- Date: Tue, 11 Jan 2000 19:11:33 -0800 (PST)
- Delivery-date: Tue, 11 Jan 2000 22:17:53 -0800
- Envelope-to: mibs-data@psg.com
This MIB caused us some confusion this week. Somebody wanted a TC for
generic Internet-layer addresses. We naturally thought of this
end-point MIB. Unfortunately, they had the possibility of needing IPX
addresses which are not supported by draft-ops-endpoint-mib-03.txt.
The closest they could find for TCs in a standard MIB, which met their
needs, was the InternetworkAddr and InternetworkAddrType TCs defined in
ftp://ftp.atmforum.com/pub/approved-specs/af-mpoa-0092.000.pdf
The InternetworkAddrType TC defined there is more general-purpose in
that it's an enumerated value based on "Address Family Numbers" as
assigned by IANA (see http://www.iana.org/numbers.html#A). Was there
ever any thought of using this more general mechanism for the
draft-ops-endpoint-mib-xx MIB ?
[Note that even though DNS names do not currently have an Address
Family Number, I would presume that whoever made the case to include
them in this MIB could also make the case to persuade IANA to assign an
Address Family Number to DNS names.]
Keith.