- mice-discuss - lists.micemn.net

Non-Profit Status
by Richard Laager Sept. 20, 2016

Sept. 20, 2016

I'd like to request the board provide an actual update on the non-profit status, preferably here before the meeting. I've been mailing off-list regularly since the last UG, and the answer seems to be that: 1) We need to get some form to someone (lawyers or IRS?). 2) This form may need some financial details. 3) The board member responsible for this is busy and will do this "next week". It's been "next week" every time. Another member tells me off-list that they've been doing the same thing, for the same amount of time, and are getting the same answer. I've so far avoided commenting publicly, but enough is enough. We need to move this along. -- Richard

4 4

Proposed Membership and Sponsorship Model
by David Farmer Sept. 19, 2016

Sept. 19, 2016

I'm not a candidate and will not be a candidate for the Board. However, I propose the following Membership and Sponsorship Model, including both Membership Dues and Sponsorship levels for MICE Members and Non-Member Sponsors. The dollar values are just my suggestions, I think they should work but they are primarily intended to illustrate the model. With this Model, any network may connect to the Exchange, but all networks participating in governance, known as Members, will have some minimal skin-in-the-game. Further, the Model implies Networks with 10G or larger ports probably should participate at a more significant level, but this is not a requirement for access to 10G or larger ports or even to participate in governance. The Friends of MICE Sponsorship level is intended to be accessible to anyone interested, including individual users of the Internet. My proposal; As an Open Internet Exchange any network with a uniquely registered Autonomous System Number (ASN) may connect to MICE. However, Non-Member networks are provided ports on the Exchange on an as-available basis only and Non-Members do not participate in the governance of the Exchange or the MICE Organization, but may observe and participate in its discussions. Networks connected to the Exchange, or Data Centers hosting an Exchange switch, may become Members and participate in the governance of the Exchange and the MICE Organization by paying Membership Dues at either level listed below. Members are provided prefered access to 1G Exchange ports, and are provided access to 10G or larger Exchange ports on an as-available basis. Sustaining or higher Members are committed to sustaining and growing the Exchange by electing to pay Sustaining Membership Dues and/or paying Basic Membership Dues and providing other Sponsorship to the Exchange of a value totaling $1000 or more. In recognition to this additional commitment, Sustaining or higher Members are provided prefered access to 10G or larger Exchange ports. Basic Membership Dues - $100 Sustaining Membership Dues - $1000 (Dues are paid in cash or cash equivalents only, and may not be provided through in-kind services or equipment) Beyond Dues from Members, MICE accepts Sponsorship both from Members and Non-Members Sponsors as cash, cash equivalents, in-kind services or equipment. Sponsorship is recognized at the following escalating levels based on the total value provided annually. Friends of MICE - Sponsorship of $50 ore more annually Sustaining Members or Sponsors - Sponsorship of $1,000 or more annually Silver Members or Sponsors - Sponsorship of $2,500 or more annually Gold Members or Sponsors - Sponsorship of $5,000 or more annually Platinum Members or Sponsors - Sponsorship of $10,000 or more annually Sponsorship of $20,000 or more are recognized with multiple years at the Platinum level. Friends of MICE are list on a page on the MICE website. Sustaining or higher Members are annotated as such in their listings on the MICE website. All Sustaining or higher Members and Sponsors are listed on the MICE website, with higher levels receiving more prominent placement. Silver or higher Members and Sponsors are recognized in MICE marketing materials, with higher levels receiving more prominent placement. Thanks -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================

13 18

FW: How do I start an Internet Exchange Point?
by Michael Hemphill Sept. 17, 2016

Sept. 17, 2016

