Re: [v6ops] draft-ietf-v6ops-6to4-to-historic WGLC

Michael Newbery <newbery@gmail.com> Tue, 19 April 2011 23:51 UTC

Return-Path: <newbery@gmail.com>
X-Original-To: v6ops@ietfc.amsl.com
Delivered-To: v6ops@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 9A613E075C for <v6ops@ietfc.amsl.com>; Tue, 19 Apr 2011 16:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[AWL=1.378, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eS4Ai3J6yvtW for <v6ops@ietfc.amsl.com>; Tue, 19 Apr 2011 16:51:06 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfc.amsl.com (Postfix) with ESMTP id 9117EE0715 for <v6ops@ietf.org>; Tue, 19 Apr 2011 16:51:06 -0700 (PDT)
Received: by pzk30 with SMTP id 30so139228pzk.31 for <v6ops@ietf.org>; Tue, 19 Apr 2011 16:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:mime-version:content-type:subject:date :in-reply-to:to:references:message-id:x-mailer; bh=JLV35223JDGy2joS7qK+8OMvFWwa27ypOrlMEaoOhL0=; b=YyFxsV/4Z781mSPnPNhsOaCqZ4dORjFMoxQxPXsPbCiPJ5lAdODacoTv2PoONO6IiV xBKVysIOs4XD7/t6uSDVCz10odLpden534O9n9FASoQdyV6Lt6cUJETdUPACk1l46Mff vmMLo6AtffHjz2FZ/EGmxeJaEgKbkYhOY+qvw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; b=aCvxAL/36KOK8WZ9YJfWDQ+EQIC2ZeV/CR3vG5CVtINXGgEqVTxYXUF/s3DZJAR8oR vTo5L7mFUJ9ksDEZuqFUL2Gh8JiwzQdJw0JrJvNSyKSvW+yOhlP0igPz5GyxZvlAI6Do kcW18DW5k26qttSN9D1HVzkxQ1UrKennxRlx4=
Received: by 10.68.40.65 with SMTP id v1mr9809744pbk.154.1303257065868; Tue, 19 Apr 2011 16:51:05 -0700 (PDT)
Received: from [10.201.64.122] ([203.98.18.214]) by mx.google.com with ESMTPS id d9sm243389pba.16.2011.04.19.16.51.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 19 Apr 2011 16:51:05 -0700 (PDT)
From: Michael Newbery <newbery@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary="Apple-Mail-4-679829607"; protocol="application/pkcs7-signature"; micalg="sha1"
Date: Wed, 20 Apr 2011 11:50:56 +1200
In-Reply-To: <54E900DC635DAB4DB7A6D799B3C4CD8E10C7F13B@PLSWM12A.ad.sprint.com>
To: IPv6 Ops WG <v6ops@ietf.org>
References: <4984B8F2-AC42-491E-9C2B-BE999B279759@cisco.com> <4DACEF1F.8060608@gmail.com> <600F516F-8A57-48E2-8CD7-AD2611E9D5DA@apple.com> <54E900DC635DAB4DB7A6D799B3C4CD8E10C7EBDF@PLSWM12A.ad.sprint.com> <E4BC3273-F288-4AC1-A1B5-9FB630C52E07@gmail.com> <54E900DC635DAB4DB7A6D799B3C4CD8E10C7F13B@PLSWM12A.ad.sprint.com>
Message-Id: <39F82D4C-7757-450F-B486-FA2B0363436C@gmail.com>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [v6ops] draft-ietf-v6ops-6to4-to-historic WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2011 23:51:07 -0000

On 20/04/2011, at 11:18 AM, George, Wes E IV [NTK] wrote:
> [WEG] 5 letters... DDWRT. It shows as proof positive that there is a MUCH wider variety of hardware that CAN support IPv6 that
> DOESN'T due to a specific choice on the part of the OEM vendor. Yes, there are going to be some that actually can't, and "support"
> means different things on different hardware, but assuming that most of the ones that don't is due to hardware limitations is being
> quite generous. 

DDWRT runs on a relatively high end piece of equipment, namely a 802.11 router. There are a lot of plain old WAN-LAN routers though, especially in the xDSL world. It was to them that I was referring. I estimate that the majority of our xDSL customers have gateways that are incapable of being firmware upgraded to IPv6. Even if they have a DDWRT capable router at home that does them no good if the WAN/LAN router can't do IPv6 native.
 
Cable is slightly different, with the cable modem typically being (mostly) layer 2. I estimate that about 50% of our cable customers run some sort of RG and that the other 50% currently have a single PC directly connected. Of the 50% that have RGs, I would estimate that the majority are not capable of being firmware upgraded to IPv6 native. Fortunately, the 50% that have directly connected PCs *are* mostly capable, via an OS upgrade.

And lest anyone misunderstand, I am trying as hard as I can, as fast as I can, to roll out native IPv6 support. I consider tunnels a stopgap and LSN an ineffective abomination (to which I fortunately don't have to resort.)