<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">From some traces I ran a while ago, it
looked like Internode had a BGP adjacency with AS703 at one
point....<br>
<br>
On 12/11/12 16:17, Matthew Moyle-Croft wrote:<br>
</div>
<blockquote
cite="mid:7281EB4C-2ACF-486B-8E26-E43971F0DC24@mmc.com.au"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<br>
<div>
<div>On 11/11/2012, at 9:00 PM, Joshua D'Alton <<a
moz-do-not-send="true" href="mailto:joshua@railgun.com.au">joshua@railgun.com.au</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">AARNet is a special case though, just as
the various other research networks around the world get
peering. Level3 for example doesn't accept any new peering at
all, yet there have been 4 since 2000, all research networks.<br>
</blockquote>
<div><br>
</div>
<div>AARNet is not the only AU network outside the GoF with
AS703 peering.</div>
<div><br>
</div>
<div>MMC</div>
<div><br>
</div>
<blockquote type="cite">
<br>
<div class="gmail_quote">On Mon, Nov 12, 2012 at 3:55 PM, Mark
Prior <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mrp@mrp.net" target="_blank">mrp@mrp.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
AARNet met Verizon's requirements and got peering with
them. I believed we also met AAPT's until AAPT changed
their policy.<span class="HOEnZb"><font color="#888888"><br>
<br>
Mark.</font></span>
<div class="HOEnZb">
<div class="h5"><br>
<br>
On 12/11/12 3:18 PM, Chris Ricks wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
With that said (AS703s requirements being met by
AAPT, Optus and<br>
Telstra), is it likely that any other Australian
carrier would be likely<br>
to meet them as well?<br>
<br>
<br>
On 12/11/12 15:32, Matthew Moyle-Croft wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 11/11/2012, at 8:29 PM, Chris Ricks <<a
moz-do-not-send="true"
href="mailto:chris.ricks@securepay.com.au"
target="_blank">chris.ricks@securepay.com.au</a>>
wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
There's been on list discussion stating that if
the other 3 members of<br>
the GoF were evaluated using Verizon's published
policy, they wouldn't<br>
get to keep the current arrangement - do you
have an opinion on that<br>
either way?<br>
<br>
</blockquote>
I'd suggest that untrue. All would meet AS703s
requirements.<br>
<br>
MMC<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
On 12/11/12 15:13, Mark Prior wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
On 12/11/12 12:25 PM, Chris Ricks wrote:<br>
<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
Even if a merger of M2, iiNet and TPG
occurred, their traffic volume<br>
would not put them in a position to discuss
settlement-free or SKA<br>
peering with any of the GoF without
government intervention - that is<br>
the crux of the issue here.<br>
</blockquote>
I wouldn't put Verizon in the same box as the
other three. They have a<br>
written peering policy and if you satisfy the
policy via a test<br>
peering then you get to keep it.<br>
<br>
AAPT had a policy (I wrote the first version
:-) but it's a moving<br>
target, at least it was when I last tried to
use it to get peering.<br>
Telstra's peering policy is mission impossible
and Optus can't spell<br>
peering.<br>
<br>
Mark.<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net"
target="_blank">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net"
target="_blank">AusNOG@lists.ausnog.net</a><br>
<a moz-do-not-send="true"
href="http://lists.ausnog.net/mailman/listinfo/ausnog"
target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div>
</div>
</blockquote>
</div>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a moz-do-not-send="true"
href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>