Hello MICE people, I saw this post on LinkedIn today & thought it may offer some more help and/or confusion to the current discussions. Mike Mike Hemphill ColoConnect 612-812-5242 mikeh(a)ColoConnect.net<mailto:mikeh@ColoConnect.net> [Kurt-Erik "Kurtis" Lindqvist]<https://www.linkedin.com/in/klindqvist>Kurt-Erik "Kurtis" Lindqvist<https://www.linkedin.com/in/klindqvist>CMO at LINX ( The London Internet Exchange) How do I start an Internet Exchange Point? September 17, 2016 • 13 Likes • 3 Comments I have been involved in helping a lot of Internet Exchange Points (IXPs) get of the ground and I have also been to several countries and regions to help IXPs to prosper and sometimes even to explain to the IXP, the members and the regulators why things have failed. I have helped IXPs in Europe, Asia, the Middle East and even North America. In addition to this I have together with Philip Smith and others thought numerous classes for APRICOT<http://www.apricot.net/>s, MENOG<http://www.menog.org/>s, ISOC<http://www.isoc.org/>, AfPIF<http://www.internetsociety.org/events/afpif> and others on how routing, IXPs and peering work. Because of this involvement I very often get asked advice by people wanting to establish an IXP or even newly formed IXPs. At LINX we are always very supportive of new IXPs being formed, and we try and contribute as much as we can. For those wanting to start an IXP I thought I would write up some comments that observations I have made over the years and post it here. There are already a large number of resources for new IXPs, and I will also list some of these considerations below. Establishing the IXP The hard part with establishing an IXP is not really the technical part, but building up a community and a community with trust with that. Also, an IXP needs to be sustainable beyond the establishment phase, i.e. have enough funds to operate, and in the future upgrade the equipment they need as technology develops and traffic grows. Most IXPs ensure this by setting up a mutual or membership association so that the users of the IXP have equal say in the operation of the IXP. This is by far the most successful model of IXPs today. The members pay a fee based on their port size to the association, so one fee for a 1GE port and one for a 10GE port. Not based on the actual traffic, but the port speed. The membership all have one vote each in the running of the organisation and normally appoints a board for the day to day operation of the IXP. Secondly, new IXPs tend to believe it is a good idea to offer free ports to large content networks in order to attract other members. At first glance this might seem like a good idea, but you will quickly find yourself squeezed between the content networks and the broadband operators that then also want their ports for free. Generally it is better to charge everyone equally and threat everyone equally. It might make it slightly harder for the IXP to get off the ground but it certainly makes running the IXP easier in the long run. Most of the large content owners are also quite supportive of new IXPs being formed in locations or regions where no IXP exists. Thirdly, what is very important is to ensure that the IXP does not in any way interfere with the peering arrangements across the IXP. If the members want to for example sell transit to each other across the IXP, that is fine. If someone only want to peer with a subset of the members, that is also fine. Selecting the location for your IXP Besides creating the community in order to support the IXP, the other important factor for establishing a successful IXP is the location. Successful IXPs needs to be accessible for everyone so a neutral datacenter, where any fibre infrastructure can be build in. These locations can be hard to find, but are very critical for the success. The wider the choice of fibre providers (or wlan for that matter in some parts of the world) and choice of carriers that are available, the better. Datacenters owned by current or former incumbents are not good choices as they generally tend to be very restrictive in what choice of infrastructure providers they offer. Besides easy infrastructure access, the datacenter also needs to provide a stable power feed, or you need to ensure you have UPSes and perhaps even generators (depending on ambition, stability of power grid and if the datacenter provides generator power). Also make sure there is room to grow the IXP. You might only two racks to start with, but if you are successful you might need more and moving the IXP is always painful. What type of switch do I need? There is an excellent presentation<http://ripe71.ripe.net/presentations/30-1000-dollar-exchange-ripe71.pdf> by Remco van Mook that covers many of the same topics as this post, and that also points out that ~50% of IXPs carry less than 20Gbps of traffic. As a new start-up IXP you will most certainly carry less than 20Gbps. What you need is a switch that will support 1GE and 10GE ports, preferably via SFPs, not an expensive and large switch with massive amount of features (although the vendors will try and sell you one). Instead, make sure you get a switch that you can manage and that you can monitor. These are the most important components of an IXP switch. Co-location of services For the benefit of the membership of your IXP as well as the local Internet community, you should co-locate some critical shared resources with the IXP. The most important ones are * The local ccTLD slave service (i.e .uk, .fr, .sg, .bd etc). If the ccTLD registry is supportive of the IXP, the contact them and ask if they are willing to locate one of their unicast slaves behind your IXP router. Never connect the DNS slaves directly to IXP L2 domain. * It is likely that the ccTLD registry also uses an anycast provider for their slave service. In that case it might be worth contacting that DNS anycast provider and ask them to connect to the IXP. You should in any cast contact the DNS anycast providers as they are more than happy to peer at many of the IXPs. Many of these also operate or provide service to one the DNS root-servers. These are a critical part of the internet infrastructure and having one co-located with your IXP will provide a lot of value to your local Internet community. PCH<http://www.pch.net/>, Verisign<http://www.verisign.com/> and Netnod<http://www.netnod.se/> are some of the DNS Anycast providers that locate nodes around the world. * Route-servers are also important to offer to your members, especially as you start to grow. The most stable software for route-servers today is BIRD<http://bird.network.cz/>. Providing two route-servers also adds redundancy as if one fails, the peering sessions will go down. Last, some IXPs offer NTP services as part of the IXP to their community. This is a very good service, and something that the community should make use of. However, for a new start-up IXP, NTP services is quite expensive to provide and definitely not needed at the first stage. Managing my IXP and members The guys over at INEX<http://www.inex.ie/> has created an amazing tool called The IXP Manager<http://www.inex.ie/ixp/index/about> that provides you all the software you need to mange your IXP and the tools for your members. This is really an amazing resource that you should use for setting up the IXP! How do I know if my IXP is a success? What makes an IXP successful varies very much from each individual case. A small land-locked country where all ISPs or Internet Operators are forced to use Satellite capacity for Internet access will benefit enormously from an IXP no matter how little traffic that is exchanged, as each bit is a huge saving! Value of peering is always in the eye of the beholder. Access to one single route or Internet prefix can be extremely valuable to one ISP, while another might need large traffic volumes before it creates value to them. In the end a successful IXP is defined by the membership. If there is a community that uses and continuous to see benefit from the IXP they will continue to support it. By being stable and sustainable the IXP is successful! Other resources IXP Associations * IX-F<http://www.ix-f.net/> * Euro-IX<http://www.euro-ix.net/> * APIX<http://apix.asia/> * LACIX<http://www.lac-ix.net/> * AF-IX<http://www.af-ix.net/> The IXP toolkit<http://www.ixptoolkit.org/> is a collection of resources for IXPs. The Euro-IX movie<http://youtu.be/QuBde4Sn3f0> is a great resource for explaining in a non-technical manner how an IXP works and what it does. You are always welcome to contact me for questions and advice! Written by [Kurt-Erik "Kurtis" Lindqvist]<https://www.linkedin.com/in/klindqvist>Kurt-Erik "Kurtis" Lindqvist<https://www.linkedin.com/in/klindqvist>CMO at LINX ( The London Internet Exchange) 3 comments [ ] 2h [https://media.licdn.com/mpr/mpr/shrink_100_100/AAEAAQAAAAAAAAltAAAAJDMwNWY0…]<https://www.linkedin.com/in/ivanbev> Ivan Beveridge<https://www.linkedin.com/in/ivanbev> Seeking network/systems opportunities in… Typo correction: Establishing the IXP .... "Generally it is better to charge everyone equally and threat everyone equally" - threat -> treat LikeReply 2h [https://media.licdn.com/mpr/mpr/shrink_100_100/p/2/000/03f/0cb/2aae6f1.jpg]<https://www.linkedin.com/in/muhammad-aslam-1868a15> Muhammad Aslam<https://www.linkedin.com/in/muhammad-aslam-1868a15> Chief Operating Officer at ADRAS Great article - mostly the technical would agree with the points mentioned in the article including the Remco van Mook presentation in terms of the technical and costing matrix. The biggest dilemma with the developing economies would be that their consulting partner being ITU that provides different approach towards the setup of IXP , so the question would be how to convin… See more LikeReply 1 1h [https://media.licdn.com/mpr/mpr/shrink_100_100/AAEAAQAAAAAAAAltAAAAJDMwNWY0…]<https://www.linkedin.com/in/ivanbev> Ivan Beveridge<https://www.linkedin.com/in/ivanbev> Seeking network/systems opportunities in… You say "ITU that provides different approach towards the setup of IXP". Can you elaborate? What is their approach? LikeReply 1h [https://media.licdn.com/mpr/mpr/shrink_100_100/AAEAAQAAAAAAAAltAAAAJDMwNWY0…]<https://www.linkedin.com/in/ivanbev> Ivan Beveridge<https://www.linkedin.com/in/ivanbev> Seeking network/systems opportunities in… Good article, highlighting important topics and linking to additional resources. I guess the particularly tricky part comes when wishing to setup in areas where there are few/no neutral colocation centres. I suspect such instances need to be treated on a case-by-case basis; is this what you/people (eg Bill, Gaurab, etc) have found?

