[99053] in North American Network Operators' Group
RE: An informal survey... round II
daemon@ATHENA.MIT.EDU (tariq biziou)
Fri Aug 31 09:07:47 2007
Date: Fri, 31 Aug 2007 08:57:11 -0400
From: "tariq biziou" <tariq.biziou@gmail.com>
To: nanog@merit.edu
Cc: adrian@creative.net.au
Errors-To: owner-nanog@merit.edu
------=_Part_4739_23936747.1188565031219
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
> > > Why should we announce tiny recycled blocks? If there is a /16 in the
> > > swamp in which half the space is free but its all /24's, why wouldn't
> > > wouldn't we allocate all the free /24's to a single entity and
> > > instruct the entity to announce it as a "holey" /16? The existing /24
> > > holders will override (punch holes in) the /16 for their /24's.
> >
> > And when they withdraw the more specific or you glop them together in
> > your fib in the name of agregation a 3rd party gets all their traffic?
> > I'm sure that will work really well.
>
> Only the next hop. The game to play is "I want to dump traffic to a
> neighboring AS who has more a chance of getting it to its relevant
> destination." Partial routes (eg, filtering on say a /24 boundary
> with a default route) already sort of gives you that.
this idea has been flawed from the beginning:
1. prefix length indicates neither network capacity nor volume of traffic
2. most people prefer not to pay for traffic that is neither theirs nor a
customer's
--
--tariq
------=_Part_4739_23936747.1188565031219
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<span class="Apple-style-span" style="font-family: Times; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">> > > Why should we announce tiny recycled blocks? If there is a /16 in the
<br>> > > swamp in which half the space is free but its all /24's, why wouldn't<br>> > > wouldn't we allocate all the free /24's to a single entity and<br>> > > instruct the entity to announce it as a "holey" /16? The existing /24
<br>> > > holders will override (punch holes in) the /16 for their /24's.<br>> ><br>> > And when they withdraw the more specific or you glop them together in<br>> > your fib in the name of agregation a 3rd party gets all their traffic?
<br>> > I'm sure that will work really well.<br>> <br>> Only the next hop. The game to play is "I want to dump traffic to a<br>> neighboring AS who has more a chance of getting it to its relevant<br>
> destination." Partial routes (eg, filtering on say a /24 boundary<br>> with a default route) already sort of gives you that.</span><br clear="all"><br><div>this idea has been flawed from the beginning:</div><div>
<br><div>1. prefix length indicates neither network capacity nor volume of traffic</div><div><br class="webkit-block-placeholder"></div><div>2. most people prefer not to pay for traffic that is neither theirs nor a customer's
</div><div><br>-- <br>--tariq
</div></div>
------=_Part_4739_23936747.1188565031219--
