Re: Q: Conflict between TSIG RFC and GSS-API documents

[Paul Vixie <paul@vix.com>]

> As the implementor that found the problem that placed the lock 
> on the GSS-API document, I belive that the lock should be removed 
> once the TSIG RFC has the appropriate modifications made to allow
> the GSS-TSIG draft to advance.  I don't think we should advance a
> Draft that is not in compliance with the RFC it is ment to enhance.

procedurally, there's also the option of adding an "Amends:" header
to the gss-tsig rfc, and putting in a paragraph that says "for the
purpose of gss-tsig, the following restriction in the original tsig
rfc is relaxed."  that seems like the easiest, fastest solution.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>