From ahmed@tamkien.com Tue Feb 1 02:23:08 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D29123A68F3 for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 02:23:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.003 X-Spam-Level: X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001] 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 Q0NBz8-zmi8f for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 02:23:07 -0800 (PST) Received: from nm17-vm0.bullet.mail.ac4.yahoo.com (nm17-vm0.bullet.mail.ac4.yahoo.com [98.139.53.208]) by core3.amsl.com (Postfix) with SMTP id 961CE3A6BB4 for <3gv6@ietf.org>; Tue, 1 Feb 2011 02:23:07 -0800 (PST) Received: from [98.139.52.193] by nm17.bullet.mail.ac4.yahoo.com with NNFMP; 01 Feb 2011 10:26:21 -0000 Received: from [98.139.52.134] by tm6.bullet.mail.ac4.yahoo.com with NNFMP; 01 Feb 2011 10:26:21 -0000 Received: from [127.0.0.1] by omp1017.mail.ac4.yahoo.com with NNFMP; 01 Feb 2011 10:26:21 -0000 X-Yahoo-Newman-Id: 313666.38966.bm@omp1017.mail.ac4.yahoo.com Received: (qmail 29697 invoked from network); 1 Feb 2011 10:26:21 -0000 Received: from mTOSH (ahmed@92.62.116.85 with login) by smtp115.biz.mail.re2.yahoo.com with SMTP; 01 Feb 2011 02:26:20 -0800 PST X-Yahoo-SMTP: Lha92E6swBDQOvc4cp4YoQvOX.m.z3U- X-YMail-OSG: pKNUFscVM1nEcbBCvFh1Z_av1GuaUpwEh.q7QPCgBkDnOp6 owkbLYEsCC6FHp8YLTZYRcymwEtFq.57nc.2u1yPZtJ.U5xQeKZViFfBJ3hf hMWpu8jqs2vrxwOkLMpf7tFSFjKwqTqC_3YT3lIzbPkcF7vLphHxaDw4gHXp shg1YyU_m7iUJBdXm1LHwazifv6_gLzRjYC6vjhaZ6dDJqrX6W0ECiZYbxig V9vMP_oqlh5nUzhS_fx.mCMmuuBG4hDdnnq.8lL.PBpAibuAYSMXYrjm53Ge 0_0nG7EUfLezYMGVyOCvxKMe_ou5Yn9ACIyPdXv3xOIkx9lgsCgxIDr.FxHu jMS_bIPw5.D_WB2ORvbz41X8X9nt7j2gqPDiOVIZp4pbSx2_MINxhfQ-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> From: "Ahmed Abu-Abed" To: <3gv6@ietf.org> References: In-Reply-To: Date: Tue, 1 Feb 2011 12:26:16 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B8_01CBC20B.38AA8840" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 Subject: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Feb 2011 10:23:08 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_01B8_01CBC20B.38AA8840 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello everyone, IPv4 depletion at the top registry level just happened but this mail = list has been very quiet.=20 Is there any interest on this mail list for discussing implementing IPv6 = over existing 3G & upcoming LTE networks ?=20 -Ahmed ------=_NextPart_000_01B8_01CBC20B.38AA8840 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello everyone,
 
IPv4 depletion at the top registry = level just=20 happened but this mail list has been very quiet.
 
Is there any interest on this mail list for=20 discussing implementing IPv6 over existing 3G & = upcoming LTE=20 networks ?
 
-Ahmed

------=_NextPart_000_01B8_01CBC20B.38AA8840-- From denghui02@gmail.com Tue Feb 1 18:34:01 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC38F3A6BB9 for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 18:34:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.916 X-Spam-Level: X-Spam-Status: No, score=-102.916 tagged_above=-999 required=5 tests=[AWL=0.682, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] 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 HNUAV5exYCVw for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 18:34:00 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 9C9C13A6CB3 for <3gv6@ietf.org>; Tue, 1 Feb 2011 18:34:00 -0800 (PST) Received: by fxm9 with SMTP id 9so8203161fxm.31 for <3gv6@ietf.org>; Tue, 01 Feb 2011 18:37:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Ci6dk2JjH6DuTsOSTiYajVrEboZWY8WUZyikKU+O+6E=; b=kXzDepWMgsj+2QAqkz1cBQvy58fAaJguXgTrQFZgmXmzUdw6FQw5dykPUvOiPKjgwR Zob+LvMUGmu3zBqsVLP7ORuPVyjxbUr1T9cIQ75/LLLqW2qQis/vBw50k3N8DVBXwqtL QXYs19r/NsKkhFcZ4lx9vp3Vwf/4r6gvyJIH4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=btXxF+MUX6/gxvboaVg8Cx+yZ9f0o+esfvt3Qz/jBfABECUS0cit2AhIl7qBe1CloQ TWDW3Lpslfn6pCjJ1Grz88UUXWztrAs13ZEvRpMzn9Y34l646vBGoxwoap6bcB8+DtGG /HbVS1vmg5w0H5bLuC3RF4shHWj3G9rTRfoJ4= MIME-Version: 1.0 Received: by 10.223.72.197 with SMTP id n5mr8116828faj.8.1296614238284; Tue, 01 Feb 2011 18:37:18 -0800 (PST) Received: by 10.223.96.14 with HTTP; Tue, 1 Feb 2011 18:37:18 -0800 (PST) In-Reply-To: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> References: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> Date: Wed, 2 Feb 2011 10:37:18 +0800 Message-ID: From: Hui Deng To: Ahmed Abu-Abed Content-Type: multipart/alternative; boundary=20cf3054a4f9156b11049b438797 Cc: 3gv6@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 02:34:02 -0000 --20cf3054a4f9156b11049b438797 Content-Type: text/plain; charset=ISO-8859-1 please go ahead if any implemention needed and could benefit for mobile network. regards, -Hui 2011/2/1 Ahmed Abu-Abed > Hello everyone, > > IPv4 depletion at the top registry level just happened but this mail list > has been very quiet. > > Is there any interest on this mail list for discussing implementing IPv6 > over existing 3G & upcoming LTE networks ? > > -Ahmed > > > _______________________________________________ > 3gv6 mailing list > 3gv6@ietf.org > https://www.ietf.org/mailman/listinfo/3gv6 > > --20cf3054a4f9156b11049b438797 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
please go ahead if any implemention needed and could benefit for mobil= e network.
=A0
regards,
=A0
-Hui

