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

GangChen <phdgang@gmail.com> Wed, 24 July 2013 11:24 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 BB61811E8203 for <v6ops@ietfa.amsl.com>; Wed, 24 Jul 2013 04:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 khm6Rjt99LOI for <v6ops@ietfa.amsl.com>; Wed, 24 Jul 2013 04:24:39 -0700 (PDT)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id DAC9F11E8200 for <v6ops@ietf.org>; Wed, 24 Jul 2013 04:24:38 -0700 (PDT)
Received: by mail-qc0-f175.google.com with SMTP id k14so168431qcv.20 for <v6ops@ietf.org>; Wed, 24 Jul 2013 04:24:38 -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=FKVR91pcfHO+w3PBjmHNkQ+4sBNoHxWWBdaTfRSQjrA=; b=jB7LgDWC7b5hNtu+etkArRRqk4dnzRHL7MXC0k+IV5AcIfXtatDqwpgaHLwA+dSRnX JDJ2iucOIj1pgwc/Jyrvt39WFQ9WUZdHEDctV0DYY23PlQAbk3/THpX5yqSyAm42dsdt kSgbx4/1aOCS1vSKr9469e2+xBVGlEseCVVjkVzXODrrKpZzjulGt9D0MspN+DRUNh7k SzVwPQPslMO57g3gc8qPylP3vcmdZakwrNEjQsWe3BmTQAADRcAnKBuBIi/kqOJuN3zF xaHeN9LI1myenhLggPGZ2QDJklRp2U/Eh8YG09jac7Ly0u825AmrcZvFxKCFLC58GuRz DULw==
MIME-Version: 1.0
X-Received: by 10.224.75.133 with SMTP id y5mr16511887qaj.72.1374665078374; Wed, 24 Jul 2013 04:24:38 -0700 (PDT)
Received: by 10.224.182.74 with HTTP; Wed, 24 Jul 2013 04:24:38 -0700 (PDT)
In-Reply-To: <AFAB9759B1DE4F4187483FC509B501990112D147A1E1@HE111490.emea1.cds.t-internal.com>
References: <201307091245.r69Cj0Q08784@ftpeng-update.cisco.com> <AFAB9759B1DE4F4187483FC509B501990112D147A1E1@HE111490.emea1.cds.t-internal.com>
Date: Wed, 24 Jul 2013 19:24:38 +0800
Message-ID: <CAM+vMES1zsyg-ANkQmpjA0sKy3Gi=cjqVpB0jOjCQOm-HjtwCg@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: holger.metschulat@telekom.de
Content-Type: text/plain; charset="ISO-8859-1"
Cc: 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: Wed, 24 Jul 2013 11:24:39 -0000

Hi Holger,

2013/7/23, holger.metschulat@telekom.de <holger.metschulat@telekom.de>:
> Hi all,
>
> this is an interesting document that will help in the introduction of IPv6
> and the combination of IPv4/IPv6 into mobile networks, however, I believe it
> needs a bit of evolution...

Thanks for your interests. The evolution would be made according to
discussions on the list.

> 1. Can you distinguish between IP local breakout and home routed traffic,
> because there is a significant difference on what the visited network must
> support?

We realized the importance to differentiate those two cases. Yes. It
will be distinguished.

> 2. GSMA's IR.21 should be taken into account as well.

It will be cited

> 3. For home routed traffic, the visited network, and also the home network,
> have influence on the PDP context types that are successfully established,
> or that are rejected. Could this be described as well?

Yes. As suggested by Jouni, the combination of HLR configuration, UE
PDP context requests and visited network supported will be described
in the next update.

> Should this document only enumerate "things that went wrong and lessons
> learnt", or should it go through all possible combinations of a roaming
> situation and provide information what does work and what does not work?

The original draft is trying to circulate all the possible roaming
cases, and, make a detailed description/analysis to the failure cases.
The audience could check with their own conditions.
We would also like to hear the group's opinions. The wg inputs are
most important to the document's evolution.

Best Regards

Gang


> Holger