Re: [kitten] Murray Kucherawy's No Objection on draft-ietf-kitten-krb-spake-preauth-11: (with COMMENT)

[Simo Sorce <[e-mail]>]

The scope of this registry is to avoid conflicts in implementations,
having expired drafts is not really a big issue, unless you are running out of space, and there is no indication that this is a problem.

So there is nothing bad in registering a number for a promising I-D that could become an RFC, even if in the end it does not pan out.

On Fri, 2024-01-19 at 06:22 +0000, Eric Vyncke (evyncke) wrote:
> I can only second Murray’s point: having a IANA registry (specification required) with pointers to expired drafts is ‘unfortunate’ to say the least.
> 
> Nothing actionable though except changing RFC 8126 with a bis to prevent repeating this situation
> 
> -éric
> 
> 
> The IANA Kerberos preauthentication registry contains references
> to numerous expired drafts besides this one.
> 
> I think that's unfortunate, since the whole idea of having a specification be required is that it needs to be relatively stable, and something that has expired is, to me at least, not.
> 
> -MSK
> 

-- 
Simo Sorce
Distinguished Engineer
RHEL Crypto Team
Red Hat, Inc