2011/2/1 Ahmed Abu-Abed <ahmed@tamkien.com>
Hello everyone,
=A0
IPv4 depletion at=A0the top registry level=A0ju= st happened but this mail list has been very quiet.
=A0
Is there any interest on this mail list for dis= cussing=A0implementing IPv6 over=A0existing 3G & upcoming=A0LTE network= s=A0?
=A0
-Ahmed


______________= _________________________________
3gv6 mailing list
3gv6@ietf.org
https://www.ietf.org/mailman/listinfo/3g= v6


--20cf3054a4f9156b11049b438797-- From scott.brim@gmail.com Tue Feb 1 18:58:08 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 151973A6CC2 for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 18:58:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.799 X-Spam-Level: X-Spam-Status: No, score=-101.799 tagged_above=-999 required=5 tests=[AWL=1.799, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] 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 pl4L6Mmt+Vjy for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 18:58:07 -0800 (PST) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id BA30B3A6BB6 for <3gv6@ietf.org>; Tue, 1 Feb 2011 18:58:06 -0800 (PST) Received: by eyd10 with SMTP id 10so3990393eyd.31 for <3gv6@ietf.org>; Tue, 01 Feb 2011 19:01:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ebSgWWnvsqI6QE8TcIuoW71r7mY26zKeTLtYoBtyIPo=; b=qmITk8K7utmcjue+eZsU2e6wA1qty0sKg0b3FAK1KMhZNHo4Yx+6AT6VtHSTbZ1XPR pPZWmPKBK+SJ4MgtFaUFc1ilTGXy6XrbLFkKbqbotnxW0eO0lo8WJvVakSAkIal2rl2N SHxBCzQX/BW0SdO07lA0l2cU/JOPNtHloX/Us= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bHjcQilJTxBOprVymIXn7EXdWR+Xuae1iDmiAdeXkqFGE3h7JPRZVlNdGH4SAUkssN +P1dfLcEn+T2/awoW4C6ob5wWHGTDl3gCvJEoViYSNOldQZ8iMNXe7zthJQ4sFsBYSl+ nWCJuc20r393OKQMcCgVRhk2Hcsbq6c/8X3y8= MIME-Version: 1.0 Received: by 10.213.29.210 with SMTP id r18mr2381021ebc.62.1296615683577; Tue, 01 Feb 2011 19:01:23 -0800 (PST) Received: by 10.213.30.15 with HTTP; Tue, 1 Feb 2011 19:01:23 -0800 (PST) Received: by 10.213.30.15 with HTTP; Tue, 1 Feb 2011 19:01:23 -0800 (PST) In-Reply-To: References: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> Date: Tue, 1 Feb 2011 22:01:23 -0500 Message-ID: From: Scott W Brim To: Hui Deng Content-Type: multipart/alternative; boundary=000e0cd1d2d83ad6a1049b43dd64 Cc: 3gv6@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 02:58:08 -0000 --000e0cd1d2d83ad6a1049b43dd64 Content-Type: text/plain; charset=ISO-8859-1 In case you hadn't heard, the GSMS has produced the first of two white papers on v4/v6 transition and coexistence, focusing mainly but not exclusively on interoperability. This first paper is for end-to-end user plane traffic. It is now in the hands of their "interworking and roaming experts" group, who will flesh out the details, produce the equivalent of a handbook, etc. The second paper will be on the transport plane and local breakout. They will be working on that one through the Spring. I am concerned about duplication of effort and confusion of results. Could you possibly work within GSMA? They are the worldwide body that coordinates operational issues for almost all mobile operators. If independent groups produce conflicting recommendations, they are the ones who will have to resolve the conflicts in any case. The next face-to-face meeting is in Shanghai, the same week as the IETF. Scott [Sent from my mobile.] On Feb 1, 2011 9:37 PM, "Hui Deng" wrote: > please go ahead if any implemention needed and could benefit for mobile > network. > > regards, > > -Hui > > 2011/2/1 Ahmed Abu-Abed > >> Hello everyone, >> >> IPv4 depletion at the top registry level just happened but this mail list >> has been very quiet. >> >> Is there any interest on this mail list for discussing implementing IPv6 >> over existing 3G & upcoming LTE networks ? >> >> -Ahmed >> >> >> _______________________________________________ >> 3gv6 mailing list >> 3gv6@ietf.org >> https://www.ietf.org/mailman/listinfo/3gv6 >> >> --000e0cd1d2d83ad6a1049b43dd64 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

In case you hadn't heard, the GSMS has produced the first of two whi= te papers on v4/v6 transition and coexistence, focusing mainly but not excl= usively on interoperability.=A0 This first paper is for end-to-end user pla= ne traffic.=A0 It is now in the hands of their "interworking and roami= ng experts" group, who will flesh out the details, produce the equival= ent of a handbook, etc.=A0 The second paper will be on the transport plane = and local breakout. They will be working on that one through the Spring.

I am concerned about duplication of effort and confusion of results.=A0 = Could you possibly work within GSMA?=A0 They are the worldwide body that co= ordinates operational issues for almost all mobile operators.=A0 If indepen= dent groups produce conflicting recommendations, they are the ones who will= have to resolve the conflicts in any case.

