September 2018 - mice-discuss

Re: UG 29 Meeting & Election

by Reid Fishler

I dont get to make a can with my own face, and make a speech? Darn! :-) Thanks everyone! Reid On Fri, Sep 28, 2018 at 9:52 AM Michael Hemphill <mikeh(a)coloconnect.net> wrote: > Congrats Reid! > You bring a global perspective to the board and along with your > involvement with other exchanges you are invaluable to MICE. > Thanks for your service to the MICE Community! > Mike > > Mike Hemphill > ColoConnect > 612-812-5242 > mikeh(a)ColoConnect.net > http://www.ColoConnect.net/ > > > > -----Original Message----- > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of > Richard Laager > Sent: Friday, September 28, 2018 3:29 AM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: Re: [MICE-DISCUSS] UG 29 Meeting & Election > > On 09/24/2018 10:48 PM, Richard Laager wrote: > > A member pointed out that it is hard to instruct a proxy without knowing > > the final slate of candidates. Accordingly, we will close nominations at > > 5:00 PM Central on this Thursday, September 27. Following that, I will > > send another email confirming the final slate of candidates. > > Having heard no other nominations, the final slate of candidates is: > - Reid Fishler > > -- > Richard > -- Reid Fishler Director Hurricane Electric +1-510-580-4178

Sept. 28, 2018

Re: UG 29 Meeting & Election

by Michael Hemphill

Congrats Reid! You bring a global perspective to the board and along with your involvement with other exchanges you are invaluable to MICE. Thanks for your service to the MICE Community! Mike Mike Hemphill ColoConnect 612-812-5242 mikeh(a)ColoConnect.net http://www.ColoConnect.net/ -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Richard Laager Sent: Friday, September 28, 2018 3:29 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] UG 29 Meeting & Election On 09/24/2018 10:48 PM, Richard Laager wrote: > A member pointed out that it is hard to instruct a proxy without knowing > the final slate of candidates. Accordingly, we will close nominations at > 5:00 PM Central on this Thursday, September 27. Following that, I will > send another email confirming the final slate of candidates. Having heard no other nominations, the final slate of candidates is: - Reid Fishler -- Richard

Sept. 28, 2018

Re: UG 29 Meeting & Election

by Mike Horwath

On Fri, Sep 28, 2018 at 03:29:23AM -0500, Richard Laager wrote: > Having heard no other nominations, the final slate of candidates is: > - Reid Fishler Congrats! -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Sept. 28, 2018

Re: UG 29 Meeting & Election

by Richard Laager

On 09/24/2018 10:48 PM, Richard Laager wrote: > A member pointed out that it is hard to instruct a proxy without knowing > the final slate of candidates. Accordingly, we will close nominations at > 5:00 PM Central on this Thursday, September 27. Following that, I will > send another email confirming the final slate of candidates. Having heard no other nominations, the final slate of candidates is: - Reid Fishler -- Richard

Sept. 28, 2018

Re: Fwd: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials

by Jeremy Lumby

Even if you are not on an exchange that requires IRRs, I would highly recommend utilizing the tutorial for getting IRRs setup with ARIN if you do not already have them. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Richard Laager Sent: Tuesday, September 25, 2018 10:43 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Fwd: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials This is from the SeattleIX announce list. I'm forwarding it, with Chris's permission, in case this is relevant to anyone here. -------- Forwarded Message -------- Subject: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials Date: Tue, 25 Sep 2018 22:22:14 +0000 (UTC) From: Chris Caputo <ccaputo(a)seattleix.net> To: announce(a)seattleix.net tl;dr: - RIPE made changes which don't break anything now, but may in future. - I recommend you move your IRR records to the RIR which assigned or allocated your prefixes. - link to ARIN RPKI tutorial at bottom. Many of you that used RIPE to create your Internet Routing Registry (IRR) objects received an email from RIPE at the beginning of September about a change in their registry in which non-RIPE prefixes are now labeled with "source: RIPE-NONAUTH". This is part of an effort to improve the quality of IRR data for the purposes of reducing accidental or fraudulent BGP announcements. The idea being that the Regional Internet Registries (RIRs) know best who addresses have been assigned/allocated to. If you have your records at RIPE (or elsewhere and want to move to ARIN), I recommend you do the following: (note the example with my AS6456 will soon no longer work because I will be deleting my records at RIPE since they have been moved to ARIN) - First, determine your maintainer object name. This can be figured out by going to http://www.radb.net/query/ and running a query on your ASN or prefixes. For example, a query on my AS6456 reveals a RIPE maintainer "mnt-by" field "MAINT-ALTOPIA-RIPE". You may find you have multiple maintainers and multiple IRRs. Focus on the RIPE one if that is what you want to move. aut-num: AS6456 [...] mnt-by: MAINT-ALTOPIA-RIPE source: RIPE-NONAUTH - Using my "MAINT-ALTOPIA-RIPE" I can do an inverse query at RIPE to see all of my objects: $ whois -h whois.ripe.net -i mnt-by -B MAINT-ALTOPIA-RIPE aut-num: AS6456 as-name: ALTOPIA-6456 descr: Altopia AS 6456 [...] as-set: AS-ALTOPIA descr: Altopia Corporation members: AS6456 [...] route: 208.90.168.0/22 descr: ALTOPIA-V4-1 assigned by ARIN origin: AS6456 [...] route6: 2620:0:cf0::/48 descr: ALTOPIA-V6-1 assigned by ARIN origin: AS6456 [...] etc... - Save a copy of all of your objects so you can use the result to aide in your move to ARIN. - Refer to https://www.seattleix.net/irr-tutorial#arin for a new tutorial on how to get set up at ARIN's IRR. - Use http://irrexplorer.nlnog.net to visualize which IRRs are reporting your prefixes or ASN. - After all of your ARIN objects are moved to ARIN, work to delete your ARIN objects at RIPE or elsewhere as part of being tidy. Bonus! I also made an ARIN Resource Public Key Infrastructure (RPKI) tutorial. Turns out RPKI is pretty easy to configure, with respect to making it so your own ARIN prefixes are somewhat (*) protected from being announced by unauthorized ASNs. (*: with respect to networks running RPKI validators) - https://www.seattleix.net/irr-tutorial#arinrpki Feedback & corrections welcome! Chris

