[db-wg] Proposal: key-cert update procedure change
- Previous message (by thread): [db-wg] Proposal: key-cert update procedure change
- Next message (by thread): [db-wg] Updated proposal for clean-up of references by name
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Dmitry Morozovsky
marck at rinet.ru
Tue Dec 17 19:18:12 CET 2002
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 at ripe.net to actually change read-only attribute. 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: key-cert update procedure change
- Next message (by thread): [db-wg] Updated proposal for clean-up of references by name
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]