RFC 2704 on The KeyNote Trust-Management System

RFC Editor <rfc-ed@ISI.EDU> Thu, 30 September 1999 23:05 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22352; Thu, 30 Sep 1999 19:05:26 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA24603 for ietf-123-outbound.10@ietf.org; Thu, 30 Sep 1999 18:45:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA24466 for <all-ietf@loki.ietf.org>; Thu, 30 Sep 1999 18:26:14 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20988 for <all-ietf@ietf.org>; Thu, 30 Sep 1999 18:26:13 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA25538; Thu, 30 Sep 1999 15:26:13 -0700 (PDT)
Message-Id: <199909302226.PAA25538@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2704 on The KeyNote Trust-Management System
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 30 Sep 1999 15:26:13 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2704:

        Title:	    The KeyNote Trust-Management System Version 2
        Author(s):  M. Blaze, J. Feigenbaum, J. Ioannidis,
                    A. Keromytis
        Status:     Informational
	Date:       September 1999
        Mailbox:    mab@research.att.com, jf@research.att.com,
                    ji@research.att.com, angelos@dsl.cis.upenn.edu
        Pages:      37
        Characters: 79998
	Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-blaze-ietf-trustmgt-keynote-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2704.txt


This memo describes version 2 of the KeyNote trust-management system.
It specifies the syntax and semantics of KeyNote `assertions',
describes `action attribute' processing, and outlines the application
architecture into which a KeyNote implementation can be fit.  The
KeyNote architecture and language are useful as building blocks for
the trust management aspects of a variety of Internet protocols and
services.

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 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.
ftp://ftp.isi.edu/in-notes/rfc2704.txt"><ftp://ftp.isi.edu/in-notes/rfc2704.txt>