[v4tov6transition] comments draft-tsou-v4v6tran-mobile-transition-guide
Cameron Byrne <cb.list6@gmail.com> Tue, 21 September 2010 01:58 UTC
Return-Path: <cb.list6@gmail.com>
X-Original-To: v4tov6transition@core3.amsl.com
Delivered-To: v4tov6transition@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED3C23A68D8 for <v4tov6transition@core3.amsl.com>; Mon, 20 Sep 2010 18:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level:
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=0.330, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L+39tR7v8kco for <v4tov6transition@core3.amsl.com>; Mon, 20 Sep 2010 18:58:08 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id DB1973A68D2 for <v4tov6transition@ietf.org>; Mon, 20 Sep 2010 18:58:07 -0700 (PDT)
Received: by gwb20 with SMTP id 20so2073486gwb.31 for <v4tov6transition@ietf.org>; Mon, 20 Sep 2010 18:58:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=Vci5yuU249h8BZWrRMQPnycxZ72ZUgYlZ5r8TXFKItw=; b=pZIkseyw4JG00tYOf3JUF9qrkx2V/jeVTrGZYyAu6251Z6L8ksTp77gIuf6aep4vMS aoHk7nk9hIM2Li76bUTs3rw2GxdJiJzk5OEAm7YzwLDwZXvsFGrm7gN+DdbapBR3opVd Sx4gictXaSHJTYycuP9xPVTRXLtOBMQ5vxp9Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oO7kKUNPLbPZ+ZE0Cn5u8O8r4w3GhGdwi7kZ9no9ulVYe8rZH8jUtcW65l+Yu4qY+O lsGP+7gbzLAmy+9pHxtrc9VtPwbC78dQf5mjqqIzXNmi/8WEq7byQEZeeDEl5DBWOGgs iovEAB9CRN3pQ/NLnRoYrjEz3QmbhgvSph8AE=
MIME-Version: 1.0
Received: by 10.151.26.11 with SMTP id d11mr10003380ybj.192.1285034311134; Mon, 20 Sep 2010 18:58:31 -0700 (PDT)
Received: by 10.151.9.16 with HTTP; Mon, 20 Sep 2010 18:58:31 -0700 (PDT)
Date: Mon, 20 Sep 2010 18:58:31 -0700
Message-ID: <AANLkTin3Z75TZ5Yn0juci4YVSc3k7AzA38bmpZnj0_NB@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: v4tov6transition@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [v4tov6transition] comments draft-tsou-v4v6tran-mobile-transition-guide
X-BeenThere: v4tov6transition@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <v4tov6transition.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v4tov6transition>
List-Post: <mailto:v4tov6transition@ietf.org>
List-Help: <mailto:v4tov6transition-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4tov6transition>, <mailto:v4tov6transition-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2010 01:58:09 -0000
Few comments on this draft 1. Gi-DS-lite is one of many paths for 3GPP IPv6, i do not think it is relevant to focus only on this path. I think it is more helpful to say it is one of many paths. Architecturally, Gi-DS-Lite is not very impactful in my mind. It is a relevant path. It is a dual-stack bearer with a tunnel to an AFTR / CGN. So, for me, it is just another variant of DS + NAT44. Sorry if my understanding of this is simplistic. 2. " Conversion of the private internal network to pure IPv6 operation should be an early objective, for at least two reasons. " I do not think this is a prudent recommendation. Various telco systems are very specialized and barely do IPv4, if at all. Many are legacy TDM only interfaces. Asking SigTran or Diameter or any of the other telco systems to go IPv6 is hard, and will not achieve a lot since they use so few addresses relative to the UE. In my mobile IPv6, we only have a use case / business case for transition the mobile UE to IPv6 and the systems that interact directly with that data bearer (top deck, mms, IMS ...). There is no business case for doing anything else with IPv6, especially internal systems. If you are just looking for experience with IPv6, setup test servers with IPv6, not critical telco infrastructure. 3. "As usual, because of the time it will take to transition all users, IPv4 access to the content and applications must continue to be provided, until the last Windows XP computer ceases to be tethered to a mobile device for Internet access." It really bores me to read about XP. The users today all have IPv4 addresses. They work. In my network, i have positioned the IPv6 offering as "new customers, new devices" ... and no Legacy. Growth comes from new subscribers, not the legacy people on XP. The good thing about 3GPP mobile networks is that every UE when attaching to the network today, it request IPv4 or IPv6. If the service, the customer, and the device are designed to be IPv6, then they can be IPv6 without any legacy requirements on IPv4. 4. 3GPP specifications for mobile devices have required dual stack support for at least a year (i.e., as of Release 8.) What does this mean? How does it get enforced? ... i don't think it means anything and will not be enforced .... 5. When the operator converts a given area to Gateway-Initiated DS-lite access, a number of public IPv4 addresses are freed because of the introduction of address sharing. I think most large mobile operators already do address sharing, so there is no gain here. Regards, Cameron
- [v4tov6transition] comments draft-tsou-v4v6tran-m… Cameron Byrne