Open Letters to Sixxs

Meftah Tayeb tayeb.meftah at gmail.com
Thu Sep 15 17:01:33 CEST 2011


Good thinking mike
i do have a VoIp carrier single homed with Cogent.
any solution?
(*NO IPV4!*)

----- Original Message ----- 
From: "Mike Jones" <mike at mikejones.in>
To: "Meftah Tayeb" <tayeb.meftah at gmail.com>
Cc: "Arjan Van Der Oest" <Arjan at voiceworks.nl>; <nanog at nanog.org>; 
<ipv6-ops at lists.cluenet.de>
Sent: Thursday, September 15, 2011 4:58 PM
Subject: Re: Open Letters to Sixxs


> On 15 September 2011 15:12, Meftah Tayeb <tayeb.meftah at gmail.com> wrote:
>> ok, that's a positive answer.
>> but let me ask you a question:
>> do HE.NET peer with cogent? level3?
>
>  4   189 ms   134 ms    99 ms  10gigabitethernet7-4.core1.nyc4.he.net
> [2001:470:0:3e::1]
>  5   131 ms   152 ms   111 ms  2001:470:0:202::2
>  6   144 ms   147 ms   238 ms  2001:1900:19:7::4
>  7   132 ms   241 ms   143 ms  vl-4060.car2.NewYork2.Level3.net
> [2001:1900:4:1::fe]
> [Jitter is my cable connection, not reflective of the performance of
> HEs network]
>
> As for cogent - Does anyone really care? this is only a problem for
> reaching a single homed network behind cogent, and anyone running such
> a network knows that their IPv6 connectivity doesn't work properly
> anyway and they are the broken ones.
>
> Whatever you think of the issues surrounding the peering dispute (I am
> sure at least comcast agree with cogent that a Tier 1 network should
> pay what is essentially a Tier 2 network for peering!), the fact
> remains that HE did get there first with their defacto tier 1 status,
> and for the time being at least "working IPv6" is realistically
> "working IPv6 connection to HE and peers".
>
> The more users/content that is behind HE and peers that is not
> reachable from cogent the better, as it puts more pressure on them to
> start behaving themselves and peering properly like everyone else.
>
> - Mike
>
>
> __________ Information provenant d'ESET NOD32 Antivirus, version de la 
> base des signatures de virus 6465 (20110915) __________
>
> Le message a été vérifié par ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> 


__________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6465 (20110915) __________

Le message a été vérifié par ESET NOD32 Antivirus.

http://www.eset.com






More information about the ipv6-ops mailing list