My only comment is that I find it ironic that these two paragraphs appear in the same message:
>Fortunately you cannot change GSS-API v2, and I will do all that I can >to prevent a spec from entering the standards track that calls itself >a revision of GSS-API v2 does not have gss_canonicalize_name() and >gss_export_name() fully backwards compatible with current GSS-API v2. [...] >A few years ago the IESG was quite explicit that the IETF is not >a rubber-stamping authority. If you want something standardized >you must be prepared for changes to the (initial) proposal. >I hope the IESG still lives up to its standards. --Ken -++**==--++**==--++**==--++**==--++**==--++**==--++**== This message was posted through the Stanford campus mailing list server. If you wish to unsubscribe from this mailing list, send the message body of "unsubscribe ietf-cat-wg" to [EMAIL PROTECTED]
