Re: [v6ops] A good "state of the art" overview of IPv6 Transition from FCC

"t.petch" <ietfc@btconnect.com> Tue, 04 January 2011 12:12 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BE723A6BAF for <v6ops@core3.amsl.com>; Tue, 4 Jan 2011 04:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 jzbrJSsFL3RZ for <v6ops@core3.amsl.com>; Tue, 4 Jan 2011 04:12:57 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by core3.amsl.com (Postfix) with ESMTP id 5333A3A6B7A for <v6ops@ietf.org>; Tue, 4 Jan 2011 04:12:56 -0800 (PST)
Received: from host86-172-77-68.range86-172.btcentralplus.com (HELO pc6) ([86.172.77.68]) by c2bthomr13.btconnect.com with SMTP id BEY22264; Tue, 04 Jan 2011 12:14:57 +0000 (GMT)
Message-ID: <008701cbac00$2f387e00$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, Tom Taylor <tom111.taylor@bell.net>
References: <C94805B3.6166%yiu_lee@cable.comcast.com>
Date: Tue, 04 Jan 2011 12:11:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4D230F41.0043, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4D230F44.0221, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] A good "state of the art" overview of IPv6 Transition from FCC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 04 Jan 2011 12:12:58 -0000

----- Original Message ----- 
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Tom Taylor" <tom111.taylor@bell.net>
Cc: "IPv6 Ops WG" <v6ops@ietf.org>
Sent: Tuesday, January 04, 2011 5:02 AM

> Well, when DHCPv6 is getting more popular, we may be able to work around
> this limitation. However, 18 trillion^2 addresses are still a lot^2.

True but not necessarily relevant.

When I first studied IPv6 all those years ago, I was also active in ATM and it
immediately struck me that IPv6 had not left enough room in the interface part
for an ATM address, so that an IPv6 address would always be too small.

Tom Petch


> On 1/3/11 10:56 PM, "Tom Taylor" <tom111.taylor@bell.net> wrote:
> 
> >But isn't it only 18 trillion trillion because everyone is getting at
> >least a /64?
> >
> >On 03/01/2011 10:35 PM, Lee, Yiu wrote:
> >>
> >>> We can only hope that 340 trillion trillion trillion is enough for a
> >>> while...
> >>>
> >>>
> >>> Amen!
> >>
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> >>
> >>
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops