[db-wg] Replacing "changed" with "last-modified" implementation plan

Dear working group,

Following the consensus call we looked into the proposal to replace “changed” with “created” and “last-modified”.

Part of this proposal involves the removal of an attribute that is currently mandatory, and this has a potential big impact on both consumers (querying for objects) and producers (creating/updating objects) of the RIPE DB. To make sure that everything goes as smoothly as possible we therefore propose a multi phase approach allowing for ample testing and communication, and migration from using the current attribute to the new ones.

Before starting implementation we would like to discuss this proposal with the WG, both on list and in person at RIPE 69. The dates mentioned below should be regarded as provisional in that context. Once we have the okay from the working group to proceed we will communicate a finalised implementation plan. Also, we will communicate about each phase separately in future. Phase 1 and 2 to the mailing list, phase 3 can be discussed on the mailing list, and in person at RIPE 70.


Phase 1: Introduce new attributes: “created” and “last-modified”
========================================================================
Shortly after RIPE 69
26 Nov 2014: RC
10 Dec 2014: Production (2 weeks of RC)

- “last-modified” & “created” are added to output
  (adding new attributes is RFC compliant, parsers should ignore it if they don't understand)
- “changed” is accepted as-is today

Users of the RIPE DB that are using the “changed” attribute should migrate their tools to rely on “created” and “last-modified” instead during this phase.



Phase 2: “changed” becomes optional
========================================================================
Two months after RIPE 69
21 Jan 2015: RC
4 Mar 2015: Production (6 weeks of RC)

- When an object is submitted with “changed" attributes a WARNING is generated, but the update is accepted
- When an object is submitted _without_ the “changed” attribute it is accepted
- The “changed” attribute is marked as 'optional' in the RPSL schema

Users of the RIPE DB that are still using the “changed” attribute will start to see objects without any “changed” attributes. They are once more encouraged to migrate to using “created” and “last-modified” instead.

Users are encouraged to stop including “changed” attributes when they submit objects.


Phase 3: “changed” is completely deprecated
========================================================================
Two months after RIPE 70
27 May 2015: RC
8 Jul 2015: Production (6 weeks of RC)

- The “changed” attribute will be removed from all outputs: whois, restful, NRTM, ftpdump 
- When an object is submitted with “changed" attributes a ERROR is generated, and the update is rejected
- The “changed” attribute is removed from the RPSL schema

As the final step of deprecating the “changed” attribute all users are forced to stop using it. This means that users who are still submitting “changed” attributes, will start seeing their updates rejected at this point (after having received warnings for 4 months).

This step is necessary as the WG agreed that the “changed” attribute is no longer needed.



Kind regards,



Tim Bruijnzeels

Assistent Manager Software Engineering
RIPE NCC