Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming-analysis-02.txt
GangChen <phdgang@gmail.com> Wed, 06 August 2014 10:42 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 C9ED41B2923 for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 03:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, 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 zKPtczw9IVYv for <v6ops@ietfa.amsl.com>; Wed, 6 Aug 2014 03:42:49 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 445201B292E for <v6ops@ietf.org>; Wed, 6 Aug 2014 03:42:46 -0700 (PDT)
Received: by mail-qg0-f44.google.com with SMTP id e89so2452916qgf.31 for <v6ops@ietf.org>; Wed, 06 Aug 2014 03:42:45 -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=QM0Xg2zPlajZ4BOiaXEwL4Khq75TsNb0LVtml0Kb+hs=; b=V/OgTcO8UHDX3tPsEqvHrH0Iow2hymq36dD4EDjouWgIbI3/7Ke59Q0mqFt5zCXP9Z 9zDPcFQjyzFSfZnY+fkfNVNOIha2GJ0wYTBxPu514q6qtTj8kly4EIfJXR0faHiV6iFx BDN3KLc5cdPCx3DjYke4rY7FiJ8DK1Mt4rh1PA4JZu4mIqrHAaUe7t6e5YO/6M2Vp1tJ 2aoHSp/bpE6DYhgFFlAga6n9m5JWCk3swrNktey7ZEIL0674OuABO10NxsAh4wmn1/Qp 9sJgOJv+17o5NGmpHIK6t1ty8mrZs2wDYGBN37kzyelNsXpi5CkiXtrPRWaGAE/qjNSa TmCg==
MIME-Version: 1.0
X-Received: by 10.224.119.193 with SMTP id a1mr15715484qar.18.1407321765331; Wed, 06 Aug 2014 03:42:45 -0700 (PDT)
Received: by 10.224.46.10 with HTTP; Wed, 6 Aug 2014 03:42:45 -0700 (PDT)
In-Reply-To: <6536E263028723489CCD5B6821D4B21303B6F82C@UK30S005EXS06.EEAD.EEINT.CO.UK>
References: <20140804010755.5662.75071.idtracker@ietfa.amsl.com> <CAM+vMETtTvs9oeNtg5T7ReyyH1o3g7VXtpG+g-3bKbm6dpAoEQ@mail.gmail.com> <8E890204-B4A8-4EDC-BFF6-FC33A2C30FC6@eircom.net> <alpine.DEB.2.02.1408041827340.7929@uplift.swm.pp.se> <CAM+vMEQDmabh1Smm-qibzNfZtj-RWYxyFO7xMVJUaH3yCccD2Q@mail.gmail.com> <B0BB2BF3-7BEF-478D-B255-3E174E447CD8@gmail.com> <D047CA2A-9015-4E96-8511-CCB418392A8D@eircom.net> <6536E263028723489CCD5B6821D4B21303B6F82C@UK30S005EXS06.EEAD.EEINT.CO.UK>
Date: Wed, 06 Aug 2014 18:42:45 +0800
Message-ID: <CAM+vMETAeJ-7pV_cBUFtYSkae56-AgJmrgL3x0iCetQ0+xxRTw@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: "Heatley, Nick" <nick.heatley@ee.co.uk>, Ross Chandler <ross@eircom.net>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/JqMhk5Ro0rwhEkEUWyJ3NfGUFBQ
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
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: Wed, 06 Aug 2014 10:42:50 -0000
Ross and Nick, The draft doesn't intend to advocate any deployment mode. To be clear, "dual-stack deployment is recommended in most cases" will be removed at the next update. Gang 2014-08-05 23:53 GMT+08:00, Heatley, Nick <nick.heatley@ee.co.uk>: >>So there's an argument to remove "dual-stack deployment is recommended in >> most cases" from this draft, particularly if it has already been discussed >> and agreed not to promote any solution. > > Agree. > > Also the standards statement: > "A UE which is IPv6 and IPv4 capable shall request for PDN type IPv4v6". > does not mean that the UE is placed into a dual stack mode of operation. It > is signalling to the network that it can support all modes. > (We desire the UE to request IPv4v6 in the home network and we can let the > core network push the UE to IPv6-only mode of operation. > When on legacy small-cells, where the access-points do not support the new > PDN types, the device can gracefully fallback to IPv4, if it requests > IPv4v6.) > Nick > > From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Ross Chandler > Sent: 05 August 2014 12:33 > To: v6ops@ietf.org > Subject: Re: [v6ops] I-D Action: > draft-ietf-v6ops-ipv6-roaming-analysis-02.txt > > > On 5 Aug 2014, at 11:53, Jouni > <jouni.nospam@gmail.com<mailto:jouni.nospam@gmail.com>> wrote: > > > > On Aug 5, 2014, at 1:28 PM, GangChen wrote: > > > 2014-08-05 0:31 GMT+08:00, Mikael Abrahamsson > <swmike@swm.pp.se<mailto:swmike@swm.pp.se>>: > > > Section 7, discussions, says "dual-stack deployment is recommended in > most cases". > Is that still the consensus position? Going straight to single-stack IPv6 > is looking very viable now > when the UE supports a method of providing translated IPv4 access over the > IPv6 PDP/PDN > connection. > > I don't think there is consensus here. The draft could point out pros and > cons with each approach. > > I'm not a fan of dual-stack deployment. However, I have to point out > if you take look at TS23.060 or TS23.401, you may find the sentence "A > UE which is IPv6 and IPv4 capable shall request for PDN type IPv4v6". > GSMA quotes the similar language from 3GPP for roaming guidance. > Therefore, that is at least a consensus in other SDOs. > > The draft intends to state the issues and potential workarounds in > various scenarios. Argument of selection of dual-stack or IPv6-only > may not be the goal of the draft. > > We had this discussion a long ago.. and back then we agreed not to promote > any specific solution (like XLAT etc) but just give facts how different > approaches work. > > - Jouni > > > The TS23.975 recommendations do allow for a second strategy. I can't find > TS23.975 explicitly saying dual-stack is preferred or recommended over > single stack. > Although at the time they were writing it they were probably implicitly > assuming that. TS23.975 mentions DS-Lite, NAT64 and BIH but was too early > for 464XLAT, or MAP-T/E. > > "The second strategy, consisting of providing the UE with IPv6-only > connectivity, can be considered as a first stage or an ultimate target > scenario for operators." > > So there's an argument to remove "dual-stack deployment is recommended in > most cases" from this draft, particularly if it has already been discussed > and agreed not to promote any solution. > > BR > Ross > > NOTICE AND DISCLAIMER > This e-mail (including any attachments) is intended for the above-named > person(s). If you are not the intended recipient, notify the sender > immediately, delete this email from your system and do not disclose or use > for any purpose. > > We may monitor all incoming and outgoing emails in line with current > legislation. We have taken steps to ensure that this email and attachments > are free from any virus, but it remains your responsibility to ensure that > viruses do not adversely affect you. > > EE Limited > Registered in England and Wales > Company Registered Number: 02382161 > Registered Office Address: Trident Place, Mosquito Way, Hatfield, > Hertfordshire, AL10 9BW >
- [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roaming… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Mikael Abrahamsson
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Jouni
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Heatley, Nick
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… GangChen
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler
- Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-roa… Ross Chandler