[AusNOG] Small Pipe BNE/Agile issue

[James Spenceley]

In the past I've used de-aggregation to great effect to engineer more  
traffic in dense peer meshes. It works a treat where your transit  
provider has private peering with many of the your public peers (with  
the peers typically local-prefing private peering higher than public).

I don't see it as anti-social, it's not effecting anyone globally and  
is generally getting traffic on better / more direct paths. Where is  
the problem ?

As for de-aggregating past a /24, I've never seen a written rule that  
a /24 is ok to distribute and a /25 isn't, globally nothing works past  
a /24, that's generally accepted but peering is a bi-lateral  
relationship (even with an MLPA). If using /25 or greater has a  
required effect there is no reason not to use it but likewise no  
requirement to accept it.

--
James


On 14/06/2008, at 10:35 PM, David J. Hughes wrote:

>
> Hey MMC,
>
>> PIPE allow people to advertise longer than /24s.
>
> Ok, I wasn't aware of that as we don't accept them.  Call us fussy,
> but we also don't accept default from an IX :-).
>
> May I suggest to any PIPE or Equinix peering participants that expect
> WebCentral / MelbourneIT content to be delivered via the IX that they
> do not deaggregate past a /24 for TE purposes.  Guys, if the same
> prefix is visible via peering or transit you'd be on the mark if you
> expect us to use a peering connection wherever possible.  That's our
> decision and that's what local-pref is for.  Gross deaggregation by
> the origin AS is not a reliable solution and is anti-social behviour.
>
>
> Thanks
>
> David
> ...
> _______________________________________________
> AusNOG mailing list
> AusNOG at ausnog.net
> http://www.ausnog.net/mailman/listinfo/ausnog