This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Previous message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Massimiliano Stucchi
max at stucchi.ch
Tue Feb 25 20:30:21 CET 2020
Hi everyone, On 20/02/2020 15:39, Petrit Hasani wrote: > As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussion of the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. > > At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. Today, me and the other proposers of this policy change had a meeting to discuss the feedback we have been receiving on the list. We understand that many people find this proposal controversial, and many have expressed themselves against it in the past days. We would like to encourage discussion and provide us with a bit of guidance on how the community would like to proceed. At present we have identified three ways of progressing: A) We can try to go ahead with this proposal, although it will be hard to get consensus; B) We can drop the proposal, and leave everything as is; C) We can change the proposal to a different ask for RIPE NCC. The idea could be to ask RIPE NCC to provide a SLURM file (similar to what APNIC does), so that single users can decide if they want to feed it to their validators. From what we gathered in the discussions, I think B) could be the most sought-after decision, but we would like to propose C) as the way forward. It would give the possibility to those who want to implement this solution to do it in a lightweight fashion. It would for sure be much much cheaper to implement. In any case, as Job already pointed out, I prepared a simple tool to generate a SLURM file using either the Team Cymru bogons list, or considering any unassigned space from the NRO delegated stats file. RIPE NCC has kindly provided help and patches to improve it. If you want to give it a go, you can find it here: https://github.com/stucchimax/rpki-as0-bogons Thank you for any suggestion or any discussion around this. Ciao! -- Massimiliano Stucchi MS16801-RIPE Twitter/Telegram: @stucchimax -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/routing-wg/attachments/20200225/530588ae/attachment.sig>
- Previous message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
- Next message (by thread): [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]