- mice-discuss - lists.micemn.net

Re: Subscription Mail: Re: [MICE-DISCUSS] [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance Window

by James Urwiller

Ahh IC.. because the routes are still valid during the timeout. I was thinking it would be like a fiber cut where we have no valid routes while timers count down. NICE! James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Ryan Goldberg Sent: Friday, January 18, 2019 12:56 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Subscription Mail: Re: [MICE-DISCUSS] [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance Window I believe the idea is to block tcp port 179 ahead of time so the session “dies” and this creates the least disruptive way to do this type of work for all parties. > On Jan 18, 2019, at 12:52 PM, James Urwiller > <james.urwiller(a)TURNKEY-TELECOM.COM> wrote: > > Is this still happening @2PM today? By "blocking bgp" u mean shutdown > on your end? > > James Urwiller > Network Architect > Stealth Broadband > james.urwiller(a)stealthbroadband.com > > > -----Original Message----- > From: MICE Announcements <MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET> On Behalf > Of Richard Laager > Sent: Thursday, January 10, 2019 18:39 > To: MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET > Subject: [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance > Window > > -------- Forwarded Message -------- > Subject: MICE 100Gig Card Replacement Maintenance Window > Date: Thu, 10 Jan 2019 17:35:00 -0600 > From: Jeremy Lumby <jlumby(a)MNVOIP.COM> > Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > Organization: Minnesota VoIP > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > After yesterday's meeting discussion about the 100G card replacement > on the MICE core switch, I now have a tracking number for a new 100G > card from Arista. Based on needing 7 days of major maintenance > notice, and a request to complete before MLK day it looks like Friday > 1/18/2019 at 2PM CST will be the best time to complete the > maintenance. The new card requires a switch OS upgrade. Based on an > Arista recommendation, I will be upgrading to 4.20.11M prior to the > card replacement. This will cause a total traffic disruption on the > MICE core switch. Prior to the maintenance I will be blocking BGP on > all ports of the core switch to allow traffic to gracefully reroute. > If you choose to shutdown BGP on your own prior to the maintenance, > please leave your interface enabled so that link can be verified after the > maintenance completes. > > 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 > > ###################################################################### > ## > > To unsubscribe from the MICE-ANNOUNCE list, click the following link: > &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF); >

Jan. 18, 2019

Re: Subscription Mail: Re: [MICE-DISCUSS] [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance Window

by Ryan Goldberg

I believe the idea is to block tcp port 179 ahead of time so the session “dies” and this creates the least disruptive way to do this type of work for all parties. > On Jan 18, 2019, at 12:52 PM, James Urwiller <james.urwiller(a)TURNKEY-TELECOM.COM> wrote: > > Is this still happening @2PM today? By "blocking bgp" u mean shutdown on > your end? > > James Urwiller > Network Architect > Stealth Broadband > james.urwiller(a)stealthbroadband.com > > > -----Original Message----- > From: MICE Announcements <MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET> On Behalf Of > Richard Laager > Sent: Thursday, January 10, 2019 18:39 > To: MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET > Subject: [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance Window > > -------- Forwarded Message -------- > Subject: MICE 100Gig Card Replacement Maintenance Window > Date: Thu, 10 Jan 2019 17:35:00 -0600 > From: Jeremy Lumby <jlumby(a)MNVOIP.COM> > Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > Organization: Minnesota VoIP > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > > After yesterday's meeting discussion about the 100G card replacement on > the MICE core switch, I now have a tracking number for a new 100G card > from Arista. Based on needing 7 days of major maintenance notice, and a > request to complete before MLK day it looks like Friday 1/18/2019 at 2PM > CST will be the best time to complete the maintenance. The new card > requires a switch OS upgrade. Based on an Arista recommendation, I will > be upgrading to 4.20.11M prior to the card replacement. This will cause a > total traffic disruption on the MICE core switch. Prior to the > maintenance I will be blocking BGP on all ports of the core switch to > allow traffic to gracefully reroute. If you choose to shutdown BGP on > your own prior to the maintenance, please leave your interface enabled so > that link can be verified after the maintenance completes. > > 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 > > ######################################################################## > > To unsubscribe from the MICE-ANNOUNCE list, click the following link: > &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF); >

Jan. 18, 2019

Re: [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance Window

by James Urwiller

Is this still happening @2PM today? By "blocking bgp" u mean shutdown on your end? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com -----Original Message----- From: MICE Announcements <MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET> On Behalf Of Richard Laager Sent: Thursday, January 10, 2019 18:39 To: MICE-ANNOUNCE(a)LISTS.IPHOUSE.NET Subject: [MICE-ANNOUNCE] MICE 100Gig Card Replacement Maintenance Window -------- Forwarded Message -------- Subject: MICE 100Gig Card Replacement Maintenance Window Date: Thu, 10 Jan 2019 17:35:00 -0600 From: Jeremy Lumby <jlumby(a)MNVOIP.COM> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Organization: Minnesota VoIP To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET After yesterday's meeting discussion about the 100G card replacement on the MICE core switch, I now have a tracking number for a new 100G card from Arista. Based on needing 7 days of major maintenance notice, and a request to complete before MLK day it looks like Friday 1/18/2019 at 2PM CST will be the best time to complete the maintenance. The new card requires a switch OS upgrade. Based on an Arista recommendation, I will be upgrading to 4.20.11M prior to the card replacement. This will cause a total traffic disruption on the MICE core switch. Prior to the maintenance I will be blocking BGP on all ports of the core switch to allow traffic to gracefully reroute. If you choose to shutdown BGP on your own prior to the maintenance, please leave your interface enabled so that link can be verified after the maintenance completes. 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 ######################################################################## To unsubscribe from the MICE-ANNOUNCE list, click the following link: &*TICKET_URL(MICE-ANNOUNCE,SIGNOFF);

Jan. 18, 2019

Re: Zayo Belle Plaine Remote Switch Port Channel Augement

by Doug McIntyre

On Thu, Jan 17, 2019 at 07:34:02AM -0600, Jay Hanke wrote: >Zayo is adding port: > >Ethernet5.43 (Main Switch) > >To their existing port channel (Po9) feeding the remote switch at >their Belle Plaine data center. I've configured the switch to add 5/43 into Po9 as their 3rd link now. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Jan. 17, 2019

Zayo Belle Plaine Remote Switch Port Channel Augement

by Jay Hanke

Zayo is adding port: Ethernet5.43 (Main Switch) To their existing port channel (Po9) feeding the remote switch at their Belle Plaine data center. I have renamed the assignments from NP Belle Plaine Remote to Zayo Belle Plaine Remote in the documentation. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 17, 2019

Re: Fastly upgrade to 2x100G

by Jeremy Lumby

The switch ports have been pre-configured 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 -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Saturday, January 12, 2019 9:58 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Fastly upgrade to 2x100G Fastly is upgrading from 2x10G to 2x100G. Please configure 100G ports for Fastly (NO LAG): Ethernet3/9/1 Ethernet4/50/1 All IP addressing will remain the same. Following migration Fastly will no longer use ports: Ethernet4/46 Ethernet5/46 Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 12, 2019

Fastly upgrade to 2x100G

by Jay Hanke

Fastly is upgrading from 2x10G to 2x100G. Please configure 100G ports for Fastly (NO LAG): Ethernet3/9/1 Ethernet4/50/1 All IP addressing will remain the same. Following migration Fastly will no longer use ports: Ethernet4/46 Ethernet5/46 Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 12, 2019

MICE 100Gig Card Replacement Maintenance Window

by Jeremy Lumby

After yesterday's meeting discussion about the 100G card replacement on the MICE core switch, I now have a tracking number for a new 100G card from Arista. Based on needing 7 days of major maintenance notice, and a request to complete before MLK day it looks like Friday 1/18/2019 at 2PM CST will be the best time to complete the maintenance. The new card requires a switch OS upgrade. Based on an Arista recommendation, I will be upgrading to 4.20.11M prior to the card replacement. This will cause a total traffic disruption on the MICE core switch. Prior to the maintenance I will be blocking BGP on all ports of the core switch to allow traffic to gracefully reroute. If you choose to shutdown BGP on your own prior to the maintenance, please leave your interface enabled so that link can be verified after the maintenance completes. 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

Jan. 10, 2019

Re: ADV: [MICE-DISCUSS] Please welcome Joe's data Center to MICE!

by Doug McIntyre

On Thu, Jan 10, 2019 at 03:25:55PM -0600, Jay Hanke wrote: >Name: Joe's Datacenter >Port: MN VoIP Remote (Port?) >ASN: 19969 >IPv4: 206.108.255.134/24 >IPv6: 2001:504:27:0:0:4e01::1/64 >Peering Contact: joe(a)joesdatacenter.com >Route Servers- YES >BFD: NO The route servers are all set and ready to go. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Jan. 10, 2019

Re: Please welcome Joe's data Center to MICE!

by Jeremy Lumby

MN VoIP remote port E 15 @ 10Gig From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Thursday, January 10, 2019 3:26 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Please welcome Joe's data Center to MICE! Name: Joe's Datacenter Port: MN VoIP Remote (Port?) ASN: 19969 IPv4: 206.108.255.134/24 IPv6: 2001:504:27:0:0:4e01::1/64 Peering Contact: joe(a)joesdatacenter.com Route Servers- YES BFD: NO Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 10, 2019

Please welcome Joe's data Center to MICE!

by Jay Hanke

Name: Joe's Datacenter Port: MN VoIP Remote (Port?) ASN: 19969 IPv4: 206.108.255.134/24 IPv6: 2001:504:27:0:0:4e01::1/64 Peering Contact: joe(a)joesdatacenter.com Route Servers- YES BFD: NO Welcome Aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Jan. 10, 2019

Re: New Years Traffic

by David Farmer

FYI, As of right now the LinkedIn post I did 9 days ago, has 104 Likes, 12 Comments, and over 7000 views. https://www.linkedin.com/feed/update/urn:li:activity:6486075016726269952 Also, based on the discussion yesterday, this morning I posted the following to the LinkedIn comment thread; @Job Snijders it comes down to the interpretation of the Open-IX standard. ”The IXP MUST publish on a publicly available website the total sum of all incoming and outgoing traffic in bps from all connected networks on the public peering VLAN.” We took that as ”the sum of all ingress and egress [together].” Where it seems others took that as ”the sum of all ingress and [separately the sum of all] egress.” We discussed this at our meeting yesterday, and we are going to stick with our interpretation, at least for now. Our graph is clear; our total number is the sum of both ingress and egress, and it has them both separately identified along with the total of the two. This allows the reader to decide how to interpret the data. open-ix.silkstart.com On Thu, Jan 3, 2019 at 4:18 PM AnthonyAnderberg(a)nuvera.net < AnthonyAnderberg(a)nuvera.net> wrote: > That was my personal opinion too but many years ago the majority opted for > the stacked version, we can chew on it again next week if membership wants. > > > > I had actually been creating/exporting two versions of the graph for a > long time but the non-stacked one never got referenced so it fell by the > wayside during the Arista migration. > > The non-stacked graph was similar looking to what the folks at Torix do > but with a MICEish color scheme: > > https://www.torix.ca/img/torix-day.png > > > > > > [image: signature_1212707895] > > > > *From: *MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of David > Farmer <farmer(a)UMN.EDU> > *Reply-To: *MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > *Date: *Thursday, January 3, 2019 at 3:49 PM > *To: *MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> > *Subject: *Re: [MICE-DISCUSS] New Years Traffic > > > > I did a Linkedin Post on it > > > > https://www.linkedin.com/feed/update/urn:li:activity:6486075016726269952 > > > > It has 67 likes, 7 comments, and just over 3000 views as of right now. > > > > The main reason I'm mentioning it is some comments about using > ingress+egress for traffic level. > > > > As I think I've said before, we should use one or the other, not the > sum of them. > > > > > > > > On Tue, Jan 1, 2019 at 8:35 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > > Just wanted to congratulate all MICE members for crossing the 500Gig mark > tonight for the first time. > > > > > -- > > =============================================== > David Farmer Email:farmer@umn.edu > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- =============================================== 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 ===============================================

Jan. 10, 2019

Re: UG 30 Meeting

by Richard Laager

On 1/3/19 6:42 PM, Richard Laager wrote: > The MICE UG 30 meeting will be held Wednesday, January 9, 3:00 pm, at > the 511 Building Cafeteria, 11th Avenue South, Minneapolis, MN. > > The agenda and draft UG 29 minutes are attached. > > This is the typical agenda. I'm behind on getting this together, so I > haven't put out a separate call for agenda items. If anyone has agenda > items, please let me know. > > The remote conferencing will be the same as before: > 952-562-5400 passcode MICE (6423). Attached is an updated agenda. The addition is an item about a preemptive RMA of the 100G line card. -- Richard

Jan. 9, 2019

UG 30 Meeting

by Richard Laager

The MICE UG 30 meeting will be held Wednesday, January 9, 3:00 pm, at the 511 Building Cafeteria, 11th Avenue South, Minneapolis, MN. The agenda and draft UG 29 minutes are attached. This is the typical agenda. I'm behind on getting this together, so I haven't put out a separate call for agenda items. If anyone has agenda items, please let me know. The remote conferencing will be the same as before: 952-562-5400 passcode MICE (6423). -- Richard

Jan. 4, 2019

Re: New Years Traffic

by AnthonyAnderberg＠nuvera.net

That was my personal opinion too but many years ago the majority opted for the stacked version, we can chew on it again next week if membership wants. I had actually been creating/exporting two versions of the graph for a long time but the non-stacked one never got referenced so it fell by the wayside during the Arista migration. The non-stacked graph was similar looking to what the folks at Torix do but with a MICEish color scheme: https://www.torix.ca/img/torix-day.png [signature_1212707895] From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of David Farmer <farmer(a)UMN.EDU> Reply-To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Date: Thursday, January 3, 2019 at 3:49 PM To: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] New Years Traffic I did a Linkedin Post on it https://www.linkedin.com/feed/update/urn:li:activity:6486075016726269952 It has 67 likes, 7 comments, and just over 3000 views as of right now. The main reason I'm mentioning it is some comments about using ingress+egress for traffic level. As I think I've said before, we should use one or the other, not the sum of them. On Tue, Jan 1, 2019 at 8:35 PM Jeremy Lumby <jlumby(a)mnvoip.com<mailto:jlumby@mnvoip.com>> wrote: Just wanted to congratulate all MICE members for crossing the 500Gig mark tonight for the first time. -- =============================================== David Farmer Email:farmer@umn.edu<mailto:Email%3Afarmer@umn.edu> Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 =============================================== ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Jan. 3, 2019

Re: New Years Traffic

by Andrew Hoyos

If you take a look some of the others that publicly report bandwidth levels, as an example: https://www.seattleix.net/statistics/ https://www.netnod.se/ix-stats/sums/All.html https://www.torix.ca/traffic-statistics/ https://ix-denver.org/traffic/ http://www.kcix.net/ All seem to be reporting/collecting both in/out, but not stacking them together. I’d agree that the 500gbps seems “double counted”. — Andrew Hoyos hoyosa(a)gmail.com > On Jan 3, 2019, at 3:48 PM, David Farmer <farmer(a)UMN.EDU> wrote: > > I did a Linkedin Post on it > > https://www.linkedin.com/feed/update/urn:li:activity:6486075016726269952 <https://www.linkedin.com/feed/update/urn:li:activity:6486075016726269952> > > It has 67 likes, 7 comments, and just over 3000 views as of right now. > > The main reason I'm mentioning it is some comments about using ingress+egress for traffic level. > > As I think I've said before, we should use one or the other, not the sum of them. > > On Tue, Jan 1, 2019 at 8:35 PM Jeremy Lumby <jlumby(a)mnvoip.com <mailto:jlumby@mnvoip.com>> wrote: > Just wanted to congratulate all MICE members for crossing the 500Gig mark tonight for the first time. > > > -- > =============================================== > David Farmer Email:farmer@umn.edu <mailto:Email%3Afarmer@umn.edu> > Networking & Telecommunication Services > Office of Information Technology > University of Minnesota > 2218 University Ave SE Phone: 612-626-0815 > Minneapolis, MN 55414-3029 Cell: 612-812-9952 > =============================================== > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1>

Jan. 3, 2019

Re: New Years Traffic

by David Farmer

I did a Linkedin Post on it https://www.linkedin.com/feed/update/urn:li:activity:6486075016726269952 It has 67 likes, 7 comments, and just over 3000 views as of right now. The main reason I'm mentioning it is some comments about using ingress+egress for traffic level. As I think I've said before, we should use one or the other, not the sum of them. On Tue, Jan 1, 2019 at 8:35 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > Just wanted to congratulate all MICE members for crossing the 500Gig mark > tonight for the first time. > -- =============================================== 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 ===============================================

Jan. 3, 2019

Re: New Years Traffic

by Reid Fishler

Woohoo! Reid On Tue, Jan 1, 2019, 9:35 PM Jeremy Lumby <jlumby(a)mnvoip.com wrote: > Just wanted to congratulate all MICE members for crossing the 500Gig mark > tonight for the first time. > >

Jan. 2, 2019

New Years Traffic

by Jeremy Lumby

Just wanted to congratulate all MICE members for crossing the 500Gig mark tonight for the first time.

Jan. 2, 2019

Re: ip route objects in MICE

by Justin Krejci

While I find the idea interesting, I am doubtful there will be any ubiquitous technique that every or even most networks will be willing to implement for this purpose, especially since not every prefix is likely to be presented from a single geo; some operators likely have one prefix broken into smaller networks, each of which are in disparate geos while being presented to eBGP/DFZ as an aggregate prefix because, you know, they are trying to be good netizens by being mindful of RIB and FIB limitations. Even if some sort of self-applied geo-tagging of prefixes were defined clearly by some body like IETF or something, it would likely take a tremendous amount of motivation to get operators to actually implement such a thing and then also keep it up to date over time. We can't even get people to do the sensible BCP38 filtering on a large scale and that has pretty significant benefits whereas I, at least at first glance, don't see any noteworthy value of such a geo-tagging mechanism to provoke active implementation by the majority. Maybe something could be embedded in BGP origin validation rpki... like stuff some additional geo bits stuffed into that. This is not a thoroughly thought out idea, just kind of tossing it out there as it is something that is gaining some momentum and sits in the same realm of administratively assessing BGP prefixes. You might consider something fully within your own administrative control like RTT testing to IP addresses on various prefixes to gauge an approximate distance, though I suppose this idea would be severely unreliable due to many variable conditions affecting RTT that have nothing to do with geographic distance. ¯\_(?)_/¯ Best of luck on your search ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Timothy Peiffer <peiffer(a)UMN.EDU> Sent: Friday, December 28, 2018 3:39 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] ip route objects in MICE I am interested in gathering data for a firewall ruleset that allows more direct usage from networks that are in the metro region of Twin Cities and Duluth, and to a lesser degree communities and surrounding areas for Crookston and Morris. For the participants of MICE, do you have a way of easily presenting your routes by geolocation? I pulled down our route tables for one of our Northern Lights routers connected and matched the base address against max mind geolocate. The result was a list of about 7,000 routes that I thought was unmanageable. Is there a better way, maybe through BGP communities or similar methods, to get more direct relevant info? I want to have a ruleset that permits <ISP x>/minneapolis but denies <ISP x>/atlanta. -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 29, 2018

ip route objects in MICE

by Timothy Peiffer

I am interested in gathering data for a firewall ruleset that allows more direct usage from networks that are in the metro region of Twin Cities and Duluth, and to a lesser degree communities and surrounding areas for Crookston and Morris. For the participants of MICE, do you have a way of easily presenting your routes by geolocation? I pulled down our route tables for one of our Northern Lights routers connected and matched the base address against max mind geolocate. The result was a list of about 7,000 routes that I thought was unmanageable. Is there a better way, maybe through BGP communities or similar methods, to get more direct relevant info? I want to have a ruleset that permits <ISP x>/minneapolis but denies <ISP x>/atlanta. -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota

Dec. 28, 2018

Re: Amazon issues?

by Frank Bulk

We saw the same thing – I’m sending a note to the technical contact PeeringDB to inquire. Interesting that the graphs didn’t show a dip at those times. Regards, Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of James Urwiller Sent: Friday, December 21, 2018 10:14 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Amazon issues? thats what I was thinking.. my times match. thanks! Sent from my iPhone 7 On Dec 21, 2018, at 10:12, Timothy Peiffer <peiffer(a)UMN.EDU<mailto:peiffer@UMN.EDU>> wrote: Yes, Northern Lights GigaPOP showed bounces around 4:20, 5:50, and 8:55 according to our alerts. I can get more precise reading the logs. -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota On Fri, Dec 21, 2018 at 9:12 AM James Urwiller <james.urwiller(a)turnkey-telecom.com<mailto:james.urwiller@turnkey-telecom.com>> wrote: I have seen my peer with Amazon bounce a few times this AM, anyone else? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com<mailto:james.urwiller@stealthbroadband.com> <image001.jpg> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota ________________________________ 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

Dec. 21, 2018

Re: Amazon issues?

by Jeff Wilde

I’m surprised amazon answered your peer request. Jeff Wilde IT Manager Park Region Telephone Company P: 218-826-8330 E: jeff.wilde(a)parkregion.com<mailto:jeff.wilde@parkregion.com> From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of James Urwiller Sent: Friday, December 21, 2018 10:14 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Amazon issues? thats what I was thinking.. my times match. thanks! Sent from my iPhone 7 On Dec 21, 2018, at 10:12, Timothy Peiffer <peiffer(a)UMN.EDU<mailto:peiffer@UMN.EDU>> wrote: Yes, Northern Lights GigaPOP showed bounces around 4:20, 5:50, and 8:55 according to our alerts. I can get more precise reading the logs. -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota On Fri, Dec 21, 2018 at 9:12 AM James Urwiller <james.urwiller(a)turnkey-telecom.com<mailto:james.urwiller@turnkey-telecom.com>> wrote: I have seen my peer with Amazon bounce a few times this AM, anyone else? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com<mailto:james.urwiller@stealthbroadband.com> <image001.jpg> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota ________________________________ 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

Dec. 21, 2018

Re: Amazon issues?

by James Urwiller

thats what I was thinking.. my times match. thanks! Sent from my iPhone 7 > On Dec 21, 2018, at 10:12, Timothy Peiffer <peiffer(a)UMN.EDU> wrote: > > Yes, Northern Lights GigaPOP showed bounces around 4:20, 5:50, and 8:55 according to our alerts. I can get more precise reading the logs. > > > -- > Regards, > > Tim Peiffer > +1 612-626-7884 > Network Engineer > Office of Information Technology (OIT) > University of Minnesota > >> On Fri, Dec 21, 2018 at 9:12 AM James Urwiller <james.urwiller(a)turnkey-telecom.com> wrote: >> I have seen my peer with Amazon bounce a few times this AM, anyone else? >> >> >> >> James Urwiller >> >> Network Architect >> >> Stealth Broadband >> >> james.urwiller(a)stealthbroadband.com >> >> <image001.jpg> >> >> >> >> >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >> > > > -- > Regards, > > Tim Peiffer > +1 612-626-7884 > Network Engineer > Office of Information Technology (OIT) > University of Minnesota > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 21, 2018

Re: Amazon issues?

by Timothy Peiffer

Yes, Northern Lights GigaPOP showed bounces around 4:20, 5:50, and 8:55 according to our alerts. I can get more precise reading the logs. -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota On Fri, Dec 21, 2018 at 9:12 AM James Urwiller < james.urwiller(a)turnkey-telecom.com> wrote: > I have seen my peer with Amazon bounce a few times this AM, anyone else? > > > > James Urwiller > > Network Architect > > Stealth Broadband > > james.urwiller(a)stealthbroadband.com > > [image: stealth300] > > > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 > -- Regards, Tim Peiffer +1 612-626-7884 Network Engineer Office of Information Technology (OIT) University of Minnesota

Dec. 21, 2018

Amazon issues?

by James Urwiller

I have seen my peer with Amazon bounce a few times this AM, anyone else? James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300]

Dec. 21, 2018

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

by Doug McIntyre

On Tue, Dec 18, 2018 at 03:05:36PM -0600, Jay Hanke wrote: >Name: Router12 >Port: Ethernet 1 (SFN Albert Lea Remote) 10GE >ASN: 55009 >IPv4: 206.108.255.118/24 >IPv6: 2001:504:27:0:0:d6e1::1/64 >Peering Contact: rmalek(a)router12.net >Route Servers- YES >BFD: NO I've added them into the route-servers. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Dec. 19, 2018

Please Welcome Router12 to MICE!

by Jay Hanke

Name: Router12 Port: Ethernet 1 (SFN Albert Lea Remote) 10GE ASN: 55009 IPv4: 206.108.255.118/24 IPv6: 2001:504:27:0:0:d6e1::1/64 Peering Contact: rmalek(a)router12.net Route Servers- YES BFD: NO Welcome aboard! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 18, 2018

Re: WIN/Airstream 10G LAG Augment

by Jeremy Lumby

The switch config is complete From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jay Hanke Sent: Tuesday, December 18, 2018 8:09 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] WIN/Airstream 10G LAG Augment Airstream has been allocated Ethernet5/18 to add to their existing LAG. Please update the switch configuration. The new LAG is 30G. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 18, 2018

WIN/Airstream 10G LAG Augment

by Jay Hanke

Airstream has been allocated Ethernet5/18 to add to their existing LAG. Please update the switch configuration. The new LAG is 30G. -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 18, 2018

Re: Facebook MICE Connection Active

by Justin Krejci

That is also with some of us establishing PNIs to Facebook too but I concur, it is a great addition!! ________________________________ From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> on behalf of Darin Steffl <darin.steffl(a)MNWIFI.COM> Sent: Monday, December 17, 2018 9:18 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Facebook MICE Connection Active 12 days later and Facebook is already peaking at 15.48 Gbps last night. And that's with needing to establish direct peering. I'd say this was a great addition to MICE. On Wed, Dec 5, 2018 at 4:49 PM Jay Hanke <jayhanke(a)southfront.io<mailto:jayhanke@southfront.io>> wrote: The Facebook MICE connections are active. If your network would like to peer with Facebook over MICE please email requests to peering(a)fb.com<mailto:peering@fb.com>. Facebook does NOT connect to the MICE route servers so each network will need to establish their own BGP sessions directly with Facebook. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io<mailto:jayhanke@southfront.io> Phone 612-204-0000 -- Darin Steffl Minnesota WiFi www.mnwifi.com<http://www.mnwifi.com/> 507-634-WiFi [http://www.snoitulosten.com/wp-content/uploads/2010/01/facebook-small.jpg]<http://www.facebook.com/minnesotawifi> Like us on Facebook<http://www.facebook.com/minnesotawifi> ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 17, 2018

Re: Facebook MICE Connection Active

by Darin Steffl

12 days later and Facebook is already peaking at 15.48 Gbps last night. And that's with needing to establish direct peering. I'd say this was a great addition to MICE. On Wed, Dec 5, 2018 at 4:49 PM Jay Hanke <jayhanke(a)southfront.io> wrote: > The Facebook MICE connections are active. If your network would like > to peer with Facebook over MICE please email requests to > peering(a)fb.com. > > Facebook does NOT connect to the MICE route servers so each network > will need to establish their own BGP sessions directly with Facebook. > > Thanks! > > -- > Jay Hanke, President > South Front Networks > jayhanke(a)southfront.io > Phone 612-204-0000 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 17, 2018

Re: Longlines Contact Update

by Richard Laager

On 12/10/18 4:10 PM, Jay Hanke wrote: > Longlines has requested to update the peering contact to > > llarsen(a)longlines.biz Done. -- Richard

Dec. 10, 2018

Longlines Contact Update

by Jay Hanke

Longlines has requested to update the peering contact to llarsen(a)longlines.biz Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 10, 2018

Marco 1g-10G conversion

by Jay Hanke

Marco is moving to a dedicated 10G port on the main switch. The new port is Ethernet5/19. Welcome aboard (again) -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 10, 2018

Re: Amazon peering

by Darin Steffl

They replied just now that their ETA for peering is now February 2019. I'll set my calendar reminder and see if they can pull it off. On Thu, Dec 6, 2018 at 5:17 PM Jeremy Lumby <jlumby(a)mnvoip.com> wrote: > Sorry for the spam, I miss clicked, and replied to the wrong email > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *Jeremy Lumby > *Sent:* Thursday, December 06, 2018 5:15 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] Amazon peering > > > > Do you want call waiting off, or just the tone? > > > > *From:* MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] *On Behalf > Of *James Urwiller > *Sent:* Thursday, December 06, 2018 4:30 PM > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* Re: [MICE-DISCUSS] Amazon peering > > > > Nevermind.. our Amazon peer is up, someone else here must have finished > the turn-up. my bad. > > > > James Urwiller > > Network Architect > > Stealth Broadband > > james.urwiller(a)stealthbroadband.com > > [image: stealth300] > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin > Steffl > *Sent:* Thursday, December 6, 2018 14:47 > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Amazon peering > > > > Hello, > > > > We've been trying to peer with Amazon since Dec. 2017 and their most > recent response is that we're still in their provisioning queue after 1 > year. > > > > Does anyone have a contact there I can escalate this to? I've reached out > to the two contacts listed in PeeringDB and that was their response. I find > this unacceptable to be approved to peer with them a year ago but still be > waiting to configure their BGP session, which took me all of 1 minute to > complete on my router. > > > > Any ideas? All other direct peering we've done has been completed within 1 > week like Netflix, Google, Akamai, Cloudflare, etc. > > > > Thank you > > > > > -- > > Darin Steffl > > Minnesota WiFi > > www.mnwifi.com > > 507-634-WiFi > > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > > ------------------------------ > > 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 > > > ------------------------------ > > 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 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 6, 2018

Re: Amazon peering

by Jeremy Lumby

Sorry for the spam, I miss clicked, and replied to the wrong email From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Thursday, December 06, 2018 5:15 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Amazon peering Do you want call waiting off, or just the tone? From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Thursday, December 06, 2018 4:30 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Amazon peering Nevermind.. our Amazon peer is up, someone else here must have finished the turn-up. my bad. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Darin Steffl Sent: Thursday, December 6, 2018 14:47 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Amazon peering Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi Like us on Facebook 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 To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 6, 2018

Re: Amazon peering

by Jeremy Lumby

Do you want call waiting off, or just the tone? From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of James Urwiller Sent: Thursday, December 06, 2018 4:30 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Amazon peering Nevermind.. our Amazon peer is up, someone else here must have finished the turn-up. my bad. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Darin Steffl Sent: Thursday, December 6, 2018 14:47 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Amazon peering Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi Like us on Facebook 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

Dec. 6, 2018

Re: Amazon peering

by Darin Steffl

Thanks guys. I'll update if/when this gets completed and which Amazon contact was the one that got it done for us. On Thu, Dec 6, 2018 at 4:53 PM Phil Sampson <phil(a)sampso.net> wrote: > ragmuc(a)amazon.com and Kadaru(a)amazon.com are the email addresses that have > finished peering for me in the past. > > On Thu, Dec 6, 2018 at 4:33 PM Darin Steffl <darin.steffl(a)mnwifi.com> > wrote: > >> Find who finished it and tell me the secret James ;) >> >> I'll keep emailing Amazon contacts until they're so annoyed they have to >> turn it up. >> >> On Thu, Dec 6, 2018 at 4:30 PM James Urwiller < >> james.urwiller(a)turnkey-telecom.com> wrote: >> >>> Nevermind.. our Amazon peer is up, someone else here must have finished >>> the turn-up. my bad. >>> >>> >>> >>> James Urwiller >>> >>> Network Architect >>> >>> Stealth Broadband >>> >>> james.urwiller(a)stealthbroadband.com >>> >>> [image: stealth300] >>> >>> >>> >>> *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin >>> Steffl >>> *Sent:* Thursday, December 6, 2018 14:47 >>> *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>> *Subject:* [MICE-DISCUSS] Amazon peering >>> >>> >>> >>> Hello, >>> >>> >>> >>> We've been trying to peer with Amazon since Dec. 2017 and their most >>> recent response is that we're still in their provisioning queue after 1 >>> year. >>> >>> >>> >>> Does anyone have a contact there I can escalate this to? I've reached >>> out to the two contacts listed in PeeringDB and that was their response. I >>> find this unacceptable to be approved to peer with them a year ago but >>> still be waiting to configure their BGP session, which took me all of 1 >>> minute to complete on my router. >>> >>> >>> >>> Any ideas? All other direct peering we've done has been completed within >>> 1 week like Netflix, Google, Akamai, Cloudflare, etc. >>> >>> >>> >>> Thank you >>> >>> >>> >>> >>> -- >>> >>> Darin Steffl >>> >>> Minnesota WiFi >>> >>> www.mnwifi.com >>> >>> 507-634-WiFi >>> >>> <http://www.facebook.com/minnesotawifi> Like us on Facebook >>> <http://www.facebook.com/minnesotawifi> >>> >>> >>> ------------------------------ >>> >>> 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 >>> >> >> >> -- >> Darin Steffl >> Minnesota WiFi >> www.mnwifi.com >> 507-634-WiFi >> <http://www.facebook.com/minnesotawifi> Like us on Facebook >> <http://www.facebook.com/minnesotawifi> >> >> ------------------------------ >> >> 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 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 6, 2018

Re: Amazon peering

by James Urwiller

Looks like after my initial email to them, a “Raghavendra Mucherla” ( ragmuc(a)amazon.com) replied to our NOC saying it was ready and one of my guys just enabled the session. In my initial email I gave them my MICE IP, my ASN, and the prefix’s I was to announce. Looks like it took about 2 months in total. Hope this helps. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300] *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin Steffl *Sent:* Thursday, December 6, 2018 16:33 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* Re: [MICE-DISCUSS] Amazon peering Find who finished it and tell me the secret James ;) I'll keep emailing Amazon contacts until they're so annoyed they have to turn it up. On Thu, Dec 6, 2018 at 4:30 PM James Urwiller < james.urwiller(a)turnkey-telecom.com> wrote: Nevermind.. our Amazon peer is up, someone else here must have finished the turn-up. my bad. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300] *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin Steffl *Sent:* Thursday, December 6, 2018 14:47 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] Amazon peering Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi> ------------------------------ 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 -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi> ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 6, 2018

