North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: IPv6 daydreams

  • From: David Barak
  • Date: Mon Oct 17 07:44:48 2005
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=VVv6jZo0bZ2DA7Q01EcjrX7gt4aBEa4fxQgzi4iYr77sidur7NUxBHn3cA02UCxaS4YXBehoSkElFHO0IGA+Kw1y7G5zvocJmxQWfuoVjF1GJINeHQDr94LNx70c8WtMcfzKoZoubpa16XQ5jjxV7BuXoKKiybCEo+d6Oz8yGsA= ;

--- Mark Smith
<[email protected]>
wrote:

> Why have people, who are unhappy about /64s for
> IPv6, been happy enough
> to accept 48 bit addresses on their LANs for at
> least 15 years? Why
> aren't people complaining today about the overheads
> of 48 bit MAC
> addresses on their 1 or 10Gbps point-to-point links,
> when none of those
> bits are actually necessary to identify "the other
> end" ? Maybe because
> they have unconsciously got used to the convenience,
> and, if they've
> thought about it, realise that the byte
> overhead/cost of that
> convenience is not worth worrying about, because
> there are far higher
> costs elsewhere in the network (including
> administration of it) that
> could be reduced.

Wrong issue.  What I'm unhappy about is not the size
of the address - you'll notice that I didn't say "make
the whole address space smaller."  What I'm unhappy
about is the exceedingly sparse allocation policies
which mean that any enduser allocation represents a
ridiculously large number of possible hosts.  The only
possible advantage I could see from this is the
protection against random scanning finding a user -
but new and fun worms will use whatever mechanism the
hosts use to find each other: I guarantee that the
"find a printer" function won't rely on a sequential
probe of all of the possible host addresses in a /64
either...

Also, the 64-bit addressing scheme is sized to include
the MAC address, right?  Why would encoding L2 data
into L3 be a good thing?  The conceptual problem that
I have had with v6 from the beginning is that it's not
trying to optimize a single layer, it's really trying
to merge several layers into one protocol.  Ugh.

-David Barak-
-Fully RFC 1925 Compliant-

David Barak
Need Geek Rock?  Try The Franchise: 
http://www.listentothefranchise.com


		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/