[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RRG] Six/One Router Design Clarifications
- To: Christian Vogt <christian.vogt@nomadiclab.com>
- Subject: Re: [RRG] Six/One Router Design Clarifications
- From: Brian E Carpenter <brian.e.carpenter@gmail.com>
- Date: Wed, 16 Jul 2008 09:06:59 +1200
- Cc: Routing Research Group Mailing List <rrg@psg.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=SVCf1vJXdRdl8sJFIg+gtAVT3q8Ured/UvDASe8SEPrxQ0wN25e4AGGM3/z3hblx5R vJfpry0oQaZ/i6n3+KTaZWQ93cUvoxv5aHpI+Rclro9dup4kmccc9Y5lpLa34JKI76zI x59fTh7M7he5iuPWK18AZD2tFTguzf/Stfmdc=
- In-reply-to: <3E69201D-DA45-42ED-9031-D852ACD35E81@nomadiclab.com>
- Organization: University of Auckland
- References: <3E69201D-DA45-42ED-9031-D852ACD35E81@nomadiclab.com>
- User-agent: Thunderbird 2.0.0.6 (Windows/20070728)
Chrsitian
On 2008-07-13 01:42, Christian Vogt wrote:
...
> For communications between upgraded and legacy edge networks, address
> rewriting happens unilaterally on the border of the upgraded edge
> network. To avoid address inconsistencies between IP header and
> payload also in this case, Six/One Router relies on application
> functionality for network address translator traversal. Applications
> that may be affected by such address inconsistencies depend on this
> functionality already today, due to the existing deployment of network
> address translators. It is hence safe to assume that those
> applications, which use addresses in packet payloads, also support
> network address translator traversal.
I don't find this OK in an IPv6 environment. We've worked very hard for
years to make sure that IPv6 deployment doesn't require NAT, and it
is not a correct assumption that applications can support NAT kludges
for IPv6 just because they must do so for IPv4 (including IPv6-IPv4
packet level translation).
Brian
--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg