2.7.6 Common Authentication Technology Next Generation (kitten)

NOTE: This charter is a snapshot of the 78th IETF Meeting in Maastricht, Netherlands. It may now be out-of-date.

Last Modified: 2010-07-23


Tom Yu <tlyu@mit.edu>
Shawn Emery <shawn.emery@oracle.com>

Security Area Director(s):

Sean Turner <turners@ieca.com>
Tim Polk <tim.polk@nist.gov>

Security Area Advisor:

Tim Polk <tim.polk@nist.gov>

Mailing Lists:

General Discussion: kitten@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/kitten
Archive: http://www.ietf.org/mail-archive/web/kitten/current/maillist.html

Description of Working Group:

The Generic Security Services (GSS) API and Simple Authentication and
Security Layer (SASL) provide various applications with a security
framework for secure network communication.  The purpose of the Common
Authentication Technology Next Generation (Kitten) working group (WG) is
to develop extensions/improvements to the GSS-API, shepherd specific
GSS-API security mechanisms, and provide guidance for any new SASL-
related submissions.

This working is chartered to specify the following extensions and
improvements (draft-yu-kitten-api-wishlist-00) to the GSS-API:

* Provide new interfaces for credential management, which include the
  initializing credentials
  iterating credentials
  exporting/importing credentials

* Specify interface for asynchronous calls.

* Define interfaces for better error message reporting.

* Provide a more programmer friendly GSS-API for application developers.
This could include reducing the number of interface parameters, for
example, by eliminating parameters which are commonly used with the
default values.

This WG is also chartered to transition proposed SASL mechanisms as
GSS-API mechanisms:

* A SASL Mechanism for OpenID
* A SASL Mechanism for SAML

The transition from SASL to GSS-API mechanisms will allow a greater set
of applications to utilize said mechanisms with SASL implementations
that support the use of GSS-API mechanisms in SASL (draft-ietf-sasl-

* Shepherd draft-ietf-sasl-digest-to-historic to publication.

This WG should review proposals for new SASL and GSS-API mechanisms, but
may take on work on such mechanisms only through a revision of this
charter.  The WG should also review non-mechanism proposals related to
SASL and the GSS-API. However, work that adds SASL or GSS-API support in
application protocols should be handled by the application's WG.


* GSS-API: initializing credentials

* GSS-API: iterating credentials

* GSS-API: exporting/importing credentials

* GSS-API: specification for asynchronous calls

* GSS-API: interfaces/improvements for better error message reporting

* GSS-API: programmer friendly interfaces

* GSS-API: transition SASL mechanism for OpenID

* GSS-API: transition SASL mechanism for SAML

* GSS-API: publish draft-ietf-kitten-gssapi-extensions-iana

* GSS-API: publish draft-ietf-kitten-gssapi-naming-exts

* SASL: publish draft-melnikov-digest-to-historic

Goals and Milestones:

Done  Submit naming-exts to the IESG as Proposed Standard
Aug 2010  WGLC on gssapi-extensions-iana
Aug 2010  Submit gssapi-extensions-iana to the IESG as Proposed Standard


  • draft-ietf-kitten-gssapi-extensions-iana-06.txt
  • draft-ietf-kitten-gssapi-naming-exts-08.txt
  • draft-ietf-kitten-digest-to-historic-02.txt
  • draft-ietf-kitten-sasl-openid-00.txt
  • draft-ietf-kitten-sasl-saml-00.txt

    Request For Comments:

    RFC4178 Standard The Simple and Protected Generic Security ServiceApplication Program Interface (GSS-API) Negotiation Mechanism
    RFC4401 Standard A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)
    RFC4402 Standard A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) Mechanism
    RFC4768 I Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming
    RFC5178 PS Generic Security Service Application Program Interface (GSS-API) Internationalization and Domain-Based Service Names and Name Type
    RFC5179 PS Generic Security Service Application Program Interface (GSS-API) Domain-Based Service Names Mapping for the Kerberos V GSS Mechanism
    RFC5554 PS Clarifications and Extensions to the Generic Security Service Application Program Interface (GSS-API) for the Use of Channel Bindings
    RFC5587 PS Extended Generic Security Service Mechanism Inquiry APIs
    RFC5588 PS Generic Security Service Application Program Interface (GSS-API) Extension for Storing Delegated Credentials
    RFC5653 PS Generic Security Service API Version 2: Java Bindings Update

    Meeting Minutes


    kitten update
    Naming Extensions Lessons Learned