- mice-discuss - lists.micemn.net

interesting anti-spam technique

by Mike Horwath

That died about 15 years ago :) ... <HTML><BODY><BIG>Sender Address Authentication </BIG> This email address is protected by a system that requires a simple, one-time authentication of new senders. To authenticate your email address and immediately deliver your email, <A href="http://m.USGOauth.net/_val?:cleared-this-variable-so-it-isn't-resent">click this link</A> There is no need to re-send your original email as long as you click the link within one week. If you have trouble making the link work, please notify system administrators by replying to this email. Refer to the message headers below if you have questions about the authenticity of this notification. =============================================================================== <PRE> Date: Wed, 18 May 2016 17:49:57 +0000 From: Chris Wopat <wopat(a)WISCNET.NET> ... LISTSERV didn't catch this unfortunately. I have released the email in question. I really didn't think anyone used callback verification anymore and was surprised. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Mike Horwath

> On May 18, 2016, at 11:34, Matthew Beckwell <matthewb(a)AITECH.NET> wrote: > > Doug & Chih, Thanks for your efforts on this. > > Mike H, can you post to MICE-ANNOUNCE? Of course! -- Mike Horwath via iPad.

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Steve Howard

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Chris Wopat

The idea is to ONLY clear these specific action communities, leaving all other communities alone. -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Andrew Hoyos

Chris is referring to deleting the communities that the route server is using to take action (i.e.: it should be transparent in that regard and not leak communities). The original example I had sent on how to do this in Bird has this as part of it as well, and would be considered standard and best practice. These shouldn’t be leaked back and forth between participants. see: https://gitlab.labs.nic.cz/labs/bird/wikis/Route_server_with_community_base… function bgp_out(int peeras) { if !bgp_out_comm(peeras) then return false; # Remove IXP related communities bgp_community.delete([(0,*)]); bgp_community.delete([(myas,*)]); bgp_ext_community.delete([(ro,0,*)]); bgp_ext_community.delete([(ro,myas,*)]); return true; } -- Andrew Hoyos hoyosa(a)gmail.com > On May 18, 2016, at 1:00 PM, Steve Howard <showard(a)paulbunyan.net> wrote: > > Like I said. Perhaps I don't understand the question... > > I understand the statement "If an IX participant wants to control traffic directly with another peer, they would work with that participant to use their possibly pre existing action communities." But, how will that work if all communities are cleared by the route servers? Or are you saying only strip the communities that the route server uses to take action? > > > On 05/18/2016 12:49 PM, Chris Wopat wrote: >> The route servers are performing the action of not advertising. It shouldn't be on all IX participants to perform action on these communities or they wouldn't work as intended. >> >> If an IX participant wants to control traffic directly with another peer, they would work with that participant to use their possibly pre existing action communities. >> >> -- >> Chris Wopat >> Network Engineer, WiscNet >> wopat(a)wiscnet.net 608-210-3965 >> >> From: Steve Howard <showard(a)PAULBUNYAN.NET> >> Sent: May 18, 2016 12:23 PM >> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> Subject: Re: [MICE-DISCUSS] Route Server BGP communities (& OS upgrades) - 5/22/2016 >> >> On 05/18/2016 12:03 PM, Chris Wopat wrote: >>> On 05/18/2016 11:53 AM, Doug McIntyre wrote: >>>> Would you want the export function to >>>> clear any communities it had at the end? (Something that is NOT done >>>> right now). >>> >>> Yes, I would consider it standard practice to clear action communities after the action was taken so they don't propagate/leak beyond AS 53679. >>> >>> IX members may wish to filter them on import as well [1]. Both is probably the most sane outcome. >>> >>> [1] - ras's BGP community presentation is always good to review - https://www.nanog.org/meetings/nanog40/presentations/BGPcommunities.pdf >>> >>> >> >> Perhaps I don't understand the specific question? But, I would prefer that the communities not be stripped. If they are stripped, how would we pass action communities onto other MICE members that require action on their networks? Perhaps just strip out the 53679:* communities would be a better choice? >> >> 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 >

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Richard Laager

