Securely Available Credentials Protocol
RFC 3767, “Securely Available Credentials Protocol”, is a Proposed Standard document published in June 2004 by S. Farrell. It has since been updated by RFC 8996. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3767 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3766 Determining Strengths For Public Keys Used For Exchanging Symmetric Keys
- RFC 3768 Virtual Router Redundancy Protocol
- RFC 3765 NOPEER Community for Border Gateway Protocol Route Scope Control
- RFC 3769 Requirements for IPv6 Prefix Delegation
- RFC 3764 enumservice registration for Session Initiation Protocol Addresses-of-Record
- RFC 3770 Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol and Wireless Local Area Networks
- RFC 3763 One-way Active Measurement Protocol Requirements
- RFC 3771 The Lightweight Directory Access Protocol Intermediate Response Message