[ARIN-consult] discounting registration fees for IPv6 assignments

[Jesse D. Geddis]

Robert,

	Oh I don't know. When I started doing this routers had 256m or less RAM
and you had to spend mad money for a 100mbps FDDI. Now they have 4-8gigs
and 100gbps interfaces. No one believed you'd ever need speed like that
just like everyone believed we had plenty of address space. The market
place has a way of sorting such things out but you have to start
somewhere. Aggregation and summarization do a good job.

	I don't think it would hurt anything to use a standard flat fee per block
size. I have a feeling it would lower costs significantly for the vast
majority of people and I think it would also server better to get IPv6 out
there. I also think it would force carriers to take efficiency in
addressing much more seriously than they do now. All of these are good
things There's no better time than now, with IPv6 in relative infancy to
start fostering such things with policy and fees.


-- 
Jesse D. Geddis

LA Broadband LLC
AS 16602




On 10/30/12 2:07 PM, "Robert E. Seastrom" <rs at seastrom.com> wrote:


"Jesse D. Geddis" <jesse at la-broadband.com> writes:

> I wonder if we can get to a point where every end user has their own
> block that can be ported like a phone number from carrier to
> carrier. I think we can get there. From a technology standpoint I
> don't see any reason why that isn't possible today.

Various schemes (my personal favorite being draft-odell-8+8 [*]) have
been proposed over the years for separation of locators (routing) and
identifiers (hosts).  Institutionalizing this separation would have
enabled the sort of address portability you suggest above.  None ever
went very far, unfortunately...  and that ship sailed a decade and a
half ago.

Absent this separation, as Bill pointed out, the default-free zone is
ever-growing and hopefully we stay on the right side of Moore's Law in
terms of our ability to hold, propagate and converge a full RIB.
Every bit of (significant, non-aggregated) routing information needs
to be carried in every corner of the network no matter how locally
irrelevant.

With the current routing technology, a (permanent, portable) prefex
per end user is not possible.  It does not scale.

-r

[*] No reading list for "the Internet that never was" would be
complete without citations to RFC 1955 and
http://ana-3.lcs.mit.edu/~jnc/nimrod/archdoc_v4.txt