[154773] in North American Network Operators' Group
Re: LEVEL3, FLAG, NTT peering policies
daemon@ATHENA.MIT.EDU (Jared Mauch)
Wed Jul 11 09:15:56 2012
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <a5e448d26d13395c2e419d306e53e3cb@mail.gmail.com>
Date: Wed, 11 Jul 2012 09:13:36 -0400
To: Luqman Kondeth <luqman.kondeth@nyu.edu>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
NTT uses a variety of routing registries.
Please see http://www.us.ntt.net/support/policy/rr.cfm for information.
- Jared
On Jul 11, 2012, at 8:47 AM, Luqman Kondeth wrote:
> HI All,
>=20
> Apologies if this has been asked before, I was hoping to get a quick =
answer
> to rescue a situation J.
>=20
> We are advertising our prefixes to an ISP in the region who has =
level3, ntt
> & flag telecom as its upstream providers. I wanted to know if ntt & =
flag
> telecom have any BGP filtering policy based on AS or IP prefixes?
>=20
> I know level3 has such policies which are downloaded from the RIPE DB
> according to their published peering policy document.
>=20
> I=92ve read through the peering policies of NTT & FLAG (
> http://www.us.ntt.net/support/policy/routing.cfm ,
> http://www.onesc.net/communities/as15412/ ) and donot see anything =
which
> would suggest they use the ripe db or any other db for filtering based =
on
> AS or IP prefixes. Infact, it doesn=92t seem they have an inbound =
filter
> policy on IP prefixes or AS
>=20
>=20
>=20
> Could someone please confirm?
>=20
>=20
>=20
> Many thanks
