RFC 2876 on KEA and SKIPJACK Algorithms in CMS

RFC Editor <rfc-ed@ISI.EDU> Thu, 13 July 2000 00:26 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18824; Wed, 12 Jul 2000 20:26:45 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA02557 for ietf-123-outbound.10@ietf.org; Wed, 12 Jul 2000 20:25:01 -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 UAA02525 for <all-ietf@loki.ietf.org>; Wed, 12 Jul 2000 20:15:09 -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 UAA18740 for <all-ietf@ietf.org>; Wed, 12 Jul 2000 20:15:08 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA13974; Wed, 12 Jul 2000 17:15:08 -0700 (PDT)
Message-Id: <200007130015.RAA13974@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2876 on KEA and SKIPJACK Algorithms in CMS
Cc: rfc-ed@ISI.EDU, ietf-smime@IMC.ORG
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 12 Jul 2000 17:15:08 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2876

        Title:	    Use of the KEA and SKIPJACK Algorithms in CMS 
        Author(s):  J. Pawling
        Status:     Informational
	Date:       July 2000
        Mailbox:    john.pawling@wang.com
        Pages:      13
        Characters: 29265
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-smime-cmskea-05.txt

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


This document describes the conventions for using the Key Exchange
Algorithm (KEA) and SKIPJACK encryption algorithm in conjunction with
the Cryptographic Message Syntax [CMS] enveloped-data and
encrypted-data content types.

This document is the product of the S/MIME Mail Security 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 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/rfc2876.txt"><ftp://ftp.isi.edu/in-notes/rfc2876.txt>