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 (SLURM file for Unallocated and Unassigned RIPE NCC Address Space)
- Previous message (by thread): [routing-wg] Ensuring RPKI ROAs match your routing intent
- Next message (by thread): [routing-wg] 2019-08 Review Phase (SLURM file for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
ebais at a2b-internet.com
Thu Jul 2 17:24:05 CEST 2020
Dear WG, I know I'm a bit late (not for a lack of interest btw.. ) But as the WG Chairs are still debating on how to proceed on this policy .. I would like to add some additional questions on this.. Who will use this un-authenticated additional service from the RIPE NCC that people have to opt-in for and nobody is looking forward to ? Can't we use our resources and NCC funds for better things that this depreciated consensus result (that probably nobody is waiting for ? ) It is just another file that needs monitoring, procedures etc.. and I really can't see why ... If the previous version didn't get any consensus (even in an additional TAL .. ) .. why should we entertain this further... It is not that this version is an improvement on the implementation in the light of RPKI or routing .. or realtime processing .. Kind regards, Erik Bais On 25/05/2020, 16:08, "routing-wg on behalf of Petrit Hasani" <routing-wg-bounces at ripe.net on behalf of phasani at ripe.net> wrote: Dear colleagues, Policy proposal 2019-08, “SLURM file for Unallocated and Unassigned RIPE NCC Address Space", is now in the Review Phase. The proposal aims for the RIPE NCC to publish a SLURM file (Simplified Local Internet Number Resource Management with the RPKI), containing assertions with the origin “AS0” for all unallocated and unassigned address space under our control. The proposal has been updated following the last round of discussion. Version 3 of the proposal has moved from instructing the RIPE NCC to create ROAs to creating a SLURM file for use with Relying Parties/Validators. The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-08 https://www.ripe.net/participate/policies/proposals/2019-08#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-08/draft 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 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. We encourage you to read the proposal, impact analysis and draft document and send any comments to <routing-wg at ripe.net> before 23 June 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC
- Previous message (by thread): [routing-wg] Ensuring RPKI ROAs match your routing intent
- Next message (by thread): [routing-wg] 2019-08 Review Phase (SLURM file for Unallocated and Unassigned RIPE NCC Address Space)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]