[db-wg] "status:" attribute values in the RIPE database

Hi

Taking my co-chair hat off, my personal view is, yes it is a bad idea
to add a remark. This has been done many times in the past where
objects have been modified as part of an agreed update. Some of these
remarks have never been removed. They have been there for over 10
years. Objects then get bloated with multiple remarks about several
updates. It just becomes unnecessary clutter. If the update has been
well announced on the mailing list, maintainers have been notified of
the modification and it shows in the object history then I don't think
a remark is needed as well.

cheers
denis

On Wed, 4 Aug 2021 at 16:06, Sylvain Baya <abscoco at gmail.com> wrote:
>
> 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
>>
>> >
>> >> [...]
>> >>
>>