Re: [v6ops] Operational Consensus on deployment

James Woodyatt <jhw@nestlabs.com> Wed, 27 August 2014 16:29 UTC

Return-Path: <jhw@nestlabs.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B91E1A0B01 for <v6ops@ietfa.amsl.com>; Wed, 27 Aug 2014 09:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.522
X-Spam-Level:
X-Spam-Status: No, score=0.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MANGLED_SONATA=2.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yi4UxwkjvSgH for <v6ops@ietfa.amsl.com>; Wed, 27 Aug 2014 09:29:34 -0700 (PDT)
Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0C2F1A06ED for <v6ops@ietf.org>; Wed, 27 Aug 2014 09:29:33 -0700 (PDT)
Received: by mail-oi0-f43.google.com with SMTP id u20so327026oif.16 for <v6ops@ietf.org>; Wed, 27 Aug 2014 09:29:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=/9voVhMHtLkvl0RhDtQClEBzWRZP5NyO6RB0HlAbmY4=; b=j9j74asiM2LW+/KcQLYs0K3zBwUjrVdOxkxXiM573WdwlaYsB8Csby+f7k6jXC9+wR QmBs1B8qDInpGsG/90WN+vWiNd183pATVdEgDNf86DttGNHXZw382e3Jl+3uTQx/1UKz SovPuzFS2PJcCz3yE5U0PM2vJd2/xbnuaUeKvmUq0qWpGE5ABM3laNDPCqN5SreMvDSt 1qgRf9vmV3O8IQd0cT7/6COb9iUuZ6W8GjmITFcP1fU0DF+f+GsyWWtr6dLqQZIpfugj GpvlEgcFA7vrwa6jsF1TTa3WzziYU+nDrENASD4boYOYQPGkrxB/3sMfyQrxnEPcZXjt WWsQ==
X-Gm-Message-State: ALoCoQkbZggmwJ3Njln40fMkB8Ak1Tq/qHrBvjtePtzV+uhA8XrctmvWm0n3s9qt0SeZXLctP7WE
MIME-Version: 1.0
X-Received: by 10.182.219.116 with SMTP id pn20mr2507651obc.86.1409156973151; Wed, 27 Aug 2014 09:29:33 -0700 (PDT)
Received: by 10.76.96.180 with HTTP; Wed, 27 Aug 2014 09:29:32 -0700 (PDT)
In-Reply-To: <D7A0AFA1-86F3-4658-B3BB-B8C4721843DF@delong.com>
References: <DE860EBC-171E-46E7-A3B6-5E8B79A453CC@cisco.com> <53DFEC6C.3010707@gmail.com> <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com> <53E06AC9.9010908@fud.no> <4F7D76F6-BD81-453B-94DC-A3C3DFF68505@delong.com> <8600C096-37D0-4651-92C1-BCFDBA674433@nominum.com> <CAD6AjGTBfyT-zNDJtBKCNtRxd=Hi07678Sr_-HgSGYbjAiF3Tg@mail.gmail.com> <C5281716-DC04-42E6-AC82-0D53E5DA0284@nominum.com> <53E1236A.605@fud.no> <m1XEkJJ-0000BuC@stereo.hq.phicoh.net> <20140805195402.GO51793@Space.Net> <m1XElwg-0000BbC@stereo.hq.phicoh.net> <D00834AF.68B6C%Lee@asgard.org> <CAD6AjGQJ3PXpGkk9Cd4d-MhExZ9QrpiseyAqPqmpXzQ-HCyDwQ@mail.gmail.com> <CAKD1Yr2=dMg6sua+9v28t173TQVYet6pDU7Xv6RWkbGjqA1ziA@mail.gmail.com> <6536E263028723489CCD5B6821D4B21303B7DB43@UK30S005EXS06.EEAD.EEINT.CO.UK> <20140820003344.23DE61D105DD@rock.dv.isc.org> <D7A0AFA1-86F3-4658-B3BB-B8C4721843DF@delong.com>
Date: Wed, 27 Aug 2014 09:29:32 -0700
Message-ID: <CADhXe53yucmTprtF+vqsPsgqF+4-w6RAAqoN2SsFatccZNT=6g@mail.gmail.com>
From: James Woodyatt <jhw@nestlabs.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="e89a8ff248b5d163f905019eec61"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/4j83nhDKlypr0kBesdn7ELOVgtg
Subject: Re: [v6ops] Operational Consensus on deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 27 Aug 2014 16:29:35 -0000