The next face-to-face meeting is in Shanghai, the same week as the IETF.=

Scott

[Sent from my mobile.]

On Feb 1, 2011 9:37 PM, "Hui Deng" <= ;denghui02@gmail.com> wrote:<= br type=3D"attribution">> please go ahead if any implemention needed and= could benefit for mobile
> network.
>
> regards,
>
> -Hui
>
&= gt; 2011/2/1 Ahmed Abu-Abed <ahmed@= tamkien.com>
>
>> Hello everyone,
>>
>> IPv4 depletion at the top registry level just happened but this ma= il list
>> has been very quiet.
>>
>> Is there a= ny interest on this mail list for discussing implementing IPv6
>> = over existing 3G & upcoming LTE networks ?
>>
>> -Ahmed
>>
>>
>> ___________= ____________________________________
>> 3gv6 mailing list
>&= gt; 3gv6@ietf.org
>> https://www.ietf.org/mailma= n/listinfo/3gv6
>>
>>
--000e0cd1d2d83ad6a1049b43dd64-- From cb.list6@gmail.com Tue Feb 1 19:07:10 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66D263A6CAA for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 19:07:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.276 X-Spam-Level: X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] 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 5faU4cbfvVNf for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 19:07:09 -0800 (PST) Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 753383A6BB9 for <3gv6@ietf.org>; Tue, 1 Feb 2011 19:07:09 -0800 (PST) Received: by qwi2 with SMTP id 2so7894625qwi.31 for <3gv6@ietf.org>; Tue, 01 Feb 2011 19:10:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=YePWEEFbkBH4ZDNwU+X2ALD6JZpH3/wetJHlX7kEbAo=; b=Aw2qFITRBzqTfIodw7QEAtZTifPBd5xkxJ8QoxUknDGep/lOF7xZhM9hKycvAu9nNC ciseZSz//hEtzGD+wTI3cwE7oGqdTSePGgRSLDEIkpDmD39n4N5n6zXh9t+hxn1wAnLa 9gYoc5fPTFiTJUm3XfwejPogl+VVhHNEhLF50= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TNnSBOVgKm6AAhX6ueeWunvEZgHFubBZdQ/xT6uQjS51tYSe4xaglRzToJThyVVOrF AImmww+yrKKtTsvcZnYY/kTlFyJ2JfTN4oaRf2yO7/6Rv+6NQC/gtxjYzxmqWpFrivO3 6iae/HVqA62fpftvjEGEO/J/MsXFug/7VPJ8c= MIME-Version: 1.0 Received: by 10.229.87.149 with SMTP id w21mr5886078qcl.68.1296616227392; Tue, 01 Feb 2011 19:10:27 -0800 (PST) Received: by 10.229.224.79 with HTTP; Tue, 1 Feb 2011 19:10:27 -0800 (PST) In-Reply-To: References: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> Date: Tue, 1 Feb 2011 19:10:27 -0800 Message-ID: From: Cameron Byrne To: Scott W Brim Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: 3gv6@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 03:07:10 -0000 On Tue, Feb 1, 2011 at 7:01 PM, Scott W Brim wrote: > In case you hadn't heard, the GSMS has produced the first of two white > papers on v4/v6 transition and coexistence, focusing mainly but not > exclusively on interoperability.=A0 This first paper is for end-to-end us= er > plane traffic.=A0 It is now in the hands of their "interworking and roami= ng > experts" group, who will flesh out the details, produce the equivalent of= a > handbook, etc.=A0 The second paper will be on the transport plane and loc= al > breakout. They will be working on that one through the Spring. > > I am concerned about duplication of effort and confusion of results.=A0 C= ould > you possibly work within GSMA?=A0 They are the worldwide body that coordi= nates > operational issues for almost all mobile operators.=A0 If independent gro= ups > produce conflicting recommendations, they are the ones who will have to > resolve the conflicts in any case. I agree that they are the right party to do this standards work. But, the issue is, I am rolling out IPv6 now, as are many other mobile operators. >From the original poster "Is there any interest on this mail list for discussing implementing IPv6 over existing 3G & upcoming LTE networks ?" There was no mention of standards work or confusion of roles within the industry. I believe the answer is yes, there is interest on this topic. I am unaware of the GSMAs ability to deliver. Cameron From scott.brim@gmail.com Tue Feb 1 19:14:39 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BA1B3A7132 for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 19:14:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.698 X-Spam-Level: X-Spam-Status: No, score=-102.698 tagged_above=-999 required=5 tests=[AWL=0.900, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] 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 w21nxaqE1ikT for <3gv6@core3.amsl.com>; Tue, 1 Feb 2011 19:14:38 -0800 (PST) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 97E1F3A712F for <3gv6@ietf.org>; Tue, 1 Feb 2011 19:14:38 -0800 (PST) Received: by eyd10 with SMTP id 10so3993866eyd.31 for <3gv6@ietf.org>; Tue, 01 Feb 2011 19:17:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=/FhusTHA3wa59G6qkCCnugFtsyQCK86nJLso2FB3mTM=; b=PzfvonmJSppB3Dz683KGbD6bxUJAD/V9H20iEIwLPdp1zTa46xIG30mizAvFP5FPjf O14kOxwnMSpIEhnMLlTIm6NAusuBL3Opro0Ev/lahzhx1zGxhcR5Lo5MckMBeax0BZGF LI8AI8MCclw0mPqsFavq3Af55CfA9rwQZgsIM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=xcgB+UYu8F9aXPW+kKjzU3Z963JL+umm3AV32dVTzIB1jeao8Wt3bNGEDXEtLZpjef vuGtHGRl4htQkahZ4luCQHSJrniUs+k1CBhWslH4SRJO2gUSN2Z67yz2Fqbe8EebVRop OPBpJBqPtMIW76OIgG57ddznC0+uEY1LFmA50= MIME-Version: 1.0 Received: by 10.213.15.135 with SMTP id k7mr9413348eba.26.1296616676570; Tue, 01 Feb 2011 19:17:56 -0800 (PST) Received: by 10.213.30.15 with HTTP; Tue, 1 Feb 2011 19:17:56 -0800 (PST) Received: by 10.213.30.15 with HTTP; Tue, 1 Feb 2011 19:17:56 -0800 (PST) Date: Tue, 1 Feb 2011 22:17:56 -0500 Message-ID: From: Scott W Brim To: Cameron Byrne Content-Type: multipart/alternative; boundary=0015174bde366ab656049b4418ab Cc: 3gv6@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 03:14:39 -0000 --0015174bde366ab656049b4418ab Content-Type: text/plain; charset=ISO-8859-1 Cameron, you know more than perhaps any other operator about v6 and transition. You're a contributor more than a consumer. No matter where it's produced you'll be writing some of it. [Sent from my mobile.] On Feb 1, 2011 10:10 PM, "Cameron Byrne" wrote: --0015174bde366ab656049b4418ab Content-Type: text/html; charset=ISO-8859-1

