ObsoletedINFORMATIONALIETF stream

RFC 3989: Middlebox Communications (MIDCOM) Protocol Semantics

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5189.

Current version: RFC 5189Middlebox Communication (MIDCOM) Protocol Semantics

In plain English — editorial summary, not part of the RFC

This memo specifies semantics for a Middlebox Communication (MIDCOM) protocol to be used by MIDCOM agents for interacting with middleboxes such as firewalls and Network Address Translators (NATs). The semantics discussion does not include any specification of a concrete syntax or a transport protocol. However, a concrete protocol is expected to implement the specified semantics or, more likely, a superset of it. The MIDCOM protocol semantics is derived from the MIDCOM requirements, from the MIDCOM framework, and from working group decisions. This memo provides information for the Internet community.

Document record

Document ID
RFC3989
Published
February 2005
Authors
M. Stiemerling; J. Quittek; T. Taylor
Status
INFORMATIONAL
Stream
IETF
Area
tsv
Pages
70
Also known as
Obsoleted by:
RFC 5189

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3989-middlebox-communications-midcom-protocol-semantics