Re: [Curdle] Time to Review IANA SSH Registries Policies?

[Peter Gutmann <[e-mail]>]

denis bider <[e-mail]> writes:

>For most things, I'm not willing to go through this effort.

It is an excessive amount of effort in many cases.  Some years ago I assisted
in the creation of an RFC used by an industry body that amounted to "if you
see the value 27 in this location, assume X".  The RFC itself was something
like ten to fifteen pages of IETF-mandated gunk that no-one in the industry
body knew what to do with, it was only the fact that I sort-of volunteered to
do the work that prevented use of the previous approach, "take the last-
currently-used value and add ten or twenty and hope no-one ever gets to it".
There'a Laffer curve at play here, and the current process seems to be too far
off to the right of it.

Not sure what the solution is, but it should at least be less painful to
comply with the process than to circumvent it.

(My suggestion for a Security Considerations section that read "The number 27
may be offensive to some religions; caution is advised", just so we could say
something interesting somewhere, wasn't accepted).

Peter.