Re: [v4tov6transition] [Softwires] ISP support of Native IPv6 across NAT44 CPEs -Proposed 6a44 Specification

Ole Troan <otroan@employees.org> Thu, 07 October 2010 19:27 UTC

Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v4tov6transition@core3.amsl.com
Delivered-To: v4tov6transition@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 552793A70DD; Thu, 7 Oct 2010 12:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=-0.126, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 FiJfL3bZ39tB; Thu, 7 Oct 2010 12:27:22 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 1FA733A70CD; Thu, 7 Oct 2010 12:27:21 -0700 (PDT)
Received: by ewy21 with SMTP id 21so177205ewy.31 for <multiple recipients>; Thu, 07 Oct 2010 12:28:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=nAEn+7kyV6CZqCNuE6yIqv7NgfJ1kWE8jUzOATt4t2Q=; b=u0LkWPtDwhcwZDXFaTcoc017MOVLaqb1Q4WFSoDAL6Fx/xn2n5B5W2Re7Hd6LMJ/Sh Ihvvm089hID6WxxUI5LT/U6MyQ9acv48lIgHgW6gqOXbzgY7KLWM6PBFMGa64Ck5tjvQ /wWd+81NWb4WW2pYnjB0rFzI+UW6u0hLx/PXc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=XzUliaAodyebn0EDk+wZxLaor9Vt7sREG9D56ayOeUGELIoBprZylJQHJxLPpblhQo WtKvIVyjy+TOQyC+dHD6q0CAhTslT0BKRNr5YkUfq7V8tTYTvxMVezfzpkwt7JuqmG+4 ReLhfOj2Qhyn/5oVFequMYJQAwz29JGkUXe8M=
Received: by 10.213.113.147 with SMTP id a19mr819419ebq.24.1286479703697; Thu, 07 Oct 2010 12:28:23 -0700 (PDT)
Received: from ams3-vpn-dhcp4939.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id z55sm3983116eeh.9.2010.10.07.12.28.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 07 Oct 2010 12:28:22 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <0BEE26F5-AB86-407C-98B2-FACADF2BBC95@free.fr>
Date: Thu, 7 Oct 2010 21:28:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <90B266CA-8D13-4F4C-8FED-273F07A3F7CE@employees.org>
References: <C8D29306.3EDBD%yiu_lee@cable.comcast.com> <FC864BDE-D5C7-4EEF-AE66-18AF523CDB67@free.fr> <8F8FE644-4E46-4579-8D77-9C5613F6419E@employees.org> <0BEE26F5-AB86-407C-98B2-FACADF2BBC95@free.fr>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-Mailer: Apple Mail (2.1081)
Cc: Softwires <softwires@ietf.org>, v4tov6transition@ietf.org
Subject: Re: [v4tov6transition] [Softwires] ISP support of Native IPv6 across NAT44 CPEs -Proposed 6a44 Specification
X-BeenThere: v4tov6transition@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <v4tov6transition.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v4tov6transition>
List-Post: <mailto:v4tov6transition@ietf.org>
List-Help: <mailto:v4tov6transition-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 19:27:23 -0000

Remi,

[...]

> ISPs that aren't concerned with what their customer would like to have will eventually face competition.

we are in complete agreement of the end goal. it is just how we get there...

> A key point is that supporting 6a44 is very inexpensive compared to other supports they have to envisage.
> 
> Yet, as Yiu says, this still depends on which hosts will support 6a44.
> My personal hope is that we will soon see trials, including with mobile phones.  

issues I have with host tunneling:
 - how to communicate with native IPv6 nodes on the same network?
 - how to communicate to another 6a44 host on a different link in the same home?
 - do you need non-congruent topology multi-homing policy?
   http://tools.ietf.org/html/draft-troan-multihoming-without-nat66-01
   how do you distribute that policy when you don't have a on-link router?
 - a general unease that now every host is supposed to have a "VPN" connection?
   how do I configure my own firewall and other network border policy?

how much would a new CPE cost the customer? 80USD? that's only 5 pints of beer (if bought in Norway.)
I really liked the dongle idea by the way. perhaps with a L2TP LAC.

cheers,
Ole