[163518] in North American Network Operators' Group
Re: Single AS multiple Dirverse Providers
daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Mon Jun 10 13:18:24 2013
From: "Patrick W. Gilmore" <patrick@ianai.net>
In-Reply-To: <20130610165402.GA75895@gweep.net>
Date: Mon, 10 Jun 2013 13:18:04 -0400
To: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Jun 10, 2013, at 12:54 , Joe Provo <nanog-post@rsuc.gweep.net> wrote:
> =08On Mon, Jun 10, 2013 at 11:36:44AM -0500, Dennis Burgess wrote:
>> I have a network that has three peers, two are at one site and the =
third
>> is geographically diverse, and there is NO connection between the two
>> separate networks.
>=20
> So, you have two islands? Technically, that would be separate=20
> ASNs as they are separatre routing policies, but the modern=20
> world has adapted.=20
Should we change the rules? I know with 64-bit ASNs mean it is tough to =
run out of ASNs, but not sure we really want each island to be its own =
AS going forward.
Comments from the peanut gallery?
--=20
TTFN,
patrick
>> Currently we are announcing several /24s out one network and other =
/24s
>> out the second network, they do not overlap. To the internet this =
works
>> fine, however, providers a/b at site1 do not send us the two /24s =
from
>> site b.. We have requested them to, but have not seen them come in,
>> nor do we have any filters that would prohibit them from coming in.=20=
>>=20
>> Is this normal? Can we receive those routes even though they are =
from
>> our own AS? What is the "best practice" in this case? =20
>=20
> To prevent loops in the global Internet the BGP specification
> dictates this behavior, and has in all versions. Depending on=20
> your platform and theirs, you will all need to turn several=20
> knobs before you are allowed to break these rules. I would=20
> recommend that you gain more than passing familiarity with=20
> why the protocol is built this way, how it affects your use
> case, and what concerns you might have WRT your providers
> before you change the behavior for your case.
>=20
> Cheers,
>=20
> Joe
>=20
> --=20
> RSUC / GweepNet / Spunk / FnB / Usenix / SAGE / NANOG
>=20
