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: [EMAIL PROTECTED],
[EMAIL PROTECTED],
[EMAIL PROTECTED]
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 [EMAIL PROTECTED] Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [EMAIL PROTECTED]
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [EMAIL PROTECTED] with the message body
help: ways_to_get_rfcs. For example:
To: [EMAIL PROTECTED]
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 [EMAIL PROTECTED] Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
[EMAIL PROTECTED] Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf-announce
