RE: what problem is solved by proscribing non-64 bit prefixes?
"TJ" <trejrco@gmail.com> Thu, 02 October 2008 12:25 UTC
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipngwg-archive@lists.ietf.org
Delivered-To: ietfarch-ipngwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C32A3A6970; Thu, 2 Oct 2008 05:25:23 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 633233A6970 for <ipv6@core3.amsl.com>; Thu, 2 Oct 2008 05:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.635
X-Spam-Level:
X-Spam-Status: No, score=-2.635 tagged_above=-999 required=5 tests=[AWL=-0.036, 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 G-Zwie4s+WXB for <ipv6@core3.amsl.com>; Thu, 2 Oct 2008 05:25:20 -0700 (PDT)
Received: from mail-gx0-f16.google.com (mail-gx0-f16.google.com [209.85.217.16]) by core3.amsl.com (Postfix) with ESMTP id 99A4F3A659B for <ipv6@ietf.org>; Thu, 2 Oct 2008 05:25:14 -0700 (PDT)
Received: by gxk9 with SMTP id 9so1259330gxk.13 for <ipv6@ietf.org>; Thu, 02 Oct 2008 05:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=gRbDiZB6vSVMzl46EFODsQBDtH4t6Bi5pUUgUMuVeMo=; b=NHm4RU2PXOG7u1nI+ZhFkV2vV7DRKzppTglsG64Alyg4TdemYxd7leZCb487h6oPZu I3pYa5ksOBaayNJZsWUaPJTj8J/Lv2eui6A5ickWnQ5lH3gufr40cXHBq/pjkKpuDXwX tcQlukNXVGZq+qynX0oZiEdFSa47YAvI6fG4Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :content-language; b=gC8O669c8jQtbknDANniafHxbnwH64DYJBQbSHm/0+sV4Fxm89f/kARa4ULpfY18Bh 7a2z/pLMRjzW0Ms/SNF2n5tgbsOrlotVbWNIVX1ViS39jlUfQOA7+z1Jt3Hnq84wXzeS xAlJ40ZKcedua/ljON76vjlFmgy6JojPmkhrE=
Received: by 10.151.102.21 with SMTP id e21mr14010317ybm.131.1222950264355; Thu, 02 Oct 2008 05:24:24 -0700 (PDT)
Received: from Lapci010 ([98.174.20.11]) by mx.google.com with ESMTPS id i27sm2677647elf.4.2008.10.02.05.24.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Oct 2008 05:24:23 -0700 (PDT)
From: TJ <trejrco@gmail.com>
To: ipv6@ietf.org
References: <C0F2465B4F386241A58321C884AC7ECC085AB2AF@E03MVZ2-UKDY.domain1.systemhost.net> <48E37330.3060801@gmail.com> <0AC4B700F00DBB4C94F95727E0991414014B24F5@IMCSRV7.MITRE.ORG> <48E3E0D1.7090006@gmail.com> <0AC4B700F00DBB4C94F95727E0991414014B250E@IMCSRV7.MITRE.ORG>
In-Reply-To: <0AC4B700F00DBB4C94F95727E0991414014B250E@IMCSRV7.MITRE.ORG>
Subject: RE: what problem is solved by proscribing non-64 bit prefixes?
Date: Thu, 02 Oct 2008 08:24:20 -0400
Message-ID: <000601c92489$cd923380$68b69a80$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AckkBk8m+25dh/KCTHa9GEji42yc1QAM8W7AABOiMYA=
Content-Language: en-us
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
Funny, "On the other hand I see enormous value in allowing any size of network on any customer's premises. It's not for this generation of engineers and ISPs to constrain what our great-grandchildren might invent" is something I see as an argument for sticking with /64s. You never know what may be developed that needs all those host bits (or, atleast - needs more than we expect ... think things like per-sessions IP addresses and such 'craziness' :) ) Thanks! /TJ >-----Original Message----- >From: ipv6-bounces@ietf.org [mailto:ipv6-bounces@ietf.org] On Behalf Of >Dunn, Jeffrey H. >Sent: Wednesday, October 01, 2008 11:04 PM >To: Brian E Carpenter >Cc: Alexandru Petrescu; ipv6@ietf.org; Steve_Eiserman@ao.uscourts.gov; >ralph.liguori@disa.mil; Pasi.Eronen@nokia.com; Sherman, Kurt T.; draft-ietf- >v6ops-addcon@tools.ietf.org; rbonica@juniper.net; night@nist.gov; >dougm@nist.gov; v6ops-chairs@tools.ietf.org; Martin, Cynthia E. >Subject: RE: what problem is solved by proscribing non-64 bit prefixes? > >Brian, > >Your point about raising the size of the address space to the fourth power >is not quite correct. If we constrain the network prefix to be 64-bits, >then, assuming that the longest routable IPv4 prefix is 24, we have only >raised the prefix size by the power 2.67. Now assume that we start handing >out /28 prefixes to ISPs for their residential customers (who are now all >behind a NAT), we have now only raised the number of subnets to the 1.17. My >argument is that it is not the number of unique end system addresses that is >the issue, rather the number of subnets. > >As to your observation concerning this generation's engineers, I whole >heartedly second your suggestion. > >Best Regards, > >Jeffrey Dunn >Info Systems Eng., Lead >MITRE Corporation. >(301) 448-6965 (mobile) > > >-----Original Message----- >From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] >Sent: Wednesday, October 01, 2008 4:43 PM >To: Dunn, Jeffrey H. >Cc: Alexandru Petrescu; michael.dillon@bt.com; Sherman, Kurt T.; >ipv6@ietf.org; rbonica@juniper.net; Steve_Eiserman@ao.uscourts.gov; >Pasi.Eronen@nokia.com; draft-ietf-v6ops-addcon@tools.ietf.org; >ralph.liguori@disa.mil; night@nist.gov; dougm@nist.gov; v6ops- >chairs@tools.ietf.org; Martin, Cynthia E. >Subject: Re: what problem is solved by proscribing non-64 bit prefixes? > >On 2008-10-02 02:04, Dunn, Jeffrey H. wrote: >> More to the point, what would a individual household do with >Avogadro's >> number worth of IPv6 addresses (2^80 = 1.2x10^24)? This seems >> extremely wasteful. Further, a reasonable sized ISP with a couple of >> million customers would require a /28 or more just for their >> residential customer base. This sounds like a prescription for >address >> exhaustion. > >Not in the least. Please remember that we have raised the size of the >address space to the *fourth* power; we squared it and squared it again. >Even if we'd stuck to the original plan of assigning /48s everywhere, that >means we've *squared* the size of the subnet prefix space (/24 to /48). >Unless really stupid allocation mechanisms are allowed, that is enough for >any imaginable future. And all the evidence is that the RIRs are being >extremely conservative in their practices for allocation. So I don't see >even a remote cause for concern. > >On the other hand I see enormous value in allowing any size of network on >any customer's premises. It's not for this generation of engineers and ISPs >to constrain what our great-grandchildren might invent. > > Brian >-------------------------------------------------------------------- >IETF IPv6 working group mailing list >ipv6@ietf.org >Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >-------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- v6ops-addcon and longer than 64 bit prefixes Jari Arkko
- RE: v6ops-addcon and longer than 64 bit prefixes Tony Hain
- Re: v6ops-addcon and longer than 64 bit prefixes Erik Kline
- Re: v6ops-addcon and longer than 64 bit prefixes Fred Baker
- RE: v6ops-addcon and longer than 64 bit prefixes Dunn, Jeffrey H.
- Re: v6ops-addcon and longer than 64 bit prefixes Turchanyi Geza
- Re: v6ops-addcon and longer than 64 bit prefixes Brian E Carpenter
- Re: v6ops-addcon and longer than 64 bit prefixes Geoff Huston
- RE: the IPv6 Ethernet lost bits - fffe TJ
- Re: v6ops-addcon and longer than 64 bit prefixes Fred Baker
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: v6ops-addcon and longer than 64 bit prefixes Azinger, Marla
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- RE: what problem is solved by proscribing non-64 … michael.dillon
- Re: the IPv6 Ethernet lost bits - fffe Jeroen Massar
- Re: what problem is solved by proscribing non-64 … Pekka Savola
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- Re: v6ops-addcon and longer than 64 bit prefixes Brian E Carpenter
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- RE: what problem is solved by proscribing non-64 … Manfredi, Albert E
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 … michael.dillon
- RE: what problem is solved by proscribing non-64 … michael.dillon
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Mohacsi Janos
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: the IPv6 Ethernet lost bits - fffe (was: what… Alexandru Petrescu
- Re: the IPv6 Ethernet lost bits - fffe Jeroen Massar
- RE: what problem is solved by proscribing non-64 … TJ
- Re: the IPv6 Ethernet lost bits - fffe Tim Chown
- RE: the IPv6 Ethernet lost bits - fffe TJ
- RE: what problem is solved by proscribing non-64 … Azinger, Marla
- RE: what problem is solved by proscribing non-64 … Azinger, Marla
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: Why would anyone want to use a 64 bit interfa… Alexandru Petrescu
- RE: Why would anyone want to use a 64 bit interfa… Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- RE: the IPv6 Ethernet lost bits - fffe Dunn, Jeffrey H.
- RE: Why would anyone want to use a 64 bit interfa… TJ
- Re: Why would anyone want to use a 64 bit interfa… Alexandru Petrescu
- RE: the IPv6 Ethernet lost bits - fffe TJ
- RE: Why would anyone want to use a 64 bit interfa… TJ
- Re: the IPv6 Ethernet lost bits - fffe Alexandru Petrescu
- Re: Why would anyone want to use a 64 bit interfa… Alexandru Petrescu
- RE: Why would anyone want to use a 64 bit interfa… TJ
- RE: the IPv6 Ethernet lost bits - fffe Chip Popoviciu (cpopovic)
- Re: what problem is solved by proscribing non-64 … Antonio Querubin
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- Re: what problem is solved by proscribing non-64 … Brian Dickson
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- RE: what problem is solved by proscribing non-64 … michael.dillon
- RE: what problem is solved by proscribing non-64 … Antonio Querubin
- Re: what problem is solved by proscribing non-64 … slblake
- Re: the IPv6 Ethernet lost bits - fffe Francis Dupont
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- Re: what problem is solved by proscribing non-64 … Christopher Morrow
- Re: Why would anyone want to use a 64 bit interfa… Mark Andrews
- Re: Why would anyone want to use a 64 bit interfa… Jeroen Massar
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … Pekka Savola
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … TJ
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … TJ
- Re: what problem is solved by proscribing non-64 … Brian E Carpenter
- RE: what problem is solved by proscribing non-64 … Dunn, Jeffrey H.
- RE: what problem is solved by proscribing non-64 … Pekka Savola
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: what problem is solved by proscribing non-64 … Alexandru Petrescu
- Re: IPv6 Firewire - fffe (was: what problem is so… Alexandru Petrescu
- Re: IPv6 Firewire - fffe Brian E Carpenter
- Re: what problem is solved by proscribing non-64 … Mark Smith
- Re: v6ops-addcon and longer than 64 bit prefixes Jari Arkko
- Re: what problem is solved by proscribing non-64 … Jari Arkko