RE: what problem is solved by proscribing non-64 bit prefixes?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: what problem is solved by proscribing non-64 bit prefixes?
- To: "Brian E Carpenter" <brian.e.carpenter at gmail.com>
- Subject: RE: what problem is solved by proscribing non-64 bit prefixes?
- From: "Dunn, Jeffrey H." <jdunn at mitre.org>
- Date: Wed, 1 Oct 2008 23:04:07 -0400
- Cc: Alexandru Petrescu <alexandru.petrescu at gmail.com>, ipv6 at ietf.org, Steve_Eiserman at ao.uscourts.gov, ralph.liguori at disa.mil, Pasi.Eronen at nokia.com, "Sherman, Kurt T." <ksherman at mitre.org>, draft-ietf-v6ops-addcon at tools.ietf.org, rbonica at juniper.net, night at nist.gov, dougm at nist.gov, v6ops-chairs at tools.ietf.org, "Martin, Cynthia E." <cemartin at mitre.org>
- Delivered-to: ietfarch-ipv6-web-archive at core3.amsl.com
- Delivered-to: ipv6 at core3.amsl.com
- In-reply-to: <48E3E0D1.7090006 at gmail.com>
- List-archive: <https://www.ietf.org/mailman/private/ipv6>
- List-help: <mailto:ipv6-request@ietf.org?subject=help>
- List-id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
- List-post: <mailto:ipv6@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
- References: <C0F2465B4F386241A58321C884AC7ECC085AB2AF at E03MVZ2-UKDY.domain1.systemhost.net> <48E37330.3060801 at gmail.com> <0AC4B700F00DBB4C94F95727E0991414014B24F5 at IMCSRV7.MITRE.ORG> <48E3E0D1.7090006 at gmail.com>
- Sender: ipv6-bounces at ietf.org
- Thread-index: AckkBk8m+25dh/KCTHa9GEji42yc1QAM8W7A
- Thread-topic: 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 at gmail.com]
Sent: Wednesday, October 01, 2008 4:43 PM
To: Dunn, Jeffrey H.
Cc: Alexandru Petrescu; michael.dillon at bt.com; Sherman, Kurt T.;
ipv6 at ietf.org; rbonica at juniper.net; Steve_Eiserman at ao.uscourts.gov;
Pasi.Eronen at nokia.com; draft-ietf-v6ops-addcon at tools.ietf.org;
ralph.liguori at disa.mil; night at nist.gov; dougm at nist.gov;
v6ops-chairs at 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 at ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.