Skip to content

[IMPROVEMENT]: Discuss the topic of departing and returning registrants #19

@JesseCoretta

Description

@JesseCoretta

Q: What is the proper procedure for revolving (DEDICATED) registrants? For example, a registrant is added, serves as a currentAuthority for one or more OIDs, then departs, is reduced to firstAuthority (previous) status, but then later returns to resume the same role -- whether or not the same OIDs are implicated?

A: There is no single answer, so we'll produce individual perspectives separately

  1. Are <X>StartTimestamp and possibly <X>EndTimestamp values important? In other words are you preserving the dates during which the "hand-off" of authority takes place? If so, the best solution would be to create a new registrant entry at the commencement of each "stint". As opposed to "exhuming" or "resurrecting" a firstAuthority and re-branding it as a currentAuthority, which causes GAPS in the timeline of authorities, it is best to create a new registrant for that objective only.

  2. If the answer was NO for question 1, one can simply perform the aforementioned "resurrection" of a firstAuthority followed by a conversion to currentAuthority and an appropriate DN update for referencing registration values.

Metadata

Metadata

Assignees

Labels

RADITThe OID Directory: The RA DITTENTATIVEUnconfirmed changes for considerationdocumentationImprovements or additions to documentationenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions