idnits 2.17.1 draft-ietf-midcom-requirements-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3304 5 Title: Middlebox Communications (midcom) Protocol 6 Requirements 7 Author(s): R. P. Swale, P. A. Mart, P. Sijben, S. Brim, 8 M. Shore 9 Status: Informational 10 Date: August 2002 11 Mailbox: richard.swale@bt.com, paul.sijben@picopoint.com, 12 philip.mart@marconi.com, sbrim@cisco.com, 13 mshore@cisco.com 14 Pages: 9 15 Characters: 16187 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-midcom-requirements-05.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3304.txt 22 This document specifies the requirements that the Middlebox 23 Communication (midcom) protocol must satisfy in order to meet the 24 needs of applications wishing to influence the middlebox function. 25 These requirements were developed with a specific focus on network 26 address translation and firewall middleboxes. 28 This document is a product of the Middlebox Communication Working 29 Group of the IETF. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.