[db-wg] last-modified:, a succesor to changed:
- Next message (by thread): [db-wg] Replacing "changed" with "last-modified" implementation plan
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nigel Titley
nigel at titley.com
Mon Sep 1 16:01:01 CEST 2014
On 27/05/14 14:37, Job Snijders wrote: > Dear Working Group, > > This proposal has lingered around on the mailinglist for some time now, > and discussion seems to be finished. I'd like to offer this summary: > > Add two and remove one attributes to all objects with source: RIPE. > > * Addition of a "last-modified" attribute, example: > last-modified: 2014-04-15T13:15:30Z > * Addition of a "created" attribute, example: > created: 2014-04-15T13:15:30Z > * Deprecation of the "changed:" attribute (in phases!). > > Object updates that include a "changed:" line should receive a soft > warning and not a blocking error, this way existing scripts need not be > modified. In some future release 'changed:' lines will no longer be > published by the Whois Server, completing the deprecation. > > The 'last-modified:' and 'created:' attributes will be automatically > generated by the RIPE Whois Software. When clients include them in > updates the Whois Server will ignore them. > > Chairs, can we move this forward? > > Checking back on the discussion I think that consensus has been reached on this proposal. RIPE NCC can you proceed with it please? Nigel
- Next message (by thread): [db-wg] Replacing "changed" with "last-modified" implementation plan
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]