Consider metadata in delta/snapshot files

mxsasha / nrtmv4

Ideas and work on the NRTM v4 protocol and implementations.

5 stars 7 forks source link

Consider metadata in delta/snapshot files #7

Closed mxsasha closed 2 months ago

mxsasha commented 3 years ago

In the delta and/or snapshot files, we could add space for metadata. What kind of data is useful there? IRRd has, for each individual object change, the reason for the change and a unique serial, which might help in tracing. This might depend on individual implementations.

job commented 2 years ago

Perhaps

a set of counters on the number of objects added/removed in a given snapshot or delta?
set of counters about how many objects in which class
A generation timestamp, and perhaps time elapsed to generate the file
hostname of the machine that generated the file

stkonst commented 2 years ago

A counter like how many times this object has been updated within the X amount of time is something useful. Also the amount of days until the key will rotate would be useful.

But I believe that once the draft goes out for public review we would have more suggestions on that subject. However, is good that the option exists to accommodate future needs.

sumkincpp commented 1 year ago

Timestamp for deltas are very useful - one can check if it's local snapshot up-to-date based on it's value.

Though, the latest timestamp in notification file should probably match the timestamp for the latest delta.

mxsasha commented 6 months ago

Discussed at RIPE88: we will add a place for metadata in the UNF to aid in debugging.

mxsasha commented 6 months ago

PR in #38