[rfc-dist] RFC 3767 on Securely Available Credentials Protocol

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Mon Jun 21 11:55:37 PDT 2004

A new Request for Comments is now available in online RFC libraries.

        RFC 3767

        Title:      Securely Available Credentials Protocol
        Author(s):  S. Farrell, Ed.
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    stephen.farrell at cs.tcd.ie
        Pages:      25
        Characters: 49552
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sacred-protocol-bss-09.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3767.txt

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). 

This document is a product of the Securely Available Credentials
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at RFC-EDITOR.ORG
        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 RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list