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> 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> On Behalf Of Richard Laager Sent: Friday, January 28, 2022 5:31 PM To: 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