Middlebox communication architecture and framework
RFC 3303, “Middlebox communication architecture and framework”, is an Informational document published in August 2002 by P. Srisuresh, J. Kuthan, J. Rosenberg, A. Molitor, A. Rayhan. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3303 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3302 Tag Image File Format - image/tiff MIME Sub-type Registration
- RFC 3304 Middlebox Communications Protocol Requirements
- RFC 3301 Layer Two Tunnelling Protocol : ATM access network extensions
- RFC 3305 Report from the Joint W3C/IETF URI Planning Interest Group: Uniform Resource Identifiers , URLs, and Uniform Resource Names : Clarifications and Recommendations
- RFC 3300 Internet Official Protocol Standards
- RFC 3306 Unicast-Prefix-based IPv6 Multicast Addresses
- RFC 3307 Allocation Guidelines for IPv6 Multicast Addresses
- RFC 3298 Service in the Public Switched Telephone Network/Intelligent Network Requesting InTernet Service Protocol Requirements