[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Calling LinkedIn, Amazon and Akamai @ DE-CIX NY
- Subject: Calling LinkedIn, Amazon and Akamai @ DE-CIX NY
- From: bryan at shout.net (Bryan Holloway)
- Date: Thu, 31 Jan 2019 19:00:06 -0600
- In-reply-to: <[email protected]>
- References: <[email protected]> <CA+LTh5XD7bhuVBk63fr3O6V6SUW==SqoR07_4hgCNH7xB8EDUg@mail.gmail.com> <[email protected]> <CAF3KE_=+WNgLfaDZ+u9Vk-W4qsk3eYSP6ztAih0tW8Qmj+Hngg@mail.gmail.com> <[email protected]>
What do IXes do (or can do) to enforce the completion of a renumbering?
For example, Chicago Equinix announced a renumbering beginning of 2018,
and while 99% of our peers have renumbered, we still have an albeit
small handful who have not. (I will not name names.)
That situation didn't get nearly the "media attention" that DE-CIX New
York did, if any.
The "end of migration period" was May 1st 2018; here we are.
What's the next step, if any?
On 1/30/19 4:05 PM, Thomas King wrote:
> Hi all,
>
> Thanks for your support! This helps us getting all peers on the new IPv4
> space.
>
> Our looking glass shows which peers already have changed the IP settings
> (see section â??BGP session establishedâ??) and which peers are still
> working on it (see section â??BGP sessions downâ??):
>
> https://lg.de-cix.net/routeservers/rs1_nyc_ipv4#sessions-up
>