- mice-discuss - lists.micemn.net

Netflix Ramping Up
by Jeremy Lumby Oct. 22, 2014

Oct. 22, 2014

I see Netflix is ramping up, and the link to the CNS switch is getting close to saturating. The University may need to move to the main switch soon to alleviate the link. 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

9 11

Agenda - MICE UG 14 - 22 Oct 2014
by Shaun Carlson Oct. 21, 2014

Oct. 21, 2014

All, Please see the attached agenda, if you have any additions, please let me know. Please see the attached minutes from our previous meeting. If you have any additions or corrections, please let me know. One agenda note, we'll be discussing the potential change of MICE to a 501.(c)6 non-profit organization. I've attached some discussion points and would encourage you to *send your questions and comments to the list.* Jeff Clancy from Stinson Leonard Street LLP will be present at the meeting to answer questions and facilitate our next steps should we choose to move forward with the conversion. Last, we are still in need of a sponsor for refreshments at Wednesday's meeting, any volunteers? *Remote Dial-in Info:* www.webex.com Meeting Number: 193 507 116 Meeting Password: MICEUG14 * Please try to have a web-cam hooked up to facilitate the best possible interaction. ** I will start this web conference 15 minutes prior to the meeting to allow you to dial-in and work past any technical difficulties. One request, does anyone have a projector they could bring to the meeting for this web conference? I would need it approx. 30 minutes prior to the meeting. Thanks! s *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

3 7

Route Server Announcement Control?
by Charles Monson Oct. 19, 2014

Oct. 19, 2014

Do the MICE route servers offer any way to control BGP announcement to specific peers? I didn't see anything on the micemn.net website about ways to do that. With some of the larger content providers connecting to the exchange, the folks who have mostly inbound traffic might want a way to stop the route servers announcements to those potentially high traffic peers without entirely withdrawing advertisements to the route servers. Some of the other exchanges we connect at let you send a community indicating the ASN you don't want your prefixes advertisements to reach (e.g. you send a community of "0:11796" to stop the route servers from advertising your prefixes to Airstream). It would be nice to have something similar at MICE. Is this something already supported that I missed? Or something that may be considered as a future feature? Charles Monson Associate Network Administrator Airstream Communications, LLC Wisconsin Independent Network, LLC

4 4

FW: MICE L2 Security Project
by Anthony Anderberg Oct. 16, 2014

Oct. 16, 2014

As a reminder, we're planning on making the last of the changes below that will include all of our ports. As before we don't expect there to be any issues or downtime, I can be reached at 320-234-5539 if anyone has issues. Cheers, anthony Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net<http://www.nutelecom.net> From: Anthony Anderberg Sent: Wednesday, October 01, 2014 11:58 PM To: MICE Discuss (MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>); 'MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET' Subject: MICE L2 Security Project We're at a point where the L2 security team feels ready to make the config changes we've talked about in the past. Although these changes can't protect us from every scenario they should protect the exchange from the many common issues. As discussed at the last meeting member ports will be limited to 5 MAC addresses, storm control will be enabled at 20%, and spanning tree BPDU packets will be filtered. Additionally the exchange will support jumbo frames should members want to exchange them with each other. Obviously if any member needs alternate configuration we'll strive to be as accommodating as possible within the larger project goals. We do not anticipate any downtime, but will send out a group reminder before starting the configuration work. Our schedule: Thursday 10/9/2014 at 10AM = Make global config changes and port changes for beta testers Thursday 10/16/2014 at 10AM = Make port config changes for all other members The beta testers are: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. Below is the configuration we'll be using and will publish on our web site for members to review and enjoy. As always questions and comments are welcome, anthony ----------------------------- **Cisco Switch Config ** Global Config: system mtu 1998 # Already set system mtu jumbo 9198 # Already set mac address-table aging-time 14400 errdisable detect cause link-flap errdisable recovery cause link-flap errdisable recovery cause storm-control vtp mode transparent Cisco Port Config: switchport block multicast switchport block unicast # Unknown unicasts that is. switchport port-security maximum 5 switchport port-security switchport port-security violation restrict storm-control broadcast level 20.00 spanning-tree bpdufilter enable no cdp enable ----------------------------- ** Juniper Switch Config ** Juniper Core Switch Global: set protocols rstp bridge-priority 1 # On the main switch stack set ethernet-switching-options storm-control interface all Juniper Port Config: set interface XXX mtu 9216 set protocols rstp interface XXX edge set ethernet-switching-options bpdu-block interface XXX set ethernet-switching-options bpdu-block disable-timeout 60 set ethernet-switching-options secure-access-port interface XXX mac-limit 5 set storm-control interface XXX level 20 -----------------------------

1 0

Please welcome Google to MICE!
by Jason Hanke Oct. 15, 2014

Oct. 15, 2014

Network Name: Google IPv4: 206.108.255.37/24 IPv6: 2001:504:27:0:0:8cc8::1/64 ASN: 36040 Port: Main Switch xe-0/0/25 Peering Contact: peering(a)google.com Please configure route servers and switches! 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

2 1

Connect Minnesota event
by Mike Hemphill Oct. 14, 2014

Oct. 14, 2014

All, Cologix is hosting an event “Connect Minnesota” on October 22nd. See below. Breakfast or lunch. This is the same day as the 4PM MICE UG meeting in the 511 Building Cafeteria. You are welcome to attend. Please register from the flyer below. Thanks, I look forward to seeing as many of you as possible on the 22nd. Best regards, Mike Mike Hemphill General Manager | *Cologix, Inc.* <http://www.cologix.com/> 511 11th Ave S, Suite 450 | Minneapolis, MN 55415 P: 1+612.333.1922 | M: 1+612.812.5242 mike.hemphill(a)cologix.com [image: cid:image001.jpg@01CFE70E.D63D3E50] <http://events.r20.constantcontact.com/register/event?oeidk=a07e9xlel5t157da…>