Cameron, you know more than perhaps any other operator about v6 and transition. You're a contributor more than a consumer. No matter where it's produced you'll be writing some of it.

[Sent from my mobile.]

On Feb 1, 2011 10:10 PM, "Cameron Byrne" <cb.list6@gmail.com> wrote:
--0015174bde366ab656049b4418ab-- From ahmed@tamkien.com Wed Feb 2 01:32:34 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F4A33A7129 for <3gv6@core3.amsl.com>; Wed, 2 Feb 2011 01:32:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.297 X-Spam-Level: X-Spam-Status: No, score=-1.297 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001] 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 zwXYcaAc4nug for <3gv6@core3.amsl.com>; Wed, 2 Feb 2011 01:32:32 -0800 (PST) Received: from nm4.bullet.mail.ac4.yahoo.com (nm4.bullet.mail.ac4.yahoo.com [98.139.52.201]) by core3.amsl.com (Postfix) with SMTP id 89F443A7142 for <3gv6@ietf.org>; Wed, 2 Feb 2011 01:32:30 -0800 (PST) Received: from [98.139.52.195] by nm4.bullet.mail.ac4.yahoo.com with NNFMP; 02 Feb 2011 09:35:46 -0000 Received: from [98.139.52.131] by tm8.bullet.mail.ac4.yahoo.com with NNFMP; 02 Feb 2011 09:35:46 -0000 Received: from [127.0.0.1] by omp1014.mail.ac4.yahoo.com with NNFMP; 02 Feb 2011 09:35:46 -0000 X-Yahoo-Newman-Id: 506553.31640.bm@omp1014.mail.ac4.yahoo.com Received: (qmail 49124 invoked from network); 2 Feb 2011 09:35:46 -0000 Received: from mTOSH (ahmed@92.62.116.85 with login) by smtp115.biz.mail.re2.yahoo.com with SMTP; 02 Feb 2011 01:35:45 -0800 PST X-Yahoo-SMTP: Lha92E6swBDQOvc4cp4YoQvOX.m.z3U- X-YMail-OSG: U5Zn0QkVM1knP4AhOJQFGxs5rln7ISjXLSClrVbA.TT9ljF 6jh3NoALHGxXFm0t0HyxWvalv8MNUXJyDWWpVSs3dRBQv5uH3HPJ4rw2YxaV PM73LN.f_9m48ojB0qD3pOFhdyQQ8XWKmSdBp0VHH.fXB87SMwUg5l66NBz8 6c_5c0jbnrR4uJw08yghyHMBDBCrPStlFprWHHkwPHPdS0Ul8LxNUT7uomoE aGP_ZCS4NIFiEwhxGL2iyr3l8ggjx6CUCF36OyShpq75ib6oYSLKGl1f6OO_ ZLaUdq3gCowpCCwiLRCl0keQk9ECncTKJ9Bk- X-Yahoo-Newman-Property: ymail-3 Message-ID: From: "Ahmed Abu-Abed" To: "Scott W Brim" References: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> In-Reply-To: Date: Wed, 2 Feb 2011 11:35:39 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0467_01CBC2CD.512E1590" X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726 Cc: 3gv6@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 09:32:34 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0467_01CBC2CD.512E1590 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Please provide a link to the papers, it will be good to know what is the = planned transition architecture. Keep in mind many RIRs will likely run out of 'big' blocks of IPv4 = within 6 to 9 months, around October 2011. After that one, and only one, = assignment of 1024 addresses (ie /22 of IPv4) will be made to each = operator from the RIR's last /8, which is hardly enough to sustain = growth if you have a large subscriber base. I think RIPE and APNIC are = following this policy. Practically, the implications are more nested NATing, which may break a = few things, or getting out of public IPv4 completely and assigning only = public IPv6 addresses to subscribers via NAT64/DNS64, or some form of = DS-Lite v4-in-v6 tunneling. Will any of these schemes be ready for field = implementation operators by Q3 2011 ? -Ahmed From: Scott W Brim=20 Sent: Wednesday, February 02, 2011 5:01 AM To: Hui Deng=20 Cc: Ahmed Abu-Abed ; 3gv6@ietf.org=20 Subject: Re: [3gv6] IPv4 depletion just happened In case you hadn't heard, the GSMS has produced the first of two white = papers on v4/v6 transition and coexistence, focusing mainly but not = exclusively on interoperability. This first paper is for end-to-end = user plane traffic. It is now in the hands of their "interworking and = roaming experts" group, who will flesh out the details, produce the = equivalent of a handbook, etc. The second paper will be on the = transport plane and local breakout. They will be working on that one = through the Spring. I am concerned about duplication of effort and confusion of results. = Could you possibly work within GSMA? They are the worldwide body that = coordinates operational issues for almost all mobile operators. If = independent groups produce conflicting recommendations, they are the = ones who will have to resolve the conflicts in any case. The next face-to-face meeting is in Shanghai, the same week as the IETF. Scott [Sent from my mobile.] On Feb 1, 2011 9:37 PM, "Hui Deng" wrote: > please go ahead if any implemention needed and could benefit for = mobile > network. >=20 > regards, >=20 > -Hui >=20 > 2011/2/1 Ahmed Abu-Abed >=20 >> Hello everyone, >> >> IPv4 depletion at the top registry level just happened but this mail = list >> has been very quiet. >> >> Is there any interest on this mail list for discussing implementing = IPv6 >> over existing 3G & upcoming LTE networks ? >> >> -Ahmed >> >> >> _______________________________________________ >> 3gv6 mailing list >> 3gv6@ietf.org >> https://www.ietf.org/mailman/listinfo/3gv6 >> >> ------=_NextPart_000_0467_01CBC2CD.512E1590 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Please provide a link to the papers, it will = be good to=20 know what is the planned transition architecture.
 
