This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Proposal: key-cert update procedure change
- Previous message (by thread): [db-wg] Proposal for automated clean-up of references by name
- Next message (by thread): [db-wg] Proposal: key-cert update procedure change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dmitry Morozovsky
marck at rinet.ru
Wed Dec 11 13:00:47 CET 2002
Dear colleagues, changing today our key-cert objects, I'd encounter a bit of inconvenience: one can't cut'n'paste key-cert object from whois request: [s]he should manually delete method/owner/fingerpr attributes. My suggestion is: if one of r/o attributes exists in the object processed, DB should check whether auto-computed value of the attribute matches supplied value; - if yes, no error/warning should be produced - if no -- it should of course be reported; I think, it's up to the community to decide whether this condition should be treated as error or simply as warning. I think, the same procedure should be also applied to other de-facto read-only attributes, such as person name in person object. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru *** ------------------------------------------------------------------------
- Previous message (by thread): [db-wg] Proposal for automated clean-up of references by name
- Next message (by thread): [db-wg] Proposal: key-cert update procedure change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]