[AusNOG] Why is peering in Australia so hard?

[Tom Paseka]

Wolfgang,

Australia isn't opposed to peering any more or less so than Europe.
Difference is many operators wont set up direct sessions over the fabric,
instead relying on peering with the Route Server(s) to exchange routes.

Cheers,
Tom

On Sat, Aug 3, 2013 at 7:24 AM, Wolfgang Nagele <
wolfgang.nagele at ausregistry.com.au> wrote:

>  Hi,
>
>  Coming from Europe I have to say that I am still surprised about the
> reluctance in Australia to peer with each other. Leaving the large players
> and their various (mainly) political motives aside, why the reluctance
> among the small providers here?
>
>  To put it into perspective, we've just recently rolled out a substantial
> global Anycast deployment and while we are struggling to get decent numbers
> of peers at various IXes here we've established many in both Europe and the
> US.
>
>  Anybody can shed some light on this issue for me?
>
>  And for those that actually just would like to peer - our details are
> here: http://as58620.peeringdb.com
>
>  Regards,
>
>   --
> Wolfgang Nagele
> IT Manager
> AusRegistry Pty Ltd
> Level 8, 10 Queens Road
> Melbourne, Victoria, Australia, 3004
> Phone +61 3 9866 3710
> Email: wolfgang.nagele at ausregistry.com.au
> Web: www.ausregistry.com.au
>
>
>  The information contained in this communication is intended for the
> named recipients only. It is subject to copyright and may contain legally
> privileged and confidential information and if you are not an intended
> recipient you must not use, copy, distribute or take any action in reliance
> on it. If you have received this communication in error, please delete all
> copies from your system and notify us immediately.
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20130803/a7bae5b9/attachment.html>