Kerberized Internet Negotiation of Keys (kink)

This Working Group did not meet

NOTE: This charter is a snapshot of the 55th IETF Meeting in Altanta, Georgia USA. It may now be out-of-date.

Last Modifield: 06/17/2002

Chair(s):
Derek Atkins <derek@ihtfp.com>
J Trostle <jtrostle@world.std.com>
Security Area Director(s):
Jeffrey Schiller <jis@mit.edu>
Steve Bellovin <smb@research.att.com>
Security Area Advisor:
Jeffrey Schiller <jis@mit.edu>
Mailing Lists:
General Discussion: ietf-kink@vpnc.org
To Subscribe: majordomo@vpnc.org
In Body: subscribe ietf-kink
Archive: www.vpnc.org/ietf-kink/
Description of Working Group:
The KINK working group is chartered to create a standards track protocol to facilitate centralized key management for IPsec security associations as defined in RFC 2401, as an alternative to IKE (RFC 2409). Participating systems will use the Kerberos architecture as defined in RFC 1510 (and its successors) for key management. The goal of the working group is to produce a streamlined, fast, easily managed, and cryptographically sound protocol that does not require public key operations, and is compatible with existing and future Kerberos infrastructures.

The working group will not require changes to either IPsec (RFC 2401), or Kerberos (RFC 1510).

Goals and Milestones:
Done  Reach Consensus on requirements document
Done  Meet at San Diego IETF to review drafts
JAN 01  Reach Consensus on base draft protocol
FEB 01  Conduct WG last call on base draft prototol
MAR 01  Begin Interoperability bakeoffs
AUG 01  Document interoperability results. Make decision to recycle or move forward
Internet-Drafts:
  • - draft-ietf-kink-kink-03.txt
    • Request For Comments:
    RFCStatusTitle
    RFC3129 I Requirements for Kerberized Internet Negotiation of Keys

    Current Meeting Report

    None received.

    Slides

    None received.