I want to thank several of you for finding and fixing issues, here's what's left; * 63.144.82.0/23 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i *> 66.44.129.0/24 69.147.218.107 180 0 25615 23430 23430 i *> 66.44.152.0/22 69.147.218.107 180 0 25615 23430 23430 i *> 66.44.166.0/24 69.147.218.107 180 0 25615 23430 23430 23430 23430 i *> 66.44.176.0/22 69.147.218.107 180 0 25615 23430 23430 i * 70.35.96.0/20 69.147.218.107 180 0 25615 32264 ? * 199.86.16.0/22 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 199.199.147.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 199.199.151.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.8.2.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.90.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.205.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.208.0/23 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.215.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.216.0/23 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.220.0/23 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.9.240.0 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i * 206.53.192.0/21 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i *> 206.146.40.0/21 69.147.218.107 180 0 25615 21730 i * 209.131.224.0/21 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i *> 209.191.222.0 69.147.218.107 0 180 0 25615 i * 216.188.192.0/19 69.147.218.105 0 180 0 15011 i *> 69.147.218.105 0 180 0 15011 i On 12/16/12 19:45 , David Farmer wrote:
OK, I think it is now time for a little public shaming; the following MICE participants are only announcing their prefixes using the old next-hop addresses through the route servers. We were all suppose to be using only the new addresses as of two weeks ago. There is one other participant announce with both the old and the new next-hop address, we (Northern Lights GigAPOP) just stopped doing this earlier today, and are now announcing using only the new next-hop addresses. All other participants are announcing to the route servers are using only the new next-hop addresses.
AS33362 Wikstrom Telephone Company (Wiktel) AS25694 Atomic Data AS15011 Jaguar Communications AS3599 CDW/Berbee
Please convert your peering session to announcing with the new next-hop addresses, ASAP. If for some reason you can't do this in the next week, please send a note to the MICE-DISCUSS mailing list detailing when you will be converting.
As a reminder, here is the original cutover schedule that was emailed out several months ago:
Addition of Address Secondary: before 10/1/2012 New Prefix Announcements: after 10/1/2012 Final use of old IP address next-hop: before 11/30/2012 Removal of old IP address range: after 12/1/2012 Project End: 12/31/2012
Thanks.
-- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1