[NANOG] Purpose of Internap's PNET AS22212

Tue Apr 29 21:30:30 UTC 2008

It's actually very easy to explain. The InterNAP Flow Control (FCP)
was designed to route traffic via the cheapest link available provided
the link is within an operating range. Over the years the PNAPs have
"preferred" different transit providers based on the underlying
contract rate - but what rate could possibly be better than free(1)?
So as time passes you will more than likely see more and more of
AS22212 in your path.

-Max

1. Peering is not free, but much less expensive than paying AT&T.

On Mon, Apr 28, 2008 at 9:13 AM, Randy Epstein <repstein at chello.at> wrote:
> Thurber,
>
>  PNET (AS22212) is looked upon by InterNAP's PNAPs (its various ASes) as just
>  another transit provider in the mix.
>
>  So yes, InterNAP technically peers (under AS22212), but there is no
>  guarantee its various PNAPs would choose that path, depending upon a number
>  of factors.
>
>  (Disclaimer: This is what I've gathered from public information, not from
>  information obtained under non-disclosure.)
>
>  Regards,
>
>  Randy
>
>
>
>  -----Original Message-----
>  From: Thurber [mailto:ct at datagram.com]
>  Sent: Monday, April 28, 2008 12:01 PM
>  To: nanog at nanog.org
>  Subject: [NANOG] Purpose of Internap's PNET AS22212
>
>  Can anybody shed some light on Internap's PNET AS22212? Specifaly how it
>  relates to their PNAP architecture?  Is Internap now doing peering? I was
>  under the impression that their entire business model was based around
>  isolated PNAPs and being a backboneless provider. Attempts at getting an
>  explanation from Internap have been fruitless.
>
>  CT
>
>
>
>  _______________________________________________
>  NANOG mailing list
>  NANOG at nanog.org
>  http://mailman.nanog.org/mailman/listinfo/nanog
>
>
>  _______________________________________________
>  NANOG mailing list
>  NANOG at nanog.org
>  http://mailman.nanog.org/mailman/listinfo/nanog
>