Re: Comments on draft-ietf-kitten-gssapi-extensions-iana-02.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Comments on draft-ietf-kitten-gssapi-extensions-iana-02.txt
Nicolas Williams wrote:
>On Tue, Mar 25, 2008 at 12:25:43PM -0400, Jeffrey Hutzelman wrote:
>
>
>>You are both missing the point.
>>Why does the entry need to have a status at all?
>>What purpose does it serve?
>>
>>
>You're right, it serves little purpose.
>
>Rather, we need to document how the entry came about (from the
>publication of an RFC, individual registration).
>
>
Sure.
>A way to mark an entry as obsoleted might be nice though. Someone adds
>GSS_Foo(), then later realizes that it should have some extra argument
>and they register GSS_Foobar() -- it'd be nice if they could mark
>GSS_Foo() as updated/obsoleted bu GSS_Foobar().
>
>
Indeed, "obsolete" is very useful. Adding an entry as experimental ("I
don't know if this is going to work, I might have to change the API
later on") might be useful as well.
_______________________________________________
Kitten mailing list
Kitten at ietf.org
https://www.ietf.org/mailman/listinfo/kitten
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.