I think about this a little differently.

I contend the incentive for customers to upgrade will happen when "have you
tried disabling IPv4?" and "do you have IPv6?" are the responses you start
seeing in troubleshooting forums in response to questions in the category
"Why is $APPLICATION not working / too slow / so unstable?"


On Tue, Aug 26, 2014 at 5:07 PM, Owen DeLong <owen@delong.com> wrote:

> The incentive for customers to upgrade will start to happen when ISPs
> start sending out notices to the following effect:
>
> ————————
>
> Due to the aging nature of the IPv4 protocol and the increased costs of
> continuing to support customers on this protocol,
> we will have to start adding an IPv4 surcharge to your bill if you wish to
> continue IPv4 service.
>
> We recognize that today, many customers will consider IPv4 still an
> essential service. Unfortunately, several content providers,
> such as Amazon, Twitter, Bing, Wordpress, etc. still haven’t joined the
> modern internet by upgrading to IPv6.
>
> However, we do not feel that it is fair to penalize customers who no
> longer need IPv4 by asking them to share the costs of
> continuing to support this aging protocol, so, for those customers that
> do, we will begin adding $5/month to your bill effective
> <date>
>
> ————————
>
> (Or something like it)
>
> I believe this will happen sooner than many people think.
>
> Owen
>
> On Aug 19, 2014, at 5:33 PM, Mark Andrews <marka@isc.org> wrote:
>
> >
> > In message
> <6536E263028723489CCD5B6821D4B21303B7DB43@UK30S005EXS06.EEAD.EEINT.C
> > O.UK>, "Heatley, Nick" writes:
> >> If I may stick my neck out.
> >>
> >> Id like v6ops to consider at least two items:
> >>
> >> 1.       (Carrier Grade) NAT64 vs NAT44  a deathmatch.
> >
> >       Most of the problem with NAT64 vs NAT44 is getting CPE
> >       devices upgraded.  464xlate worked for cellular networks
> >       because the devices were replaced to support 4G services
> >       and those new devices support 464xlate.  Additionally cell
> >       phones are fragile devices that get stolen, lost, dropped,
> >       stepped on, driven over, and is some market need to be
> >       replaced to change carrier ... so there is a high turnover.
> >
> >       For wired connections there is no incentive for the customer
> >       to replace the CPE device so NAT44 is a required part of
> >       the solution space just to share the limited IPv4 address
> >       space between the IPv4 only customers.  Cable and DSL modems
> >       work for 10+ years.  Home routers work for similar lengths
> >       of time.  You can still buy IPv4 only routers and they are
> >       cheaper than anything with IPv6 in it.  If you are on a
> >       limited budget a IPv4 only router with 802.11g "will do".
> >
> >       Add to that ISP's not offering / promoting IPv6 there is
> >       no incentive for the customer to buy the IPv6 capable device
> >       over the IPv4 only one.  The choice of device is made on
> >       other factors.  If ISPs offered to do 2G of IPv6 data for
> >       the price of 1G of IPv4 data one might actually get customers
> >       to buy IPv6 capable routers.  A 12 month rebate for installing
> >       a IPv6 capable CPE device could offset the costs of installing
> >       more CGNAT boxes.  IPv6 capable 802.11n routers can be got
> >       for AUD80 today.  Even on a AUD$20 plan the rebates would
> >       cover the costs if the usual +50% taffic shift to IPv6
> >       occurs.
> >
> >       Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>