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/[email protected]/

[db-wg] last-modified:, a succesor to changed:

Previous message (by thread): [db-wg] [ncc-services-wg] Blocking Access to Personal Data Objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Job Snijders job at instituut.net
Tue May 27 15:37:06 CEST 2014

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? 

Kind regards,

Job

Previous message (by thread): [db-wg] [ncc-services-wg] Blocking Access to Personal Data Objects in the RIPE Database

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]