RFC 3767: Securely Available Credentials Protocol
In plain English — editorial summary, not part of the RFC
This document describes a protocol whereby a user can acquire cryptographic credentials (e.g., private keys, PKCS #15 structures) from a credential server, using a workstation that has locally trusted software installed, but with no user-specific configuration. The protocol's payloads are described in XML. This memo also specifies a Blocks Extensible Exchange Protocol (BEEP) profile of the protocol. Security requirements are met by mandating support for TLS and/or DIGEST-MD5 (through BEEP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3767
- Published
- June 2004
- Authors
- S. Farrell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 25
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3620The TUNNEL ProfileUpdated
October 2003
- RFC 3081Mapping the BEEP Core onto TCPCurrent
March 2001
- RFC 3080The Blocks Extensible Exchange Protocol CoreCurrent
March 2001
- RFC 3529Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)Updated
April 2003
- RFC 3275(Extensible Markup Language) XML-Signature Syntax and ProcessingCurrent
March 2002
- RFC 3195Reliable Delivery for syslogCurrent
November 2001
- RFC 4765The Intrusion Detection Message Exchange Format (IDMEF)Current
March 2007
- RFC 4767The Intrusion Detection Exchange Protocol (IDXP)Current
March 2007
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?