Re: [kitten] taking on new work?

[Benjamin Kaduk <[e-mail]>]

On Wed, Apr 05, 2017 at 08:40:27AM -0400, Jeffrey Altman wrote:
> On 4/5/2017 12:55 AM, Benjamin Kaduk wrote:
> >
> > To give some historical perspective on the sense of the working
> > group, back in Buenos Aires the chairs had a (very broad!) list of:
> > draft-williams-kitten-krb5-pkcross
> > draft-williams-kitten-krb5-extra-rt
> > draft-williams-kitten-generic-naming-attributes
> > draft-williams-kitten-impersonation-naming-attr
> > draft-vanrein-kitten-rfbsasl
> > draft-vanrein-dnstxt-krb1
> > draft-vanrein-krb5-kdh
> > draft-vanrein-kitten-krb5-pseudonymity
> > draft-mccallum-kitten-krb-spake-preauth
> > draft-kaduk-kitten-des-des-des-die-die-die
> > draft-howard-gssapi-aead
> > draft-mccallum-kitten-krb-service-discovery
> 
> Not on this list (possibly because the draft was expired at the time of
> the Buenos Aires meeting) is
> 
>   https://datatracker.ietf.org/doc/draft-cantor-ietf-kitten-saml-ec/


That was adopted years ago and became
https://datatracker.ietf.org/doc/draft-ietf-kitten-sasl-saml-ec/ ,
though apparently no one set the right metadata to show it as
replacing the draft-cantor version.

If you think it is ready to publish, please send a review of the
latest version to the list (or a link to one you already sent), and
we can make a github repo to track reviews of that document and try
to move it forward.  I did not un-expire it with my batch from last
week because I was unsure if there was any WG interest in moving it
forward, though it seems I now have the answer to that question.

> which has an open source implementation for Shibboleth at
> 
>   https://github.com/fedushare/mech_saml_ec
> 
> > and the sense of the room was that
> > draft-mccallum-kitten-krb-spake-preauth and
> > draft-williams-kitten-krb5-pkcross were the most promising.
> > 
> > (draft-mccallum-kitten-krb-service-discovery has since been adopted)
> > 
> > Recall that our current work items are listed at:
> > https://datatracker.ietf.org/wg/kitten/documents/ , some of which
> > are believed to be ready to send to the IESG or nearly so.
> > 
> > What do people currently feel are the top one or two highest
> > priority items for the WG to consider?  (Such items need not be
> > limited to the above list, of course; note that, e.g.,
> > draft-schmaus-kitten-sasl-ht-00 has recently appeared on the list of
> > related internet-drafts.)
> > 
> > I'll also note that we should be able to ask the curdle WG to take
> > on draft-kaduk-kitten-des-des-des-die-die-die, which is simple
> > deprecation of RC4 and 3DES (and some registry cleanup from RFC
> > 6649).  I'll plan to do that unless people want to do it in kitten
> > instead.  One might also ask about moving
> > draft-ietf-kitten-pkinit-alg-agility to curdle (since it moves
> > PKINIT off SHA1), but that's a little more complicated since it
> > first has to add the agility to do so, and judging by the reviews
> > accumulated and noted at
> > https://github.com/kittenwg/draft-ietf-kitten-pkinit-alg-agility ,
> > it should be basically done already.
> 
> I believe that draft-kaduk-kitten-des-des-des-die-die-die fine as-is and
> should simply be published by Kitten.

Have you reviewed a specific revision of it so as to form that
opinion?  Again, if we don't have a number of reviews that we can
track, the document is just going to sit there and not move forward.

> I would like to see the following documents be adopted
> 
>   draft-williams-kitten-krb5-pkcross
>   draft-howard-gssapi-aead
>   draft-cantor-ietf-kitten-saml-ec

Hmm, that is only "one or two" on a technicality (the
draft-cantor-ietf-kitten-saml-ec is already a WG item).

-Ben