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

Vízdal Aleš <ales.vizdal@t-mobile.cz> Wed, 06 August 2014 12:39 UTC

Return-Path: <ales.vizdal@t-mobile.cz>
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 818EA1B29AF for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 05:39:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.253
X-Spam-Level:
X-Spam-Status: No, score=-0.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 WNqB51xbxWqE for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 05:39:41 -0700 (PDT)
Received: from ctxmailhub.t-mobile.cz (ctxmailhub.t-mobile.cz [93.153.104.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E0671B29A5 for <v6ops@ietf.org>; Wed, 6 Aug 2014 05:39:39 -0700 (PDT)
From: Vízdal Aleš <ales.vizdal@t-mobile.cz>
To: Tore Anderson <tore@fud.no>, Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt
Thread-Index: AQHPsUhsF/ChxSljdUaZmsTWKszVy5vDezSw
Date: Wed, 06 Aug 2014 12:39:35 +0000
Message-ID: <3f59106bc21840dfb144c7933215294f@srvhk403.rdm.cz>
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>
In-Reply-To: <53E1D951.8030200@fud.no>
Accept-Language: en-GB, cs-CZ, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.254.57.29]
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Loop: 2
X-CFilter-Loop: Forwarded
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/KPt87Ey9njFdqH2fgm-r91DWKig
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: Wed, 06 Aug 2014 12:39:43 -0000

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Tore
> Anderson
> Sent: Wednesday, August 06, 2014 9:29 AM
> To: Mikael Abrahamsson
> Cc: IPv6 Ops WG
> Subject: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-
> analysis-02.txt

> 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.

Tore,

Let me try to clarify.

The APN settings set at the UE (handset) are telling the UE
what to 'request' from the mobile network (e.g. APN name to
connect to, PDP type ipv4 or ipv6 or ipv4v6...). The mobile
network is than comparing what was 'requested' by the UE/subscriber
with subscriber's profile at the HLR/HSS. I can be that the
network will allow both IPv4/IPv6, but the UE will be configured
to request IPv6 at home and IPv4 while roaming, so it won't break.

Some UEs such as Android since some version I cannot recall
offer to specify the Home network PDP Type to control what
will the UE request while at the Home network and a dedicated
PDP Type setting for roaming, so that a different PDP Type
can be used if necessary.

> Tore

Ales

Zásady komunikace, které společnost T-Mobile Czech Republic a.s. užívá při sjednávání smluv, jsou uvedeny zde  http://www.t-mobile.cz/zasady. Není-li v zásadách uvedeno jinak, nepředstavuje tato zpráva konečný návrh na uzavření či změnu smlouvy ani přijetí takového návrhu. The communication principles which T-Mobile Czech Republic a.s. applies when negotiating contracts are defined here http://www.t-mobile.cz/principles. Unless otherwise stated in the principles, this message does not constitute the final offer to contract or an amendment of a contract or acceptance of such offer.