[99898] in North American Network Operators' Group
Re: How Not to Multihome
daemon@ATHENA.MIT.EDU (Keegan.Holley@sungard.com)
Mon Oct 8 18:39:17 2007
In-Reply-To: <470AAAC1.6030607@psg.com>
To: Randy Bush <randy@psg.com>
Cc: nanog <nanog@merit.edu>, owner-nanog@merit.edu,
"Justin M. Streiner" <streiner@cluebyfour.org>
From: Keegan.Holley@sungard.com
Date: Mon, 8 Oct 2007 18:25:29 -0400
Errors-To: owner-nanog@merit.edu
This is a multipart message in MIME format.
--=_alternative 007B2F848525736E_=
Content-Type: text/plain; charset="US-ASCII"
I'm really interested to see what happens when we start filling those same
routers with ipv6 routes.
Randy Bush <randy@psg.com>
Sent by: owner-nanog@merit.edu
10/08/2007 06:10 PM
To
"Justin M. Streiner" <streiner@cluebyfour.org>
cc
nanog <nanog@merit.edu>
Subject
Re: How Not to Multihome
> It's not 'law' per se, but having the customer originate their own
> announcements is definitely the Right Way to go.
it is interesting, and worrysome, to consider this in light of likely
growth in the routing table (ref ipv4 free pool run out discussion) and
vendors' inability to handle large ribs and fibs on enterprise class
routers.
randy
--=_alternative 007B2F848525736E_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">I'm really interested to see what happens
when we start filling those same routers with ipv6 routes.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Randy Bush <randy@psg.com></b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-nanog@merit.edu</font>
<p><font size=1 face="sans-serif">10/08/2007 06:10 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">"Justin M. Streiner" <streiner@cluebyfour.org></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">nanog <nanog@merit.edu></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: How Not to Multihome</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2><br>
> It's not 'law' per se, but having the customer originate their own<br>
> announcements is definitely the Right Way to go.<br>
<br>
it is interesting, and worrysome, to consider this in light of likely<br>
growth in the routing table (ref ipv4 free pool run out discussion) and<br>
vendors' inability to handle large ribs and fibs on enterprise class<br>
routers.<br>
<br>
randy<br>
<br>
<br>
</font></tt>
<br>
--=_alternative 007B2F848525736E_=--
