NTAC Peering Working Group

[Jeff Bartig <>]

On 1/2/18, 1:18 PM, David Farmer wrote:

There is no route6 object anywhere for 2001:468::/32.

This is probably because 2001:468::/32 was being routed long before route6 objects existed. So, It would probably be a good idea for someone within Internet2 or the NOC to fix this by create a route6 object for it or add an "Origin AS" within ARIN Online.

While I was at it, I looked at IPv4 too;

For 162.252.68.0/22, 162.244.104.0/21 and 198.71.44.0/22 all have "Origin AS" within ARIN Whois.

For 163.253.0.0/16, all but one sub block that is routed has a route object in RADB, but nothing for the aggregate /16, but maybe that is the way it should be.

For 64.57.16.0/20, there is no route object or "Origin AS" within ARIN Whois.  So, It would probably be a good idea for someone within Internet2 or the NOC to fix this too.

Hi Dave,

I believe all of the items you note above and others I found have been cleaned up.  RADB updates should be live.  ARIN updates might take a while to become visible via whois.

There are no plans to advertise the aggregate 163.253.0.0/16 route, but I did add a route object just to provide a default origin for any more specifics that do get advertised.  I also created route objects for all of the more specifics that already exist under 163.253.0.0/16.

Jeff

--
Jeff Bartig
Interconnection Architect
Internet2  AS11164 / AS11537
+1-608-616-9908