LEVEL3, FLAG, NTT peering policies

Jared Mauch jared at puck.nether.net
Wed Jul 11 13:13:36 UTC 2012


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,
> 
> Apologies if this has been asked before, I was hoping to get a quick answer
> to rescue a situation J.
> 
> 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?
> 
> I know level3 has such policies which are downloaded from the RIPE DB
> according to their published peering policy document.
> 
> I’ve 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’t seem they have an inbound filter
> policy on IP prefixes or  AS
> 
> 
> 
> Could someone please confirm?
> 
> 
> 
> Many thanks





More information about the NANOG mailing list