1 0

Wikstrom Telephone MICE Port Move
by Jason Hanke Sept. 9, 2016

Sept. 9, 2016

Wikstrom Telephone is moving their connection from the Mankato Networks Remote Switch to the Main Switch The new port will be xe-2/0/6 on the main stack. IP information will remain the same. Welcome aboard (again)! -- 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

1 0

Richard Laager Board Seat
by Jason Hanke Sept. 9, 2016

Sept. 9, 2016

Richard Laager has thrown his hat in the ring for the open MICE board seat. -- 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

Candidate Question
by Jason Hanke Sept. 8, 2016

Sept. 8, 2016

Question for all candidates- Up to this point MICE has been fairly successful without any required port fees for members. There have been minor difficulties paying hardware support and annual ARIN fees. We have reached a long-term (5 year) agreement with Cologix to continue the existing no cost relationship for space and power. Do you see the finical current model as sustainable for MICE? What changes would you suggest on the business side? -- 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 15

MICE UG/Elections
by Jason Hanke Sept. 7, 2016

Sept. 7, 2016

We will be holding elections at the MICE UG on September 27th. As of now we have two candidates listed in the spreadsheet. Owen Delong (Akamai) James Renken (ipHouse) If your name is missing from the list or you would like to be on the list please email peering(a)micemn.net. The nomination period will close September 20th. Also, please RSVP to the Facebook event if you're planning to attend. https://www.facebook.com/events/1734560673466829/ Thanks! -- 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 5