Re: Amazon peering

by Phil Sampson

ragmuc(a)amazon.com and Kadaru(a)amazon.com are the email addresses that have finished peering for me in the past. On Thu, Dec 6, 2018 at 4:33 PM Darin Steffl <darin.steffl(a)mnwifi.com> wrote: > Find who finished it and tell me the secret James ;) > > I'll keep emailing Amazon contacts until they're so annoyed they have to > turn it up. > > On Thu, Dec 6, 2018 at 4:30 PM James Urwiller < > james.urwiller(a)turnkey-telecom.com> wrote: > >> Nevermind.. our Amazon peer is up, someone else here must have finished >> the turn-up. my bad. >> >> >> >> James Urwiller >> >> Network Architect >> >> Stealth Broadband >> >> james.urwiller(a)stealthbroadband.com >> >> [image: stealth300] >> >> >> >> *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin >> Steffl >> *Sent:* Thursday, December 6, 2018 14:47 >> *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> *Subject:* [MICE-DISCUSS] Amazon peering >> >> >> >> Hello, >> >> >> >> We've been trying to peer with Amazon since Dec. 2017 and their most >> recent response is that we're still in their provisioning queue after 1 >> year. >> >> >> >> Does anyone have a contact there I can escalate this to? I've reached out >> to the two contacts listed in PeeringDB and that was their response. I find >> this unacceptable to be approved to peer with them a year ago but still be >> waiting to configure their BGP session, which took me all of 1 minute to >> complete on my router. >> >> >> >> Any ideas? All other direct peering we've done has been completed within >> 1 week like Netflix, Google, Akamai, Cloudflare, etc. >> >> >> >> Thank you >> >> >> >> >> -- >> >> Darin Steffl >> >> Minnesota WiFi >> >> www.mnwifi.com >> >> 507-634-WiFi >> >> <http://www.facebook.com/minnesotawifi> Like us on Facebook >> <http://www.facebook.com/minnesotawifi> >> >> >> ------------------------------ >> >> 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 >> > > > -- > Darin Steffl > Minnesota WiFi > www.mnwifi.com > 507-634-WiFi > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > ------------------------------ > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 >

