Re: [Softwires] Host based translation: v4-v6

Zhen Cao <caozhenpku@gmail.com> Thu, 03 December 2009 14:37 UTC

Return-Path: <caozhenpku@gmail.com>
X-Original-To: softwires@core3.amsl.com
Delivered-To: softwires@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C4603A688D for <softwires@core3.amsl.com>; Thu, 3 Dec 2009 06:37:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.616
X-Spam-Level:
X-Spam-Status: No, score=-2.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599]
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 Jf+jMrltLHHS for <softwires@core3.amsl.com>; Thu, 3 Dec 2009 06:37:20 -0800 (PST)
Received: from mail-pz0-f187.google.com (mail-pz0-f187.google.com [209.85.222.187]) by core3.amsl.com (Postfix) with ESMTP id 328A73A687F for <softwires@ietf.org>; Thu, 3 Dec 2009 06:37:20 -0800 (PST)
Received: by pzk17 with SMTP id 17so1350552pzk.6 for <softwires@ietf.org>; Thu, 03 Dec 2009 06:37:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WQG3HPblO+RrgvtpB4d+5bsNxpY5H+I1ynd/Yu3+iVU=; b=OcINWfFsuN3wrepoDlKKR9+C96AJc+cGBGTj3r/UwG4WnuKdFzOCOSvSzK/aOYQd7q 3XDnMpPeVILpX0pyEOAZC93kw86peW4/JIVMPM9UNII5jvgDrfrpPzLkEfF5gK+saXuC e+Td3vIfIw2c0TGa5iJT8jOFvAH7i7NXkkzxo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UaD+0Kz7kITWQ83jy5LqJRxIqbbnPaT5CyQKRB+jtnzIoQ+UfmexIfeVHIqL2Bhe08 7b9noC+Jc7/NmacelRYpWU3wv7zSuQWJAmReJTC3UGHVGEj+ArvbP4t5OLb0q7QdtTKQ sgoFPm3w8riEFmKIcIMzcafrLiI9dQ5JFsFkg=
MIME-Version: 1.0
Received: by 10.142.5.27 with SMTP id 27mr213325wfe.59.1259851029650; Thu, 03 Dec 2009 06:37:09 -0800 (PST)
In-Reply-To: <4B17CA51.3020403@viagenie.ca>
References: <C73A80AA.3978%sgundave@cisco.com> <4B154549.4060101@viagenie.ca> <a7c8d0a30912030610pfd42f2dwd289a496912404a5@mail.gmail.com> <4B17CA51.3020403@viagenie.ca>
Date: Thu, 03 Dec 2009 22:37:09 +0800
Message-ID: <a7c8d0a30912030637q596a111bvd8d7fc4eab78fd98@mail.gmail.com>
From: Zhen Cao <caozhenpku@gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: softwires <softwires@ietf.org>
Subject: Re: [Softwires] Host based translation: v4-v6
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2009 14:37:21 -0000

On Thu, Dec 3, 2009 at 10:25 PM, Simon Perreault
<simon.perreault@viagenie.ca> wrote:
> Zhen Cao wrote, on 2009-12-03 09:10:
>>> New "IPv6 apps" are usually not IPv6-only. They are version-independent. See
>>> e.g. RFC4038. So your future app will try IPv4 if it cannot get IPv6
>>> connectivity. Which, it seems to me, would make case 4 fold into case 2.
>>
>> Hi Simon, I checked 4038 and found it is informational. And I do not
>> think applications developers will indeed follow this.
>
> The fact that it is information is irrelevant. This is how applications are
> being developed *right now*. We have experience with this, having ported many
> applications to IPv6. This method is taught in seminars, books, etc. There is no
> speculation here.

Good. You are saying that this happens for ported applications, but
that's only part of the story. We will have many new IPv6 applications
in the future.

>
>> For example,
>> RFC4294 defines IPsec as a MUST for IPv6 node, but from our equipment
>> test, we found this is a myth.
>
> How is IPsec relevant to an application?

I referred to this to prove that applications developers do not go
ahead as documented.

>
> As far as I know, the IPsec API is still in early stages:
> http://tools.ietf.org/html/draft-ietf-btns-c-api-04
> http://tools.ietf.org/html/draft-mglt-btns-ipsec-api-requirements-00
>
> Simon
> --
> DNS64 open-source   --> http://ecdysis.viagenie.ca
> STUN/TURN server    --> http://numb.viagenie.ca
> vCard 4.0           --> http://www.vcarddav.org
>