It seems pretty obvious to me that the route servers shouldn't clear ALL communities. Whether they need to clear 53679:* is another question. -- Richard

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Steve Howard

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Chris Wopat

The route servers are performing the action of not advertising. It shouldn't be on all IX participants to perform action on these communities or they wouldn't work as intended. If an IX participant wants to control traffic directly with another peer, they would work with that participant to use their possibly pre existing action communities. -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965 ________________________________ From: Steve Howard <showard(a)PAULBUNYAN.NET> Sent: May 18, 2016 12:23 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Route Server BGP communities (& OS upgrades) - 5/22/2016 On 05/18/2016 12:03 PM, Chris Wopat wrote: On 05/18/2016 11:53 AM, Doug McIntyre wrote: Would you want the export function to clear any communities it had at the end? (Something that is NOT done right now). Yes, I would consider it standard practice to clear action communities after the action was taken so they don't propagate/leak beyond AS 53679. IX members may wish to filter them on import as well [1]. Both is probably the most sane outcome. [1] - ras's BGP community presentation is always good to review - https://www.nanog.org/meetings/nanog40/presentations/BGPcommunities.pdf Perhaps I don't understand the specific question? But, I would prefer that the communities not be stripped. If they are stripped, how would we pass action communities onto other MICE members that require action on their networks? Perhaps just strip out the 53679:* communities would be a better choice? ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Steve Howard

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Chris Wopat

On 05/18/2016 11:53 AM, Doug McIntyre wrote: > Would you want the export function to > clear any communities it had at the end? (Something that is NOT done > right now). Yes, I would consider it standard practice to clear action communities after the action was taken so they don't propagate/leak beyond AS 53679. IX members may wish to filter them on import as well [1]. Both is probably the most sane outcome. [1] - ras's BGP community presentation is always good to review - https://www.nanog.org/meetings/nanog40/presentations/BGPcommunities.pdf -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Doug McIntyre

On Wed, May 18, 2016 at 11:30:25AM -0500, Chris Wopat wrote: > Is it possible to see examples of the config? Or at least verify that these > communities are stripped out on the route server after the action is taken? Here's what I'm doing now function bgp_out_comm(int peeras) { if ! (source = RTS_BGP ) then return false; if peeras > 65535 then { if (ro,0,peeras) ~ bgp_ext_community then return false; if (ro,MICEAS,peeras) ~ bgp_ext_community then return true; if ((ro,0,MICEAS) ~ bgp_ext_community) then return false; } else { if ((0,peeras) ~ bgp_community) || ((ro,0,peeras) ~ bgp_ext_community) then return false; if ((MICEAS,peeras) ~ bgp_community) || ((ro,MICEAS,peeras) ~ bgp_ext_community) then return true; if ((0, MICEAS) ~ bgp_community) || ((ro,0,MICEAS) ~ bgp_ext_community) then return false; } return true; } The route server would need to keep the community state, this is the export function per peer back out. So I guess I'm not understanding the last part of the request. Would you want the export function to clear any communities it had at the end? (Something that is NOT done right now). -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Richard Laager

> On May 18, 2016, at 11:34, Matthew Beckwell <matthewb(a)AITECH.NET> wrote: > > maybe we can convince Richard to throw up a section on the micemn.net technical page that lists the communities? :) Yes, will do. I have a few updates pending from the new members in the last couple days. I should have this all done in a few hours. -- Richard

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Matthew Beckwell

