Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WGLC
GangChen <phdgang@gmail.com> Tue, 29 July 2014 02:26 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 7749D1A0B00 for <v6ops@ietfa.amsl.com>; Mon, 28 Jul 2014 19:26:14 -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 s3wFyNdHHy0w for <v6ops@ietfa.amsl.com>; Mon, 28 Jul 2014 19:26:09 -0700 (PDT)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D25711A0AFB for <v6ops@ietf.org>; Mon, 28 Jul 2014 19:26:08 -0700 (PDT)
Received: by mail-qg0-f51.google.com with SMTP id a108so9267208qge.38 for <v6ops@ietf.org>; Mon, 28 Jul 2014 19:26:08 -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=eEe0o1dSxDj4uEJcqDLkHBrL1UcpINZKNoPuwZqrfMY=; b=bSORJo6N4T5bTh50Ae/OF8Ji0PKvewPk6T1fM9lCeIMD84hQsOY08DRIED99EI2sOj davKcSqbd6MUufKCYZvu1IiYSdQolD8ukdnCR2ncKaTAnPp6XacuygXqgIcySISK5TB1 T2q435vVjGUUZpjqfZztVzy3oIB7pI4zu5lvw/XoO/H8ervEmLOSPJQZqRsw/8ucdcXz upvGNVVn+HlPf5++FGdd7VaPyIc9rfZXEZpPEoyg1qq3eYsTs3TwS/spuHmCafBE5/KV krf+q9Nu25n1Qk95hOQcLKn1wQFhsAErpWVXYrqVH7CPotbeaRCHsU8+qkSHnkCidkwJ Bx/A==
MIME-Version: 1.0
X-Received: by 10.229.211.132 with SMTP id go4mr4100315qcb.0.1406600768020; Mon, 28 Jul 2014 19:26:08 -0700 (PDT)
Received: by 10.224.46.10 with HTTP; Mon, 28 Jul 2014 19:26:07 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.02.1407280906590.7929@uplift.swm.pp.se>
References: <201407271800.s6RI04sj008989@irp-lnx1.cisco.com> <alpine.DEB.2.02.1407280906590.7929@uplift.swm.pp.se>
Date: Tue, 29 Jul 2014 10:26:07 +0800
Message-ID: <CAM+vMETcGw4TPd2Sy2i7a_0OoFk3844nG=g6Tphi9JDM4h4epA@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/4-g9pEOr9rj7o2gtTmrriigiZGo
Cc: v6ops@ietf.org
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, 29 Jul 2014 02:26:14 -0000
2014-07-28 15:15 GMT+08:00, Mikael Abrahamsson <swmike@swm.pp.se>: > On Sun, 27 Jul 2014, fred@cisco.com wrote: > >> This is to initiate a two week working group last call of >> http://tools.ietf.org/html/draft-ietf-v6ops-ipv6-roaming-analysis. >> Please read it now. If you find nits (spelling errors, minor suggested >> wording changes, etc), comment to the authors; if you find greater >> issues, such as disagreeing with a statement or finding additional >> issues that need to be addressed, please post your comments to the >> list. >> >> We are looking specifically for comments on the importance of the >> document as well as its content. If you have read the document and >> believe it to be of operational utility, that is also an important >> comment to make. > > I have re-read the document. I still find it useful. However, when reading > it I can't help of feeling that this document isn't ready for publication > yet. It definitely needs a do-over when it comes to language and spelling. > > Also, on the technical side, I feel the document could be clearer, but I > don't know exactly how. I know my comment here isn't really helpful, apart > from saying that the document might need more work. > > One thing that came to mind though, would be a section on how to best > provision users in HLR. At least one vendor I know of, doesn't support > setting "IPv4v6" on a user in their HLR. In order to support all cases of > "IPv4", "IPv6" and "IPv4+IPv6" (dual bearer) and "IPv4v6", one needed to > give the user two profiles, one being IPv4+ext_pdp IPv6, and also > IPv6+ext_pdp, otherwise the user couldn't connect using IPv6 only. 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. I guess one way to provision users if HLR can suppor ext_pdp: two profiles: #1: PDP-Context ::= SEQUENCE { pdp-ContextId ContextId, pdp-Type PDP-Type, IPv4 & IPv6 pdp-Address PDP-Address OPTIONAL, .... apn-oi-Replacement APN-OI-Replacement OPTIONAL, -- this apn-oi-Replacement refers to the APN level apn-oi-Replacement and has -- higher priority than UE level apn-oi-Replacement. ext-pdp-Type Ext-PDP-Type OPTIONAL, -- contains the value IPv4v6 defined in 3GPP TS 29.060 [105], if the PDP can be -- accessed by dual-stack UEs ext-pdp-Address PDP-Address OPTIONAL, -- contains an additional IP address in case of dual-stack static IP address assignment -- for the UE. -- it may contain an IPv4 or an IPv6 address/prefix, and it may be present -- only if pdp-Address is present; if both are present, each parameter shall -- contain a different type of address (IPv4 or IPv6). ... } #2: PDP-Context ::= SEQUENCE { pdp-ContextId ContextId, pdp-Type PDP-Type, IPv4 & IPv6 pdp-Address PDP-Address OPTIONAL, .... apn-oi-Replacement APN-OI-Replacement OPTIONAL, -- this apn-oi-Replacement refers to the APN level apn-oi-Replacement and has -- higher priority than UE level apn-oi-Replacement. } HLR sends ISR with #1 to vSGSN that above R9; otherwise, it sends #2 to vSGSN that is pre-R9 BRs Gang > -- > Mikael Abrahamsson email: swmike@swm.pp.se > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops >
- [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WG… fred
- [v6ops] draft-ietf-v6ops-ipv6-roaming-analysis WG… fred
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… Mikael Abrahamsson
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… GangChen
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… Mikael Abrahamsson
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… Ross Chandler
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… gangchen
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… GangChen
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… Ross Chandler
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… GangChen
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… Ross Chandler
- Re: [v6ops] draft-ietf-v6ops-ipv6-roaming-analysi… Jouni Korhonen