October 2018 - mice-discuss - lists.micemn.net

Re: ADV: [MICE-DISCUSS] Please Welcome Xcel Energy to MICE!

by Doug McIntyre

On Tue, Oct 16, 2018 at 01:31:49PM -0500, Jay Hanke wrote: >Name: Xcel Energy >Port: Ethernet 4/25 (Main Switch) >ASN: 215 >IPv4: 206.108.255.115/24 <http://206.108.255.114/24> >IPv6: 2001:504:27:0:0:00d7::1 /64 >Route Server: YES >BFD Support: YES >Peering Contact: Andrew.Schmidt(a)xcelenergy.com > They have been added to the route servers and everything waits for their connection. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 16, 2018

Please Welcome Xcel Energy to MICE!

by Jay Hanke

Name: Xcel Energy Port: Ethernet 4/25 (Main Switch) ASN: 215 IPv4: 206.108.255.115/24 <http://206.108.255.114/24> IPv6: 2001:504:27:0:0:00d7::1 /64 Route Server: YES BFD Support: YES Peering Contact: Andrew.Schmidt(a)xcelenergy.com Please join our mailing lists for technical updates and governance information at http://lists.iphouse.net/cgi-bin/wa?A0=MICE-DISCUSS Also, Please update/create your entry at PeeringDB.com listing your connection to the MICE Internet Exchange. We also strongly recommend that you have up to date IRR entries for your networks. Please provide your Arista compatible SFP+ optic to Cologix when you order your cross connect. Welcome Aboard! -- Jay Hanke, Peering Coordinator Midwest Internet Cooperative Exchange peering(a)micemn.net

Oct. 16, 2018

Global Net (AS395466) - Upcoming Maintenance 10/15

by Global Net NOC

MICEMN Members - We have a short maintenance window scheduled for Monday, October 15th to perform a software upgrade at our edge. Our BGP sessions will flap several times. Start: 10/15/18 1000 GMT End: 10/15/18 1010 GMT Thanks, Global Net NOC noc(a)theglobal.net Global Net Peering peering(a)theglobal.net

Oct. 12, 2018

Re: ADV: [MICE-DISCUSS] Please Welcome ImOn Communications to MICE!

by Doug McIntyre

On Thu, Oct 11, 2018 at 08:17:54AM -0500, Jay Hanke wrote: >Name: Imon Communications >Port: MN VoIP Remote >ASN: 393238 >IPv4: 206.108.255.114/24 >IPv6: 2001:504:27:0:6:0016::1 /64 >Route Server: YES >BFD Support: YES >Peering Contact: ImOnAdmins(a)imon.net I've added them to the route servers. Welcome aboard! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Oct. 12, 2018

Please Welcome ImOn Communications to MICE!

by Jay Hanke

Name: Imon Communications Port: MN VoIP Remote ASN: 393238 IPv4: 206.108.255.114/24 IPv6: 2001:504:27:0:6:0016::1 /64 Route Server: YES BFD Support: YES Peering Contact: ImOnAdmins(a)imon.net Please join our mailing lists for technical updates and governance information at http://lists.iphouse.net/cgi-bin/wa?A0=MICE-DISCUSS Also, Please update/create your entry at PeeringDB.com listing your connection to the MICE Internet Exchange. We also strongly recommend that you have up to date IRR entries for your networks. Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Oct. 11, 2018

Re: MICE Route Filtering

by David Farmer

On Sat, Oct 6, 2018 at 9:07 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > I am in favor of this, especially if we have someone that is experienced > that is willing to help. I would propose that we start with RS#2 and test > for a while, then we can notify people who's prefixes are being rejected > prior to applying to RS#1. I would also propose that at the same time we > set RS#2 to be passive so that it cuts down on the chatter that it is > creating on the exchange waiting for people to connect, or people who have > not yet turned up their v6 sessions. I think this would be a great point > of discussion at the next UG. > Generally, that is the suggested plan, but also set a two or three week deadline between filtering on RS#2 and RS#1, and no white listing execptions either. Yes, we should discuss this on Wednesday. I think it is really important to hear from anyone who doesn't think this is a good idea, and why. Thanks =============================================== David Farmer Email:farmer@umn.edu 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 ===============================================

Oct. 8, 2018

Re: MICE Route Filtering

by Richard Laager

On 10/06/2018 09:06 PM, Jeremy Lumby wrote: > I would propose that we start with RS#2 and test for a while, then we > can notify people who's prefixes are being rejected prior to applying to > RS#1. That would be ideal. > I would also propose that at the same time we set RS#2 to be > passive so that it cuts down on the chatter that it is creating on the > exchange waiting for people to connect, or people who have not yet > turned up their v6 sessions. Yes, please. -- Richard

Oct. 7, 2018

Re: MICE Route Filtering

by Jeremy Lumby

