draft-freed-gatesec

Last Version:	draft-freed-gatesec-03.txt		Tracker Entry
Date:	19-Jul-2000
Disposition:	RFC2480 (diff)
Previous Versions:	draft-freed-gatesec-03.txt (diff)    - 29-Jan-1999
	draft-freed-gatesec-02.txt (diff)    - 09-Apr-2002
	draft-freed-gatesec-01.txt (diff)    - 09-Apr-2002
	draft-freed-gatesec-00.txt (diff)    - 09-Apr-2002

--NextPart


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


        RFC 2480:

        Title:	    Gateways and MIME Security Multiparts
	Author(s):  N. Freed
	Status:     Proposed Standard
	Date:       January 1999
        Mailbox:    ned.freed@innosoft.com
	Pages:      6
        Characters: 11751
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-freed-gatesec-03.txt


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


This document examines the problems associated with use of
MIME security multiparts and gateways to non-MIME
environments. A set of requirements for gateway behavior are
defined which provide facilities necessary to properly
accomodate the transfer of security multiparts through
gateways.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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