To:
Daniel Senie <dts@senie.com>
cc:
dnsop@cafax.se
From:
Dean Anderson <dean@av8.com>
Date:
Thu, 3 Apr 2003 12:56:15 -0500 (EST)
In-Reply-To:
<5.2.0.9.2.20030402183738.01bbe988@mail.amaranth.net>
Sender:
owner-dnsop@cafax.se
Subject:
RE: I-D ACTION:draft-ietf-dnsop-inaddr-required-04.txt
On Wed, 2 Apr 2003, Daniel Senie wrote: > It is the purpose of this draft to define the reasons to promote the use of > INADDR, and to also discourage usage that can be harmful and which provides > false security (please note that most or all of the text regarding NOT > using INADDR came from contributions from the DNSOP WG at or shortly after > the Pittsburgh IETF, and were not in the original document). Then it should include a statement to the effect of: ------------ IN-ADDR should not be used for any logging, auditing, identification, authentication, or authorization purpose. Its sole purpose is for the convenience of such applications as traceroute. Application developers should be aware that IN-ADDR may not be available in IPV6, and IPV6 applications should be prepared to use ICMP node identification or other alternatives. ------------ #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.