<br>
<br><font size=2><tt>ppml-bounces@arin.net wrote on 05/29/2007 09:58:36
AM:<br>
<br>
> <br>
> > - IPv6 space is not infinite. It's a 64-72 bit address
space. That's<br>
> > right, subnets with > 256 hosts are very uncommon today,
so we've wasted<br>
> > 64 bits to number 256 things. That makes the space
effectively on the<br>
> > long end 72 bits.<br>
> <br>
> according to <http://www.ipv6conference.com/conference.htm>,
i gave a talk<br>
> entitled "DHCPv6 - The Case Against Stateless Autoconfig"
at NAV6TF'2005.<br>
> <br>
> according to <http://www.isc.org/index.pl?/sw/dhcp/dhcp4_0.php>,
there's<br>
> now code in "alpha test release" status to handle DHCPv6.<br>
> <br>
> imho, the days of EUI64 are numbered. at home i'll probably
use a /120 for<br>
> each LAN. at work, we might splurge and use /96's. not
that a /56 isn't<br>
> enough for my house or anything, i just want the sparseful wastitude
of the<br>
> new address bits in IPV6 to all be at the top end. i'm using
a /124 for my<br>
> T1, mostly to make the PTR's easy to write and read.<br>
</tt></font>
<br><font size=2><tt>I agree that requireing the use of 64 bits for interface
identifiers is a</tt></font>
<br><font size=2><tt>monumental waste of address space. Is there a proposal
of any type to change</tt></font>
<br><font size=2><tt>the requirement to use EUI64 interface identifiers
with globally routable PI</tt></font>
<br><font size=2><tt>address space?</tt></font>
<br>
<br><font size=2><tt>> <br>
> > But more importantly, we have the T-Shirt from this exercise.<br>
> > Back in the 80's we gave out Class A's. It was the
right thing<br>
> > to do.<br>
> <br>
> was it? DEC got 16.0.0.0/8 on the basis of having 130000 employees
and<br>
> something like 10000 offices. they turned in five class B's
to get the A.<br>
> does anybody here think that DEC needed a class A by ARIN's current
<br>
> standards? this was a post-subnet, post-CIDR allocation.<br>
> <br>
> > I predict with the current allocation procedures IPv6
will be<br>
> > "used up" in my lifetime. I also predict
the groups today getting<br>
> > /32's (and larger) will look like the legacy class A holders
in<br>
> > 20 years time. When your doorknob automatically
requests a ULA-C<br>
> > /64 when you bring it home, and your house has 2,000 of
them as every<br>
> > individual system talks to each other we'll be looking
at this quite<br>
> > differently.<br>
> <br>
> i include this only so that i can say, i nearly agree. unless
we have an<br>
> IP architecture that splits EID/RID, those doorknobs will not be globally<br>
> reachable. (not that this is a problem for doorknobs but it
might be for<br>
> microwave ovens or something.)<br>
> _______________________________________________<br>
> This message sent to you through the ARIN Public Policy Mailing List<br>
> (PPML@arin.net).<br>
> Manage your mailing list subscription at:<br>
> http://lists.arin.net/mailman/listinfo/ppml<br>
</tt></font>