Re: [v6ops] new draft: draft-chen-v6ops-ipv6-roaming-analysis

GangChen <phdgang@gmail.com> Sun, 28 July 2013 18:25 UTC

Return-Path: <phdgang@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB1B21F9D66 for <v6ops@ietfa.amsl.com>; Sun, 28 Jul 2013 11:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.225
X-Spam-Level:
X-Spam-Status: No, score=-2.225 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GRTs1HHWtfV1 for <v6ops@ietfa.amsl.com>; Sun, 28 Jul 2013 11:25:28 -0700 (PDT)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id B00C221F9D4C for <v6ops@ietf.org>; Sun, 28 Jul 2013 11:25:09 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id bq6so1281956qab.18 for <v6ops@ietf.org>; Sun, 28 Jul 2013 11:25: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=Wof9o4YqVsoGulyU7fVJ5stSdy3qArX6A+piX2sPAFQ=; b=GJXSrETUxpB7D3ry3n03y+i1m9pwCFJmzeGxcfhToPcDS8RpKEJh+l2Yy4af7lY12f 7qFAqna/kJOZYh3a+VezR7rpKrS1RhC4/MvrBg9JyjXmkmRRfLhumCFWRyzejAmrHVSN 7lDli/aW1I1KQbVJDl1pJL98lKjMw3cAkIwx46+plV8KfzXE2vz8mWd8Vs8i1RWKhmYs VxbhSBvplrvHWfnvOA4P9kD+aYUa/0eZDu5lVxc9urgZhDdJn1nF7os3yYJOGrK4FCeV HJS/H+hP7byhIwzSytrwqs5rMRB+jyTO+mIr4acWEoSXtMkn7aE5PqZ5ZpeOBqbJSFJ2 EPbw==
MIME-Version: 1.0
X-Received: by 10.224.130.195 with SMTP id u3mr769528qas.80.1375035905007; Sun, 28 Jul 2013 11:25:05 -0700 (PDT)
Received: by 10.224.182.74 with HTTP; Sun, 28 Jul 2013 11:25:04 -0700 (PDT)
In-Reply-To: <CAD6AjGSPgs8JzN7yuPUVSr1Pz5POY6JsMo0_33zK3Kn++RxBBQ@mail.gmail.com>
References: <201307091245.r69Cj0Q08784@ftpeng-update.cisco.com> <CAD6AjGSPgs8JzN7yuPUVSr1Pz5POY6JsMo0_33zK3Kn++RxBBQ@mail.gmail.com>
Date: Mon, 29 Jul 2013 02:25:04 +0800
Message-ID: <CAM+vMERF4izK5_1x_PMBdezjsiAtXnEmcwmZ94X6px3yh4dWsw@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: "cb.list6" <cb.list6@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: IPv6 Ops WG <v6ops@ietf.org>, draft-chen-v6ops-ipv6-roaming-analysis@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-chen-v6ops-ipv6-roaming-analysis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 28 Jul 2013 18:25:50 -0000

Hi Cameron,

Thank you for the comments.

2013/7/28, cb.list6 <cb.list6@gmail.com>:
> As general feedback
>
> 1. As others have noted, it is important to clarify that home routed
> is the default case and local-breakout is only relavent for IMS, but

local-breakout may not be only for IMS. We have deployed that for all
the data roaming between different province's networks in China. It
offers efficient routes. Besides, 3GPP specified the SIPTO
architecture for roaming. That may bring impacts in the future.

> IMS based roaming and local breakout is yet to see its first
> deployment, and may still be years in the future for roaming to work
> this way.  So, local breakout is not  a real case and seems to be
> causing more confusion.
>
> 2.  There is a hazard in assuming the well known prefix is always
> available.  Any device should not assume the well known prefix is
> available.  This is essentially a misconfiguration that should not
> occur.

Ok. You don't recommend using WKP. How about taking different priority
for the deployment

High priority:  nat64-discovery
Medium: WKP
Low: manual configuration



> 3.  What i have learned
>
> a.  dual-stack 2 PDP will never work, charging issues in the billing
> system, and too much capacity wasted for no real gain
>
> b.  dual-stack 1 PDP (v4v6) will not work any time soon.  Enabling
> this feature in the HSS/HLR breaks roaming and there is no way to
> ensure this issue is fixed in the hundreds of networks that are
> potentially impacted.  There are some backs to do on the home network
> that can make this easier but not exposing partner networks to the new
> release 8 features.
>
> c.  What does work and adds value (saves IPv4 address for the common
> case of not-roaming) :  IPv6-only single PDP 464XLAT on the home
> network, IPv4-only single PDP when roaming.  This is how i am moving
> forward.  The when at home, the UE has default configs for ipv6-only
> and when roaming the ue only attempts to connect using IPv4.  This
> gets the vast majority of users in my home network off v4 and keeps
> ipv4 for the complicated yet relatively small percentage of roaming
> users.
>

Thanks for the good summary. That is the lesson we have leaned.

BRs

Gang


>
> On Tue, Jul 9, 2013 at 5:45 AM,  <fred@cisco.com> wrote:
>>
>> A new draft has been posted, at
>> http://tools.ietf.org/html/draft-chen-v6ops-ipv6-roaming-analysis. Please
>> take a look at it and comment.
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>