[db-wg] "status:" attribute values in the RIPE database
- Previous message (by thread): [db-wg] Historical queries
- Next message (by thread): [db-wg] "status:" attribute values in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sylvain Baya
abscoco at gmail.com
Wed Aug 4 16:06:07 CEST 2021
Dear DB-WG, Le mer. 28 juil. 2021 à 4:15 PM, Edward Shryane via db-wg <db-wg at ripe.net> a écrit : > Dear Colleagues, > > Hi Edward, Thanks for your notification, brother. > Thanks to the co-chairs for declaring a consensus, the DB team will start > working on the implementation. > > The implementation plan consists of two parts: > > [...] > As only the case of the "status:" value is changed, the objects remain > syntactically the same. We will not send notification emails to maintainers > for the change, apart from notifying the db-wg. The "last-modified:" value > will not change, but a new object version will be created (so the change > will be visible in the version history). > ...ok, cool! Question, please: is it a bad idea to add a comment as in "remarks:" attribute? Shalom, --sb. > All changes will be visible in NRTM as the objects are updated. The change > can be considered a NOOP. > > All changes will be visible in that night's database dump and split files. > > [...] > > Please let me know if you have any questions. > > Regards > Ed Shryane > RIPE NCC > > > > >> [...] > >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20210804/5ba6bcdf/attachment.html>
- Previous message (by thread): [db-wg] Historical queries
- Next message (by thread): [db-wg] "status:" attribute values in the RIPE database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]