[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-ops-endpoint-mib-04.txt
>>>>> Keith McCloghrie writes:
Keith> In generating this response, I went looking for the ION and
Keith> MPLS MIBs, and here's what I found: the work item you identify
Keith> in point d) below has already been undertaken by IANA. Here's
Keith> a quote from RFC 2677:
[...]
Yes, I am familiar with this text. I actually proposed to move this TC
out of the NHRP-MIB and to put it into an IANA controlled MIB module
when I played the MIB nanny for RFC 2677. ;-)
Keith> Note that the above quote has been copied verbatim into
Keith> draft-ietf-mpls-ldp-mib-03.txt (and a similar TC was defined in
Keith> draft-srinivasan-mpls-te-mib-01.txt).
Keith> Given the above, I now think that InetAddressType should be
Keith> deleted from this MIB, and the AddressFamilyNumbers TC from
Keith> IANA-ADDRESS-FAMILY-NUMBERS-MIB should be IMPORTed and used
Keith> instead, This will promote greater consistency across IETF
Keith> MIBs.
Some questions:
Where do you define the TCs for the various address families? Do they
go under IANA control as well? Or do they go into RFC(s)? If they go
into RFC(s) and need additions over time, do we put them in multiple
modules do avoid locks on the standards track? Or do we have no locks
since the MIB modules only import InetAddress and not the specific
TCs?
How do we solve the problem with non-global IPv6 addresses? Do we use
a 20 byte IPv6 address all the time (setting the scope identifier to
zero most of the time)? We currently have two IPv6 address formats to
work around this problem.
Is it likely that we can make IANA accept DNS names as an address
family? (Or do you not care since you dislike the concept of DNS names
anyway?)
How do other people on this list think about this issue?
/js
--
Juergen Schoenwaelder Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de> Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>