Doug & Chih, Thanks for your efforts on this. Mike H, can you post to MICE-ANNOUNCE? And maybe we can convince Richard to throw up a section on the micemn.net technical page that lists the communities? :) Thanks guys. ~Matthew On Wed, May 18, 2016 at 11:11 AM, Doug McIntyre <merlyn(a)iphouse.net> wrote: > Thanks to Chih Chen's help at the U of Wisc, I have testing done for > phase1 of the BGP communities exporting that have been requested. > (Phase2 would be doing prepends, but I'll have to lab up that > functionality as I saw the export function grow 10 times or so before I > stopped). > Most of the delay was waiting for others to test with me. > > I plan on implementing this MICE site wide on Sunday, 5/22/2016, starting > at > around 10:00PM - 11:59PM. > > All the testing looked good to us during testing, the functions > behaved as expected. This function is an expansion of what was tested > before. > ipHouse has had this export function on it since the end of winter. > > It is written to properly handle 32-bit ASNs (I believe, that part was > provided > by the BIRD WIKI author). And of course IPv4 and IPv6 make no difference. > > The communities supported by this setup will include > > 0:peerAS -- Don't export route prefix to this peer. > 53679:peerAS -- Always export route prefix to this peer. > 0:53679 -- Don't export route prefix to all MICE peers. > > > The steps of actually implementing this would be non-eventful, but I know > some will want to drop for it. > > > > ALSO, we really should upgrade the OS that is running the route > servers too. So I'll be doing OS updates and other upgrades that will > upgrade BIRD as well in the same window. BIRD moves from > 1.4.5 -> 1.5.0. The release notes say it mostly is OSPF changes, > I expect no problems in this update, BIRD has been very stable, and the OS > has been stable in production use here. > > Thanks. > > -- > Doug McIntyre <merlyn(a)iphouse.net> > ~.~ ipHouse ~.~ > Network Engineer/Provisioning/Jack of all Trades >

May 18, 2016

Re: Route Server BGP communities (& OS upgrades) - 5/22/2016

by Chris Wopat

On 05/18/2016 11:11 AM, Doug McIntyre wrote: > Thanks to Chih Chen's help at the U of Wisc, I have testing done for > phase1 of the BGP communities exporting that have been requested. > (Phase2 would be doing prepends, but I'll have to lab up that > functionality as I saw the export function grow 10 times or so before I stopped). > Most of the delay was waiting for others to test with me. > > I plan on implementing this MICE site wide on Sunday, 5/22/2016, starting at > around 10:00PM - 11:59PM. > > All the testing looked good to us during testing, the functions > behaved as expected. This function is an expansion of what was tested before. > ipHouse has had this export function on it since the end of winter. > > It is written to properly handle 32-bit ASNs (I believe, that part was provided > by the BIRD WIKI author). And of course IPv4 and IPv6 make no difference. > > The communities supported by this setup will include > > 0:peerAS -- Don't export route prefix to this peer. > 53679:peerAS -- Always export route prefix to this peer. > 0:53679 -- Don't export route prefix to all MICE peers. > > > The steps of actually implementing this would be non-eventful, but I know > some will want to drop for it. > > > > ALSO, we really should upgrade the OS that is running the route > servers too. So I'll be doing OS updates and other upgrades that will > upgrade BIRD as well in the same window. BIRD moves from > 1.4.5 -> 1.5.0. The release notes say it mostly is OSPF changes, > I expect no problems in this update, BIRD has been very stable, and the OS > has been stable in production use here. Great work folks, glad to see this coming in to production. Is it possible to see examples of the config? Or at least verify that these communities are stripped out on the route server after the action is taken? Cheers, -- Chris Wopat Network Engineer, WiscNet wopat(a)wiscnet.net 608-210-3965

May 18, 2016

Route Server BGP communities (& OS upgrades) - 5/22/2016

by Doug McIntyre

