IETF Logo Mail Archive

Re: [v6ops] Operational Consensus on deployment

Tore Anderson <tore@fud.no> Tue, 05 August 2014 05:26 UTC

Return-Path: <tore@fud.no>
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 B230C1B2893 for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 22:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 VVCJxDE1FC85 for <v6ops@ietfa.amsl.com>; Mon, 4 Aug 2014 22:26:52 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3EDF1A011E for <v6ops@ietf.org>; Mon, 4 Aug 2014 22:26:51 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1000] (port=48913 helo=echo.ms.redpill-linpro.com) by greed.fud.no with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tore@fud.no>) id 1XEXGs-0006Ub-0F; Tue, 05 Aug 2014 07:26:50 +0200
Message-ID: <53E06AC9.9010908@fud.no>
Date: Tue, 05 Aug 2014 07:25:29 +0200
From: Tore Anderson <tore@fud.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: Ca By <cb.list6@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <256EAE0B-5C11-42C7-BCA1-CEC7EE6713A7@cisco.com> <53DFD634.4020304@fud.no> <DE860EBC-171E-46E7-A3B6-5E8B79A453CC@cisco.com> <53DFEC6C.3010707@gmail.com> <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com>
In-Reply-To: <CAD6AjGRUWxT5XiNxMi_S5VgYtGMLb_FVHXN-ZfGpcY=geix15g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/NfmT9z3mkoTlWNO7aCluRj9-n7Y
Cc: IPv6 Ops WG <v6ops@ietf.org>
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: Tue, 05 Aug 2014 05:26:53 -0000

* Ca By

> With 464xlat, afaik, there are globally 3 cellular providers that offer
> default ipv6 (464xlat at tmobile us and Orange PL and DS at VZ).

Make that four, Telenor Norway has been doing IPv6-only/NAT64/464XLAT
since early June.

http://www.telenor.no/privat/kundeservice/mobilhjelp/internettpamobilen/feilsokingmmsoginternett.jsp

So far only one model (Samsung S5) defaults to the new IPv6-only APN,
but from what I hear they'll keep adding new models and push OTA updates
to other existing ones.

* Brian E Carpenter

>> (In parenthesis, I've never seen sunsetting IPv4 as a real problem.
>> One day somebody will notice that there are no more IPv4 packets. But
>> that is many years in the future.)

The thing is, if you've built your infrastructure on IPv4, removing it
is going to be a royal pain in the arse. Even if all the IPv4 users have
left the public internet, if your application server speaks to your
database server over IPv4, and the database server speaks to the iSCSI
array over IPv4, and so on and so on, then you're simply not in a
position to easily shut IPv4 off.

Tore

v2.23.0 | Report a Bug | By Email