idnits 2.17.1 draft-ietf-midcom-framework-07.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 3303 5 Title: Middlebox communication architecture and framework 6 Author(s): P. Srisuresh, J. Kuthan, J. Rosenberg, A. Molitor, 7 A. Rayhan 8 Status: Informational 9 Date: August 2002 10 Mailbox: srisuresh@yahoo.com, kuthan@fokus.fhg.de, 11 jdrosen@dynamicsoft.com, amolitor@visi.com, 12 rayhan@ee.ryerson.ca 13 Pages: 34 14 Characters: 91209 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-midcom-framework-07.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3303.txt 21 A principal objective of this document is to describe the underlying 22 framework of middlebox communications (MIDCOM) to enable complex 23 applications through the middleboxes, seamlessly using a trusted 24 third party. This document and a companion document on MIDCOM 25 requirements ([REQMTS]) have been created as a precursor to 26 rechartering the MIDCOM working group. 28 There are a variety of intermediate devices in the Internet today 29 that require application intelligence for their 30 operation. Datagrams pertaining to real-time streaming applications, 31 such as SIP and H.323, and peer-to-peer applications, such as Napster 32 and NetMeeting, cannot be identified by merely examining packet 33 headers. Middleboxes implementing Firewall and Network Address 34 Translator services typically embed application intelligence 35 within the device for their operation. The document specifies an 36 architecture and framework in which trusted third parties can 37 be delegated to assist the middleboxes to perform their operation, 38 without resorting to embedding application intelligence. Doing 39 this will allow a middlebox to continue to provide the services, 40 while keeping the middlebox application agnostic. 42 This document is a product of the Middlebox Communication Working 43 Group of the IETF. 45 This memo provides information for the Internet community. It does 46 not specify an Internet standard of any kind. Distribution of this 47 memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.