You are here: Home > Participate > Join a Discussion > RIPE Forum
RIPE Forum v1.4.1

Routing Working Group

Threaded
Collapse

[routing-wg] De-bogonising 2a10::/12

Nikolas Pediaditis

2020-01-08 12:17:43 CET

RIPE NCC staff member

Dear colleagues,

A few months ago the RIPE NCC became the first RIR to receive an additional /12 IPv6 allocation (2a10::/12) from IANA.

We will soon begin to delegate space from this IPv6 block to LIRs. Prior to this, in order to improve routability and minimise the risk of filtering, the RIPE NCC will perform several de-bogonising activities in the next few weeks.

We plan to start announcing the full /12, as well as a few /32 or longer blocks out of 2a10::/12 from AS12654 (RIPE Routing Information System (RIS)), within the next few days. We will analyse data from RIS and RIPE Atlas and we plan to write up an analysis around this effort.

We want to remind everybody to update their bogon filters and allow routes originating from 2a10::/12 in their network.


Kind regards,

Nikolas Pediaditis
Registration Services and Policy Development Manager
RIPE NCC
User Image

Emile Aben

2020-01-16 09:07:06 CET

RIPE NCC staff member

Dear colleagues,

We have now started de-bogonising 2a10::/12!

As part of this, we are announcing a couple of prefixes out of 2a10::/12
from AS12654 (RIPE's Routing Information Service, RIS). Pingable targets
have been configured in these prefixes, and we invite network operators
to test for themselves whether this address space is reachable.

The simplest way to do this would be to perform a ping6 to 2a10:4::1 .

Using RIPE Atlas and RIS, we will also be carrying out our own tests in
order to investigate connectivity and filtering for this address space.
We plan to share our results with the RIPE community via RIPE Labs
within the next few days.

For those who want to do other testing, beyond the basic test described
above, we have a total of 8 targets available for this, with 2 different
prefix lengths and all variations of having ROUTE objects in the RIPE DB
and/or ROAs.

2a10:3:4::1  /48 ROUTE object + ROA
2a10:3:5::1  /48 no ROUTE object + ROA
2a10:3:6::1  /48 ROUTE object + no ROA
2a10:3:7::1  /48 no ROUTE object + no ROA

2a10:4::1    /32 ROUTE object + ROA
2a10:5::1    /32 no ROUTE object + ROA
2a10:6::1    /32 ROUTE object + no ROA
2a10:7::1    /32 no ROUTE object + no ROA

Kind regards,

Emile Aben
RIPE NCC