RFC 3304: Middlebox Communications (midcom) Protocol Requirements
In plain English — editorial summary, not part of the RFC
This document specifies the requirements that the Middlebox Commu- nication (midcom) protocol must satisfy in order to meet the needs of applications wishing to influence middlebox function. These requirements were developed with a specific focus on network address translation and firewall middleboxes.
Document record
- Document ID
- RFC3304
- Published
- August 2002
- Authors
- R. P. Swale; P. A. Mart; P. Sijben; S. Brim; M. Shore
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 3104RSIP Support for End-to-end IPsecCurrent
October 2001
- RFC 3103Realm Specific IP: Protocol SpecificationCurrent
October 2001
- RFC 3102Realm Specific IP: FrameworkCurrent
October 2001
- RFC 3989Middlebox Communications (MIDCOM) Protocol SemanticsObsoleted
February 2005
- RFC 4787Network Address Translation (NAT) Behavioral Requirements for Unicast UDPUpdated
January 2007
- RFC 5189Middlebox Communication (MIDCOM) Protocol SemanticsCurrent
March 2008
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?