I am in favor of this, especially if we have someone that is experienced that is willing to help. I would propose that we start with RS#2 and test for a while, then we can notify people who's prefixes are being rejected prior to applying to RS#1. I would also propose that at the same time we set RS#2 to be passive so that it cuts down on the chatter that it is creating on the exchange waiting for people to connect, or people who have not yet turned up their v6 sessions. I think this would be a great point of discussion at the next UG. From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer Sent: Saturday, October 06, 2018 11:20 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] MICE Route Filtering At NANOG it was strongly suggested we, privately for MICE and more generally for all IXes, should implement IRR filtering on our route servers ASAP. We are now one of the bigger IXes not already filtering, especially in the US. We should probably block routes with invalid RPKI ROAs too. Arouteserver was recommended as one of the better and easier to implement options. There are offers to help us with this from Theo de Raadt <deraadt(a)yycix.ca> of the Calgary Internet Exchange (YYCIX) and by others. https://blog.apnic.net/2017/03/17/ixp-automation-made-easy-new-open-source-… https://github.com/pierky/arouteserver https://arouteserver.readthedocs.io/en/latest/ FYI additionally, Fastly already filters based on IRR objects, and HE has recently started filtering. https://www.fastly.com/peering http://routing.he.net/algorithm.html Also at NANOG, it was announced by Google that they plan to begin filtering routes based IRR data early next year. See slide 114 of the following; https://pc.nanog.org/static/published/meetings/NANOG74/1760/20181003_Tzveta… There is lots of other good stuff in the deck, but the fact that Google plans to start filtering based on IRR objects is BIG news. So, we need to escalate doing route filtering on our Route Servers. Furthermore, if you don't already have IRR objects, you should probably start working on them. The following is a handy tool to check the consistency of your IRR objects. http://irrexplorer.nlnog.net/ Thanks. -- =============================================== David Farmer Email:farmer@umn.edu 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 =============================================== To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Oct. 7, 2018

MICE Route Filtering

by David Farmer

At NANOG it was strongly suggested we, privately for MICE and more generally for all IXes, should implement IRR filtering on our route servers ASAP. We are now one of the bigger IXes not already filtering, especially in the US. We should probably block routes with invalid RPKI ROAs too. Arouteserver was recommended as one of the better and easier to implement options. There are offers to help us with this from Theo de Raadt < deraadt(a)yycix.ca> of the Calgary Internet Exchange (YYCIX) and by others. https://blog.apnic.net/2017/03/17/ixp-automation-made-easy-new-open-source-… https://github.com/pierky/arouteserver https://arouteserver.readthedocs.io/en/latest/ FYI additionally, Fastly already filters based on IRR objects, and HE has recently started filtering. https://www.fastly.com/peering http://routing.he.net/algorithm.html Also at NANOG, it was announced by Google that they plan to begin filtering routes based IRR data early next year. See slide 114 of the following; https://pc.nanog.org/static/published/meetings/NANOG74/1760/20181003_Tzveta… There is lots of other good stuff in the deck, but the fact that Google plans to start filtering based on IRR objects is BIG news. So, we need to escalate doing route filtering on our Route Servers. Furthermore, if you don't already have IRR objects, you should probably start working on them. The following is a handy tool to check the consistency of your IRR objects. http://irrexplorer.nlnog.net/ Thanks. -- =============================================== David Farmer Email:farmer@umn.edu 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 ===============================================

Oct. 6, 2018

Fwd: Voting Now Open for the 2018 ARIN Board of Trustees, ARIN Advisory Council, and NRO NC Elections

by David Farmer

If you are an ARIN Member voting contact please remember to vote. If you are not your organizations voting contact please remind your voting contact to vote. If you would like suggestions on who to vote for please email me off the list. By the way, I'm not up until next year, but voting is still important. Thanks. ---------- Forwarded message --------- From: ARIN <info(a)arin.net> Date: Thu, Oct 4, 2018 at 5:01 PM Subject: [arin-announce] Voting Now Open for the 2018 ARIN Board of Trustees, ARIN Advisory Council, and NRO NC Elections To: <arin-announce(a)arin.net> Cast your online ballot now in the 2018 ARIN Elections to fill two seats on the ARIN Board of Trustees, five seats on the ARIN Advisory Council, and one seat on the Number Resource Organization Number Council (NRO NC). Eligible Voting Contacts from General Members in Good Standing as of the voter eligibility deadline of 20 August, may cast an online ballot now through 6:00 PM EDT, Friday, 12 October. To vote, simply log in to ARIN Online and look for the “Vote Now” link on your dashboard. To view candidate biographies, please view the ARIN Elections 2018 Voter Guide at: https://www.arin.net/participate/elections/candidate_bios.pdf To view or submit a Statement of Support, please click on the link below. Anyone, regardless of voter status, is eligible to submit a Statement of Support for a candidate. https://www.bigpulse.com/p51139/ During the week of 8 October, all eligible Voting Contacts should be aware that an ARIN representative will be personally calling them as a gentle reminder to please vote and to answer any election-related questions they may have. Participation in the election process is crucial, requires only minutes of a voter’s time, is done online, and is an important member responsibility. A single cast ballot provides eligible member organizations an opportunity to shape the future of ARIN, our community, and the Internet. For questions about voting, or if you encounter an issue with the election system, please contact a member of the Member Services team immediately via email at members(a)arin.net or submit a question via ARIN Online and direct it to Meetings/Elections. Regards, Wendy Leedy Member Engagement Coordinator American Registry for Internet Numbers (ARIN) -- =============================================== David Farmer Email:farmer@umn.edu 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 ===============================================

Oct. 6, 2018