Dec. 6, 2018

Re: Amazon peering

by Darin Steffl

Find who finished it and tell me the secret James ;) I'll keep emailing Amazon contacts until they're so annoyed they have to turn it up. On Thu, Dec 6, 2018 at 4:30 PM James Urwiller < james.urwiller(a)turnkey-telecom.com> wrote: > Nevermind.. our Amazon peer is up, someone else here must have finished > the turn-up. my bad. > > > > James Urwiller > > Network Architect > > Stealth Broadband > > james.urwiller(a)stealthbroadband.com > > [image: stealth300] > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin > Steffl > *Sent:* Thursday, December 6, 2018 14:47 > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Amazon peering > > > > Hello, > > > > We've been trying to peer with Amazon since Dec. 2017 and their most > recent response is that we're still in their provisioning queue after 1 > year. > > > > Does anyone have a contact there I can escalate this to? I've reached out > to the two contacts listed in PeeringDB and that was their response. I find > this unacceptable to be approved to peer with them a year ago but still be > waiting to configure their BGP session, which took me all of 1 minute to > complete on my router. > > > > Any ideas? All other direct peering we've done has been completed within 1 > week like Netflix, Google, Akamai, Cloudflare, etc. > > > > Thank you > > > > > -- > > Darin Steffl > > Minnesota WiFi > > www.mnwifi.com > > 507-634-WiFi > > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > > ------------------------------ > > 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 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 6, 2018