1 0

Meeting Reminder
by Shaun Carlson Oct. 9, 2014

Oct. 9, 2014

Good afternoon all! I wanted to send out a quick reminder of our upcoming user group meeting (UG 14!!) on October 22nd at 4 pm in the 511 building. We're working on getting a web meeting set up, however, we've had some technical difficulties, so it would be better to be there in person (hint, hint). Ok, last item, a call for Agenda items. I'm planning to send out the initial agenda on Monday, so please send me any items you'd like added to the agenda and I'll get them on there. We've got a lot to talk about this quarter, so see you all on the 22nd! Thanks! s *Shaun Carlson*Senior Manager of Information Technology | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com

2 2

FW: MICE L2 Security Project
by Anthony Anderberg Oct. 9, 2014

Oct. 9, 2014

This first phase is complete, if anyone has trouble peering with the beta testers let us know. Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net<http://www.nutelecom.net> From: Anthony Anderberg Sent: Thursday, October 09, 2014 9:08 AM To: MICE Discuss (MICE-DISCUSS(a)LISTS.IPHOUSE.NET) Subject: FW: MICE L2 Security Project As a reminder, at 10am this morning we'm planning on making the first set of changes below for our beta testers: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. I can be reached at 320-234-5539 if anyone has issues. Cheers, anthony Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net<http://www.nutelecom.net> From: Anthony Anderberg Sent: Wednesday, October 01, 2014 11:58 PM To: MICE Discuss (MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>); 'MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET' Subject: MICE L2 Security Project We're at a point where the L2 security team feels ready to make the config changes we've talked about in the past. Although these changes can't protect us from every scenario they should protect the exchange from the many common issues. As discussed at the last meeting member ports will be limited to 5 MAC addresses, storm control will be enabled at 20%, and spanning tree BPDU packets will be filtered. Additionally the exchange will support jumbo frames should members want to exchange them with each other. Obviously if any member needs alternate configuration we'll strive to be as accommodating as possible within the larger project goals. We do not anticipate any downtime, but will send out a group reminder before starting the configuration work. Our schedule: Thursday 10/9/2014 at 10AM = Make global config changes and port changes for beta testers Thursday 10/16/2014 at 10AM = Make port config changes for all other members The beta testers are: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. Below is the configuration we'll be using and will publish on our web site for members to review and enjoy. As always questions and comments are welcome, anthony ----------------------------- **Cisco Switch Config ** Global Config: system mtu 1998 # Already set system mtu jumbo 9198 # Already set mac address-table aging-time 14400 errdisable detect cause link-flap errdisable recovery cause link-flap errdisable recovery cause storm-control vtp mode transparent Cisco Port Config: switchport block multicast switchport block unicast # Unknown unicasts that is. switchport port-security maximum 5 switchport port-security switchport port-security violation restrict storm-control broadcast level 20.00 spanning-tree bpdufilter enable no cdp enable ----------------------------- ** Juniper Switch Config ** Juniper Core Switch Global: set protocols rstp bridge-priority 1 # On the main switch stack set ethernet-switching-options storm-control interface all Juniper Port Config: set interface XXX mtu 9216 set protocols rstp interface XXX edge set ethernet-switching-options bpdu-block interface XXX set ethernet-switching-options bpdu-block disable-timeout 60 set ethernet-switching-options secure-access-port interface XXX mac-limit 5 set storm-control interface XXX level 20 -----------------------------

1 0

FW: MICE L2 Security Project
by Anthony Anderberg Oct. 9, 2014

Oct. 9, 2014

As a reminder, at 10am this morning we'm planning on making the first set of changes below for our beta testers: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. I can be reached at 320-234-5539 if anyone has issues. Cheers, anthony Anthony Anderberg Sr. Systems Analyst [NUtel_email_logo_1] 320-234-5239 anthonyanderberg(a)nu-telecom.net<mailto:anthonyanderberg@nu-telecom.net> www.nutelecom.net<http://www.nutelecom.net> From: Anthony Anderberg Sent: Wednesday, October 01, 2014 11:58 PM To: MICE Discuss (MICE-DISCUSS(a)LISTS.IPHOUSE.NET) 'MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET' Subject: MICE L2 Security Project We're at a point where the L2 security team feels ready to make the config changes we've talked about in the past. Although these changes can't protect us from every scenario they should protect the exchange from the many common issues. As discussed at the last meeting member ports will be limited to 5 MAC addresses, storm control will be enabled at 20%, and spanning tree BPDU packets will be filtered. Additionally the exchange will support jumbo frames should members want to exchange them with each other. Obviously if any member needs alternate configuration we'll strive to be as accommodating as possible within the larger project goals. We do not anticipate any downtime, but will send out a group reminder before starting the configuration work. Our schedule: Thursday 10/9/2014 at 10AM = Make global config changes and port changes for beta testers Thursday 10/16/2014 at 10AM = Make port config changes for all other members The beta testers are: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. Below is the configuration we'll be using and will publish on our web site for members to review and enjoy. As always questions and comments are welcome, anthony ----------------------------- **Cisco Switch Config ** Global Config: system mtu 1998 # Already set system mtu jumbo 9198 # Already set mac address-table aging-time 14400 errdisable detect cause link-flap errdisable recovery cause link-flap errdisable recovery cause storm-control vtp mode transparent Cisco Port Config: switchport block multicast switchport block unicast # Unknown unicasts that is. switchport port-security maximum 5 switchport port-security switchport port-security violation restrict storm-control broadcast level 20.00 spanning-tree bpdufilter enable no cdp enable ----------------------------- ** Juniper Switch Config ** Juniper Core Switch Global: set protocols rstp bridge-priority 1 # On the main switch stack set ethernet-switching-options storm-control interface all Juniper Port Config: set interface XXX mtu 9216 set protocols rstp interface XXX edge set ethernet-switching-options bpdu-block interface XXX set ethernet-switching-options bpdu-block disable-timeout 60 set ethernet-switching-options secure-access-port interface XXX mac-limit 5 set storm-control interface XXX level 20 -----------------------------

