[db-wg] Decision on NWI-2 Historical queries
- Previous message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
- Next message (by thread): [db-wg] Decision on NWI-2 Historical queries
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Mon Apr 4 23:33:36 CEST 2022
Hi, I am sorry for the delayed response but I object to removing that constraint. It feels problematic to me from a privacy perspective, and it feels like the last deletion point is a fair balance between providing useful info and not providing too much info. I don't think this restriction should be removed, at least not without a very good reason to do so. -Cynthia On Thu, Mar 31, 2022 at 1:32 PM denis walker via db-wg <db-wg at ripe.net> wrote: > > Colleagues > > When I wrote the spec for historical queries, almost 10 years ago, I > included an arbitrary constraint to only show history back to the most > recent deletion point. This was to get something in production quickly > and see how useful it was. Over the years several people have asked > for this arbitrary constraint to be removed. No one has objected to > removing it. The co-chairs therefore recommend that this arbitrary > constraint be removed. The co-chairs now ask the RIPE NCC to produce > an impact analysis and implementation plan to remove it. We will then > seek a final approval from the community on the plan. > > cheers > denis > co-chair DB-WG > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/db-wg
- Previous message (by thread): [db-wg] Decision on NWI-4 INETNUM status values
- Next message (by thread): [db-wg] Decision on NWI-2 Historical queries
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]