[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I-D Action:draft-daley-ipv6-nonat6-00.txt
- To: email@example.com
- Subject: Re: I-D Action:draft-daley-ipv6-nonat6-00.txt
- From: Brian E Carpenter <firstname.lastname@example.org>
- Date: Sun, 12 Jul 2009 16:55:37 +0100
- Cc: IPv6 Operations <email@example.com>
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=aE5pFsqHPPd7GbeG+8d1kMTcclLZ4AcpJS8HEyolDaAXThkM5XKKD+eLj8CPIqU12F 9p8rmCZCuDDthdM7ZrpmEssM0Ax5NLNj58p0tENgCMyJ0ZLdYfTpRP0G3sq21BF2b5wz 8Td7r9GUZs5c23jWLxZs3NGSrxpg0YHHi3t3Y=
- In-reply-to: <20090706234501.47BC13A6D43@core3.amsl.com>
- Organization: University of Auckland
- References: <20090706234501.47BC13A6D43@core3.amsl.com>
- User-agent: Thunderbird 184.108.40.206 (Windows/20070728)
I'm not sure I understand your citation of RFC4864 in this draft:
> Until now, NATs have only existed for IPv4, and for transitioning
> from an IPv6 network to an IPv4 network [RFC2766][RFC4864].
The whole point of 4864 was to identify the claimed benefits of NAT
and discuss how IPv6 can provide them without NAT. It's certainly
relevant to your draft, but I think it would be useful to be explicit
about which parts of the gap analysis in 4864 you are addressing,
and about whether 4864 missed part of the gap. It doesn't use the
phrase "address independence" but does cover
Privacy and Topology Hiding,
Independent Control of Addressing in a Private Network
Global Address Pool Conservation
Multihoming and Renumbering with NAT
Note, I'm not particularly disagreeing with your draft, I just think
it could be better explained how it fits with the RFC4864 gap analysis.
We also suggested some possible directions for topology hiding
in 4864, including using Mobile IP tunnels on larger sites.
I'm not sure we need any new mechanisms.