[rfc-dist] RFC 3304 on Middlebox Communications (midcom) Protocol Requirements

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Mon, 19 Aug 2002 16:51:12 -0700


--NextPart


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


        RFC 3304

        Title:	    Middlebox Communications (midcom) Protocol
                    Requirements 
        Author(s):  R. P. Swale, P. A. Mart, P. Sijben, S. Brim,
                    M. Shore 
        Status:	    Informational
	Date:       August 2002
        Mailbox:    richard.swale@bt.com, paul.sijben@picopoint.com,
                    philip.mart@marconi.com, sbrim@cisco.com,
                    mshore@cisco.com 
        Pages:      9
        Characters: 16187
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-midcom-requirements-05.txt

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


This document specifies the requirements that the Middlebox
Communication (midcom) protocol must satisfy in order to meet the
needs of applications wishing to influence the middlebox function.
These requirements were developed with a specific focus on network
address translation and firewall middleboxes. 

This document is a product of the Middlebox Communication 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.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

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

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

RETRIEVE: rfc
DOC-ID: rfc3304

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

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

--OtherAccess--
--NextPart--