[rfc-dist] RFC 4430 on Kerberized Internet Negotiation of Keys (KINK)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Mar 29 15:18:31 PST 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4430

        Title:      Kerberized Internet Negotiation of Keys 
        Author:     S. Sakane, K. Kamada, 
                    M. Thomas, J. Vilhuber
        Status:     Standards Track
        Date:       March 2006
        Mailbox:    Shouichi.Sakane at jp.yokogawa.com, 
                    Ken-ichi.Kamada at jp.yokogawa.com, 
                    mat at cisco.com, vilhuber at cisco.com
        Pages:      40
        Characters: 91261
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-kink-kink-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4430.txt

This document describes the Kerberized Internet Negotiation of Keys
(KINK) protocol.  KINK defines a low-latency, computationally
inexpensive, easily managed, and cryptographically sound protocol to
establish and maintain security associations using the Kerberos
authentication system.  KINK reuses the Quick Mode payloads of the
Internet Key Exchange (IKE), which should lead to substantial reuse
of existing IKE implementations.  [STANDARDS TRACK]

This document is a product of the Kerberized Internet Negotiation of Keys
Working Group of the IETF

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list