Thanks to Chih Chen's help at the U of Wisc, I have testing done for phase1 of the BGP communities exporting that have been requested. (Phase2 would be doing prepends, but I'll have to lab up that functionality as I saw the export function grow 10 times or so before I stopped). Most of the delay was waiting for others to test with me. I plan on implementing this MICE site wide on Sunday, 5/22/2016, starting at around 10:00PM - 11:59PM. All the testing looked good to us during testing, the functions behaved as expected. This function is an expansion of what was tested before. ipHouse has had this export function on it since the end of winter. It is written to properly handle 32-bit ASNs (I believe, that part was provided by the BIRD WIKI author). And of course IPv4 and IPv6 make no difference. The communities supported by this setup will include 0:peerAS -- Don't export route prefix to this peer. 53679:peerAS -- Always export route prefix to this peer. 0:53679 -- Don't export route prefix to all MICE peers. The steps of actually implementing this would be non-eventful, but I know some will want to drop for it. ALSO, we really should upgrade the OS that is running the route servers too. So I'll be doing OS updates and other upgrades that will upgrade BIRD as well in the same window. BIRD moves from 1.4.5 -> 1.5.0. The release notes say it mostly is OSPF changes, I expect no problems in this update, BIRD has been very stable, and the OS has been stable in production use here. Thanks. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 18, 2016

Re: Please welcome NebraskaLink to MICE

by Doug McIntyre

On Tue, May 17, 2016 at 05:57:42PM -0500, Jason Hanke wrote: > Name: NebraskaLink > ASN: 16851 > Port: NP MSP1 Remote xe-0/0/3 > IPv4: 206.108.255.70/24 > IPv6: 2001:504:27:0:0:41d3::1/64 > Contact: noc(a)nebraskalink.com > > Route Servers and website please! > > Welcome aboard! Sure thing, I have the route servers setup for this entry, ready to go. -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 18, 2016

Re: Please welcome NebraskaLink to MICE

by Hannigan, Martin

Wow! Lots of MICEicles today!! Welcome everyone! > On May 17, 2016, at 18:57, Jason Hanke <jayhanke(a)NEUTRALPATH.NET> wrote: > > Name: NebraskaLink > ASN: 16851 > Port: NP MSP1 Remote xe-0/0/3 > IPv4: 206.108.255.70/24 > IPv6: 2001:504:27:0:0:41d3::1/64 > Contact: noc(a)nebraskalink.com > > Route Servers and website 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

May 17, 2016

Please welcome NebraskaLink to MICE

by Jason Hanke

Name: NebraskaLink ASN: 16851 Port: NP MSP1 Remote xe-0/0/3 IPv4: 206.108.255.70/24 IPv6: 2001:504:27:0:0:41d3::1/64 Contact: noc(a)nebraskalink.com Route Servers and website 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

May 17, 2016

Re: Please welcome Paragon Solutions Group to MICE

by Doug McIntyre

On Tue, May 17, 2016 at 09:36:33AM -0500, Jason Hanke wrote: > Name: Paragon Solutions Group > Port: ge-2/0/9 (main switch ex4550) > ASN: 55043 > IPv4: 206.108.255.57/24 > IPv6: 2001:504:27:0:0:d703::1/64 > Contact: chris.dye(a)paragon.net > > Route Server and website updates please. Sure, had to do some switch work too, as I'm assuming all fiber ports are all 10Gbps now, but we don't have any 1G only fiber ports left. Got them in the route servers too. All set to go. Welcome aboard! -- Doug McIntyre <merlyn(a)iphouse.net> ~.~ ipHouse ~.~ Network Engineer/Provisioning/Jack of all Trades

May 17, 2016

MICE Facebook Page

by Jason Hanke

We have a Facebook page! Like it! https://www.facebook.com/MNMICE/ We also have a Facebook event for MICE UG20 in Eau Claire! https://www.facebook.com/events/695794023896344/ -- 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

May 17, 2016

Please welcome Paragon Solutions Group to MICE

by Jason Hanke

Name: Paragon Solutions Group Port: ge-2/0/9 (main switch ex4550) ASN: 55043 IPv4: 206.108.255.57/24 IPv6: 2001:504:27:0:0:d703::1/64 Contact: chris.dye(a)paragon.net Route Server and website updates please. Paragon will provide an SFP to Cologix for installation. 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

