Hi,

On Tue Oct 25 18:12:41 2016, [email protected] wrote:
> Pascal Thubert (pthubert) writes:
> > CC ing Amanda for clarification on "RFC Required". 
> > For all I know,  with "RFC required", the IANA must also request
> > that the IESG designate an expert to review the new registration. 
> > The difference if I am correct is that "RFC required" adds limit the
> > use of the IETF IE only to address requests from IETF
> > specifications. 
> > Amanda: is this correct?
> 
> I do not think that is correct. When using specification required,
> then designated expert is also needed to say whether the specification
> is clear enough etc.
> 
> When using RFC required, then any RFC is enough, including RFC Editor
> Independent submission. There is no expert needed, as the RFCs are
> considered to be good enough documents.
> 
> From RFC 5226:
> 
>     RFC Required - RFC publication (either as an IETF submission or as
>         an RFC Editor Independent submission [RFC3932]) suffices.
>       Unless otherwise specified, any type of RFC is sufficient
>       (e.g., Informational, Experimental, Standards Track, etc.).

That's correct. The only procedures that require expert review are the Expert 
Review and Specification Required procedures. 

The next-most-rigorous procedure is RFC Required, which as Tero noted, can mean 
any type of RFC.

If you want to require an IETF-stream RFC without requiring a standards-track 
RFC, the procedure you want would be IETF Review. 

There are a few registries that use hybrid registration procedures. If it's 
what fits the registry best, you could state that the registration procedure is 
"IETF-stream RFC reviewed by an IESG-designated expert" (or "IETF Review with 
Expert Review"). 

Alternatively, if an RFC is not required, but there are specific requirements 
an IESG-designated expert should take into account, these could be listed in a 
sub-section of the IANA Considerations section. 

Best regards,

Amanda Baber
Lead IANA Services Specialist
PTI

_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch

Reply via email to