Now forwarded.
https://www.ripe.net/participate/mail/forum/routing-wg/PDM2OTU0RkJFLUU0OEUtN...
---------- Forwarded message --------- From: Nikolas Pediaditis <npediaditi@ripe.net> Date: Wed, 8 Jan 2020 at 14:28 Subject: [nog-org] Fwd: [routing-wg] De-bogonising 2a10::/12 To: <nog-org@ripe.net> Dear colleagues, Earlier today we sent the bellow announcement to several mailing lists. Could you please pass it on to your respective NOG’s mailing lists as well? Thank you in advance! Best regards, Nikolas Pediaditis RIPE NCC Begin forwarded message: From: Nikolas Pediaditis <npediaditi@ripe.net> Subject: [routing-wg] De-bogonising 2a10::/12 Date: 8 January 2020 at 12:17:43 CET To: routing-wg@ripe.net, Menog@menog.net, afnog@afnog.org, nanog@nanog.org, lacnog@lacnic.net, discuss@enog.org, sanog-request@sanog.org 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 _______________________________________________ nog-org mailing list nog-org@ripe.net https://lists.ripe.net/mailman/listinfo/nog-org