[141537] in North American Network Operators' Group
Re: Cogent IPv6
daemon@ATHENA.MIT.EDU (Owen DeLong)
Wed Jun 8 20:56:05 2011
From: Owen DeLong <owen@delong.com>
In-Reply-To: <daf58b8ac16fbea54a4aa05e45bb2981@u13.net>
Date: Wed, 8 Jun 2011 17:51:38 -0700
To: ryan@u13.net
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jun 8, 2011, at 7:18 AM, ryan@u13.net wrote:
> On Wed, 8 Jun 2011 09:51:21 -0400, Nick Olsen wrote:
>=20
>> I'm sure someone here is doing IPv6 peering with cogent. We've got a =
Gig
>>=20
>> with them, So they don't do that dual peering thing with us. (They do =
it
>> on
>> another 100Mb/s circuit we have... I despise it.)
>> Just kind of curious how they go about it.
>> Do they issue you a small IPv6 block for your interface, just like =
they
>> do
>> for IPv4? Is it a separate session? Any things to be aware of before
>> pulling the trigger on it? (Other then them not having connectivity =
to
>> HE's
>> IPv6 side of things, Wish they would fix that already...)
>>=20
>> Nick Olsen
>> Network Operations (855) FLSPEED x106
>=20
> We have separate v4 and v6 sessions with them on the same dual-stack =
interface (a v4 /29 and v6 /112 on the interface). One session is =
between our v4 address and theirs, and carries v4 prefixes only. Then =
another session between v6 addresses that carries v6 prefixes only.
That's really the best way to do dual stack peering anyway.
Keeps things much cleaner.
Owen
