Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WGLC

Jouni Korhonen <jouni.nospam@gmail.com> Tue, 05 August 2014 07:15 UTC

Return-Path: <jouni.nospam@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 21BBE1A032A for <v6ops@ietfa.amsl.com>; Tue, 5 Aug 2014 00:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_74=0.6, 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 jxfHdK-i_hYo for <v6ops@ietfa.amsl.com>; Tue, 5 Aug 2014 00:15:45 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BBF91A017D for <v6ops@ietf.org>; Tue, 5 Aug 2014 00:15:45 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id v6so377537lbi.39 for <v6ops@ietf.org>; Tue, 05 Aug 2014 00:15:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=zC/2BQ2pJDnXimc85klUdThVNvd48Mfr8OsIDAt0HJg=; b=HedbPwGntMtH+j7WDVAx7vSLGNOW39U3HXD2JWxBqYFpRzJh6N1fkLC5kc2Fvy0UIV db4fikDayzt3tQ9WR7S/yhDmc1Bk+L1YcjIdpLBFg5D8eOGqhvPYI+oslAcEMVPq8XYH 9Lk3pv8caj3K+J0k6CnU5OBvOdXpQd6DTAM1/2CHDvstDQQ5Wxcv6KM+Qa+LeQSmWjAU 9NqAW5LAemKym0iRy2fpfBxGZP2m0TG1pEW5b+ff7HDXRkpM9ChCukEqgW1JKt5fr/R3 InxS++WYySRcylFoCRRyLOhPNjNZAl3D2nHVB/oynTvWAUlwUKZbljUcO9uxoG7KFAu5 CSrQ==
X-Received: by 10.112.34.78 with SMTP id x14mr1854259lbi.38.1407222943600; Tue, 05 Aug 2014 00:15:43 -0700 (PDT)
Received: from [188.117.15.107] ([188.117.15.107]) by mx.google.com with ESMTPSA id ue8sm469474lac.31.2014.08.05.00.15.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 05 Aug 2014 00:15:42 -0700 (PDT)
Message-ID: <53E0849C.9020208@gmail.com>
Date: Tue, 05 Aug 2014 10:15:40 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ross Chandler <ross@eircom.net>, v6ops@ietf.org
References: <201407271800.s6RI04sj008989@irp-lnx1.cisco.com> <alpine.DEB.2.02.1407280906590.7929@uplift.swm.pp.se> <CAM+vMETcGw4TPd2Sy2i7a_0OoFk3844nG=g6Tphi9JDM4h4epA@mail.gmail.com> <alpine.DEB.2.02.1407290708070.7929@uplift.swm.pp.se> <9A04228A-88BC-4123-BFC3-AF081AEDBDC9@eircom.net>
In-Reply-To: <9A04228A-88BC-4123-BFC3-AF081AEDBDC9@eircom.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/5JPc6zzzsDD9SJmUjRD9rAzDM9g
Subject: Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WGLC
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 07:15:47 -0000

The HLR I used allowed quite a bit of configuration regarding this topic:

o PDP Types IPv4, IPv6 and IPv4v6 could all have the same APN for the 
subscriber
o IPv6 could be disabled per PLMN basis

Some of these cases were briefly elaborated in Section 8.5 of RFC6459.

- Jouni

7/30/2014 1:14 AM, Ross Chandler kirjoitti:
>
> On 29 Jul 2014, at 06:10, Mikael Abrahamsson <swmike@swm.pp.se
> <mailto:swmike@swm.pp.se>> wrote:
>
>> On Tue, 29 Jul 2014, GangChen wrote:
>>
>>> Only the value IPv4v6 is allowed for ext_pdp. If HLR doesn't support
>>> IPv4v6 setting(that is the most case pre-R9), in other words, it can't
>>> set ext_pdp. It may not able to support all cases.
>>
>> Then I guess it's a matter of implementation. The HLR I was exposed
>> to, did for 2G/3G show to the user that IPv4 could have ext_pdp_type
>> IPv6, and this enabled IPv4 and IPv4v6 to work with this setting. If
>> UE asked for IPv6 only PDP context that didn’t work, so we had to add
>> a profile that said "IPv6" without ext_pdp_context_type.
>
> We have to define two allowed PDP Types for the same APN, so that legacy
> IPv4 PDPs and IPv6 PDPs for 464xlat can both be requested for the same APN.
>
> e.g.
>
> <hgppp:pdpcp=240;
> HLR PACKET DATA PROTOCOL CONTEXT PROFILE DATA
> PDPCP  APNID  EQOSID  VPAA  PDPCH    PDPTY  PDPID EPDPIND
> 240       80     1    NO             IPV4   25    NO
>            76     1    NO             IPV4   26    NO
>            74     1    NO             IPV4   31    NO
>            73     1    NO             IPV4   32    NO  <-- testdata APN V4
>            73     1    NO             IPV6   50    NO  <-- testdata APN V6
>
> If the Android UE APN Protocol is set to “IPv4/IPv6” with this it sets
> up parallel bearers to the GGSN/PGW.
>
> I agree with Mikael that it might be worth having a section noting this
> behaviour. An operator doing 464xlat could have UEs connecting with
> dual-stack done over separate bearers when they’d prefer it to either be
> single bearer with legacy IPv4 or IPv6 with 464xlat.  This applies in
> the home and roaming case.
>
> Ross
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>