IETF Logo Mail Archive

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

Ed Jankiewicz <edward.jankiewicz@sri.com> Fri, 08 October 2010 02:06 UTC

Return-Path: <edward.jankiewicz@sri.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 0EFF43A677D for <v4tov6transition@core3.amsl.com>; Thu, 7 Oct 2010 19:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.264
X-Spam-Level:
X-Spam-Status: No, score=-1.264 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6]
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 H8wxW-HSiMt6 for <v4tov6transition@core3.amsl.com>; Thu, 7 Oct 2010 19:06:10 -0700 (PDT)
Received: from mail1.sri.com (mail.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id A9D2C3A6781 for <v4tov6transition@ietf.org>; Thu, 7 Oct 2010 19:06:10 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"; format="flowed"
Received: from [192.168.1.144] ([unknown] [68.81.23.3]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L9Y009JU8K19Y70@mail.sri.com> for v4tov6transition@ietf.org; Thu, 07 Oct 2010 19:07:14 -0700 (PDT)
Message-id: <4CAE7CCF.9030205@sri.com>
Date: Thu, 07 Oct 2010 22:07:11 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
To: v4tov6transition@ietf.org
References: <C8D3492F.3EDF1%yiu_lee@cable.comcast.com> <4CAE60A8.4020206@gmail.com> <AANLkTiku-ubRWv5fs_R-q5W8isjuVpp0MX-jHWbGyhnv@mail.gmail.com>
In-reply-to: <AANLkTiku-ubRWv5fs_R-q5W8isjuVpp0MX-jHWbGyhnv@mail.gmail.com>
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 02:06:12 -0000

  a colleague asked his broadband cable provider if he could get IPv6 on 
his Internet service.  The customer service rep didn't know but assured 
him he would look into it.  He got a quick reply via e-mail "thank you 
for your recent inquiry about IPV6.  We do our best to respond to 
customer requests for specific programming but technical limitations 
mean that we can't carry every piddling little international sports 
channel that..." Or something to that effect.

They will remain nameless, but I assure you this operator is 
well-represented in IETF.  I did stand up at a v6ops meeting to tell 
that story and say "to all of you who say we are ready to turn on IPv6 
as soon as our customers demand it - they may ask for it, but if your 
customer service folks and other staff don't know about IPv6 - you will 
never hear that the customers are asking."

On 10/7/2010 9:41 PM, Cameron Byrne wrote:
> 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
> _______________________________________________
> v4tov6transition mailing list
> v4tov6transition@ietf.org
> https://www.ietf.org/mailman/listinfo/v4tov6transition

v2.23.0 | Report a Bug | By Email