[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
effect of v4 runout [Re: v6ops-nat64-pb-statement-req: DNSSEC requirement]
On Sun, 27 Jul 2008, Iljitsch van Beijnum wrote:
If you want to use DNSSEC and NAT64 together, either DNSSEC or DNS64 must be
changed to be aware of the other.
(This is a side note wrt the subject change..) Well, you could make
the v6-hosts query A records, and synthethize themselves based on
NAT64 prefix information they have. Not sure if you count this in
either of your categories above.
Yes, this is inconvenient but then again,
not being able to connect to the 99% of the internet that's still on IPv4
when your ISP can't give you an IPv4 address anymore is also quite
inconvenient.
This is a belief that needs debunking. Many drafts, this included,
make the assumption that there is major incentive to deploy v6 before
IANA's v4 space runs out. Some longer sighted ISPs may see it so
especially if the IETF and vendors can provide tools to assist them;
others won't. The ISP will just provide the users private address
space and do NAT. This has been commonplace in many 2G/3G
deployments, and it will become the norm in residential connectivity
as well. So the scenario we must compare NAT64 etc. against is
ISP-provided v4 private space, not no v4 at all.
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings