[lacnog] USA to Mexico Fiber Internet Exchange Equipment Recommendations

[Norman Jester]

I agree. We have been connecting many more cloud and hybrid deployments. One major challenge remains for countries such as Mexico where long dominant telecom control was monopolistic and preventing tech advancement. Because of that, we do not see enough hybrid and/or cloud going on in mexico other than a handful of basic services which are out-dated already and small-scale.
Yes there are some trying to gain cutting edge tech however the lack of said peering and transit availability on a wide scale places pause on the advancement.

Disclaimer: I’m not all knowing. There may be some movements going on I’m not aware of but from what I have seen thus far, that is my take on it.

Norm

> On May 17, 2019, at 10:05 AM, Arturo Servin <arturo.servin en gmail.com> wrote:
> 
> 
> Transit will stay, but margins and traffic are decreasing.
> 
> My take is that some of the transit providers would move to provide connectivity to the new world of Cloud and hybrid deployments and not necessary of the traditional IP that we know.
> 
> https://cloud.google.com/hybrid-connectivity/
> https://aws.amazon.com/directconnect/
> https://azure.microsoft.com/en-us/services/expressroute/
> 
> Regards
> as
> 
>> On Fri, May 17, 2019 at 12:02 AM Norman Jester <nj en ancientalien.com> wrote:
>> Transit will always be necessary as it’s the way the internet IS the internet, “a network of networks”. SDN and cloud based services are always superimposed on top of various transit routes. While we can run packets any way we like, I’ve always views cloud/cdn as service on top of transit. That is, transit is the backbone OF those services. Whether it be MPLS VPLS SDN or whatever other encapsulation, it still needs a highway to drive on.
>> 
>> Our border crossing fiber is a perfect example. Many protocols and network methodologies are being run over those lines we have supporting many a company.
>> 
>> Norm
>> 
>>> On May 16, 2019, at 6:28 AM, Arturo Servin <arturo.servin en gmail.com> wrote:
>>> 
>>> 
>>> I think that the ship regarding CDNs and peering vs transit has shipped long ago.
>>> 
>>> Today the new evolution could be how the Internet architecture will evolve with Cloud providers and hybrid deployments.
>>> 
>>> Regards
>>> as
>>> 
>>> 
>>>> On Thu, May 16, 2019 at 1:40 AM Steven G. Huter <sghuter en nsrc.org> wrote:
>>>> Hello Arturo
>>>> 
>>>> > Large ISPs and CDNs do not really need an IX to interchange traffic among them, they need colo
>>>> > facilities.
>>>> > 
>>>> > For the small ones that might get an advantage from an IX the current ones do not have the right
>>>> > ASNs there or are in the right places to attract CDNs or large ISPs interested in connecting to
>>>> > small players.
>>>> 
>>>> As you've outlined, is this trend part of the larger evolution of the 
>>>> global Internet architecture?
>>>> 
>>>> http://www.potaroo.net/presentations/2017-02-28-death-of-transit.pdf
>>>> 
>>>> This talk that Geoff Huston has delivered in numerous NOG events outlines 
>>>> the content vs carriage/peering theme and the impact of CDNs.
>>>> 
>>>> Steve
>>>> _______________________________________________
>>>> LACNOG mailing list
>>>> LACNOG en lacnic.net
>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
>>>> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
>>> _______________________________________________
>>> LACNOG mailing list
>>> LACNOG en lacnic.net
>>> https://mail.lacnic.net/mailman/listinfo/lacnog
>>> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
>> _______________________________________________
>> LACNOG mailing list
>> LACNOG en lacnic.net
>> https://mail.lacnic.net/mailman/listinfo/lacnog
>> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
> _______________________________________________
> LACNOG mailing list
> LACNOG en lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20190517/bdcaedf6/attachment.html>