June 2017 - mice-discuss - lists.micemn.net

Re: New Cabinet Pics
by Andy Koch July 31, 2017

July 31, 2017

Thank you Jeremy, looking good. Question on the QSFP breakout panel: WiscNet is evaluating a couple of these, but I have not seen the model that is installed here. What was the source of this panel and do you have a model/manufacturer? Thanks for the info. Andy -- Andy Koch Network Engineer, WiscNet akoch(a)wiscnet.net 608-210-3967 10 May 2017 at 14:37:00, Jeremy Lumby wrote: > I officially cleaned out the old 1/3 MICE cabinet today, and got some pictures of the new cabinet. I left them full resolution so that you can use them for other things. Since they were so large, I did not want to attach them, so they are at the following links. Special thanks again to Cologix, Anthony, Doug, Richard, and Jay for their assistance with the migration. > > http://www.mnvoip.com/mice/newcab1.jpg > > http://www.mnvoip.com/mice/newcab2.jpg > > http://www.mnvoip.com/mice/newcab3.jpg > > > Jeremy Lumby > Minnesota VoIP > 9217 17th Ave S > Suite 216 > Bloomington, MN 55425 > Main: 612-355-7740 x211 > Direct: 612-392-6814 > EFax: 952-873-7425 > jlumby(a)mnvoip.com

5 5

Re: a Madison-based ICANN colleague of mine wonders if he could represent us at ICANN?
by Jeremy Lumby July 5, 2017

July 5, 2017

You have my vote Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington MN 55425 Main 612-355-7740 Direct 612-392-6814 EFax 952-873-7425 jlumny(a)mnvoip.com -------- Original message -------- From: Mike O'Connor <mike(a)HAVEN2.COM> Date: 6/14/17 1:47 PM (GMT-06:00) To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] a Madison-based ICANN colleague of mine wonders if he could represent us at ICANN? _____ >From : Mike O'Connor [mike(a)HAVEN2.COM] To : MICE-DISCUSS(a)LISTS.IPHOUSE.NET [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] Date : Wednesday, June 14 2017 13:46:01 hi all, Mark McFadden inquired as to whether he could take on the volunteer "represent MICE at ICANN" role that i used to fill. if that decision were left entirely to me i would say "absolutely" as Mark is one of the folks i held in highest regard while i was a participant at ICANN. i'm putting this request to you in much the same way that i did when i asked whether i could represent us, back in 2012. this would be a volunteer arrangement in which Mark would stand ready to provide briefings and insights as MICE requests - in return for which he would have standing within ICANN to continue his very long involvement in that organization. i did a search on "Mark McFadden ICANN" which turned up all kinds of stuff. i thought this recent letter from Mark did a pretty good job of summarizing his qualifications. ICANN: I am pleased to submit my name for consideration for the AoC Review Team on Security, Stability, and Resilience of the DNS. I have attached a short CV and my statement of interest. Note that I have a formal Conflict of Interests statement, dated 1 August 2016, on file with ICANN. I have been a participant in ICANN since its beginnings serving as Secretariat to the ISPCP constituency, the Chair of the Address Supporting Organization, member of the RSTEP, and most recently as a member of the ISPCP constituency. I have also directed work on two of the Independent Evaluation panels for the new gTLD program. I have significant experience working with DNS infrastructure in my time at BT and subsequently as an advisor for Western European governments on Internet policy related to the DNS. In that capacity, I’ve worked on DNSSEC projects, standardization efforts in the IETF, and performance and security management for large DNS implementations. I believe that the combination of technical and policy background makes for a very helpful addition to the SSR2. While with BT, I was responsible for policy and technical coordination of a global DNS implementation and worked on DNSSEC, enum and other infrastructure related issues. My interests in stability issues related to the DNS is broad. I have been a contributor to DNSOP in the IETF and to the effort to understand name collision in the context of the expansion of the DNS namespace. I believe that the DNS is in the midst of significant evolutionary change and that the security, stability and resilience of the DNS is under threat in ways that were not the case during the first SSR. My interest in SSR2 is in enhancing the security, stability and resiliency of the DNS is practical, standards-based, data-driven approaches with clear mandates for ICANN and the community that makes ICANN effective. Best regards, Mark Mark McFadden Principal Consultant, Internet Infrastructure and Governance InterConnect Communications what say you all? can i expand my "absolutely" vote from me to the rest of you? thanks for considering this idea, mike WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax:(866)-280-2356

13 29

US Internet - Scheduled Maintenance
by Justin Krejci June 29, 2017

June 29, 2017

