[routing-wg] 2019-08 Policy Proposal Withdrawn (SLURM file for Unallocated and Unassigned RIPE NCC Address Space)

Hello Jordi,

RIPE-710 describes the appeals process.

Kind regards,

Paul Hoogsteder.

> Hi all,
>
> I must insist here. What is the balance between opposition and support,
> following RFC7282, for this specific proposal. Can we have a summary of
> the inputs?
>
> I *could* (once we have the summary) agree that may be there is no
> consensus yet, but that is not a sufficient reason to withdraw a proposal.
>
> Regards,
> Jordi
> @jordipalet
>
>
>
> El 9/7/20 15:29, "routing-wg en nombre de Petrit Hasani"
> <routing-wg-bounces at ripe.net en nombre de phasani at ripe.net> escribió:
>
>     Dear colleagues,
>
>     The policy proposal 2019-08, "SLURM file for Unallocated and
> Unassigned RIPE NCC Address Space" has been withdrawn.
>
>     This proposal aimed 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 is archived and can be found at:
>     https://www.ripe.net/participate/policies/archived-policy-proposals/archive-policy-proposals/
>
>     Reason for withdrawal:
>     The WG Chair felt that raised concerns remained unaddressed and that
> there was a strong opposition against the proposal in the community.
>
>     Kind regards,
>     --
>     Petrit Hasani
>     Policy Officer
>     RIPE NCC
>
>
>
>
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of
> the individual(s) named above and further non-explicilty authorized
> disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited and will be considered a criminal offense. If you are not the
> intended recipient be aware that any disclosure, copying, distribution or
> use of the contents of this information, even if partially, including
> attached files, is strictly prohibited, will be considered a criminal
> offense, so you must reply to the original sender to inform about this
> communication and delete it.
>
>
>
>
>
>