Skip to main content

Concluded WG Kerberos (krb-wg)

Note: The data for concluded WGs is occasionally incorrect.

WG Name Kerberos
Acronym krb-wg
Area Security Area (sec)
State Concluded
Charter charter-ietf-krb-wg-08 Approved
Document dependencies
Additional resources Additional KRB-WG Web Page
Personnel Chairs Josh Howlett, Sam Hartman, Shawn M Emery
Area Director Stephen Farrell
Secretary Simon Josefsson
Mailing list Address ietf-krb-wg@lists.anl.gov
To subscribe https://lists.anl.gov/mailman/listinfo/ietf-krb-wg
Archive https://lists.anl.gov/pipermail/ietf-krb-wg/

Final Charter for Working Group

Kerberos over the years has been ported to virtually every operating
system. There are at least two open source versions, with numerous
commercial versions based on these and other proprietary implementations.
Kerberos evolution has continued in recent years, with the development
of new crypto and preauthentication frameworks, support for initial
authentication using public keys, improved support for protecting
clients' long-term keys during initial authentication, support for
anonymous and partially-anonymous authentication, and numerous
extensions developed in and out of the IETF.

However, wider deployment and advances in technology bring with them
both new challenges and new opportunities, such as exploring support
for new mechanisms for initial authentication, new cryptographic
technologies, and better integration of Kerberos with other systems
for authentication, authorization, and identity management.
In addition, several key features remain undefined.

The Kerberos Working Group will continue to improve the core Kerberos
specification, develop extensions to address new needs and technologies
related to the areas described above, and produce specifications for
missing functionality.

Specifically, the Working Group will:

  • Complete existing work, including:

  • Prepare and advance one or more standards-track specifications which
    update the Kerberos version 5 protocol to support non-ASCII principal
    and realm names, salt strings, and passwords, and localized error
    reporting. Maximizing backward compatibility is strongly desired.

  • Prepare and advance one or more standards-track specifications which
    update the Kerberos version 5 protocol in a backward-compatible way
    to support extending the unencrypted portion of a Kerberos ticket.

  • Prepare, review, and advance standards-track and informational
    specifications defining use of new cryptographic algorithms in the
    Kerberos protocol, on an ongoing basis.

  • Prepare, review, and advance standards-track and informational
    specifications defining use of new cryptographic algorithms in
    Kerberos using the RFC3961 framework. Cryptographic algorithms
    intended for standards track status must be of good quality, have
    broad international support, and fill a definite need.

  • Prepare, review, and advance standards-track and informational
    specifications defining new authorization data types for carrying
    supplemental information about the client to which a Kerberos ticket
    has been issued and/or restrictions on what the ticket can be used
    for. To enhance this ongoing authorization data work, a container
    format supporting the use cases of draft-sorce-krbwg-general-pac-01
    may be standardized.

  • Prepare a standards-track protocol to solve the use cases addressed
    by draft-hotz-kx509-01 including new support for digital signatures.

  • Prepare and advance one or more standards-track specifications
    which define mechanisms for establishing keys and configuration
    information used during authentication between Kerberos realms.

  • Prepare and advance a standards-track specification defining a
    format for the transport of Kerberos credentials within other
    protocols.

  • Today Kerberos requires a replay cache to be used in AP exchanges in
    almost all cases. Replay caches are quite complex to implement
    correctly, particularly in clustered systems. High-performance replay
    caches are even more difficult to implement. The WG will pursue
    extensions to minimize the need for replay caching, optimize replay
    caching, and/or elide the need for replay caching.

  • Produce an LDAP schema for management of the KDC's database.

Milestones

Date Milestone Associated documents
Dec 2011 Kerberos PAD authorization data to IESG
Dec 2011 Consider adopting kx509bis in response to use cases in draft-hotz-kx509-01
Oct 2011 Internationalized error support to IESG
Oct 2011 draft-ietf-krb-wg-pkinit-alg-agility to IESG
Aug 2011 draft-ietf-krbwg-camellia-cts to IESG

Done milestones

Date Milestone Associated documents
Done DHCP option for Kerberos to IESG
Done draft-ietf-krb-wg-clear-text-cred to IESG
Done draft-ietf-krb-wg-des-die-die-die to IESG
Done WGLC on DHCPv6 Option
Done WGLC on STARTTLS
Done WGLC on IAKERB
Done Anonymity back to IESG
Done WGLC on data model
Done WGLC on cross-realm issues
Done WGLC on OTP
Done WGLC on preauth framework
Done Anonymity to IESG
Done Naming Constraints to IESG
Done ECC for PKINIT to IESG
Done TCP Extensibility to IESG
Done Last Call on PKINIT ECC
Done Enctype Negotiation to IESG
Done PKINIT to IESG
Done Consensus on direction for Change/Set password
Done Last Call on OCSP for PKINIT
Done Submit K5-GSS-V2 document to IESG for consideration as a Proposed Standard
Done Complete first draft of Extensions
Done Complete first draft of Pre-auth Framework
Done Submit the Kerberos Extensions document to the IESG for consideration as a Proposed standard.
Done First meeting