[v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt

Tore Anderson <tore@fud.no> Wed, 06 August 2014 07:30 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 878901B28F5 for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 00:30:45 -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 nYkYC24LiLjv for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 00:30:44 -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 E71A91B28F4 for <v6ops@ietf.org>; Wed, 6 Aug 2014 00:30:43 -0700 (PDT)
Received: from [2a02:c0:2:1:1194:17:0:1000] (port=38484 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 1XEvgH-0006wr-SY; Wed, 06 Aug 2014 09:30:41 +0200
Message-ID: <53E1D951.8030200@fud.no>
Date: Wed, 06 Aug 2014 09:29:21 +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: Mikael Abrahamsson <swmike@swm.pp.se>
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> <53E11795.7060305@fud.no> <alpine.DEB.2.02.1408060856080.7929@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1408060856080.7929@uplift.swm.pp.se>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/hUIZHga-C-AbgYaUCCFvhxmjLwA
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt
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, 06 Aug 2014 07:30:45 -0000

(Changing the subject like Ross did.)

* Mikael Abrahamsson

> I've heard reports of platforms in use in southeast asia, I don't
> remember if it was Korea or some other country, would fail when
> presented with IPv4v6 capability.
> 
> The reason why people are not going for IPv4v6 externally is because it
> breaks things, badly, it seems, due to bugs. So this is why IPv6 only
> bearer is so appealing, because it's been around for 5-10 years and very
> few things break with it.

Yep, and to be clear, Telenor Norway does not support the IPv4v6 on
their IPv6-capable APN (nor does Tele2/Network Norway). Furthermore,
Telenor only supports IPv6 (not IPv4), while Tele2/NwN supports both
IPv6 and IPv4.

Which leads me to a point I forgot to mention before, if Telenor had
used Roaming Protocol = IPv4 as Ross suggested, or if the phone RIL did
a similar fallback, it would actually ascertain failure, since the APN
doesn't allow IPv4. If IPv6 fails, one would have to change to one of
the IPv4-only APNs.

> The scary part isn't enabling IPv6, it's enabling IPv4v6 or capability
> to do so. When advertised as capability to visiting SGSN it might refuse
> to bring up any bearer at all. So this is why the draft suggests it
> might be a good idea to not advertise this to roaming partners.

Yes, the -02 draft makes it much clearer than previous versions that
this concern is applicable specifically for IPv4v6 and not for IPv6.

In spite of this I see that some providers that are using IPv6 and home
routing chose to set the Roaming Protocol to IPv4. This is what I don't
quite understand the reason for. Perhaps due to a misunderstanding that
the problems IPv4v6 also apply for IPv6, or some other problem I have
yet to come across?

I don't really know much about what's going on "under the hood" in
mobile networks to be honest, but with my "dumb user" hat on I can
conclude that IPv6 roaming seems to work just fine with the way Telenor
and Tele2/NwN have implemented it. So I'm happy. :-)

Tore