Sept. 26, 2018

Fwd: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials

by Richard Laager

This is from the SeattleIX announce list. I'm forwarding it, with Chris's permission, in case this is relevant to anyone here. -------- Forwarded Message -------- Subject: route server IRR objects: RIPE use for ARIN addresses deprecated, ARIN IRR & RPKI tutorials Date: Tue, 25 Sep 2018 22:22:14 +0000 (UTC) From: Chris Caputo <ccaputo(a)seattleix.net> To: announce(a)seattleix.net tl;dr: - RIPE made changes which don't break anything now, but may in future. - I recommend you move your IRR records to the RIR which assigned or allocated your prefixes. - link to ARIN RPKI tutorial at bottom. Many of you that used RIPE to create your Internet Routing Registry (IRR) objects received an email from RIPE at the beginning of September about a change in their registry in which non-RIPE prefixes are now labeled with "source: RIPE-NONAUTH". This is part of an effort to improve the quality of IRR data for the purposes of reducing accidental or fraudulent BGP announcements. The idea being that the Regional Internet Registries (RIRs) know best who addresses have been assigned/allocated to. If you have your records at RIPE (or elsewhere and want to move to ARIN), I recommend you do the following: (note the example with my AS6456 will soon no longer work because I will be deleting my records at RIPE since they have been moved to ARIN) - First, determine your maintainer object name. This can be figured out by going to http://www.radb.net/query/ and running a query on your ASN or prefixes. For example, a query on my AS6456 reveals a RIPE maintainer "mnt-by" field "MAINT-ALTOPIA-RIPE". You may find you have multiple maintainers and multiple IRRs. Focus on the RIPE one if that is what you want to move. aut-num: AS6456 [...] mnt-by: MAINT-ALTOPIA-RIPE source: RIPE-NONAUTH - Using my "MAINT-ALTOPIA-RIPE" I can do an inverse query at RIPE to see all of my objects: $ whois -h whois.ripe.net -i mnt-by -B MAINT-ALTOPIA-RIPE aut-num: AS6456 as-name: ALTOPIA-6456 descr: Altopia AS 6456 [...] as-set: AS-ALTOPIA descr: Altopia Corporation members: AS6456 [...] route: 208.90.168.0/22 descr: ALTOPIA-V4-1 assigned by ARIN origin: AS6456 [...] route6: 2620:0:cf0::/48 descr: ALTOPIA-V6-1 assigned by ARIN origin: AS6456 [...] etc... - Save a copy of all of your objects so you can use the result to aide in your move to ARIN. - Refer to https://www.seattleix.net/irr-tutorial#arin for a new tutorial on how to get set up at ARIN's IRR. - Use http://irrexplorer.nlnog.net to visualize which IRRs are reporting your prefixes or ASN. - After all of your ARIN objects are moved to ARIN, work to delete your ARIN objects at RIPE or elsewhere as part of being tidy. Bonus! I also made an ARIN Resource Public Key Infrastructure (RPKI) tutorial. Turns out RPKI is pretty easy to configure, with respect to making it so your own ARIN prefixes are somewhat (*) protected from being announced by unauthorized ASNs. (*: with respect to networks running RPKI validators) - https://www.seattleix.net/irr-tutorial#arinrpki Feedback & corrections welcome! Chris

Sept. 26, 2018

Re: UG 29 Meeting & Election