On July 10th, we will be shutting down our BGP sessions through MICE as we will moving some fiber connections; we are splicing onto our new Corning Centrix frame. The window for the splicing work is 8am-noon. Justin Krejci 952-253-3200 ・ 1-800-US-INTERNET 12450 Wayzata Blvd. Suite 315 ・ Minnetonka, MN 55305 [http://www.usinternet.com/img/usi-signature.png]

1 0

Please welcome Gigamonster to MICE!
by Jason Hanke June 20, 2017

June 20, 2017

Name: Gigamonster, LLC Port: Ethernet5/10 (10G) Main Switch IPv4: 206.108.255.79/24 IPv6: 2001:504:27:0:0:7cc3::1/64 Route Server: NO BFD Support: NO Peering Contact: engr(a)gigamonster.net Billing Contact: accountspayable(a)gigamonster.net Welcome Aboard! -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke(a)neutralpath.net www.neutralpath.net

3 2

a Madison-based ICANN colleague of mine wonders if he could represent us at ICANN?
by Mike O'Connor June 14, 2017

June 14, 2017

hi all, Mark McFadden inquired as to whether he could take on the volunteer "represent MICE at ICANN" role that i used to fill. if that decision were left entirely to me i would say "absolutely" as Mark is one of the folks i held in highest regard while i was a participant at ICANN. i'm putting this request to you in much the same way that i did when i asked whether i could represent us, back in 2012. this would be a volunteer arrangement in which Mark would stand ready to provide briefings and insights as MICE requests - in return for which he would have standing within ICANN to continue his very long involvement in that organization. i did a search on "Mark McFadden ICANN" which turned up all kinds of stuff. i thought this recent letter from Mark did a pretty good job of summarizing his qualifications. ICANN: I am pleased to submit my name for consideration for the AoC Review Team on Security, Stability, and Resilience of the DNS. I have attached a short CV and my statement of interest. Note that I have a formal Conflict of Interests statement, dated 1 August 2016, on file with ICANN. I have been a participant in ICANN since its beginnings serving as Secretariat to the ISPCP constituency, the Chair of the Address Supporting Organization, member of the RSTEP, and most recently as a member of the ISPCP constituency. I have also directed work on two of the Independent Evaluation panels for the new gTLD program. I have significant experience working with DNS infrastructure in my time at BT and subsequently as an advisor for Western European governments on Internet policy related to the DNS. In that capacity, I’ve worked on DNSSEC projects, standardization efforts in the IETF, and performance and security management for large DNS implementations. I believe that the combination of technical and policy background makes for a very helpful addition to the SSR2. While with BT, I was responsible for policy and technical coordination of a global DNS implementation and worked on DNSSEC, enum and other infrastructure related issues. My interests in stability issues related to the DNS is broad. I have been a contributor to DNSOP in the IETF and to the effort to understand name collision in the context of the expansion of the DNS namespace. I believe that the DNS is in the midst of significant evolutionary change and that the security, stability and resilience of the DNS is under threat in ways that were not the case during the first SSR. My interest in SSR2 is in enhancing the security, stability and resiliency of the DNS is practical, standards-based, data-driven approaches with clear mandates for ICANN and the community that makes ICANN effective. Best regards, Mark Mark McFadden Principal Consultant, Internet Infrastructure and Governance InterConnect Communications what say you all? can i expand my "absolutely" vote from me to the rest of you? thanks for considering this idea, mike WI:(715) 598-4284 MN:(651) 647-6109 Toll Free:(800) 896-0907 Fax:(866)-280-2356

2 1

Re: Cologix Power
by Jeremy Lumby June 3, 2017

June 3, 2017

E-mail from 511: Hello Everyone, There was a car accident which caused us to go on to emergency power. Just as a precaution please verify your servers are fine. UPS did work but we are currently on Generator power until Xcel can fix the issue. Please email me if you find any issues. Thanks, 511 Building Engineering Jeremy Lumby Minnesota VoIP 9217 17th Ave S Suite 216 Bloomington MN 55425 Main 612-355-7740 Direct 612-392-6814 EFax 952-873-7425 jlumny(a)mnvoip.com -------- Original message -------- From: Jeremy Lumby <jlumby(a)mnvoip.com> Date: 6/2/17 7:31 PM (GMT-06:00) To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: RE: [MICE-DISCUSS] Cologix Power _____ >From : Jeremy Lumby [jlumby(a)mnvoip.com] To : MICE Discuss [MICE-DISCUSS(a)LISTS.IPHOUSE.NET] Date : Friday, June 2 2017 19:31:00 I saw the same temperature increase (see attached) luckily the temperature issue has resolved itself even though half of the power is still off. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Josh Cepek Sent: Friday, June 02, 2017 7:12 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Cologix Power We're seeing similar power alarms on our gear in suite 400; thanks for the update as I'm sure the on-site staff are busy if it's a suite-wide problem. The 2nd power feed is carrying the load for us. We also recorded a roughly 10 degree (F) temperature spike starting at about 18:00 until our PDU with the temp sensor lost power at 18:44 On Fri, Jun 2, 2017 at 7:00 PM, Jeremy Lumby wrote: > Looks like there is a power issue in Cologix Suite 400. I have multiple devices indicating that one of the power feeds is down. My suite 100 equipment all seems fine. -- This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, please be advised that you have received this e-mail in error and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender or call ClaimLynx at (952) 593-5969.

1 0

Cologix Power
by Jeremy Lumby June 3, 2017

June 3, 2017

Looks like there is a power issue in Cologix Suite 400. I have multiple devices indicating that one of the power feeds is down. My suite 100 equipment all seems fine.

3 3

TDS AS4181 Maintenance Notice for 6/2/2017
by Kevin Roberts June 1, 2017

June 1, 2017

TDS AS4181 will be performing maintenance on the directly connected router to MICE 6/2/17 in a window from 12:01 am to 6:00 am CST. During this maintenance window you can expect BGP sessions to AS4181 to be down during this window for 1 hour. If you have any questions please send an email to peering(a)tdstelecom.com with your BGP AS number and it will be addressed as soon as possible. Kevin Roberts IP Network Operations TDS Telecommunications peering(a)tdstelecom.com

1 0