Keep in mind many RIRs will likely run = out of 'big'=20 blocks of IPv4 within 6 to 9 months, around October 2011. After that = one, and=20 only one, assignment of 1024 addresses (ie /22 of IPv4) will be made to = each=20 operator from the RIR's last /8, which is hardly enough to sustain = growth if you=20 have a large subscriber base. I think RIPE and APNIC are following this=20 policy.
 
Practically, the implications are more nested = NATing,=20 which may break a few things, or getting out of public IPv4 completely = and=20 assigning only public IPv6 addresses to subscribers via NAT64/DNS64, or = some=20 form of DS-Lite v4-in-v6 tunneling. Will any = of these schemes be=20 ready for field implementation operators by Q3 2011 = ?
 
-Ahmed
 

Sent: Wednesday, February 02, 2011 5:01 AM
Subject: Re: [3gv6] IPv4 depletion just = happened

In case you hadn't heard, the GSMS has produced the first of two = white papers=20 on v4/v6 transition and coexistence, focusing mainly but not exclusively = on=20 interoperability.  This first paper is for end-to-end user plane=20 traffic.  It is now in the hands of their "interworking and roaming = experts" group, who will flesh out the details, produce the equivalent = of a=20 handbook, etc.  The second paper will be on the transport plane and = local=20 breakout. They will be working on that one through the Spring.

I am concerned about duplication of effort and confusion of = results. =20 Could you possibly work within GSMA?  They are the worldwide body = that=20 coordinates operational issues for almost all mobile operators.  If = independent groups produce conflicting recommendations, they are the = ones who=20 will have to resolve the conflicts in any case.

The next face-to-face meeting is in Shanghai, the same week as the = IETF.

Scott

[Sent from my mobile.]

