[rfc-dist] RFC 4557 on Online Certificate Status Protocol (OCSP) Support for Public Key Cryptography for Initial Authentication in Kerberos (PKINIT)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Jun 30 15:51:14 PDT 2006


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

        
        RFC 4557

        Title:      Online Certificate Status Protocol (OCSP) 
                    Support for Public Key Cryptography for 
                    Initial Authentication in Kerberos (PKINIT) 
        Author:     L. Zhu, K. Jaganathan,
                    N. Williams
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    lzhu at microsoft.com, 
                    karthikj at microsoft.com, 
                    Nicolas.Williams at sun.com
        Pages:      6
        Characters: 11593
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-krb-wg-ocsp-for-pkinit-06.txt

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

This document defines a mechanism to enable in-band transmission of
Online Certificate Status Protocol (OCSP) responses in the Kerberos
network authentication protocol.  These responses are used to verify
the validity of the certificates used in Public Key Cryptography for
Initial Authentication in Kerberos (PKINIT), which is the Kerberos
Version 5 extension that provides for the use of public key
cryptography.  [STANDARDS TRACK]

This document is a product of the Kerberos WG
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
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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