RFC 2628 on Crypto API

RFC Editor <rfc-ed@ISI.EDU> Fri, 02 July 1999 22:21 UTC

Message-Id: <199907022202.PAA12946@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2628 on Crypto API
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 02 Jul 1999 15:02:33 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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

        RFC 2628

        Title:	    Simple Cryptographic Program Interface (Crypto API)
        Author(s):  V. Smyslov
        Status:     Informational		
	Date:       June 1999
        Mailbox:    svan@trustworks.com
        Pages:      30
        Characters: 60070
	Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-smyslov-crypto-api-00.txt


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

This document describes a simple Application Program Interface to
cryptographic functions. The main purpose of such an interface is to
separate cryptographic libraries from internet applications, thus
allowing an independent development of both. It can be used in various
internet applications such as [IPsec], [ISAKMP], [IKE], [TLS].

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

RFC 2628 on Crypto API RFC Editor