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] last-modified:, a succesor to changed:
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Wed Apr 16 13:23:17 CEST 2014
On Wed, Apr 16, 2014 at 12:41:43PM +0200, Shane Kerr wrote: > Job Snijders <job at instituut.net> wrote: > > > I propose that we introduce a new attribute called "last-modified" as > > a replacement for functionality offered by past implementations of > > "changed:". > > One possible issue: I have been told that some LIRs don't want their > competition seeing the dates of their database activity for whatever > reason. I cannot imagine how one would benefit from hiding this information, also: the data is already public anyway, today :-) To quote Nick: > % whois -h whois.ripe.net " --list-versions AS15562" > I hope that this is a minor concern, but maybe it is good to engage with > the appropriate working group(s) early in this process to avoid any > last-minute surprise objections. I'm thinking an FYI to address policy > and NCC services might be the right approach, but maybe Wilfried can > advise better. OK. But let's first reach some consensus in this group. Comments from Wilfriend are always welcome. Kind regards, Job
- Previous message (by thread): [db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] last-modified:, a succesor to changed:
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]