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/
Immediate - Date in Changed field
- Previous message (by thread): Immediate - Date in Changed field
- Next message (by thread): Immediate - Date in Changed field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sean Shapira
sds at jazzie.com
Fri Jan 17 01:48:58 CET 1997
Wilfried wrote: > How about running the RIPE-DB (and maybe gradually all the others :-) on > a UTC basis, according to some recent suggestions? > Just for a sneak preview on one of the small agenda items for the DB WG :-) I'm glad this topic was raised, and hope it gets discussed and resolved at the DB WG. The location-centricity of some otherwise admirable DB operators can be simply astonishing when first encountered. Apparently the "changed" attribute properly belongs to the submitter, and although submitters might be encouraged to use universal time to determine the date used, it's really their choice, not the choice of the DB operator. It would be great if the workgroup could encourage current DB operators to follow this policy, e.g. encourage them to accept transactions where the "changed" attribute date is -- for their timezone -- in the future. -- Sean Shapira sds at jazzie.com (206) 443-2028
- Previous message (by thread): Immediate - Date in Changed field
- Next message (by thread): Immediate - Date in Changed field
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]