1 0

Re: Website Update
by Jeremy Lumby Oct. 7, 2014

Oct. 7, 2014

I agree, I am running 1024x768 and seeing the same thing -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Chris Wopat Sent: Sunday, April 06, 2014 5:40 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Website Update On 04/04/2014 01:55 PM, Richard Laager wrote: > I've cut in the new website design (thanks MDU Ethernet!). > > If you see any problems, please let me know. The website has some rendering issues if you view it a browser that's not at least 1200px wide and 800px tall. This is especially apparent on mobile devices. On my desktop, I tend to not run any windows full screen - my desktop browser window is generally 1024x768ish or so. I suspect I'm not the only one. The issues that appear are: * When not wide enough (1200px) the top menu items display below the overlay at the top / over the main content. * When not tall enough (800px), you cannot scroll all of the way down to view all content on each page. This is especially evident on mobile browsers. Quick fix here may be to just adjust theme to auto add a certain amount of spacing after all content, which already appears to be done at the top of each page. * When narrow (mobile browser/ < 768px wide) it is also impossible to reach some of the content on the bottom menu, such as the donate button. Here's a few screenshots, first on a desktop OS, the next two on mobile (android) * http://falz.net/static/micemn-chrome.png * http://falz.net/static/micemn-mobile1.png * http://falz.net/static/micemn-mobile2.png Cheers, -- Chris Wopat SupraNet Communications, Inc. chrisw(a)supranet.net (608) 836-0282 x302 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

3 3

Please welcome Netflix to MICE!
by Jason Hanke Oct. 3, 2014

Oct. 3, 2014

Netflix will connect to the main switch with two LAG groups LAG Group 1 IPv4 Address: 206.108.255.35/24 IPv6 address: 2001:504:27:0:0:0b5a::1/64 Member ports: xe-0/0/21, xe-0/0/22 LAG Group 2 IPv4 Address: 206.108.255.36/24 IPv6 address: 2001:504:27:0:0:0b5a::2/64 Member ports: xe-0/0/23, xe-0/0/24 ASN: 2906 Contact: peering(a)netflix.com Please configure the route servers and switches. Netflix has assigned ticket number NCO-2543 on their side if the NOC needs to be contacted. Thanks and 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

2 1

MICE L2 Security Project
by Anthony Anderberg Oct. 2, 2014

Oct. 2, 2014

We're at a point where the L2 security team feels ready to make the config changes we've talked about in the past. Although these changes can't protect us from every scenario they should protect the exchange from the many common issues. As discussed at the last meeting member ports will be limited to 5 MAC addresses, storm control will be enabled at 20%, and spanning tree BPDU packets will be filtered. Additionally the exchange will support jumbo frames should members want to exchange them with each other. Obviously if any member needs alternate configuration we'll strive to be as accommodating as possible within the larger project goals. We do not anticipate any downtime, but will send out a group reminder before starting the configuration work. Our schedule: Thursday 10/9/2014 at 10AM = Make global config changes and port changes for beta testers Thursday 10/16/2014 at 10AM = Make port config changes for all other members The beta testers are: US Internet, Paul Bunyan Communications, CNS, IP House, and Wikstrom Telephone. Below is the configuration we'll be using and will publish on our web site for members to review and enjoy. As always questions and comments are welcome, anthony ----------------------------- **Cisco Switch Config ** Global Config: system mtu 1998 # Already set system mtu jumbo 9198 # Already set mac address-table aging-time 14400 errdisable detect cause link-flap errdisable recovery cause link-flap errdisable recovery cause storm-control vtp mode transparent Cisco Port Config: switchport block multicast switchport block unicast # Unknown unicasts that is. switchport port-security maximum 5 switchport port-security switchport port-security violation restrict storm-control broadcast level 20.00 spanning-tree bpdufilter enable no cdp enable ----------------------------- ** Juniper Switch Config ** Juniper Core Switch Global: set protocols rstp bridge-priority 1 # On the main switch stack set ethernet-switching-options storm-control interface all Juniper Port Config: set interface XXX mtu 9216 set protocols rstp interface XXX edge set ethernet-switching-options bpdu-block interface XXX set ethernet-switching-options bpdu-block disable-timeout 60 set ethernet-switching-options secure-access-port interface XXX mac-limit 5 set storm-control interface XXX level 20 -----------------------------

1 0

Any update on working with Google or Netflix??
by Dan Olsen Sept. 26, 2014

Sept. 26, 2014

Greetings: Any update on working with Google or Netflix??? Dan Olsen- General Manager Windomnet 443 10th Street, PO box 38 Windom MN 56101 Southwest MN Broadband Services 110 South Hwy 86, PO Box 1006, Lakefield MN 56150 Fibernet Monticello Monticello MN Voice 507-832-8007

2 1

Bash Vulnerability - MICE cacti server is patched
by Justin Krejci Sept. 24, 2014

Sept. 24, 2014

In light of the recently announced bash vulnerability (use google if you this is news to you) I have included patching the MICE cacti server while patching other US Internet systems. FYI this is a good/quick test to see if you're vulnerable BAD: $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test" vulnerable this is a test GOOD: $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test" bash: warning: x: ignoring function definition attempt bash: error importing function definition for `x' this is a test

2 1

MICE Traffic Level
by Jason Hanke Sept. 18, 2014

Sept. 18, 2014

Was the total traffic last night a record? It looked to be about 33 Gbps on a 5 minute average. -- 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

11 11

MICE Router Server 1
by Levi Pederson Sept. 16, 2014

