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 ]
Shane Kerr
shane at time-travellers.org
Wed Apr 16 12:41:43 CEST 2014
Job, On Tue, 15 Apr 2014 15:31:36 +0200 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:". I'm not opposed. In fact I have supported such efforts in the past, which have always met with a universal "meh" from the working group. ;) However it seems you have good support now. :) 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. ("changed:" does not reveal this, as only a single you can literally put in whatever date you want there, although there may be checks to make sure that it is within the last century or so and not too far in the future.) 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. Cheers, -- Shane
- 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 ]