Search for a command to run...
A principal objective of this document is to describe the underlying framework of middlebox communications (MIDCOM) to enable complex applications through the middleboxes, seamlessly using a trusted third party.This document and a companion document on MIDCOM requirements ([REQMTS]) have been created as a precursor to rechartering the MIDCOM working group.There are a variety of intermediate devices in the Internet today that require application intelligence for their operation.Datagrams pertaining to real-time streaming applications, such as SIP and H.323, and peer-to-peer applications, such as Napster and NetMeeting, cannot be identified by merely examining packet headers.Middleboxes implementing Firewall and Network Address Translator services typically embed application intelligence within the device for their operation.The document specifies an architecture and framework in which trusted third parties can be delegated to assist the middleboxes to perform their operation, without resorting to embedding application intelligence.Doing this will allow a middlebox to continue to provide the services, while keeping the middlebox application agnostic.
DOI: 10.17487/rfc3303