RFC 2692: SPKI Requirements
In plain English — editorial summary, not part of the RFC
The SPKI Working Group first established a list of things one might want to do with certificates (attached at the end of this document), and then summarized that list of desires into requirements. This document presents that summary of requirements. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC2692
- Published
- September 1999
- Authors
- C. Ellison
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2693SPKI Certificate TheoryCurrent
September 1999
- RFC 2712Addition of Kerberos Cipher Suites to Transport Layer Security (TLS)Current
October 1999
- RFC 2660The Secure HyperText Transfer ProtocolCurrent
August 1999
- RFC 2743Generic Security Service Application Program Interface Version 2, Update 1Updated
January 2000
- RFC 2744Generic Security Service API Version 2 : C-bindingsUpdated
January 2000
- RFC 2540Detached Domain Name System (DNS) InformationCurrent
March 1999
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
- RFC 2847LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKMCurrent
June 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?