On Feb 1, 2011 9:37 PM, "Hui Deng" <denghui02@gmail.com> = wrote:> please go ahead if any implemention needed and = could=20 benefit for mobile
> network.
>
> regards,
> =
>=20 -Hui
>
> 2011/2/1 Ahmed Abu-Abed <ahmed@tamkien.com>
> =
>>=20 Hello everyone,
>>
>> IPv4 depletion at the top = registry level=20 just happened but this mail list
>> has been very=20 quiet.
>>
>> Is there any interest on this mail list = for=20 discussing implementing IPv6
>> over existing 3G & upcoming = LTE=20 networks ?
>>
>> = -Ahmed
>>
>>
>>=20 _______________________________________________
>> 3gv6 mailing = list
>> 3gv6@ietf.org
>> https://www.ietf.org/= mailman/listinfo/3gv6
>>
>>
= ------=_NextPart_000_0467_01CBC2CD.512E1590-- From Roman.Arcea@orange.md Wed Feb 2 01:44:22 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BE7D3A7129; Wed, 2 Feb 2011 01:44:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.908 X-Spam-Level: X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[AWL=0.690, BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 FGFk19YSC+Fl; Wed, 2 Feb 2011 01:44:19 -0800 (PST) Received: from mailfilter.orange.md (mailfilter.orange.md [94.243.64.204]) by core3.amsl.com (Postfix) with ESMTP id 6FA403A682E; Wed, 2 Feb 2011 01:44:18 -0800 (PST) Received: from mailfilter.orange.md (antispam.orange.md [127.0.0.1]) by localhost (Postfix) with SMTP id C4D8FB48003; Wed, 2 Feb 2011 11:47:36 +0200 (EET) Received: from postman.orange.md (unknown [172.16.1.6]) by mailfilter.orange.md (Postfix) with ESMTP id A1081B48002; Wed, 2 Feb 2011 11:47:36 +0200 (EET) In-Reply-To: References: <6803CEEF855F44AA99632847B5E1D4B0@mTOSH> To: "Ahmed Abu-Abed" MIME-Version: 1.0 X-KeepSent: 16766D7E:DE0203DB-C225782B:0035528B; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009 Message-ID: From: Roman.Arcea@orange.md Date: Wed, 2 Feb 2011 11:47:40 +0200 X-MIMETrack: Serialize by Router on postman/OrangeMD(Release 8.5.2 HF194|November 09, 2010) at 02/02/2011 11:47:36, Serialize complete at 02/02/2011 11:47:36 Content-Type: multipart/alternative; boundary="=_alternative 0035CC4DC225782B_=" Cc: 3gv6@ietf.org, 3gv6-bounces@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 09:44:22 -0000 This is a multipart message in MIME format. --=_alternative 0035CC4DC225782B_= Content-Type: text/plain; charset="US-ASCII" From: "Ahmed Abu-Abed" To: "Scott W Brim" Cc: 3gv6@ietf.org Date: 02-02-11 11:36 Subject: Re: [3gv6] IPv4 depletion just happened Sent by: 3gv6-bounces@ietf.org Please provide a link to the papers, it will be good to know what is the planned transition architecture. Keep in mind many RIRs will likely run out of 'big' blocks of IPv4 within 6 to 9 months, around October 2011. After that one, and only one, assignment of 1024 addresses (ie /22 of IPv4) will be made to each operator from the RIR's last /8, which is hardly enough to sustain growth if you have a large subscriber base. I think RIPE and APNIC are following this policy. ///yes, we are well aware... Practically, the implications are more nested NATing, which may break a few things, or getting out of public IPv4 completely and assigning only public IPv6 addresses to subscribers via NAT64/DNS64, or some form of DS-Lite v4-in-v6 tunneling. Will any of these schemes be ready for field implementation operators by Q3 2011 ? ///some of the above has been already implemented in the field in more than 1 mobile operators network. The most painful thing today is the readiness of customer equipment. It is mostly not available (besides the 1 well know vendor). When this one is in place, the service can be provided fairly quick using some of the solutions you have mentioned. Though, obviously some compromises will have to be made. There are also some areas in the mobile deployments that are very shallow today, such as IPv6 in the roaming scenarios. Roman From: Scott W Brim Sent: Wednesday, February 02, 2011 5:01 AM To: Hui Deng Cc: Ahmed Abu-Abed ; 3gv6@ietf.org Subject: Re: [3gv6] IPv4 depletion just happened In case you hadn't heard, the GSMS has produced the first of two white papers on v4/v6 transition and coexistence, focusing mainly but not exclusively on interoperability. This first paper is for end-to-end user plane traffic. It is now in the hands of their "interworking and roaming experts" group, who will flesh out the details, produce the equivalent of a handbook, etc. The second paper will be on the transport plane and local breakout. They will be working on that one through the Spring. I am concerned about duplication of effort and confusion of results. Could you possibly work within GSMA? They are the worldwide body that coordinates operational issues for almost all mobile operators. If independent groups produce conflicting recommendations, they are the ones who will have to resolve the conflicts in any case. The next face-to-face meeting is in Shanghai, the same week as the IETF. Scott [Sent from my mobile.] On Feb 1, 2011 9:37 PM, "Hui Deng" wrote: > please go ahead if any implemention needed and could benefit for mobile > network. > > regards, > > -Hui > > 2011/2/1 Ahmed Abu-Abed > >> Hello everyone, >> >> IPv4 depletion at the top registry level just happened but this mail list >> has been very quiet. >> >> Is there any interest on this mail list for discussing implementing IPv6 >> over existing 3G & upcoming LTE networks ? >> >> -Ahmed >> >> >> _______________________________________________ >> 3gv6 mailing list >> 3gv6@ietf.org >> https://www.ietf.org/mailman/listinfo/3gv6 >> >> _______________________________________________ 3gv6 mailing list 3gv6@ietf.org https://www.ietf.org/mailman/listinfo/3gv6 --=_alternative 0035CC4DC225782B_= Content-Type: text/html; charset="US-ASCII"




From:        "Ahmed Abu-Abed" <ahmed@tamkien.com>
To:        "Scott W Brim" <scott.brim@gmail.com>
Cc:        3gv6@ietf.org
Date:        02-02-11 11:36
Subject:        Re: [3gv6] IPv4 depletion just happened
Sent by:        3gv6-bounces@ietf.org



Please provide a link to the papers, it will be good to  know what is the planned transition architecture.
 
Keep in mind many RIRs will likely run out of 'big'  blocks of IPv4 within 6 to 9 months, around October 2011. After that one, and  only one, assignment of 1024 addresses (ie /22 of IPv4) will be made to each  operator from the RIR's last /8, which is hardly enough to sustain growth if you  have a large subscriber base. I think RIPE and APNIC are following this  policy.

///yes, we are well aware...
 
Practically, the implications are more nested NATing,  which may break a few things, or getting out of public IPv4 completely and  assigning only public IPv6 addresses to subscribers via NAT64/DNS64, or some  form of DS-Lite v4-in-v6 tunneling. Will any of these schemes be  ready for field implementation operators by Q3 2011 ?

///some of the above has been already implemented in the field in more than 1 mobile operators network. The most painful thing today is the readiness of customer equipment. It is mostly not available (besides the 1 well know vendor). When this one is in place, the service can be provided fairly quick using some of the solutions you have mentioned. Though, obviously some compromises will have to be made. There are also some areas in the mobile deployments that are very shallow today, such as IPv6 in the roaming scenarios.

Roman
 

From: Scott W Brim
Sent: Wednesday, February 02, 2011 5:01 AM
To: Hui Deng
Cc: Ahmed  Abu-Abed ; 3gv6@ietf.org
Subject: Re: [3gv6] IPv4 depletion just happened

In case you hadn't heard, the GSMS has produced the first of two white papers  on v4/v6 transition and coexistence, focusing mainly but not exclusively on  interoperability.  This first paper is for end-to-end user plane  traffic.  It is now in the hands of their "interworking and roaming  experts" group, who will flesh out the details, produce the equivalent of a  handbook, etc.  The second paper will be on the transport plane and local  breakout. They will be working on that one through the Spring.

I am concerned about duplication of effort and confusion of results.   Could you possibly work within GSMA?  They are the worldwide body that  coordinates operational issues for almost all mobile operators.  If  independent groups produce conflicting recommendations, they are the ones who  will have to resolve the conflicts in any case.

The next face-to-face meeting is in Shanghai, the same week as the IETF.

Scott

[Sent from my mobile.]
On Feb 1, 2011 9:37 PM, "Hui Deng" <denghui02@gmail.com> wrote:
> please go ahead if any implemention needed and could  benefit for mobile
> network.
>
> regards,
>
>  -Hui
>
> 2011/2/1 Ahmed Abu-Abed <ahmed@tamkien.com>
>
>>  Hello everyone,
>>
>> IPv4 depletion at the top registry level  just happened but this mail list
>> has been very  quiet.
>>
>> Is there any interest on this mail list for  discussing implementing IPv6
>> over existing 3G & upcoming LTE  networks ?
>>
>> -Ahmed
>>
>>
>>  _______________________________________________
>> 3gv6 mailing  list
>> 3gv6@ietf.org
>> https://www.ietf.org/mailman/listinfo/3gv6
>>
>>
_______________________________________________
3gv6 mailing list
3gv6@ietf.org
https://www.ietf.org/mailman/listinfo/3gv6

--=_alternative 0035CC4DC225782B_=-- From denghui02@gmail.com Wed Feb 2 04:04:12 2011 Return-Path: X-Original-To: 3gv6@core3.amsl.com Delivered-To: 3gv6@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8AD603A6C48 for <3gv6@core3.amsl.com>; Wed, 2 Feb 2011 04:04:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.932 X-Spam-Level: X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=0.666, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] 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 2jJ-zi0zdNeD for <3gv6@core3.amsl.com>; Wed, 2 Feb 2011 04:04:11 -0800 (PST) Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 593013A714E for <3gv6@ietf.org>; Wed, 2 Feb 2011 04:04:10 -0800 (PST) Received: by fxm9 with SMTP id 9so8646306fxm.31 for <3gv6@ietf.org>; Wed, 02 Feb 2011 04:07:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=AkPJptogP8Nry4mR+tLwWgD1quO+N1u5/lNTGLNX4co=; b=rrN34OOKVHdg2Lh9GFedyPNDddOytaO7xq60GR5bgV0Ei/kziQRHuzQePQ//Qr2PFo MX5zGmALhYo4qbeLxoixOSXm2mrKJJzhsJwYhrXKUOFdfrUgv1J6aQqws02XMQkwlsrk WPNLss4GTHML9t+fmQW+c+yG/vThAvmjQwkfg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SujJyyrdHaTdQkb4U2NIrFQ0BYGeV64O+rn3AEnSJjaJTX/IEBYlgazqgMwV3Z68Tu zgFh8yfLA0p6yLl6TnszEdg5ETKA5Egt2cyrag/0U7giwaqAR5eCA+q28iOqEgyv8MpQ Grfy7yu7gEckVxpqxxwSN8KrZyWhLNObdLevk= MIME-Version: 1.0 Received: by 10.223.114.14 with SMTP id c14mr8523394faq.103.1296648449221; Wed, 02 Feb 2011 04:07:29 -0800 (PST) Received: by 10.223.96.14 with HTTP; Wed, 2 Feb 2011 04:07:29 -0800 (PST) In-Reply-To: <001501cbc2ce$73ab2a80$5b017f80$@com> References: <001501cbc2ce$73ab2a80$5b017f80$@com> Date: Wed, 2 Feb 2011 20:07:29 +0800 Message-ID: From: Hui Deng To: 3gv6@ietf.org, Roman.Arcea@orange.md, Scott Brim Content-Type: multipart/alternative; boundary=001636c598db36e37d049b4b7e1a Subject: [3gv6] Fwd: FW: IPv4 depletion just happened X-BeenThere: 3gv6@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This mailing list is intended for discussions relating to the use of IPv6 in cellular networks." <3gv6.ietf.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2011 12:04:12 -0000 --001636c598db36e37d049b4b7e1a Content-Type: text/plain; charset=ISO-8859-1 Forward on behalf of Roman.Arcea@orange.md From: "Ahmed Abu-Abed" To: "Scott W Brim" Cc: 3gv6@ietf.org Date: 02-02-11 11:36 Subject: Re: [3gv6] IPv4 depletion just happened Sent by: 3gv6-bounces@ietf.org ------------------------------ Please provide a link to the papers, it will be good to know what is the planned transition architecture. Keep in mind many RIRs will likely run out of 'big' blocks of IPv4 within 6 to 9 months, around October 2011. After that one, and only one, assignment of 1024 addresses (ie /22 of IPv4) will be made to each operator from the RIR's last /8, which is hardly enough to sustain growth if you have a large subscriber base. I think RIPE and APNIC are following this policy. ///yes, we are well aware... Practically, the implications are more nested NATing, which may break a few things, or getting out of public IPv4 completely and assigning only public IPv6 addresses to subscribers via NAT64/DNS64, or some form of DS-Lite v4-in-v6 tunneling. Will any of these schemes be ready for field implementation operators by Q3 2011 ? ///some of the above has been already implemented in the field in more than 1 mobile operators network. The most painful thing today is the readiness of customer equipment. It is mostly not available (besides the 1 well know vendor). When this one is in place, the service can be provided fairly quick using some of the solutions you have mentioned. Though, obviously some compromises will have to be made. There are also some areas in the mobile deployments that are very shallow today, such as IPv6 in the roaming scenarios. Roman *From:* Scott W Brim *Sent:* Wednesday, February 02, 2011 5:01 AM *To:* Hui Deng *Cc:* Ahmed Abu-Abed ; 3gv6@ietf.org *Subject:* Re: [3gv6] IPv4 depletion just happened In case you hadn't heard, the GSMS has produced the first of two white papers on v4/v6 transition and coexistence, focusing mainly but not exclusively on interoperability. This first paper is for end-to-end user plane traffic. It is now in the hands of their "interworking and roaming experts" group, who will flesh out the details, produce the equivalent of a handbook, etc. The second paper will be on the transport plane and local breakout. They will be working on that one through the Spring. I am concerned about duplication of effort and confusion of results. Could you possibly work within GSMA? They are the worldwide body that coordinates operational issues for almost all mobile operators. If independent groups produce conflicting recommendations, they are the ones who will have to resolve the conflicts in any case. The next face-to-face meeting is in Shanghai, the same week as the IETF. Scott [Sent from my mobile.] On Feb 1, 2011 9:37 PM, "Hui Deng" wrote: > please go ahead if any implemention needed and could benefit for mobile > network. > > regards, > > -Hui > > 2011/2/1 Ahmed Abu-Abed > >> Hello everyone, >> >> IPv4 depletion at the top registry level just happened but this mail list >> has been very quiet. >> >> Is there any interest on this mail list for discussing implementing IPv6 >> over existing 3G & upcoming LTE networks ? >> >> -Ahmed >> >> >> _______________________________________________ >> 3gv6 mailing list >> 3gv6@ietf.org >> https://www.ietf.org/mailman/listinfo/3gv6 >> >> _______________________________________________ 3gv6 mailing list 3gv6@ietf.org https://www.ietf.org/mailman/listinfo/3gv6 --001636c598db36e37d049b4b7e1a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Forward on behalf of Roman.Arcea@orange.md=A0


