Concern about gTLD servers in India

Sun Mar 11 23:22:12 UTC 2012

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/11/2012 03:57 AM, Peter Losher wrote:
> On Mar 9, 2012, at 10:19 PM, Anurag Bhatia wrote:
> 
>> I can see India has 3 root servers hosting root zone - i, j & k in India
>> which is good. So we can resolve the root zone i.e dot within India.
> 
> 
> One correction to that; F has been operating in India from NIXI Chennai's PoP since 2005.  The reason you may not see it from your location in India is that it's a local node, so we advertise F's prefixes with the NO_EXPORT community string to limit it's reach to networks directly connected to the local IX/routeserver @NIXI Chennai.
- ---------------------------
I see 192.5.5.0/24 less widely seen by the peers as opposed to
192.5.4.0/23 maybe as you mentioned the longer prefix (/24) should be
visible to clients using local instance of f-root.

Why? It would be bad to attract traffic from half way around the world
to a local node as they are there to serve the local community.

Just wondering how do the other root keepers manage that because reminds
me of an outage (k-root related) sometime september or october time
frame of 2010 that a /24 may have leak more widely than intended from a
one of the local instances.

I know off-topic here but what caught my interest is in "no_export" set
for root server as the outage mentioned above came near the K-root local
instance in India.

regards,
/virendra

> 
> And even with that restriction as noted at APNIC 33 in Dehli, the node is one of our (F's) busiest in Asia...
> 
> -Peter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk9dM6QACgkQ3HuimOHfh+H61gD/VGHBJdphTPA1yOYUGr7nmouG
UJwR3yL4WAPcgfpDh6oA/AvwWW7kqU00ghOVE+Xioejv2gKPBQDB18hHGrmEcxtY
=RDVK
-----END PGP SIGNATURE-----