May 17, 2016

Please welcome Stealth Broadband to MICE!

by Jason Hanke

Name: Stealth Broadband ASN: TBD in Arin process now port: NP-MSP1 ge-0/0/2 IPv4: 206.108.255.69/24 IPv6: Pending ASN Contact: James.urwiller(a)stealthbroadband.com Please update the website at this time. They will be using the MICE connection to meet the multihoming requirements. We can update the other elements following the ASN assignment. 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

May 12, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Hannigan, Martin

All, I did look and we have received your requests. They will be taken care of shortly. Apologies for the delay. Best,, Marty > On May 9, 2016, at 21:38, Hannigan, Martin <marty(a)akamai.com> wrote: > > > Ill take a look in the queue. > > Thanks > > > > >> On May 9, 2016, at 21:09, Andrew Hoyos <hoyosa(a)GMAIL.COM> wrote: >> >> Likewise here, crickets…… >> >> >>> On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: >>> >>> Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. >>> >>> Jeremy >>> >>> From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin >>> Sent: Tuesday, April 26, 2016 9:34 PM >>> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >>> Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE >>> >>> >>> Greetings everyone. And Reid. :-) >>> >>> Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. >>> >>> Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. >>> >>> Thanks for your patience and for helping to build a better Internet in MSP. >>> >>> Best, >>> >>> Martin Hannigan // AS 20940 // AS 32787 >>> >>> >>> >>> >>> >>> >>> >>> ________________________________________ >>> To unsubscribe from the MICE-DISCUSS list, click the following link: >>> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 12, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Jeff Anderson

Same boat here as well. Jeff Anderson jeffa(a)implex.net 612.799.7277 Cell 612.339.8255 x200 Office 612.339.3310 Fax -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Jeremy Lumby Sent: Monday, May 9, 2016 9:05 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. Jeremy From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin Sent: Tuesday, April 26, 2016 9:34 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE Greetings everyone. And Reid. :-) Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. Thanks for your patience and for helping to build a better Internet in MSP. Best, Martin Hannigan // AS 20940 // AS 32787 ________________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 10, 2016

Re: Update for Akamai (AS 20940) < > MICE

by Hannigan, Martin

Ill take a look in the queue. Thanks > On May 9, 2016, at 21:09, Andrew Hoyos <hoyosa(a)GMAIL.COM> wrote: > > Likewise here, crickets…… > > >> On May 9, 2016, at 9:05 PM, Jeremy Lumby <jlumby(a)mnvoip.com> wrote: >> >> Has anyone heard back from peering(a)akamai.com ? It has been almost 2 weeks, my bi-lateral peering request has gone unanswered, and the session I built for them is not established. I know Marty mentioned they were working on some things, however I have not even gotten a reply acknowledging my emails. >> >> Jeremy >> >> From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Hannigan, Martin >> Sent: Tuesday, April 26, 2016 9:34 PM >> To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET >> Subject: [MICE-DISCUSS] Update for Akamai (AS 20940) < > MICE >> >> >> Greetings everyone. And Reid. :-) >> >> Our implementation is proceeding and we’re projecting that we’ll be moving bits back to the exchange in the next few weeks. >> >> Unfortunately, we’re dropping our route server sessions permanently. Everyone who is now route server only will need to established bi lateral peering. Send your peering request to peering(a)akamai.com with the requisite details (ASN, peer addresses). If you had a direct session previously, we have not forgotten it and there’s no need to restate. Traffic will return slowly, first with our SSL bits and then full on edge a few weeks after that. >> >> Thanks for your patience and for helping to build a better Internet in MSP. >> >> Best, >> >> Martin Hannigan // AS 20940 // AS 32787 >> >> >> >> >> >> >> >> ________________________________________ >> To unsubscribe from the MICE-DISCUSS list, click the following link: >> http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

May 10, 2016