<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>Re: [AusNOG] [Fwd: [bogon-announce] IANA IPv4 allocations and bogon update 1/8 and 27/8]</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>I have never heard of anyone using 1.0.0.0/8
for inter-company peering: in every case I have seen, the business has requested
an allocation from the appropriate NIC and actioned peering sessions
accordingly, although the plural of anecdote is not data.
</FONT></P>
<P><FONT size=2>I think Blizzard will be the driving force behind the allocation
of 5.0.0.0/8 - if Hamachi is dead I imagine a number of people will be rushing
out to buy Warcraft 3/Starcraft who have been using "extended evaluations".
=)</FONT></P>
<P>-Curtis</P>
<P><FONT size=2></FONT> </P>
<P><FONT size=2>On Wed, 2010-01-20 at 11:24 +1100, Skeeve Stevens wrote:<BR>
> I've head some large US carriers are using it as well.<BR>
<BR>
>From what I heard one, 1.0.0.0/8 is a de facto standard for<BR>
transitioning routers between large companies in the context of joining<BR>
networks after a merger, or other forms of inter-company peering.<BR>
<BR>
'twas what I heard once, 's all.<BR>
<BR>
Probably comes from configuring 3 LANs with the entirety of their three<BR>
RFC1918 allocations, and then wondering why they don't have much address<BR>
space to work with. ;)<BR>
<BR>
Here's hoping 5.0.0.0/8 gets allocated to disrupt Hamachi users too.<BR></P></FONT>
</BODY>
</HTML>