Hello all.

In November 2018 during the ZAPF (South Africa Peering Forum) meeting in
Cape Town, 3 major ISP's in Africa announced that they would enable
RPKI's ROV (Route Origin Validation) and the dropping of Invalid routes
as part of an effort to clean up the BGP Internet, on the 1st April, 2019.

On the 1st of April, Workonline Communications (AS37271) enabled ROV and
the dropping of Invalid routes. This applies to all eBGP sessions for
IPv4 and IPv6.

On the 5th of April, SEACOM (AS37100) enabled ROV and the dropping of
Invalid routes. This applies to all eBGP sessions with public peers,
private peers and transit providers, both for IPv4 and IPv6. eBGP
sessions toward downstream customers will follow in 3 months from now.

We are still standing by for the 3rd ISP to complete their
implementation, and we are certain they will communicate with the
community accordingly.

Please note that for the legal reasons previously discussed on various
fora, neither Workonline Communications nor SEACOM are utilising the
ARIN TAL. As a result, any routes covered only by a ROA issued under the
ARIN TAL will fall back to a status of Not Found. Unfortunately, this
means that ARIN members will not see any improved routing security for
their prefixes on our networks until this is resolved. We will each
re-evaluate this decision if and when ARIN's policy changes. We are
hopeful that this will happen sooner rather than later.

If you interconnect with either of us and may be experiencing any
routing issues potentially related to this new policy, please feel free
to reach out to:

    - noc@workonline.africa
    - peer...@seacom.mu

Workonline Communications and SEACOM hope that this move encourages the
rest of the ISP community around the world to ramp up their deployment
of RPKI ROV and dropping of Invalid routes, as we appreciate the work
that AT&T have carried out in the same vein.

In the mean time, we are happy to answer any questions you may have
about our deployments. Thanks.

Mark Tinka (SEACOM) & Ben Maddison (Workonline Communications).

Reply via email to