[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 ]
Tore Anderson
tore at fud.no
Wed Apr 16 08:05:08 CEST 2014
* Job Snijders > Assessing the "freshness" of database objects can be a useful component > in many business processes, but as it stands today the "changed:" > attribute is severely crippled: > > Eleanor:~ job$ whois -h whois.ripe.net AS15562 | grep changed You'll want to use the "-B" option: $ whois -rB AS15562 | grep changed changed: hostmaster at ripe.net 20140224 [....] changed: job at instituut.net 20140204 > I propose that we introduce a new attribute called "last-modified" as a > replacement for functionality offered by past implementations of > "changed:". Makes sense to me. While we're at it, might as well add a similar "created:" for much the same reasons. IP Analyser, asused, the IPRAs, etc. are looking at the earliest changed: line present in order to infer the registration date, but since there's no requirement to retain old changed: lines when submitting updates that doesn't necessarily align very well with reality either. (Case in point: 87.238.48.64/28.) Tore
- 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 ]