Re: Amazon peering

by James Urwiller

Nevermind.. our Amazon peer is up, someone else here must have finished the turn-up. my bad. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300] *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin Steffl *Sent:* Thursday, December 6, 2018 14:47 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] Amazon peering Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi> ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 6, 2018

Re: Amazon peering

by Darin Steffl

Being that Amazon is not on the route servers and they're still moving almost 18 Gbps at peak, there are definitely other members who are peered with them. They must have peered with them before Amazon's peering team went dark. On Thu, Dec 6, 2018 at 3:05 PM James Urwiller < james.urwiller(a)turnkey-telecom.com> wrote: > Same.. I in fact never got a response to my peering request, also over a > year ago. > > > > James Urwiller > > Network Architect > > Stealth Broadband > > james.urwiller(a)stealthbroadband.com > > [image: stealth300] > > > > *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin > Steffl > *Sent:* Thursday, December 6, 2018 14:47 > *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET > *Subject:* [MICE-DISCUSS] Amazon peering > > > > Hello, > > > > We've been trying to peer with Amazon since Dec. 2017 and their most > recent response is that we're still in their provisioning queue after 1 > year. > > > > Does anyone have a contact there I can escalate this to? I've reached out > to the two contacts listed in PeeringDB and that was their response. I find > this unacceptable to be approved to peer with them a year ago but still be > waiting to configure their BGP session, which took me all of 1 minute to > complete on my router. > > > > Any ideas? All other direct peering we've done has been completed within 1 > week like Netflix, Google, Akamai, Cloudflare, etc. > > > > Thank you > > > > > -- > > Darin Steffl > > Minnesota WiFi > > www.mnwifi.com > > 507-634-WiFi > > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> > > > ------------------------------ > > 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 > -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 6, 2018

