RFC 5189: Middlebox Communication (MIDCOM) Protocol Semantics
In plain English — editorial summary, not part of the RFC
This document 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 document obsoletes RFC 3989. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5189
- Published
- March 2008
- Authors
- M. Stiemerling; J. Quittek; T. Taylor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- tsv
- Pages
- 70
- Also known as
- —
- Obsoletes:
- RFC 3989
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5389Session Traversal Utilities for NAT (STUN)Obsoleted
October 2008
- RFC 6887Port Control Protocol (PCP)Updated
April 2013
- RFC 7383Internet Key Exchange Protocol Version 2 (IKEv2) Message FragmentationCurrent
November 2014
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 4787Network Address Translation (NAT) Behavioral Requirements for Unicast UDPUpdated
January 2007
- RFC 5766Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)Obsoleted
April 2010
- RFC 5928Traversal Using Relays around NAT (TURN) Resolution MechanismUpdated
August 2010
- RFC 6052IPv6 Addressing of IPv4/IPv6 TranslatorsCurrent
October 2010
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?