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

GangChen <phdgang@gmail.com> Thu, 07 August 2014 07:18 UTC

Return-Path: <phdgang@gmail.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 A95CC1B286A for <v6ops@ietfa.amsl.com>; Thu, 7 Aug 2014 00:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 Pg6TbUYuYFdn for <v6ops@ietfa.amsl.com>; Thu, 7 Aug 2014 00:18:06 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A4881B2855 for <v6ops@ietf.org>; Thu, 7 Aug 2014 00:18:06 -0700 (PDT)
Received: by mail-qg0-f44.google.com with SMTP id e89so4017840qgf.3 for <v6ops@ietf.org>; Thu, 07 Aug 2014 00:18:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xxzhhpH+fHE72yUZ7k6fvd6LhngSxlpovnJWqP433F8=; b=hrUMfYneUD7wuyyDiNb70rtW3d+Indvh4Gc68zkEztLttodI6TXb28q/k9TlPsbmAq csd7GZIaS2nAcpwbD5ECE6gvoGfq3F53sQiubRXHK4gxPel3hnoV/SuHc4BOSjKZnL4n x1x52+jwgLl6PBCN4W7lUvQYCc8KZksfuGYd3ZETmIN8qcxoufapkEEDPMykB/OgbJGp 8WNJL2hFBhPzWvv/dZGo5SZXlXRUXFZ6UnoIMBB2xtmQINrXzo/97TSOoMBroccP4FQ6 g1qW1+nWjekzgXow2w4FuUl27F+s+W4VHrHV/krh4Pm8919w/NHpfGxkqk73Ni/3NLCn U1GA==
MIME-Version: 1.0
X-Received: by 10.140.48.234 with SMTP id o97mr8548444qga.10.1407395885484; Thu, 07 Aug 2014 00:18:05 -0700 (PDT)
Received: by 10.224.46.10 with HTTP; Thu, 7 Aug 2014 00:18:05 -0700 (PDT)
In-Reply-To: <53E1D951.8030200@fud.no>
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> <53E1D951.8030200@fud.no>
Date: Thu, 07 Aug 2014 15:18:05 +0800
Message-ID: <CAM+vMEToVpRAgX7NjQWn+S3A1t+BhYWvRzfc3J11io2N+ahu9w@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Tore Anderson <tore@fud.no>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/VdcebaJ9NHhhbzap_v7AM25VQWg
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [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: Thu, 07 Aug 2014 07:18:08 -0000

2014-08-06 15:29 GMT+08:00, Tore Anderson <tore@fud.no>:
> (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?

Setting roaming APN with IPv4 is recommended in local breakout mode.
As described in
http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-roaming-analysis-02#section-5.3,
IPv6-only PDP/PDN can't be failed over to IPv4. In your case, I guess
traffic is home routed. When a Telenor customer roams Tele2/NwN, All
PDP/PDN request and traffic will back to Telenor network. Therefore,
it works. However, it increases the international data roaming fees to
customers, since Telenor has to pay GRX/IPX carrier for the
international traffic transit. In order to reduce the cost, local
breakout is an optimized approach. It will save the charge for GRX/IPX
transit and improve data service performance. In that case, I guess
the Telenor customer has to check if roaming APN set to IPv4-only,
since the visited network may not able to allocate IPv6 to customers.

BRs

Gang

> 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
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>