Re: Amazon peering

by Jeff Wilde

I second that. From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of James Urwiller Sent: Thursday, December 6, 2018 2:55 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Amazon peering Same.. I in fact never got a response to my peering request, also over a year ago. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com<mailto:james.urwiller@stealthbroadband.com> [stealth300] From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Darin Steffl Sent: Thursday, December 6, 2018 14:47 To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] Amazon peering Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com<http://www.mnwifi.com/> 507-634-WiFi [http://www.snoitulosten.com/wp-content/uploads/2010/01/facebook-small.jpg]<http://www.facebook.com/minnesotawifi> Like us on Facebook<http://www.facebook.com/minnesotawifi> ________________________________ 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

Dec. 6, 2018

Re: Amazon peering

by James Urwiller

Same.. I in fact never got a response to my peering request, also over a year ago. James Urwiller Network Architect Stealth Broadband james.urwiller(a)stealthbroadband.com [image: stealth300] *From:* MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> *On Behalf Of *Darin Steffl *Sent:* Thursday, December 6, 2018 14:47 *To:* MICE-DISCUSS(a)LISTS.IPHOUSE.NET *Subject:* [MICE-DISCUSS] Amazon peering Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi> ------------------------------ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Dec. 6, 2018

Amazon peering

by Darin Steffl

Hello, We've been trying to peer with Amazon since Dec. 2017 and their most recent response is that we're still in their provisioning queue after 1 year. Does anyone have a contact there I can escalate this to? I've reached out to the two contacts listed in PeeringDB and that was their response. I find this unacceptable to be approved to peer with them a year ago but still be waiting to configure their BGP session, which took me all of 1 minute to complete on my router. Any ideas? All other direct peering we've done has been completed within 1 week like Netflix, Google, Akamai, Cloudflare, etc. Thank you -- Darin Steffl Minnesota WiFi www.mnwifi.com 507-634-WiFi <http://www.facebook.com/minnesotawifi> Like us on Facebook <http://www.facebook.com/minnesotawifi>

