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

GangChen <phdgang@gmail.com> Thu, 18 July 2013 08:46 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 422E911E80EC for <v6ops@ietfa.amsl.com>; Thu, 18 Jul 2013 01:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.493
X-Spam-Level:
X-Spam-Status: No, score=-2.493 tagged_above=-999 required=5 tests=[AWL=0.107, 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 Ol4cHiSb5Ezz for <v6ops@ietfa.amsl.com>; Thu, 18 Jul 2013 01:46:23 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id A6E5F11E80E2 for <v6ops@ietf.org>; Thu, 18 Jul 2013 01:46:23 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id e10so1552752qcy.41 for <v6ops@ietf.org>; Thu, 18 Jul 2013 01:46:23 -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=jjNdgP4aE1LSCCU18/ulW3SyKvAIIYG4ahVuOdW0SM8=; b=Q2jG8lfn33qDKhrNV/ks/A2W0JktbU4M2rZyUHIdsaSy/Z1QfSOyAwoT6RHDY2LL0l GgAciubrA9/czor1PnTxX3T33gVARVNddGMu7np6bq15iJmw+cU52CwYih4DE3A+2Slm 6DXFqbFtBxin+uDFUO3J38R+hW1Q28729Ti4F2RJIGxVSGxnZn0EMRQYGbOro5RbOgOK fGrRf6YELSZP+GaPkeLTZ91bEO1xNVcxyzx6v6hGamx44sA9+hQ2rZhoWo3SxYLaTDJB W/j+slLvyNroPqt5bY4BCsglbV6MzBErF87Hm2F6cH51kebuU08Ylf2R00MP4M0XpDrI 1rlg==
MIME-Version: 1.0
X-Received: by 10.224.212.199 with SMTP id gt7mr12779378qab.80.1374137183149; Thu, 18 Jul 2013 01:46:23 -0700 (PDT)
Received: by 10.224.182.74 with HTTP; Thu, 18 Jul 2013 01:46:23 -0700 (PDT)
In-Reply-To: <806058568c3cd8d3600cb70bc520c10a@greed.fud.no>
References: <201307091245.r69Cj0Q08784@ftpeng-update.cisco.com> <88b3974ae0dcc67770c6ba6e29e09c7f@greed.fud.no> <CAM+vMETh_FyroOGabGz=TgrtH53poxnu9qH7ZY5xiP-c7SMWZQ@mail.gmail.com> <806058568c3cd8d3600cb70bc520c10a@greed.fud.no>
Date: Thu, 18 Jul 2013 16:46:23 +0800
Message-ID: <CAM+vMET7TyaAbykpSh_mnwoEnJuw2QFx1mYj=84oCxL0XhRTmw@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Tore Anderson <tore@fud.no>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: v6ops@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: Thu, 18 Jul 2013 08:46:24 -0000

2013/7/18, Tore Anderson <tore@fud.no>:
> * GangChen
>
>> Thanks for sharing your experience. Yes, you are right.
>> There is no such issue if the subscriber's traffic get back to the
>> gateway (e.g. GGSN) in the home network.
>> The described failure case occurred when the subscriber get an address
>> from the GGSN in the visited network. And traffic flows would be
>> transmitted in a local-breakout manner.  3GPP allows such
>> local-breakout because it has more efficient routing paths. 3GPP also
>> specified another architecture called "SIPTO". It guarantees the
>> subscriber would always select the closest GGSN to reside.
>
> I see. When roaming, I always get an IP address that belongs to my home
> provider (this goes both for IPv4 and IPv6), so I assume that it is the
> home network's choice whether or not to enable this "use closest GGSN"
> feature?

Yes, those behaviors could be gauged by subscriber's profile. For
example, disable local-break-out

> If so, I'd suggest adding some text that ensuring this feature is
> disabled (at least for the IPv6 PDP type, if it is possible to
> differentiate between the two) is a good way to prevent IPv6 subscribers
> from experiencing problems when roaming in IPv4-only networks.

Good suggestion. I would add the point in the next update.

Best Regards

Gang

> Tore
>