Re: [kitten] Updating IANA krb5 GSSAPI token type registry

[Simo Sorce <[e-mail]>]

On Tue, 2014-03-04 at 16:44 -0500, Jeffrey Hutzelman wrote:
> On Tue, 2014-03-04 at 16:36 -0500, Simo Sorce wrote:
> > On Tue, 2014-03-04 at 11:49 -0500, Benjamin Kaduk wrote:
> > > 
> > > To me, this seems like a(nother) bug in RFC 7055, but of course it is
> > > not one that can be reasonably fixed.  I guess that the easiest way
> > > forward is to publish a quick document that reserves 0405 and 0501
> > > noting that they were in use before the registry was established.
> > 
> > +1 if there is a registry we must avoid errors in allocations, and
> > allocating 0405 or 0501 to something else would definitely cause
> > standards issues.
> 
> No, you have it backwards.  The registry doesn't create the requirement
> to avoid conflicting allocations; it is a tool for helping to meet that
> requirement.
> 
> We probably don't actually need to publish a document; it ought to be
> sufficient to point out to IANA that there is a conflict and ask that
> the relevant numbers be marked reserved.

I think we are saying the same thing, I do not care what is the means of
getting those numbers marked as reserved as long as it is done and
quickly.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York