Sept. 16, 2014

We just noticed Router Server 1 went down on our BGP Sessions. Did this happen to anyone else? Thank you,

4 4

Odd traffic and flapping
by Eric Crist Sept. 5, 2014

Sept. 5, 2014

There were strange bursts of traffic yesterday on our MICE port, and we saw the port flap three times over night. I didn't see any messages about maintenance or an outage on announce or here. Did I miss something, or are we having problems? --- Eric F Crist System Administrator ClaimLynx, Inc (952) 593-5969 x2301 -- 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.

2 1

Monticello FiberNet
by Levi Pederson Aug. 28, 2014

Aug. 28, 2014

Monticello FiberNet has pulled up their BGP connection and is getting an "EOF" Error. Can someone please check the config on the Route Servers? Thank you,

2 6

Airstream Port Upgrade
by Jay Hanke Aug. 20, 2014

Aug. 20, 2014

Airstream is upgrading their MICE connection to 10G. Their new port is xe-0/0/20 on the main switch, all IP addressing and route server configuration will remain the same. The old port ge-1/0/10 will be decommissioned following the migration. Thanks! -- Jay Hanke CEO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net

1 0

Fwd: [#ZMH-397-87500]: Legacy IP Space from Airstream
by Jay Hanke Aug. 19, 2014

Aug. 19, 2014

---------- Forwarded message ---------- From: Charles Monson <support(a)wins.net> Date: Mon, Aug 18, 2014 at 3:39 PM Subject: [#ZMH-397-87500]: Legacy IP Space from Airstream To: peering(a)micemn.net Good Afternoon, We noticed there are still a few address with the legacy 69.147.218.0/24 IP space from Airstream Communications (WIN) still configured on the MICE exchange. I would expect everyone has moved to the new address space by now and probably just didn't remove the secondary IP addresses. We would like use this space for other purposes now that everyone should be migrated, but don't want to have routing issues for anyone with it still configured. Listed below are the IP addresses and corresponding MAC addresses still showing up when I check the ARP table (our side has 69.147.218.10 configured). Can you contact whoever is still using this space or is that something you'd prefer us to do? #show arp gig1/11 | i 69.147.218 Internet 69.147.218.101 22 5c5e.abd5.9ef0 ARPA GigabitEthernet1/11 Internet 69.147.218.103 48 000c.2923.4e35 ARPA GigabitEthernet1/11 Internet 69.147.218.44 0 b0c6.9ade.0640 ARPA GigabitEthernet1/11 Internet 69.147.218.50 150 0023.33c6.a0c0 ARPA GigabitEthernet1/11 Internet 69.147.218.53 164 10f3.1134.e6de ARPA GigabitEthernet1/11 Internet 69.147.218.104 16 5c5e.abd0.da78 ARPA GigabitEthernet1/11 Internet 69.147.218.250 175 0004.9ba4.3000 ARPA GigabitEthernet1/11 Thank you, Charles Monson Associate Network Administrator Wisconsin Independent Network Airstream Communications Phone: 866-206-2027 Ticket Details ________________________________ Ticket ID: ZMH-397-87500 Department: Network Admins Type: Request Status: In Progress Priority: Normal Support Center: https://support.wins.net/index.php? -- Jay Hanke CEO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net

7 9

Stormy exchange?
by Thomas Johnson Aug. 8, 2014

Aug. 8, 2014

Our switch port just bounced due to storm control. Is someone breaking things on a Friday? -- Thomas Johnson ClaimLynx, Inc. 952-593-5969 x2302 -- 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.

3 3

MICE MTU
by Koch, Andrew July 26, 2014

July 26, 2014

The UG 13 minutes make note that the exchange MTU is 9000 bytes. Are other members configuring their routers for an MTU of 9000? I ask as TDS has not - we have stuck with the Ethernet standard 1500 bytes. If anyone on the exchange has set an MTU of 9000 and tries to send jumbo traffic to us, it will not be accepted and no indication will be sent back to the originator. (10d in the linked document below) If no one (or few) has setup their routers for an MTU of 9000, but we as a community wish to enable this, I would recommend that we schedule a flag day so that we can minimize blackholing of traffic across the exchange. While only a draft, see http://tools.ietf.org/html/draft-mlevy-ixp-jumboframes-00 for further information on IXP Jumbo Frame operation and conversion. For those that like presentations more than IETF drafts, Martin Levy (of Hurricane Electric at the time) presented this at RIPE 64 - https://ripe64.ripe.net/presentations/139-Hurricane_Electric_-_Martin_Levy_… Best Regards, Andy Koch TDS Telecom - IP Network Operations andrew.koch(a)tdstelecom.com Desk: 608-664-4694 Cell: 608-616-0072 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

6 8

UG 13 Minutes
by Shaun Carlson July 25, 2014

July 25, 2014

Please see attached, send me any corrections or updates. As an important note: *The next meeting will be on Wednesday, October 22nd from 4pm to 7pm at the 511 Building; please mark your calendars now and plan on being there!* Thanks and see you all in October! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

5 9

Re: MICE Meeting Google Hangout
by David Farmer July 24, 2014

July 24, 2014

Please send me your email so I can invite you to the google hangout. -- =============================================== 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 =============================================== > On Jul 24, 2014, at 14:24, Russell Berg <berg(a)wins.net> wrote: > > Tried joining but it says the party is over. 8-( > > From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of David Farmer > Sent: Thursday, July 24, 2014 2:12 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] MICE Meeting Google Hangout > > we will get started shortly > > https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea > > -- > =============================================== > 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: > ?SUBED1=MICE-DISCUSS&A=1 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

5 4

MICE Meeting Google Hangout
by David Farmer July 24, 2014

July 24, 2014

we will get started shortly https://plus.google.com/hangouts/_/gvdyimpkvxef2lb3ua75qf4dnea -- =============================================== 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: ?SUBED1=MICE-DISCUSS&A=1

1 0

Meeting Reminder and Agenda
by Shaun Carlson July 23, 2014

July 23, 2014

All, Just a quick, last reminder of our meeting tomorrow *Date*: Thursday, July 24th *Time*: 2:00 pm (1400 Hours) David Farmer has the facility reserved until 5PM *Location*: University of Minnesota, Duluth campus, Griggs Center, located in the Kirby Student Center (KSC) http://www.d.umn.edu/maps/KSC/ We have discussed a web attendance option. I don't have that information handy right now and I'll send it as soon as I get confirmation. Attached is the current agenda, if you have any other items you would like added to the agenda, please drop me a note prior to the meeting and I'll get them on there! Thanks and see you tomorrow! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

1 0

Agenda Items - Last Call
by Shaun Carlson July 22, 2014

July 22, 2014

All, Please send any additional agenda (business, technical or discussion) items you may have. I plan to have the Agenda out this afternoon for Thursday's meeting. Also, one more quick reminder. If you haven't responded yet, please let me know your AS and number of people attending. Thanks! s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

5 4

IPv6 neighbor solicitation at the exchange
by James Stahr July 21, 2014

July 21, 2014

First off, Did anyone make any changes on 07/15/2014 around 08:00? The reason is that I think I've resolved an issue with our IPv6 peering with the MICE route servers, Charter, and TDS and I'm looking for a larger audience to see if it's my issue or perhaps an issue at the exchange. I believe it to be the latter, but I'm not an IPv6 expert. Starting two days ago around 8am CDT, we started experiencing BGP timeouts on some of our IPv6 BGP sessions. I was able to work around the issue by removing our COPP policy and the BGP sessions were stable for 24 hours. Reapplied the policy, sessions started to drop again. Looked at the policy to see which category is being exceeded, it's not the routing section which allows BGP/BFD/etc, but the ICMP-v6 one: ipv6 access-list COPP-icmp-v6 remark ICMP type 1/3,2,3/0,3/1,4/0,4/1,4/2,130,143 permit icmp any any destination-unreachable permit icmp any any packet-too-big permit icmp any any time-exceeded permit icmp any any parameter-problem remark nd-na, nd-ns, ra, rs permit icmp any any nd-na permit icmp any any nd-ns permit icmp any any router-advertisement permit icmp any any router-solicitation remark MLD - query, report_v2 permit icmp any any mld-query permit icmp any any 143 which is being policed like this: class Icmp-v6 police 32000 60000 120000 conform-action transmit exceed-action drop I've worked around the issue by making a 4x increase in the policing, but the question I have is what happened at the exchange to provoke my COPP policy? Alternatively, is this normal or indicate who has the problem: r-pop-min-1#deb ipv6 icmp ICMP Packet debugging is on r-pop-min-1# Jul 17 14:36:08.143 CDT: ICMPv6: Received N-Solicit, Src=FE80::56E0:3200:50CE:4178, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.178 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.281 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.281 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.285 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.359 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.433 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.435 CDT: ICMPv6: Sent N-Solicit, Src=FE80::CA4C:75FF:FE23:805, Dst=2001:504:27::8252:0:1 Jul 17 14:36:08.459 CDT: ICMPv6: Received N-Advert, Src=2001:504:27::8252:0:1, Dst=FE80::CA4C:75FF:FE23:805 Jul 17 14:36:08.535 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.535 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:08.539 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.559 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.586 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.617 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.687 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.782 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.783 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:08.783 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 r-pop-min-1# Jul 17 14:36:08.842 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:08.990 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.028 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.070 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.148 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.191 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.203 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.322 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.322 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.327 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.399 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.439 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.481 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.533 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.572 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.572 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:09.581 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.608 CDT: ICMPv6: Received N-Solicit, Src=FE80::2E21:72FF:FE71:37B1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.613 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 r-pop-min-1# Jul 17 14:36:09.659 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.831 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:09.884 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.069 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.172 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.223 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.240 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.320 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.364 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.441 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.521 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.573 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.573 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.588 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::B664:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.622 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.659 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::8252:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.684 CDT: ICMPv6: Received N-Solicit, Src=FE80::221:9BFF:FE8A:D29D, Dst=FF02::1:FF00:1 Jul 17 14:36:10.817 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.830 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::3BA3:0:1, Dst=FF02::1:FF00:1 Jul 17 14:36:10.853 CDT: ICMPv6: Received type 130, Src=FE80::21B:DFF:FEE7:15C0, Dst=FF02::1 r-pop-min-1# Jul 17 14:36:10.908 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 Jul 17 14:36:10.925 CDT: ICMPv6: Received N-Solicit, Src=2001:504:27::D1AF:0:2, Dst=FF02::1:FF00:1 I'm thinking that the answer is that this is not normal, as it looks like I'm getting duplicate solicitations in the same second. -James ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

4 5

MICE UG 13 - Duluth July 24th Note 2PM start
by Mike Hemphill July 21, 2014

July 21, 2014

Good Afternoon All! MICE UG 13 has been scheduled, as follows: Date: Thursday, July 24th Time: 2:00 pm (1400 Hours) David Farmer has the facility reserved until 5PM Location: University of Minnesota, Duluth campus, Griggs Center, located in the *Kirby Student Center (KSC) * http://www.d.umn.edu/maps/KSC/ Please send your agenda items when you have a chance! Also please invite business & other entities that may have an interest in connecting to MICE. Our goal is to extend the reach of MICE connectivity to outstate institutions & companies. Thanks! Reid, Shaun & Mike *Mike Hemphill* *General Manager | **Cologix, Inc. <http://www.cologix.com/>* *511 11th Ave S, Suite 450 | Minneapolis, MN 55415P: 1+612.333.1922 | M: 1+612.812.5242mike.hemphill(a)cologix.com <mike.hemphill(a)cologix.com>* ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

6 5

Please welcome 702 Communications to MICE
by Jay Hanke July 10, 2014

July 10, 2014

Name: 702 Communications Port: CNS switch gi0/4 ASN: 15627 IPv4: 206.108.255.54/24 IPv6: 2001:504:27:0:0:3d0b::1/64 Peering Contact: dpoehls(a)702communications.com Route Servers and website please! Welcome aboard! -- Jay Hanke CEO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

2 1

Please Welcome Acentek to MICE
by Jay Hanke July 4, 2014

July 4, 2014

Acentek ASN: 40328 Port: Kato Remote Switch ge-0/0/15 IPv4: 206.108.255.109/24 IPv6: 2001:504:27:0:0:9D88::1/64 Peering contact: peering(a)acentek.net Estimated activation 8/1/14 Website and route servers please. Welcome aboard! -- Jay Hanke CEO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

3 2

a poll about operators (that's you) participating in the IETF
by Mike O'Connor June 14, 2014

June 14, 2014

hi all, thought that some of you might find this interesting. and some of you might want to blast through the poll. mikey http://www.circleid.com/posts/20140612_the_ietfs_other_diversity_challenge/ The IETF's *Other* Diversity Challenge Jun 12, 2014 10:32 AM PDT Comments: 0 Views: 1,013 Print Comment By Chris Grundemann The Internet Engineering Task Force (IETF) is the standards body for the Internet. It is the organization that publishes and maintains the standards describing the Internet Protocol (IP – versions 4 and 6), and all directly related and supporting protocols, such as TCP, UDP, DNS (and DNSSEC), BGP, DHCP, NDP, the list goes on, and on. In their own words: The mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. But how do they do that? How does the IETF produce documents, and ensure that they are high quality, relevant, and influential? Without going into too much boring detail here, the IETF uses a system of grassroots collaboration that is really quite revolutionary in many ways. The IETF is split into broad focus "Areas" and then again into specific "Working Groups" that each target a single problem or technical topic. While there is leadership at each level, the real power of the IETF is that all the real innovation and decision making happens out on the edges, from the bottom-up rather than the top-down. Combine this grassroots collaboration within each working group with the bottom-up decision making power vested in them and then add in the openness for anyone to join any working group any time, and you start to see the magic of the IETF. All work is contributed by individuals, all decisions are based on rough consensus and running code, and the whole thing "just works." But does it work as well as it could? Nothing is perfect, of course, so shouldn't we always strive for improvement? One area that can almost always be improved in any global organization is diversity. The great benefit of an open organization, like the IETF, is that anyone can have his or her voice heard. The great tragedy is that only those who speak up can ever be heard. This makes who is participating very important indeed. We want as many voices from as many backgrounds as possible to ensure the best achievable outcome. Without having all the right people involved, we run the risk of missing something key, for lack of their perspective. The IETF is already aware of the importance of diversity and steps are being taken to help ensure representation in the IETF from all areas of the world, and more equal representation from both genders. The Internet Society Fellows program helps bring folks from around the globe who wouldn't otherwise be able to participate to IETF meetings and there is a diversity design team with an open mailing list for community (that's you) feedback to help them in "identifying diversity related issues that the IETF faces and making practical recommendations that can help in this regard." I applaud these efforts! Each of us should contribute to them, and to the overall diversity dialogue, in every way we can. But I see another diversity issue at play in the IETF as well, and I've come to learn that I'm not alone. This "other diversity challenge" may be a bit more subtle and harder for those not familiar with the Internet industry to see. The physical differences between Operators, Vendors, and Academics are markedly less than those between men and women. The differences in perspective, however, may actually be far greater in both scope and scale. The differences in the way that someone actively running a network views a problem, and the way that same problem is seen by someone writing code for routers are significant. The same goes for either of those two and someone conducting network research. We need all three of these broad views, and all the myriad of views that each contain, informing our innovation and our decision making at the IETF. Currently, it seems, that is not entirely the case. Many believe that the level of operational input into the IETF is too low. That's not to say there are no operators at the IETF, nor to infer that the operators who do participate already are somehow inadequate. Quite the opposite. Just as the first women, or Latin Americans, or Africans, or Asians to participate in the IETF paved the way for more diversity, those operators who participate today, who have participated in the past — and especially those who have participated all along — have kept the door open for additional operator input. One shining example of this is the IEPG, or Internet Engineering and Planning Group, who meet the Sunday before every IETF meeting to discuss operational issues. How do we expand on that? How do we ensure that network operators, those folks responsible for keeping the packets flowing across their (service provider, enterprise, data-center, campus, cloud, etc.) networks, are always included in those who are working to influence the way we design, use, and manage the Internet? To answer that, my team at the Internet Society decided first to research the issue. We want to know if there are, in fact, barriers to operator involvement in the IETF, and if so, what they are. This is where *you* come in. We have an informal survey posted specifically to gather information from network operators about the IETF. We particularly want to hear from folks who are network operators but do not currently participate in the IETF; we want to know why! So if you operate a network, please take our survey, and whether you do or not, please share it as well. We want to hear from people you know, in your part of the world, as well as everywhere else! The survey will close after the last day of June. On the first of July we'll begin synthesizing everything we've heard. Then we'll present it back to the global network engineering community, to network operators the world round. We'll also present it to the IETF, to share our findings and amplify the voice of the operators. Once we know we've heard everything, and recorded it correctly, we'll start working on solutions to any identified problems. I believe we'll be able to classify the solutions we find based on who is needed to implement them. There will likely be a set of things that operators themselves, or more likely operator groups, can do to help. There will probably be another set of improvements or changes that the IETF itself can make to improve operator engagement and operational input. Finally, I think we may also find some things that the Internet Society can do to help facilitate these interactions. But before we can even think about solutions, we must first define the problems. Please help us in this effort, take and share this survey before 31 June 2014 (shortlink: http://bit.ly/opsietfsurvey) Thank you! By Chris Grundemann, Internet Technologist, Author, and Speaker. All opinions are his and his alone. More blog posts from Chris Grundemann can also be read here. PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

1 0

Please welcome Code42 to MICE
by Jay Hanke June 10, 2014

June 10, 2014

Name: Code42 ASN: 62715 Main switch port xe-0/0/19 IPv4: 206.108.255.32/24 IPv6: 2001:504:27:0:0:f4fb::1/64 Contact: peering(a)code42.com Route servers and website please. Welcome aboard! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

4 3

Akamai (20940) < > MICE IXP Brief Maintenance
by Hannigan, Martin June 9, 2014

June 9, 2014

Folks, You may have seen our traffic drop off. We are conducting a brief maintenance. Traffic should return to normal levels shortly. Best, -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: ?SUBED1=MICE-DISCUSS&A=1

1 1

Please welcome Monticello Fibernet to MICE
by Jay Hanke May 21, 2014

May 21, 2014

Monticello Fibernet will be connecting to port ge-0/0/8 of the Mankato Networks remote switch. I have assigned 206.108.255.108 for their IPv4 connection. Their ASN is pending with ARIN. Please update the website. I will send out another announcement with their ASN and IPv6 subnet as soon as the ASN has been assigned. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

Wrapping up my time at ICANN
by Mike O'Connor May 10, 2014

May 10, 2014

hi all, just a quick note to announce my retirement from ICANN. i know i haven’t deluged you with lots of posts and rumpus, but i did my best to represent the views of MICE while i was there. my focus was almost entirely on nudging ICANN to do a better job at the security and stability of the DNS. thanks for letting me do that. mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Port Security
by Jeremy Lumby May 6, 2014

May 6, 2014

At the last meeting there was a group that was going to email out the proposed process to secure the ports on the MICE switches. I was just wondering how that was coming along. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Summer MICE Joint meeting
by Jay Hanke April 12, 2014

April 12, 2014

I'd like to throw out MKE or Madison as a venue for the summer meeting. I also reached out to KCIX and they are interested in coming up. I sent an email to MBIX but haven't heard back yet. There is a fair amount of interest from the OpenIX folks. There is a fair amount of OpenIX activity across the border in IL. Wisconsin folks, can we get a sponsor (location/food)? Needs to be close to an airport -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

5 7

Website Update
by Richard Laager April 6, 2014

April 6, 2014

I've cut in the new website design (thanks MDU Ethernet!). If you see any problems, please let me know. -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

6 10

MICE Cacti Server - To Be Rebooted
by Justin Krejci March 27, 2014

March 27, 2014

As the server was not originally setup to run Cacti it does not have a desirable amount of CPU and RAM. Since it is a VM the process to upgrade the hardware is barely more time than a shutdown and boot up will take. I am going to do this shortly so the server/site will be offline for a few minutes and there'll be a small gap in the data possibly. I will try and time it to be in between polling intervals so it may not even miss any data. ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 2

UG 12 Minutes
by Shaun Carlson March 26, 2014

March 26, 2014

Please see attached. Talk to Reid if you have any questions. s *Shaun Carlson*Network Engineering Manager | Arvig ph: (218) 346-8673 | em: shaun.carlson(a)arvig.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

4 3

micemn-01.micemn.net route reflector at 206.108.255.1
by Doug McIntyre March 24, 2014

March 24, 2014

We've noticed this being unresponsive several times this evening. I'm into the machine, but it is behaving badly, and from past experience, (and not direct evidence since it is remote and I can't get the relavent logs), it feels like a hard drive failing on this system. Ie. it may run some of its process out of memory for some functions, but other functions are probably locking up and not behaving correctly. Even RAIDed as it is. Probably the best course of action is to bring out a fresh drive to it and swap whatever drive is failing and let the mirror rebuild. I think we've got some of the 80GB WD800AAJS that is part of the mirror on the other route reflector around somewhere... -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

6 15

MICE User Group meeting next Wednesday
by Mike Hemphill March 21, 2014

March 21, 2014

All, Just a quick meeting reminder for our upcoming UG meeting on Wednesday, March 26th at 4:00 PM in the 511 Building cafeteria. Please send Shaun, Reid and me any agenda items you may have or any topics you want to be sure are covered. We currently do not have a sponsor for food & beverages, if your company is willing to step up, please let us know. Thanks! Mike Mike Hemphill General Manager | *Cologix, Inc.* <http://www.cologix.com/> 511 11th Ave S, Suite 450 | Minneapolis, MN 55415 P: 1+612.333.1922 | M: 1+612.812.5242 mike.hemphill(a)cologix.com ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

10 13

Akamai (20940) < > MICE IXP Upgrade to 2x10G
by Hannigan, Martin March 20, 2014

March 20, 2014

Everyone, All paperwork has been completed and Akamai will be upgrading to 20G. FYI. Best Regards, Martin Hannigan Director, Network and Data Center Architecture Akamai Technologies, Inc. ASN 20940 ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

Please Welcome Radio Link Internet to MICE
by Jay Hanke March 19, 2014

March 19, 2014

main switch: xe-0/0/17 Radio Link Internet AS: 53301 206.108.255.31/24 2001:504:27:0:0:d035::1/64 daniel.petsinger(a)radiolinkinternet.com Prefix Limit 25 They will be providing an optic for their 10G fiber connection. Route-server and defaulting graphing please. Thanks! -- Jay Hanke CTO, CCIE #19093 Mankato Networks LLC PO Box 54 619 S Front St Mankato, MN 56001-3838 Google 530-618-2398 jayhanke(a)mankatonetworks.net http://www.mankatonetworks.com http://www.neutralpath.net ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1

NTIA announcement about ICANN transition to independent entity
by Mike O'Connor March 15, 2014

March 15, 2014

hi all, i’m presuming most of you have seen the NTIA announcement by now. since i hang “MICE" on my nametag when i participate in ICANN meetings, i thought i’d push along some observations, and some links to detailed info that may not find its way into the press coverage. the announcement: http://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition… WASHINGTON – To support and enhance the multistakeholder model of Internet policymaking and governance, the U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) today announces its intent to transition key Internet domain name functions to the global multistakeholder community. As the first step, NTIA is asking the Internet Corporation for Assigned Names and Numbers (ICANN) to convene global stakeholders to develop a proposal to transition the current role played by NTIA in the coordination of the Internet’s domain name system (DNS). the FAQ on ICANN’s site; http://www.icann.org/en/about/agreements/iana/functions-transfer-faqs-14mar… want to know a LOT about these issues (like PhD level)? Here’s Samantha Dickinson’s summary of a boatload of submissions from all over the place that’s going into the upcoming Net Mundial meeting in Brazil. read all these (like i am right now) and you’ll know where the proposals lie. http://linguasynaptica.com/netmundial-submissions-on-iana/ my view is mostly “keep calm and peer on.” i’m hoping the transition could be the same level of non-event that taking down the NSF backbone network was. on the other hand, we don’t know how this is actually going to turn out until it’s done. the fearmongers in Washington aren’t being helpful. my view “from the bottom of the bottom-up process” is that i’ll be an interested observer and i’ll probably continue to put most of my energy into the day-to-day policy stuff. that’s the stuff that makes ICANN legitimate. i was on a conference call this morning where the CEO (Fadi Chehadi) and the Chair of the Board (Steve Crocker - author of RFC 0001) talked to community members about what’s going on. the points i raised were mostly about bandwidth (the community is already really overloaded) and process (a good project plan would be nice). happy to try to answer questions, although i’m still coming up to speed myself — this came as a surprise to almost everybody. i’m headed to the ICANN meeting in Singapore (leaving this Wednesday, back the following Friday). the outlines will be clearer after that. mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.) ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

DDoS Attacks
by Richard Laager March 13, 2014

March 13, 2014

Last night, we got hit by a ~3 Gbps DDoS attack. It's been a while since this has happened to us, so I'd like to make sure I'm still up on the state of the art. Is there anything more to be done than the following? 1. Identify the victim. 2. Null route the victim. 3. Propagate the null route to your upstreams (via BGP, if supported, otherwise a phone call to their NOC). 4. Move the victim to a new IP. To avoid participating in at least some classes of DDoS attacks, we: * long ago implemented uRPF (and/or similar ACLs) to block spoofed outbound packets, as recommended by BCP 38 (RFC 2827). * ensured our NTP servers (and any NTP servers of our customers) are not responding to monlist queries. The openntpproject.org website is useful here. They list vulnerable NTP servers by IP range, or you can get all NTP servers by AS (replace YOUR_AS with your AS, and optionally, add &csv=1) and then query with ntpdc -n -c monlist IP: http://openntpproject.org/searchby-asn.cgi?search_asn=YOUR_AS * just this week started addressing customers with open DNS resolvers, which can also be used in amplification attacks: http://openresolverproject.org/searchby-asn.cgi?search_asn=YOUR_AS Is there anything else we should be doing? -- Richard ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

4 3

Re: bgp flapping to 206.108.255.1
by Frank DiGravina March 13, 2014

March 13, 2014

Hello, I am shutting our peering to 206.108.255.1 until I see notice that that your route-reflector issue has been addressed. Thanks, Frank -- Frank DiGravina University of Minnesota Networking & Telecommunications Network Operations Phone: 612-626-9074 Cell: 612-386-0449 E-Mail: digravin(a)umn.edu Helpline: 612-301-HELP ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

XO issues Sunday morning?
by Frank Bulk March 10, 2014

March 10, 2014

This isn't a MICE-related question, but since so many MICE members are in the Minnesota area I thought I would ask. Sunday morning from 1:11 am to about 4:20 am we saw an unusually high number of websites time out over IPv6. We monitor 50 IPv6-enabled web sites over IPv6, performing both an ICMP check (if possible) and then HTTP over IPv6. There were at least 17 sites during that time frame that timed out on our monitoring systems' HTTP GET request. One pattern emerged -- 14 of them traceroute through an XO link that goes through Minneapolis. Here's a sample: traceroute to ipv6.test.Level3.com (2001:1900:2018:3000::105) from 2607:fe28:0:1000::5, port 80, from port 36274, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.395 ms 0.325 ms 0.319 ms 2 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 0.188 ms 0.135 ms 0.185 ms 3 v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1) 1.612 ms 1.545 ms 1.613 ms 4 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 6.667 ms 6.566 ms 8.002 ms 5 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 6.624 ms 7.995 ms 6.602 ms 6 2610:18:18b:c000::11 (2610:18:18b:c000::11) 12.108 ms 12.075 ms 12.137 ms 7 mcr1.minneapolis-mn.us.xo.net (2610:18::30b8) 21.431 ms 21.452 ms 21.421 ms 8 vb1710.rar3.chicago-il.us.xo.net (::ffff:216.156.0.169) 30.701 ms 23.639 ms 23.771 ms .... I then looked at the daily traceroutes we have on file for all 50 sites we monitor and it looks like 15 of them go through XO. So over 93% (14 out of 15) of the sites that go through XO timed out during the 1:11 am to 4:20 am time period. Did anyone with XO connectivity see issues Sunday morning? Frank ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

1 0

2 x 10GE Contact?
by Hannigan, Martin March 7, 2014

March 7, 2014

Who can I talk to about adding a second 10G? Best, , -M< ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

2 1