To:
dnsop@cafax.se
From:
Pekka Savola <pekkas@netcore.fi>
Date:
Sun, 17 Nov 2002 23:41:13 +0200 (EET)
Sender:
owner-dnsop@cafax.se
Subject:
comments on dnsop-ipv6-dns-issues-00
Hello,
As an overview, I'm very happy about the direction of this draft --
especially the recommended action in IPv4/IPv6 name space issues.
Comments.
- every single DNS zone SHOULD be served by at least an IPv4
reachable DNS server.
==> s/an/one/
8. DNSsec
There is nothing specific to IPv6 or IPv4 in DNSsec.
==> perhaps it would be appropriate that there are IPv6 specifications,
and more possibly on the way, which break DNSsec.
9. Security considerations
Using wildcard DNS records in the reverse path tree may have some
implication when used in conjunction with DNSsec.
==> add something to the effect of "Security considerations for referenced
documents are described in those memos and are not replicated here."
[RFC2766] Network Address Translation - Protocol Translation (NAT-
PT). G. Tsirtsis, P. Srisuresh. February 2000.
[NAT-PTissues] Issues with NAT-PT DNS ALG in RFC2766, A. Durand,
draft-durand-natpt-dns-alg-issues-00.txt, work in progress.
[NAT64] NAT64 - NAT46, A. Durand, draft-durand-ngtrans-
nat64-nat46-00.txt, work in progress.
==> these, at least, weren't referenced in the main body (intended to be
part of DNSsec?).
[IPv6ADDRARCH] IP Version 6 Addressing Architecture, R. Hinden,
draft-ipngwg-addr-arch-v3-09.txt, work in progress.
==> 11.
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.