RFC 3157 on SACRED - Requirements

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


        RFC 3157

        Title:	    Securely Available Credentials - Requirements 
        Author(s):  A. Arsenault, S. Farrell
        Status:     Informational
	Date:       August 2001
        Mailbox:    [email protected], [email protected]
        Pages:      20
        Characters: 45962
        Obsoletes/Updates/SeeAlso:    None

        I-D Tag:    draft-ietf-sacred-reqs-03.txt

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


This document describes requirements to be placed on Securely
Available Credentials (SACRED) protocols.

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 
help: ways_to_get_rfcs.  For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
[email protected].  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.