Dec. 6, 2018

Facebook MICE Connection Active

by Jay Hanke

The Facebook MICE connections are active. If your network would like to peer with Facebook over MICE please email requests to peering(a)fb.com. Facebook does NOT connect to the MICE route servers so each network will need to establish their own BGP sessions directly with Facebook. Thanks! -- Jay Hanke, President South Front Networks jayhanke(a)southfront.io Phone 612-204-0000

Dec. 5, 2018

Re: Please Welcome Fibernet Communications to MICE!

by Richard Laager

On 11/25/18 2:05 PM, Jay Hanke wrote: > Name: Fibernet Communications > ASN: 18883 > Port: Zayo Remote Switch (Premier Port) > IPv4: 206.108.255.133 /24 > IPv6: 2001:504:27:0:0:49c3::1 /64 > Peering Contact: peering(a)fibernetcommunications.net > > Route Server: YES > BFD Support NO I've updated the website. It seems Fibernet has no website. -- Richard

Nov. 27, 2018

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

by Doug McIntyre

On Sun, Nov 25, 2018 at 02:05:46PM -0600, Jay Hanke wrote: >Name: Fibernet Communications >ASN: 18883 >Port: Zayo Remote Switch (Premier Port) >IPv4: 206.108.255.133 /24 >IPv6: 2001:504:27:0:0:49c3::1 /64 >Peering Contact: peering(a)fibernetcommunications.net > >Route Server: YES >BFD Support NO > I've added them to the route servers. Welcome! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

Nov. 26, 2018