[RPKI-Deployers] welcome Centurylink / AS 3356 / AS 209 / etc

Tal, Guy guy.tal at centurylink.com
Wed Nov 14 18:20:11 EST 2018


Cheers all. I think I know most of you but for those that I don't, I've been in the industry about 20 years now. Other than what anyone can see on LinkedIn, of interest here could be while at GBLX many moons ago, I contributed in small measure to rpsec and s-bgp (not that much of it went anywhere) and wrote and rewrote most of the edge routing policy for most of the companies I've worked for (GBLX, LLNW, TMRK, VMW). I'm excited to be part of the group that carries RPKI over the goal line and hopefully makes things like route hijacking a thing of the past (finally).

-----Original Message-----
From: RPKI-Deployers <rpki-deployers-bounces at puck.nether.net> On Behalf Of Job Snijders
Sent: Wednesday, November 14, 2018 9:51 AM
To: rpki-deployers at puck.nether.net
Subject: [RPKI-Deployers] welcome Centurylink / AS 3356 / AS 209 / etc

Hi all,

I've added Guy Tal Weber from CenturyLink (AS 209, 3356) to this mailing list.

>From what I understand KPN intend to deploy "invalid == reject" in 12 to
18 months

Kind regards,

Job

Current members list:

    Tom Scholl              Amazon
    Jay Borkenhagen         AT&T
    Nimrod Levy             AT&T
    Jared Mauch             Akamai
    Guy Tal                 Centurylink
    Jérôme Fleury           Cloudflare
    Joel Jaeggli            Fastly
    Christopher Morrow      Google
    Nick Hilliard           INEX
    Markus Weber            KPN
    Fredrik Korsbäck        Nordunet
    Job Snijders            NTT
    William McCall          NTT
    Tim Reinders            XS4ALL
    Miquel van Smoorenburg  XS4ALL
--
RPKI-Deployers mailing list
RPKI-Deployers at puck.nether.net
https://puck.nether.net/mailman/listinfo/rpki-deployers


This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.




More information about the RPKI-Deployers mailing list