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/db-wg@ripe.net/
[db-wg] Proposal to revert NWI-10
- Previous message (by thread): [db-wg] Proposal to revert NWI-10
- Next message (by thread): [db-wg] Whois Release 1.99
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Arash Naderpour
arash.naderpour at gmail.com
Mon Dec 7 14:15:13 CET 2020
Hi, I was one of the few opping NWI-10 as I had this feeling that it could create more issues than solving any major one. but I think there is no way to revert it, unless someone proposes a new one and goes through the same process? Regards, Arash On Mon, Dec 7, 2020 at 11:58 PM Cynthia Revström via db-wg <db-wg at ripe.net> wrote: > Apologies if this email is a bit impolite. > > From the start NWI-10 seemed like a pointless policy to me and just a > policy that was made because the db-wg wanted to make more policies. > > But as it has already messed up the data on my resources, I see it as a > policy that messes up data and wastes time for no real advantage. > > Hence I suggest that we revert NWI-10 unless someone actually has a good > reason for why the legal address needs to match the delegated file, and how > to implement it in a non-messy way. > > - Cynthia > -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/db-wg/attachments/20201208/7e5af357/attachment.html>
- Previous message (by thread): [db-wg] Proposal to revert NWI-10
- Next message (by thread): [db-wg] Whois Release 1.99
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]