IETF Logo Mail Archive

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

GangChen <phdgang@gmail.com> Thu, 07 August 2014 05:59 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 5CA601A0B11 for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 22:59:00 -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 EoaxzGNl9KQ0 for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 22:58:58 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20B5E1A854B for <v6ops@ietf.org>; Wed, 6 Aug 2014 22:58:58 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id a108so3942971qge.30 for <v6ops@ietf.org>; Wed, 06 Aug 2014 22:58:57 -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:content-transfer-encoding; bh=w+Oc8VyDTOHSqZ7M+DyBAo5xqxgU4jEWKm0jjb+C6gk=; b=PaPuSs8LY2yJgwpHfaQ/vVD5yjf4rpOb99nJnOQoaBoqkz4y+z05RIxCItJwIurbOh zL58sSy8stTopZmDIjNDSuUKUBvafKz36jNTP3NT4cUhUt1jkr/v20y0tqRZwcAkgQQr bkWNe7s0pK+yNgOESQIutgpwJ0toR6zVhcVRVx2smZ3N4pdpa0Q53qUEhLwslYWDKLSf X/xD23Eiz4IyOxNyboKMoIHvhrf80/mGRUlD2mcRvsqFjPV1kPr0ZvEjGi6U9Pv27N3B VsQjIbQBOpPaD2e5qnsj7H11hIlAnDX/0h/jrETny/NFURP8XTRsi/jLxce1oTPflzd9 1uCA==
MIME-Version: 1.0
X-Received: by 10.224.119.193 with SMTP id a1mr24167745qar.18.1407391137324; Wed, 06 Aug 2014 22:58:57 -0700 (PDT)
Received: by 10.224.46.10 with HTTP; Wed, 6 Aug 2014 22:58:57 -0700 (PDT)
In-Reply-To: <DF75AC0C-098C-4EC8-9598-6F003E1887AA@eircom.net>
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> <DF75AC0C-098C-4EC8-9598-6F003E1887AA@eircom.net>
Date: Thu, 07 Aug 2014 13:58:57 +0800
Message-ID: <CAM+vMERzKa64qyUmmp8j_0e+Sxe4zXdUQwkjrRQe910=Rz+==A@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Ross Chandler <ross@eircom.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/BQd9lXQZBpka7LWUnFBxlwKWyRM
Cc: IPv6 Ops WG <v6ops@ietf.org>, Tore Anderson <tore@fud.no>
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 05:59:00 -0000

2014-08-06 2:22 GMT+08:00, Ross Chandler <ross@eircom.net>:
> Subject line change as this has turned more appropriate to the
> roaming-analysis draft.
>
> On 5 Aug 2014, at 18:42, Tore Anderson <tore@fud.no> wrote:
>
>>> 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.
>
> According to the manual my SGSN-MMEs have an “AllowIPv6ForAllVisitors”
> parameter that has to be set true to allow IPv6 PDP/PDN connections be
> set-up be visitors.
>
> Out of the box the SGSN-MME had userplane IPv6 enabled for home users. It
> needed the DAF flag to be set (to allow dual-stack in a single bearer).
>
> Proposal for  addition to the draft - it should mention “IPv6 Roaming
> friendly operator” settings (user plane IPv6 allowed, DAF=1 if possible) on
> how to make your network friendly for visitors.

It make sense. I guess the meaning of “AllowIPv6ForAllVisitors”
parameter is to enable SGSN validating the Activate PDP Context
Request with IPv6-only PDP type and sending a Create PDP Context
Request with IPv6-only PDP to GGSN/PGW.

Gang


> Ross
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email