RFC 3183 on Domain Security Services using S/MIME

RFC Editor <rfc-ed@ISI.EDU> Wed, 17 October 2001 19:14 UTC

Message-Id: <200110171848.OAA03577@ietf.org>
To: IETF-Announce:;
Subject: RFC 3183 on Domain Security Services using S/MIME
Cc: rfc-ed@ISI.EDU, ietf-smime@imc.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: RFC Editor <rfc-ed@ISI.EDU>
Date: Wed, 17 Oct 2001 14:48:21 -0400
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk


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


        RFC 3183

        Title:	    Domain Security Services using S/MIME
        Author(s):  T. Dean, W. Ottaway
        Status:     Experimental
	Date:       October 2001
        Mailbox:    tbdean@QinetiQ.com,
                    wjottaway@QinetiQ.com 
        Pages:      24
        Characters: 57129
        SeeAlso/Updates/Obsoletes:    None

        I-D Tag:    draft-ietf-smime-domsec-09.txt

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


This document describes how the S/MIME (Secure/Multipurpose Internet
Mail Extensions) protocol can be processed and generated by a number
of components of a communication system, such as message transfer
agents, guards and gateways to deliver security services.  These
services are collectively referred to as 'Domain Security Services'.

This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and
suggestions for improvement are requested.  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.

----- End Included Message -----

----------
X-Sun-Data-Type: Multipart
X-Sun-Content-Length: 490
X-Sun-Charset: us-ascii
X-Sun-Content-Lines: 22

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO@RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <011012162515.RFC@RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc3183

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc3183.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <011012162515.RFC@RFC-EDITOR.ORG>

--OtherAccess--

RFC 3183 on Domain Security Services using S/MIME RFC Editor
RFC 3183 on Domain Security Services using S/MIME RFC Editor
RFC 3183 on Domain Security Services using S/MIME RFC Editor