IETF Logo Mail Archive

Re: [v6ops] Operational Consensus on deployment

Tore Anderson <tore@fud.no> Tue, 05 August 2014 17:42 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 CCD3E1A0035 for <v6ops@ietfa.amsl.com>; Tue, 5 Aug 2014 10:42:49 -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 FHbfWAMf_0uT for <v6ops@ietfa.amsl.com>; Tue, 5 Aug 2014 10:42:48 -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 E9B681B2A90 for <v6ops@ietf.org>; Tue, 5 Aug 2014 10:42:47 -0700 (PDT)
Received: from cm-84.209.85.233.getinternet.no ([84.209.85.233]:59698 helo=envy.fud.no) by greed.fud.no with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tore@fud.no>) id 1XEil3-00052w-Dp; Tue, 05 Aug 2014 19:42:45 +0200
Message-ID: <53E11795.7060305@fud.no>
Date: Tue, 05 Aug 2014 19:42:45 +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: Ross Chandler <ross@eircom.net>, Ca By <cb.list6@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> <53E06AC9.9010908@fud.no> <CAD6AjGTwt-20gXs=RUH5zbhT+g3HKrvXHX3FnShjF1srqU21Fw@mail.gmail.com> <94146541-768B-4853-A011-7558655C361C@eircom.net>
In-Reply-To: <94146541-768B-4853-A011-7558655C361C@eircom.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/ePH6Z2mPcz8U2OBFgokAbWr4Izo
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 17:42:49 -0000

* Ross Chandler

> The APN roaming protocol setting for “telenor.mobil” listed at that
> URL says it is IPv6.
> 
> Is that really their setting? AFAIK the Android UE or more
> accurately the RIL it calls doesn’t fallback to IPv4 when IPv6 is
> explicitly requested.

Yes, that's their setting. No need for fallback when IPv6 works, right?

To be honest I've never quite understood what all the fuss is about
regarding IPv6 and 3GPP roaming. My personal experience, having been a
customer of Tele 2 Norway (formerly Network Norway) using their IPv6
pilot for about two years, then moving to Telenor about six months ago,
is that IPv6 roaming Just Works.

I've not visited every country in the world, but I have been around a
bit, and I've made a point out of trying to establish an IPv6 data
bearer to every single PLMN I can register with. So far I've had 100%
success, including on Cameron's network... Thus enabling IPv6 roaming
doesn't seem like a scary proposition to me. I'm guessing perhaps
Telenor came to the same conclusion.

Tore

v2.23.0 | Report a Bug | By Email