RFC 3767 on Securely Available Credentials Protocol
rfc-editor@rfc-editor.org Mon, 21 June 2004 21:08 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29733 for <ietf-announce-archive@ietf.org>; Mon, 21 Jun 2004 17:08:37 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcW1u-0004PN-Bg for ietf-announce-archive@ietf.org; Mon, 21 Jun 2004 17:08:38 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcW0c-0003zU-00 for ietf-announce-archive@ietf.org; Mon, 21 Jun 2004 17:07:19 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BcVzO-0003Ju-00; Mon, 21 Jun 2004 17:06:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcVey-0005HD-B8; Mon, 21 Jun 2004 16:44:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BcU1O-00053b-3v for ietf-announce@megatron.ietf.org; Mon, 21 Jun 2004 14:59:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17023 for <ietf-announce@ietf.org>; Mon, 21 Jun 2004 14:59:56 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BcU1N-0004Y2-0F for ietf-announce@ietf.org; Mon, 21 Jun 2004 14:59:57 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BcU0U-0004Hw-00 for ietf-announce@ietf.org; Mon, 21 Jun 2004 14:59:03 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BcTzi-0003n1-00 for ietf-announce@ietf.org; Mon, 21 Jun 2004 14:58:14 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i5LItaJ04775; Mon, 21 Jun 2004 11:55:36 -0700 (PDT)
Message-Id: <200406211855.i5LItaJ04775@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Mon, 21 Jun 2004 11:55:36 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Mon, 21 Jun 2004 16:44:48 -0400
Cc: ietf-sacred@imc.org, rfc-editor@rfc-editor.org
Subject: RFC 3767 on Securely Available Credentials Protocol
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
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@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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@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@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.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce