4.5. Expert Review
4.5. Expert Review
For the Expert Review policy, review and approval by a designated expert (see Section 5) is required. While this does not necessarily require formal documentation, information needs to be provided with the request for the designated expert to evaluate. The registry's definition needs to make clear to registrants what information is necessary. The actual process for requesting registrations is administered by IANA (see Section 1.2 for details).
(This policy was also called "Designated Expert" in earlier editions of this document. The current term is "Expert Review".)
The required documentation and review criteria, giving clear guidance to the designated expert, should be provided when defining the registry. It is particularly important to lay out what should be considered when performing an evaluation and reasons for rejecting a request. It is also a good idea to include, when possible, a sense of whether many registrations are expected over time, or if the registry is expected to be updated infrequently or in exceptional circumstances only.
Thorough understanding of Section 5 is important when deciding on an Expert Review policy and designing the guidance to the designated expert.
Good examples of guidance to designated experts:
- Extensible Authentication Protocol (EAP) [RFC3748], Sections 6 and 7.2
- North-Bound Distribution of Link-State and TE Information Using BGP [RFC7752], Section 5.1
When creating a new registry with Expert Review as the registration policy, in addition to the contact person field or reference, the registry should contain a field for change controller. Having a change controller for each entry for these types of registrations makes authorization of future modifications more clear. See Section 2.3.
Examples:
- EAP Method Types [RFC3748]
- HTTP Digest AKA algorithm versions [RFC4169]
- URI schemes [RFC7595]
- GEOPRIV Location Types [RFC4589]