RFC 3157: Securely Available Credentials - Requirements
In plain English — editorial summary, not part of the RFC
This document describes requirements to be placed on Securely Available Credentials (SACRED) protocols. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3157
- Published
- August 2001
- Authors
- A. Arsenault; S. Farrell
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3621Power Ethernet MIBCurrent
December 2003
- RFC 3156MIME Security with OpenPGPCurrent
August 2001
- RFC 3161Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)Updated
August 2001
- RFC 3164The BSD Syslog ProtocolObsoleted
August 2001
- RFC 3183Domain Security Services using S/MIMECurrent
October 2001
- RFC 3129Requirements for Kerberized Internet Negotiation of KeysCurrent
June 2001
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 3126Electronic Signature Formats for long term electronic signaturesObsoleted
September 2001
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?