<= /span>From:= =A0 =A0 =A0 =A0&quo= t;Ahmed Abu-Abed" <ahmed@tamkien.com>
To: = =A0 =A0 =A0 =A0"= ;Scott W Brim" <scott.brim@gmail.com>
Cc: = =A0 =A0 =A0 =A03gv6@ietf.org
Date= : =A0 =A0 =A0 =A002-= 02-11 11:36
Subject: = =A0 =A0 =A0 =A0Re: [= 3gv6] IPv4 depletion just happened
Sent= by: =A0 =A0 =A0 =A0= 3gv6-bounces@iet= f.org




Please provide= a link to the papers, it will be good to =A0know what is the planned trans= ition architecture. <= br> =A0
Keep in mind=A0many RIR= s will likely run out of 'big' =A0blocks of IPv4 within 6 to 9 mont= hs, around October 2011. After that one, and =A0only one, assignment of 102= 4 addresses (ie /22 of IPv4) will be made to each =A0operator from the RIR&= #39;s last /8, which is hardly enough to sustain growth if you =A0have a la= rge subscriber base. I think RIPE and APNIC are following this =A0policy.

///yes, we are well aware...
=A0 <= br>Practically, the implications are more neste= d NATing, =A0which may break a few things, or getting out of public IPv4 co= mpletely and =A0assigning only public IPv6 addresses to subscribers via NAT= 64/DNS64, or some =A0form of DS-Lite v4-in-v6 tunneling. Will=A0any of=A0th= ese=A0schemes be =A0ready for field=A0implementation=A0operators by Q3 2011= ?

