To be clear my messages are NOT intended to be a downvote for the proposal, I’m just intending to foster discussion. I don't think https://www.micemn.net/technical.html needs major changes. Maybe change “Operators are responsible for the costs of operating their remote switch and the links to the core switch.” to “Operators are responsible for the costs of operating their remote switch and the links [TOWARDS] the core switch.” I think it's worthwhile acknowledging the distance to the proposed remote switch, the presumed lack of redundancy in the proposed backhaul. re: reliability: Is the lack of redundancy an accurate assumption, or would this be a protected wave? AS3128 has some experience in this area [AS3128 assists in operations of a 1000mi+ fiber ring for multistate research and education, including through Minneapolis and Minnesota] so I wanted to ack that in general with distance comes decreased reliability, and eBGP stability is important since topology changes lead to packet loss during convergence. I acknowledge we already have peers at MICE that are extensions out of Chicago [Google comes to mind]. I am also aware of the options that, for example, AS32621 provides in extending folks to Seattle IX as an opt-in value add, which is contrast to the ‘auto opt-in’ stance MICE route reflectors users enjoy. re: distance: based on geography or your home AS stance, this change could result in a longer RTT between some networks. AS3128 appears at exchanges other than MICE. But if you are in this club you are probably aware that you already have this potential problem and either you deal with it or not. Admittedly, our operations are less algorithmic and more reactionary. So if I were to focus discussions on either distance or reliability, I would focus more on reliability. Ultimately with MICE per-AS BGP community support, the publication of https://www.micemn.net/participants.html, and mailing list announcements of when new peers are brought onboard, AS3128 has all the tools it needs ==IF== we need to make a traffic engineer decision, which is great. If NOCIX comes onboard, I would welcome them and would have no intentions to proactively traffic engineer away from them via MICE. -Michael From: MICE Discuss <MICE-DISCUSS@LISTS.IPHOUSE.NET> On Behalf Of Aaron Wendel Sent: Saturday, January 29, 2022 9:46 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] NOCIX MICE Extension Proposal Our agreement with MN VOIP would be for transport from KC to Minneapolis. If the link became congested, we would order additional capacity. If MN VoIP could t provide it then we would get it someplace else. In the end, our intention is to be congestion free from KC to the MICE core. Aaron On Jan 29, 2022, at 12:30 PM, Michael Hare <000000097dab80c5-dmarc-request@lists.iphouse.net<mailto:000000097dab80c5-dmarc-request@lists.iphouse.net>> wrote: Hi- As I understand this will be an extension of an extension. It looks like this may be the second of that kind. If I understand this correctly the "South Front Networks Alberta Lea Remotes" switch hangs off of Minnesota VoIP? @ https://www.micemn.net/technical.html, I see "Operators are responsible for the costs of operating their remote switch and the links to the core switch. They must monitor their traffic levels and promptly add capacity to keep the links running congestion-free." My reading of above implies the current policy assumes a remote switch will connect to the MICE core directly. Perhaps we revisit the above language as it pertains to “the core switch”. -Michael From: MICE Discuss <MICE-DISCUSS@LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Richard Laager Sent: Friday, January 28, 2022 5:31 PM To: MICE-DISCUSS@LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: [MICE-DISCUSS] NOCIX MICE Extension Proposal For everyone's review and comment per our policy on remote switches: "As per the MICE remote switch policy this letter will serve as NOCIX’s intention to deploy, pending board approval, a MICE extension switch at the 1530 Swift facility at 1530 Swift St. North Kansas City, MO 64116. The purpose of this extension is to provide additional, low cost peering in the Kansas City and surrounding markets directly to the north-central US." See the attached PDF for full details. Richard ________________________________ 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