Skip to Content.
Sympa Menu

ntacpeering - Re: No route6 object for 2001:468::/32

Subject: NTAC Peering Working Group

List archive

Re: No route6 object for 2001:468::/32


Chronological Thread 
  • From: David Farmer <>
  • To: Jeff Bartig <>
  • Cc: I2 IPv6 working group <>,
  • Subject: Re: No route6 object for 2001:468::/32
  • Date: Wed, 3 Jan 2018 17:02:23 -0600
  • Ironport-phdr: 9a23:gMYQLRIyll6jezoLktmcpTZWNBhigK39O0sv0rFitYgfKPTxwZ3uMQTl6Ol3ixeRBMOHs6sC07KempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9JDffxhEiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLdQgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QKsqUjq+8ahkVB7oiD8GNzEn9mHXltdwh79frB64uhBz35LYbISTOfFjfK3SYMkaSHJDUcZfVyJPDICyYZYRAeUdJutXtZXxqkEUoBeiGQWhBuXiwSJIiH/s2q061vwsHw/c0ww+HtIBrWnfotXvO6cIVOC60rPIxijEYvNYwzj98o3IfQ47ofyXQLJwdMzRxVMxGAzYk1WdsIroNC6b2OQKtmiU9etgVeS3hmI6qgx8rCKjytksh4THnI4Z1krI+TlhzIs0KtC0Uk52bNy+HJdNtiyWLZd6Tts/T2xppio20KMKtJ6lcCQQyZkqxATTZ+Cff4iQ/B3sSvyRITZ+hHJqZb2wnAy+/lSnyu35TsW4zVdHojRfntXSuX0A2Abf5tWbRvZy5EutxS6D2x3X5+xHO0w5l7fXJ4Quz7M/jJYfrULOFTL1lkXulKKaa0sp9+ey5+nkbbjqvIKQOot1hw3kLKgihs6yDfwmPgQSW2WX4+ex2b358UHnXblHjuc6n6vEvJ3cOM8VvLS2AxVP3YYm8xu/Dymp0NAfnXQfKVJFZAiIg5HxO1zMOvz4Cva/g0i2nDd2wvDGOKftDYvQIXjeiLvhfLB95FBAyAcr0NxS6Z1ZBqsCLf/8QEP9qdjVAx4jPwCq3+rqCs1x1oYEVmKOBq+ZPrnSsViN5u83LemDfpUVuDPjJPg//PPukHo5mVkHcaa3wJQXdWi0Hu56LEWBfXrsntABHH8MvgoiVuPllEWCXiBNaHaoXqI84D47BZmiDYfCXYCtnKeB0DmhEp1XYGBGFk6DEW3ud4qaR/cAdjieLdF8nTwZBvCdTNoD2B+g/CXz0aZmIaKA+CcRr47i2/B04fHejxc/6WYyAsiAhTKjVWZxy08BWT46lI52u0lw0B/X36FihvFCPcFW4bVEXhpsZs2U9PBzF92nAlGJRdyOUlvzB4z+WTw=

Thanks

On Wed, Jan 3, 2018 at 4:45 PM, Jeff Bartig <> wrote:
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



--
===============================================
David Farmer              
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota  
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================



Archive powered by MHonArc 2.6.19.

Top of Page