///some of the above has been already i= mplemented in the field in more than 1 mobile operators network. The most p= ainful thing today is the readiness of customer equipment. It is mostly not= available (besides the 1 well know vendor). When this one is in place, the= service can be provided fairly quick using some of the solutions you have = mentioned. Though, obviously some compromises will have to be made. There a= re also some areas in the mobile deployments that are very shallow today, s= uch as IPv6 in the roaming scenarios.

Roman
=A0

From:
Scott W= Brim
Sent: Wednesday, February 02, 2011 5:01 AM
To: Hui Deng<= span lang=3D"EN-US">
Cc: Ahmed =A0Abu-Abed ; 3gv6@i= etf.org
Subject: Re: [3gv6] IPv4 depletion just happened

In case you hadn't heard, the GSMS has produced the first of two whit= e papers =A0on v4/v6 transition and coexistence, focusing mainly but not ex= clusively on =A0interoperability.=A0 This first paper is for end-to-end use= r plane =A0traffic.=A0 It is now in the hands of their "interworking a= nd roaming =A0experts" group, who will flesh out the details, produce = the equivalent of a =A0handbook, etc.=A0 The second paper will be on the tr= ansport plane and local =A0breakout. They will be working on that one throu= gh the Spring. <= br>
I am concerned about duplication of eff= ort and confusion of results.=A0 =A0Could you possibly work within GSMA?=A0= They are the worldwide body that =A0coordinates operational issues for alm= ost all mobile operators.=A0 If =A0independent groups produce conflicting r= ecommendations, they are the ones who =A0will have to resolve the conflicts= in any case.
The next face-to-face meeting is in Sha= nghai, the same week as the IETF.

Scott=

[Sent from my mobile.]
On Feb 1, 2011 9:37 PM, "Hui Deng" <denghui02@gmail.com<= /span>> wrote:
> please go ahead if any implemention ne= eded and could =A0benefit for mobile
> network.
>
> regards,
>
> =A0-Hui
>
> 2011/2/1 Ahmed Abu-Abed <ahmed@tamkien.com>
>
>> =A0Hello = everyone,
>>
>> IPv4 depletion at the top registry= level =A0just happened but this mail list
>> has= been very =A0quiet.
>>
>> Is th= ere any interest on this mail list for =A0discussing implementing IPv6
>> over existing 3G & upcoming LT= E =A0networks ? =
>>
>> -Ahmed
>>= ;
>>

>> =A0_______________________________= ________________=
>> 3gv6 mailing =A0list
>> 3gv6@ietf.org
>> https://www.ietf.org= /mailman/listinfo/3gv6
>>
>>

_______________________________________________<= span style=3D"FONT-FAMILY: 'Courier New'" lang=3D"EN-US">
3gv6 mailing list
3gv6@ietf.org
https://www.ietf.org/mai= lman/listinfo/3gv6


--001636c598db36e37d049b4b7e1a--