Proposal: key-cert update procedure change
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@rinet.ru *** ------------------------------------------------------------------------
On 2002-12-11 15:00:47 +0300, Dmitry Morozovsky wrote:
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 this is a great idea for all generated attributes.
I think, the same procedure should be also applied to other de-facto read-only attributes, such as person name in person object.
What is the suggestion exactly? To produce a warning on changing of person/role names? -- Shane Kerr RIPE NCC
On Fri, 13 Dec 2002, Shane Kerr wrote: SK> > My suggestion is: SK> > SK> > if one of r/o attributes exists in the object processed, DB should SK> > check whether auto-computed value of the attribute matches supplied SK> > value; SK> > - if yes, no error/warning should be produced SK> > - if no -- it should of course be reported; I think, it's up to the SK> > community to decide whether this condition should be treated as SK> > error or simply as warning. SK> SK> I think this is a great idea for all generated attributes. SK> SK> > I think, the same procedure should be also applied to other de-facto SK> > read-only attributes, such as person name in person object. SK> SK> What is the suggestion exactly? To produce a warning on changing of SK> person/role names? Yes, I think DB should produce a warning, and mention contacting ripe-dbm@ripe.net to actually change read-only attribute. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
participants (2)
-
Dmitry Morozovsky -
Shane Kerr