by Richard Laager

A member pointed out that it is hard to instruct a proxy without knowing the final slate of candidates. Accordingly, we will close nominations at 5:00 PM Central on this Thursday, September 27. Following that, I will send another email confirming the final slate of candidates. Currently, Reid Fishler is running. On 09/24/2018 03:35 AM, Richard Laager wrote: > The MICE UG 29 meeting will be held Wednesday, October 10, 3:00 pm, at > the 511 Building Cafeteria, 11th Avenue South, Minneapolis, MN. > > The agenda and draft UG 28 minutes are attached. > > The remote conferencing will be the same as before: > 952-562-5400 passcode MICE (6423). > > At this meeting, we will be holding an election for a board seat. > > The board consists of three seats with staggered terms, such that one > seat comes up for re-election each year (at the fall meeting). This > year, Reid's seat is up for election. > > Reid _is_ running for re-election. If anyone else is interested in > running, please nominate yourself. > > Voting will be done in person. If you will not be attending in person, > you must designate a proxy, in advance, in writing. The bylaws state > that you send that to the Chief Manager (me, Richard Laager), and > electronic means are acceptable. So a simple email is sufficient: > rlaager(a)wiktel.com or, if you prefer, chiefmanager(a)micemn.net > > If you are having trouble finding a proxy who will be there in person, > ask on the list or I can help you find someone. > -- Richard

Sept. 25, 2018

Re: UG 29 Meeting & Election

by Justin Krejci

Nobody from US Internet will be attending this MICE meeting due to Wispapalooza; when is the latest that nominees will be accepted for Reid's seat? I hope to send a proxy vote but don't yet know who the candidates are. ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Richard Laager <rlaager(a)WIKTEL.COM> Sent: Monday, September 24, 2018 3:35 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] UG 29 Meeting & Election The MICE UG 29 meeting will be held Wednesday, October 10, 3:00 pm, at the 511 Building Cafeteria, 11th Avenue South, Minneapolis, MN. The agenda and draft UG 28 minutes are attached. The remote conferencing will be the same as before: 952-562-5400 passcode MICE (6423). At this meeting, we will be holding an election for a board seat. The board consists of three seats with staggered terms, such that one seat comes up for re-election each year (at the fall meeting). This year, Reid's seat is up for election. Reid _is_ running for re-election. If anyone else is interested in running, please nominate yourself. Voting will be done in person. If you will not be attending in person, you must designate a proxy, in advance, in writing. The bylaws state that you send that to the Chief Manager (me, Richard Laager), and electronic means are acceptable. So a simple email is sufficient: rlaager(a)wiktel.com or, if you prefer, chiefmanager(a)micemn.net If you are having trouble finding a proxy who will be there in person, ask on the list or I can help you find someone. -- Richard

Sept. 24, 2018

UG 29 Meeting & Election

by Richard Laager

The MICE UG 29 meeting will be held Wednesday, October 10, 3:00 pm, at the 511 Building Cafeteria, 11th Avenue South, Minneapolis, MN. The agenda and draft UG 28 minutes are attached. The remote conferencing will be the same as before: 952-562-5400 passcode MICE (6423). At this meeting, we will be holding an election for a board seat. The board consists of three seats with staggered terms, such that one seat comes up for re-election each year (at the fall meeting). This year, Reid's seat is up for election. Reid _is_ running for re-election. If anyone else is interested in running, please nominate yourself. Voting will be done in person. If you will not be attending in person, you must designate a proxy, in advance, in writing. The bylaws state that you send that to the Chief Manager (me, Richard Laager), and electronic means are acceptable. So a simple email is sufficient: rlaager(a)wiktel.com or, if you prefer, chiefmanager(a)micemn.net If you are having trouble finding a proxy who will be there in person, ask on the list or I can help you find someone. -- Richard

Sept. 24, 2018

Arista Test Drive Training Wednesday, October 3rd

by John McLaughlin

Hello MICE Members: If you can join us for a day of free training please use the links below to register and review what an Arista Test Drive covers. https://solutions.arista.com/2018-09-atd-minnetonka-mn <https://solutions.arista.com/2018-09-atd-minnetonka-mn> https://solutions.arista.com/atd-training <https://solutions.arista.com/atd-training> ATD TRAINING What we offer: A curriculum designed to deliver world-class content and learning experience Small, intimate class sizes, led by our local engineers, for greater classroom interaction In addition to the schedule listed, we can add classes to fit your needs. Just tell us when and where, and we take care of the rest Please reach out to your Arista Account Manager or Training(a)Arista.com <mailto:Training@Arista.com> for more information! Thanks, -JMc John McLaughlin North Central Sales jmclaughlin(a)arista.com Cell# 612-816-9024 https://www.barrons.com/articles/worlds-best-ceos-growth-leaders-1527304583…

Sept. 23, 2018