IETF Logo Mail Archive

Re: RFC3484-revise and NAT64 Well-Known Prefix

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 28 March 2011 07:52 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F16783A68EB; Mon, 28 Mar 2011 00:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gFCd46-MXQIo; Mon, 28 Mar 2011 00:52:00 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id F1FBF3A68EE; Mon, 28 Mar 2011 00:51:59 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1248319yxk.31 for <multiple recipients>; Mon, 28 Mar 2011 00:53:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UEPuUjYgd1+SCkGJ6XcHyOZRAwpBsukauLzK65mbflM=; b=lsVedPprAEsTEzAml1v/nZhw2Ze/s3zAMSHParILLwOPZdQtLLxS90hcx63DF76dA9 HaX08NRQkOT3t2vGJ1oNKlv76mRCia37Mu42fuqG9nmNBHP6cJQrhcn8HxH2zJtloWdO XTMFTAZIZC3JyFsg3jwyo2GeSxQwopEJpph1E=
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=q2dEXeRfqV8lHv/4mskDLoKqlL6BjNEpiVFNErEw2ED9ZbKPd6bf98OrxhsMtXF/3k sgqCKyWx20C2oE1xhJfVUVoKZ3RfWTAx/eiX6uudYEayUPQp1Diqwk2GLmRPhyX/RLlW ZwoDy+asOqJEAVceaIYIpDcm89l3GS51YVzN4=
Received: by 10.236.197.7 with SMTP id s7mr1099535yhn.188.1301298817069; Mon, 28 Mar 2011 00:53:37 -0700 (PDT)
Received: from [130.129.22.150] (dhcp-1696.meeting.ietf.org [130.129.22.150]) by mx.google.com with ESMTPS id x76sm1823631yhn.94.2011.03.28.00.53.00 (version=SSLv3 cipher=OTHER); Mon, 28 Mar 2011 00:53:06 -0700 (PDT)
Message-ID: <4D903E55.1010807@gmail.com>
Date: Mon, 28 Mar 2011 20:52:53 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: teemu.savolainen@nokia.com
Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
References: <916CE6CF87173740BC8A2CE443096962014C5D@008-AM1MPN1-036.mgdnok.nokia.com> <alpine.LRH.2.00.1103272227310.13893@sampo3.csc.fi> <4D9022B6.8020105@gmail.com> <916CE6CF87173740BC8A2CE443096962015109@008-AM1MPN1-036.mgdnok.nokia.com>
In-Reply-To: <916CE6CF87173740BC8A2CE443096962015109@008-AM1MPN1-036.mgdnok.nokia.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, tekivini@csc.fi, behave@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Mar 2011 07:52:01 -0000

Yes. The MIF model seems to me to be fairly broken
from an architectural point of view. Maybe you have to
forbid exporting certain information from one stack to another
on a MIF host.

   Brian

On 2011-03-28 20:19, teemu.savolainen@nokia.com wrote:
> Multi-interfaced host might have one network interface IPv6-only with NAT64 (e.g. cellular) and another network interface IPv4-only (e.g. WLAN).
> 
> Teemu
> 
>> -----Original Message-----
>> From: ext Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>> Sent: 28. maaliskuuta 2011 07:55
>> To: Teemu Kiviniemi
>> Cc: Savolainen Teemu (Nokia-MS/Tampere); behave@ietf.org; ipv6@ietf.org
>> Subject: Re: RFC3484-revise and NAT64 Well-Known Prefix
>>
>> On 2011-03-28 08:53, Teemu Kiviniemi wrote:
>>> On Sun, 27 Mar 2011, teemu.savolainen@nokia.com wrote:
>> ...
>>> I believe native IPv4 should always be preferred over NAT64.
>> That is just irrelevant and of no importance, since the only hosts
>> that use DNS64 and NAT64 in normal life are IPv6-only hosts.
>>
>> There is a side issue of what happens if a synthetic IPv6 address
>> is referred to a non-IPv6-only host, but that is a whole other
>> problem that cannot be solved at the RFC3484bis level.
>>
>> See draft-carpenter-referral-ps-02.txt...
>>
>>     Brian

v2.23.0 | Report a Bug | By Email