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

Cameron Byrne <cb.list6@gmail.com> Fri, 08 October 2010 01:40 UTC

Return-Path: <cb.list6@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 282113A67A5; Thu, 7 Oct 2010 18:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[AWL=0.493, 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 w1M5VRxXsVVr; Thu, 7 Oct 2010 18:40:06 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 354AD3A67A3; Thu, 7 Oct 2010 18:40:04 -0700 (PDT)
Received: by qyk2 with SMTP id 2so3505qyk.10 for <multiple recipients>; Thu, 07 Oct 2010 18:41:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=z8/emQack4DKzAFbGk9jslx3zPtX/U3mDUxSpZBUhIg=; b=d0Afu306zzH+70rG/PMqyMIg2pzdpTrRGoaO52JOcv5bPwiqSJN/Yx1KOE6FNZ1wpi CiBq0f7mzMEfgY0BaWS8NXPOsy963hruu8cAT46Iyn7owU+bA6kk46VGAe+KTUsNV7wf 91sQYCFA2Gbj/kr6kAaKlzCJGllCOygo5zvNo=
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; b=jn8d5FCurNYKVXu/+aC9gTml+u/CddQw1+h1IoNZ7Ka30viyVZ3G/YeWU+OOX+JsZf 5MxfsNSnatCWWG4t4x++KztcwxLDV+ulYSBIlodOLjI2e+y6QXIgqem5Z1nNRhpkLfPn 4etNFyRn6e8mEowgLo0v5i/abn0hvD84AZ6ic=
MIME-Version: 1.0
Received: by 10.229.1.143 with SMTP id 15mr1377635qcf.287.1286502067340; Thu, 07 Oct 2010 18:41:07 -0700 (PDT)
Received: by 10.229.183.146 with HTTP; Thu, 7 Oct 2010 18:41:07 -0700 (PDT)
In-Reply-To: <4CAE60A8.4020206@gmail.com>
References: <C8D3492F.3EDF1%yiu_lee@cable.comcast.com> <4CAE60A8.4020206@gmail.com>
Date: Thu, 7 Oct 2010 18:41:07 -0700
Message-ID: <AANLkTiku-ubRWv5fs_R-q5W8isjuVpp0MX-jHWbGyhnv@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Softwires <softwires@ietf.org>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, 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: Fri, 08 Oct 2010 01:40:18 -0000

On Thu, Oct 7, 2010 at 5:07 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
>> I can't say how bad operators want to support IPv6 over legacy CPEs. If
>> there is demand. Can somebody (except me :-) ) speak it out?
>
> Well, when we surveyed 31 ISPs for draft-ietf-v6ops-isp-scenarios,
> we found "When asked which types of equipment are unable to support IPv6, the
> most common answer was CPE (10 mentions)." That doesn't directly answer
> your question, but it suggests the size of the problem.
>

Brian is right.  And when a customer asks for IPv6 features in end
nodes, through any number channels (public, private, RFP, ...), the
answers is frequently something like /dev/null .  For instance,
http://tinyurl.com/2f753c5 ...

So, if you work for a vendors that makes CPE / UE, please consider
turning IPv6 on in your product.

Cameron