MICE Traffic Growth
by Jason Hanke Sept. 2, 2016

Sept. 2, 2016

Using the double counting method, MICE ran 176 Gbps using 30 minute averages Sunday night. I believe we might be the second largest non-profit ix in the US by traffic behind the SIX. Does anyone have an easy way to verify? -- 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 3

Member traffic drop
by Jason Hanke Sept. 1, 2016

Sept. 1, 2016

We're seeing a number of western MN and SD networks drop off of MICE. Is there a cut someplace? -- 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

Martin Hannigan Paypal Donation
by Jason Hanke Aug. 31, 2016

Aug. 31, 2016

Marty Hannigan has donated $300 to MICE! Thanks for your support! -- 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

1 0

MICE Pull up banner
by Jason Hanke Aug. 29, 2016

Aug. 29, 2016

Does anyone know where the MICE pull up banner is? -- 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 MN Cologix Event
by Jason Hanke Aug. 29, 2016

Aug. 29, 2016

Is anyone interested in working with me in the MICE booth at the Cologix Connect MN event? Wednesday, September 7th from 4:00 - 8:00 p.m. @ the U.S. Bank Stadium -- 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

6 9

Prefix count
by Frank Bulk Aug. 27, 2016

Aug. 27, 2016

We had a max IPv4 prefix count of 2000 with a warning when it hit 90%. At 10:20 am our BGP session was torn down when it apparently exceeded 2000: Aug 18 14:09:18 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:09:18 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:14:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:14:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:19:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:19:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:24:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:24:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 18 14:29:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 18 14:29:17 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:12:20 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:12:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:17:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:17:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:22:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:27:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:27:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 06:32:19 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1: exceeds warning limit 1800 Aug 21 06:32:50 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2: exceeds warning limit 1800 Aug 21 10:20:10 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.1 exceeds maximum prefix limit...shutdown Aug 21 10:20:10 192.168.0.85 BGP: Peer 206.108.255.1 DOWN (Peer had exceeded the prefix limit) Aug 21 10:20:11 192.168.0.85 BGP: No. of prefix received from BGP Peer 206.108.255.2 exceeds maximum prefix limit...shutdown Aug 21 10:20:11 192.168.0.85 BGP: Peer 206.108.255.2 DOWN (Peer had exceeded the prefix limit) The Cacti graph (http://micelg.usinternet.com/cacti/graph.php?action=view&local_graph_id=236…) doesn't show that ... but is there any further confirmation that there was a short burst in routes advertised by the RR's? Frank

2 2

MICE gets a shout-out in CloudFlare blog
by Frank Bulk Aug. 19, 2016

Aug. 19, 2016

https://blog.cloudflare.com/bandwidth-costs-around-the-world/ Frank

2 1

Stealth Broadband Updated Information
by Jason Hanke Aug. 18, 2016

Aug. 18, 2016

Stealth Broadband has received their ASN from ARIN, Please update ASN and IPv6 information in the route-servers and website: Name: Stealth Broadband IPv4: 206.108.255.69/24 IPv6: 2001:504:27:0:6:07BA::1/64 ASN: 395194 Port: NP MSP1 Remote ge-0/0/2 Contact: james.urwiller(a)stealthbroadband.net Thanks! -- 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

ipHouse Remote Switch
by Jason Hanke Aug. 11, 2016

Aug. 11, 2016

Is there any update on the ipHouse remote switch? -- 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

Airstream Communications Maintenance 2016/08/11
by Charles Monson Aug. 10, 2016

Aug. 10, 2016

Good Afternoon, Airstream Communications (AS11796) will be performing maintenance tonight 2016/08/11 between the hours of Midnight and 6am. We will be shutting down our BGP sessions for approximately 20 minutes to reroute traffic while work is done and turning them back up when complete. If your session to us has not returned by 6am please send an email to support(a)wins.net<mailto:support@wins.net> with your BGP AS number and we will address it as soon as possible. Charles Monson Associate Network Administrator, Airstream Communications (AS11796)

1 0

BGP sessions down...
by Frank Bulk Aug. 9, 2016

Aug. 9, 2016

Problem at MICE? Physical link is up. Frank -----Original Message----- From: nagios(a)nagios.mtcnet.net [mailto:nagios@nagios.mtcnet.net] Sent: Thursday, August 04, 2016 4:53 PM To: Frank Bulk <fbulk(a)mypremieronline.com> Subject: PROBLEM: CRITICAL alert for Premiers Spencer-facing Brocade MLXe-4 router/BGP ***** Nagios ***** This is a PROBLEM notice that Premiers Spencer-facing Brocade MLXe-4 router/BGP is CRITICAL Date/Time: Thu Aug 4 16:52:57 CDT 2016 Additional Info: CRITICAL: critical 2, warning 6 Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the BGP peer state is in state connect Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the BGP peer state is in state connect Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the elapsed time the remote peer has been in the Established state or how long since this peer was last in the Established state changed from 39 days, 19 hours, 41 minutes, 12 seconds to 0 seconds Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the elapsed time the remote peer has been in the Established state or how long since this peer was last in the Established state changed from 23 days, 4 hours, 33 minutes, 7 seconds to 0 seconds Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the number of received route prefixes changed from 1763 to 0 Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: 0 learned prefixes is less than the specified minimum of 1 Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the number of received route prefixes changed from 10 to 0 Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: 0 learned prefixes is less than the specified minimum of 1 Host 192.168.0.85 with interface to BGP peer AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: the number of installed route prefixes changed from 1763 to 0 Host 192.168.0.85 with interface to BGP peer AS29040.micemn.net [206.108.255.84/AS 20940]: the number of installed route prefixes changed from 10 to 0 BGP state of premier.spnc-mlx.fbnt.netins.net [173.215.60.1/AS 18883]: established; prefixes (received/installed): 1/1 BGP state of AS53679-MRS-1.micemn.net [206.108.255.1/AS 53679]: established; prefixes (received/installed): 1769/1769 BGP state of AS53679-MRS-2.micemn.net [206.108.255.2/AS 53679]: connect; prefixes (received/installed): 0/0 BGP state of AS6939.micemn.net [206.108.255.52/AS 6939]: established; prefixes (received/installed): 92186/91624 BGP state of AS29040.micemn.net [206.108.255.84/AS 20940]: connect; prefixes (received/installed): 0/0

3 5

route servers - bogon ASN filtering
by Andrew Hoyos Aug. 8, 2016

Aug. 8, 2016

Hi all, We recently implemented bogon ASN filtering on all transit/peering edges (see http://mailman.nanog.org/pipermail/nanog/2016-June/086078.html) There were a few participants we peer with via route servers that had bogon ASN’s in path for various prefixes which we are now rejecting. I’d suggest that we look at adding similar filtering to the route-servers as well, similar to RFC1918 filters already in place. Thoughts? — Andrew Hoyos Hoyos Consulting LLC ofc: +1 608 616 9950 andrew(a)hoyosconsulting.com http://www.hoyosconsulting.com

3 2

Re: Please welcome Yahoo to MICE!
by Jason Hanke Aug. 3, 2016

Aug. 3, 2016

Send me the optics and I'll get them installed: Neutral Path Communications Attn: Jay Hanke 3 Civic Center Plaza, STE 204 Mankato, MN 56001 On Wed, Aug 3, 2016 at 4:00 PM, Russell Lohr <lohr(a)yahoo-inc.com> wrote: > Jason, > > Zayo will be placing the Xconnect orders on Yahoo's behalf. > > Russell Lohr > Tech Yahoo| Network Eng > 404-422-5932 cell > 701 First Avenue Sunnyvale CA 94089 > lohr(a)yahoo-inc.com > > > ________________________________ > From: Jason Hanke <jayhanke(a)neutralpath.net> > To: Russell Lohr <lohr(a)yahoo-inc.com> > Cc: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Mehmet Akcin > <akcin(a)yahoo-inc.com>; Josh Lepold <josh.lepold(a)zayo.com> > Sent: Wednesday, August 3, 2016 1:52 PM > > Subject: Re: Please welcome Yahoo to MICE! > > Is Yahoo placing the orders for the cross connects in Minneapolis or > is Zayo doing that on behalf of Yahoo? > > On Wed, Aug 3, 2016 at 3:49 PM, Russell Lohr <lohr(a)yahoo-inc.com> wrote: >> Jay, >> >> Sir, in regards to the optics, that you require, where do I need to have >> these optics sent, please advise address and c/o person and we will drop >> ship the optics. Please let me know. >> >> Russell Lohr >> Tech Yahoo| Network Eng >> 404-422-5932 cell >> 701 First Avenue Sunnyvale CA 94089 >> lohr(a)yahoo-inc.com >> >> >> ________________________________ >> From: Jason Hanke <jayhanke(a)neutralpath.net> >> To: Russell Lohr <lohr(a)yahoo-inc.com> >> Cc: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Mehmet Akcin >> <akcin(a)yahoo-inc.com>; Josh Lepold <josh.lepold(a)zayo.com> >> Sent: Tuesday, August 2, 2016 12:41 PM >> Subject: Re: Please welcome Yahoo to MICE! >> >> Juniper part EX-SFP-10GE-LR or compatible >> >> We strongly recommend an optic with DOM. >> >> Thanks! >> >> On Tue, Aug 2, 2016 at 2:37 PM, Russell Lohr <lohr(a)yahoo-inc.com> wrote: >>> Jason, >>> >>> Hello sir, I have been asked to come back to you and ask what the model# >>> or >>> SKU that you use, I was asked to get this from you so that we know what >>> to >>> provide back to you. Please let me know. >>> >>> Russell Lohr >>> Tech Yahoo| Network Eng >>> 404-422-5932 cell >>> 701 First Avenue Sunnyvale CA 94089 >>> lohr(a)yahoo-inc.com >>> >>> >>> ________________________________ >>> From: Jason Hanke <jayhanke(a)neutralpath.net> >>> To: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Mehmet Akcin >>> <akcin(a)yahoo-inc.com>; Josh Lepold <josh.lepold(a)zayo.com>; Russell Lohr >>> <lohr(a)yahoo-inc.com> >>> Sent: Tuesday, August 2, 2016 7:51 AM >>> Subject: Please welcome Yahoo to MICE! >>> >>> Yahoo will be connecting to two 10G ports with NO LAG Config. >>> >>> Name: Yahoo >>> ASN: 10310 >>> Contact: peering(a)yahoo-inc.com >>> >>> Port: xe-0/2/0 (main switch) >>> IPv4: 206.108.255.58/24 >>> IPv6: 2001:504:27:0:0:2846::1/64 >>> >>> Port: xe-2/0/5 (main switch) >>> IPv4: 206.108.255.59/24 >>> IPv6: 2001:504:27:0:0:2846::2/64 >>> >>> Yahoo- >>> >>> This email will serve as your LOA/CFA. Please provide a Juniper >>> compatible SFP+ optic for each of your connections to be installed in >>> the MICE Ethernet switch. >>> >>> Route Server and web server configuration please! >>> >>> 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 > >> >>> >>> >> >> >> >> -- >> 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 >> >> > > > > -- > 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 > > -- 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

1 0

Re: Please welcome Yahoo to MICE!
by Jason Hanke Aug. 3, 2016

Aug. 3, 2016

Is Yahoo placing the orders for the cross connects in Minneapolis or is Zayo doing that on behalf of Yahoo? On Wed, Aug 3, 2016 at 3:49 PM, Russell Lohr <lohr(a)yahoo-inc.com> wrote: > Jay, > > Sir, in regards to the optics, that you require, where do I need to have > these optics sent, please advise address and c/o person and we will drop > ship the optics. Please let me know. > > Russell Lohr > Tech Yahoo| Network Eng > 404-422-5932 cell > 701 First Avenue Sunnyvale CA 94089 > lohr(a)yahoo-inc.com > > > ________________________________ > From: Jason Hanke <jayhanke(a)neutralpath.net> > To: Russell Lohr <lohr(a)yahoo-inc.com> > Cc: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Mehmet Akcin > <akcin(a)yahoo-inc.com>; Josh Lepold <josh.lepold(a)zayo.com> > Sent: Tuesday, August 2, 2016 12:41 PM > Subject: Re: Please welcome Yahoo to MICE! > > Juniper part EX-SFP-10GE-LR or compatible > > We strongly recommend an optic with DOM. > > Thanks! > > On Tue, Aug 2, 2016 at 2:37 PM, Russell Lohr <lohr(a)yahoo-inc.com> wrote: >> Jason, >> >> Hello sir, I have been asked to come back to you and ask what the model# >> or >> SKU that you use, I was asked to get this from you so that we know what to >> provide back to you. Please let me know. >> >> Russell Lohr >> Tech Yahoo| Network Eng >> 404-422-5932 cell >> 701 First Avenue Sunnyvale CA 94089 >> lohr(a)yahoo-inc.com >> >> >> ________________________________ >> From: Jason Hanke <jayhanke(a)neutralpath.net> >> To: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Mehmet Akcin >> <akcin(a)yahoo-inc.com>; Josh Lepold <josh.lepold(a)zayo.com>; Russell Lohr >> <lohr(a)yahoo-inc.com> >> Sent: Tuesday, August 2, 2016 7:51 AM >> Subject: Please welcome Yahoo to MICE! >> >> Yahoo will be connecting to two 10G ports with NO LAG Config. >> >> Name: Yahoo >> ASN: 10310 >> Contact: peering(a)yahoo-inc.com >> >> Port: xe-0/2/0 (main switch) >> IPv4: 206.108.255.58/24 >> IPv6: 2001:504:27:0:0:2846::1/64 >> >> Port: xe-2/0/5 (main switch) >> IPv4: 206.108.255.59/24 >> IPv6: 2001:504:27:0:0:2846::2/64 >> >> Yahoo- >> >> This email will serve as your LOA/CFA. Please provide a Juniper >> compatible SFP+ optic for each of your connections to be installed in >> the MICE Ethernet switch. >> >> Route Server and web server configuration please! >> >> 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 > >> >> > > > > -- > 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 > > -- 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

1 0

Please welcome Yahoo to MICE!
by Jason Hanke Aug. 3, 2016

Aug. 3, 2016

Yahoo will be connecting to two 10G ports with NO LAG Config. Name: Yahoo ASN: 10310 Contact: peering(a)yahoo-inc.com Port: xe-0/2/0 (main switch) IPv4: 206.108.255.58/24 IPv6: 2001:504:27:0:0:2846::1/64 Port: xe-2/0/5 (main switch) IPv4: 206.108.255.59/24 IPv6: 2001:504:27:0:0:2846::2/64 Yahoo- This email will serve as your LOA/CFA. Please provide a Juniper compatible SFP+ optic for each of your connections to be installed in the MICE Ethernet switch. Route Server and web server configuration please! 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

NP Remote Switch upgrade to 2x10G LAG
by Jason Hanke Aug. 3, 2016

Aug. 3, 2016

Neutral Path is upgrading the back haul to 2x10G from a single 10G today. The new port allocation on the main switch is xe-0/2/1. Thanks! -- 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 3

Re: Please welcome Yahoo to MICE!
by Jason Hanke Aug. 2, 2016

Aug. 2, 2016

Juniper part EX-SFP-10GE-LR or compatible We strongly recommend an optic with DOM. Thanks! On Tue, Aug 2, 2016 at 2:37 PM, Russell Lohr <lohr(a)yahoo-inc.com> wrote: > Jason, > > Hello sir, I have been asked to come back to you and ask what the model# or > SKU that you use, I was asked to get this from you so that we know what to > provide back to you. Please let me know. > > Russell Lohr > Tech Yahoo| Network Eng > 404-422-5932 cell > 701 First Avenue Sunnyvale CA 94089 > lohr(a)yahoo-inc.com > > > ________________________________ > From: Jason Hanke <jayhanke(a)neutralpath.net> > To: MICE Discuss <MICE-DISCUSS(a)lists.iphouse.net>; Mehmet Akcin > <akcin(a)yahoo-inc.com>; Josh Lepold <josh.lepold(a)zayo.com>; Russell Lohr > <lohr(a)yahoo-inc.com> > Sent: Tuesday, August 2, 2016 7:51 AM > Subject: Please welcome Yahoo to MICE! > > Yahoo will be connecting to two 10G ports with NO LAG Config. > > Name: Yahoo > ASN: 10310 > Contact: peering(a)yahoo-inc.com > > Port: xe-0/2/0 (main switch) > IPv4: 206.108.255.58/24 > IPv6: 2001:504:27:0:0:2846::1/64 > > Port: xe-2/0/5 (main switch) > IPv4: 206.108.255.59/24 > IPv6: 2001:504:27:0:0:2846::2/64 > > Yahoo- > > This email will serve as your LOA/CFA. Please provide a Juniper > compatible SFP+ optic for each of your connections to be installed in > the MICE Ethernet switch. > > Route Server and web server configuration please! > > 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 > > -- 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

1 0

DDoS Identification / Mitigation
by Dave Williams Aug. 1, 2016

Aug. 1, 2016

Hi all - I know this isn't a MICE specific question, but I can't think of a better group of people to ask! I was wondering if anyone could share their strategy for DDoS detection and mitigation? We randomly have troubles with it and as you can imagine it's quite the pain! Thanks in advance! d Dave Williams Founder / Visionary Revelation Network Management, Inc. O: 763.367.6161 C: 763.670.5558

7 7