RFC1824 on TESS

"Joyce K. Reynolds" <jkrey@isi.edu> Fri, 11 August 1995 17:11 UTC

Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa15025; 11 Aug 95 13:11 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa13602; 11 Aug 95 13:11 EDT
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14968; 11 Aug 95 13:10 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14809; 11 Aug 95 13:05 EDT
Received: from zephyr.isi.edu by CNRI.Reston.VA.US id aa13414; 11 Aug 95 13:05 EDT
Received: from akamai.isi.edu by zephyr.isi.edu (5.65c/5.61+local-17) id <AA08317>; Fri, 11 Aug 1995 10:06:49 -0700
Message-Id: <199508111706.AA08317@zephyr.isi.edu>
To: IETF-Announce:;
Subject: RFC1824 on TESS
Cc: jkrey@isi.edu
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 11 Aug 1995 10:08:44 -0700
Sender: ietf-announce-request@IETF.CNRI.Reston.VA.US
From: "Joyce K. Reynolds" <jkrey@isi.edu>

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


        RFC 1824:

        Title:      The Exponential Security System TESS:
                    An Identity-Based Cryptographic Protocol
                    for Authenticated Key-Exchange
                    (E.I.S.S.-Report 1995/4)
        Author:     H. Danisch
        Date:       August 1995
        Mailbox:    danisch@ira.uka.de
        Pages:      21
        Characters: 42,540
        Updates/Obsoletes:  none

        URL:        ftp://ds.internic.net/rfc/rfc1824.txt


This informational RFC describes the basic mechanisms and functions of
an identity based system for the secure authenticated exchange of
cryptographic keys, the generation of signatures, and the authentic
distribution of public keys.

This memo provides information for the Internet community.  This memo
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@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

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

        To: rfc-info@ISI.EDU
        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 admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds
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://ds.internic.net/rfc/rfc1824.txt"><ftp://ds.internic.net/rfc/rfc1824.txt>