RFC 3218 on Preventing the Million Message Attack on CMS

RFC Editor <rfc-ed@ISI.EDU> Thu, 10 January 2002 19:19 UTC

Received: from above.proper.com (above.proper.com []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21922 for <smime-archive@odin.ietf.org>; Thu, 10 Jan 2002 14:19:35 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g0AIiAR28067 for ietf-smime-bks; Thu, 10 Jan 2002 10:44:10 -0800 (PST)
Received: from gamma.isi.edu (gamma.isi.edu []) by above.proper.com (8.11.6/8.11.3) with ESMTP id g0AIi8328063 for <ietf-smime@imc.org>; Thu, 10 Jan 2002 10:44:08 -0800 (PST)
Received: from ISI.EDU (jet.isi.edu []) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g0AIi2H12606; Thu, 10 Jan 2002 10:44:02 -0800 (PST)
Message-Id: <200201101844.g0AIi2H12606@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3218 on Preventing the Million Message Attack on CMS
Cc: rfc-ed@ISI.EDU, ietf-smime@imc.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 10 Jan 2002 10:44:02 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>

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

        RFC 3218

        Title:	    Preventing the Million Message Attack on 
                    Cryptographic Message Syntax
        Author(s):  E. Rescorla
        Status:     Informational
	Date:       January 2002
        Mailbox:    ekr@rtfm.com
        Pages:      7
        Characters: 16047
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-smime-pkcs1-01.txt

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

This memo describes a strategy for resisting the Million Message

This document is a 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

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.