Re: Registration policies for draft-freed-smtp-limits and elsewhere

It appears that John C Klensin  <[email protected]> said:
>As implicitly threatened above, I have just posted
>draft-klensin-iana-consid-hybrid-01, "Hybrid IANA Registration
>Policy".  ....

I looked at it and honestly, if we want to chage RFC 8126, we should
simplify the registration rules, not add yet more complication.

There are basically two kinds of regstry, small ones where we might
run out of code points, and big ones where we won't.  (Small could
be under 256 available, big is over 50,000.  I can't think of any
in between.)

For small ones, we apply traditional quality control, expert review up
to standards action. For the large ones, it's FCFS. We can certainly
encourage registrants in large ones to provide detailed specifications
and offer help to do so, but even if they don't, register it anyway. 

R's,
John