Re: Working Group Last Call: draft-ietf-kitten-krb5-gssapi-prf-02.txt and draft-ietf-kitten-gssapi-prf-02.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Working Group Last Call: draft-ietf-kitten-krb5-gssapi-prf-02.txt and draft-ietf-kitten-gssapi-prf-02.txt



On Thu, Apr 14, 2005 at 03:12:16PM -0400, Jeffrey Altman wrote:
> Today begins a Working Group Last Call on the working group
> drafts:
> 
>  * draft-ietf-kitten-gssapi-prf-02.txt
>  * draft-ietf-kitten-krb5-gssapi-prf-02.txt
> 
> There are known issues related to ID-Nits failures which will
> be addressed at the end of the working group last call period
> prior to submission to the IESG.
> 
> * draft-ietf-kitten-gssapi-prf-02.txt:
> 
>   - The IANA Considerations section is missing

I propose to add such a section claiming that "[this] document has no
IANA considerations."

>   - The boilerplate must be updated to RFC 3978
> 
>   - The IPR disclosure must be in conformance with BCP 79.

This will be done.

> * draft-ietf-kitten-krb5-gssapi-prf-02.txt:
> 
>   - The Introductions section is missing

I propose the following:

2.  Introduction

   This document specifies the Kerberos V GSS-API mechanism's pseudo-
   random funtion corresponding to [GSS-PRF].  The function is a "PRF+"
   style construction.

Alternatively I could rename the section currently named "Kerberos V GSS
Mechanism PRF" to "Introduction" :)

>   - The IANA Considerations section is missing

I propose to add such a section claiming that "[this] document has no
IANA considerations."

>   - The boilerplate must be updated to RFC 3978
> 
>   - The IPR disclosure must be in conformance with BCP 79.

This will be done.

> In addition, there are two issues which must be addressed
> for there to be a successful completion of the WGLC.
> 
> (1) Language Bindings for Java and C# should be provided as part
>     of draft-ietf-kitten-gssapi-prf

I have sent Seema and Juan Carlos proposed text, which I include here
(ignoring the PRF_READY thread):

> (2) Appropriate text specifying how the key usage for the Krb5
>     PRF function will be determined must be added.

Sam pointed out, indirectly, that no such key usage is needed.  I
proposed the removal of the text "and key usage X (TBD)" from the the
end of the first paragraph of section 2 of draft-ietf-kitten-krb5-
gssapi-prf.

> This WGLC will end on April 28, 2005.

Thanks.

I will make a proposal on the PRF_READY issue in a separate post.

Cheers,

Nico
-- 

_______________________________________________
Kitten mailing list
Kitten at lists.ietf.org
https://www1.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.