On Wed, 24 Mar 2004, David Meyer wrote: > > draft-ietf-dnsop-inaddr-required > > Any comments? Do we want to bring this back? > > Itojun Hagino - I think I have seen more operational troubles > with ipv6 case reverse lookup case. Lack of IPv6 reverse lookup > causes connection delays on stuff so I'd really like to see this > published.
"Connection delays" due to not having inaddr populated are an implementation problem, not a reason to require in-addr. It is the misunderstanding of whether in-addr is presently required that causes many implementation problems. Presently, In-addr is not required but some application implementers think it is, and these implementers think that having it somehow improves trust, though trust is not in fact improved. Asserting that implementation errors create a reason to alter the status of In-addr is the tail wagging the dog. Further, I've also discussed the issue with ARIN, and ARIN's management is is considering not offering In-addr in the future, and has gone so far as to consult with attorney's about whether it is required to do so. I was told the attorney's think they are not required to offer this service. My recollection is that the last time this was discussed, it was shown that in-addr offers no significant trust benefits, and that the improved trust claims were debunked, and that there are problems with In-addr in IPV6 that are addressed by a functional alternative in the form of Host Info. I thought this was long a dead issue. So, I have to wonder why it is such dead issues keep coming up. > Rob Austein: remember, this is the one where the title is > misleading - this is just considerations for whether to populate > reverse tree, etc. Last time it came up wg insisted it was > important, but didn't get traction on doing it. > > Will somebody write text? Author has been pelted with rotten tomatoes > so many times doesn't want to do it anymore. [This turned out to be > incorrect, author is still willing, see discussion on mailing list.] > > Itojun Hagino: I'll do it! . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
