[midcom] RFC 5189 on Middlebox Communication (MIDCOM) Protocol Semantics

rfc-editor@rfc-editor.org Tue, 25 March 2008 21:50 UTC

Return-Path: <midcom-bounces@ietf.org>
X-Original-To: ietfarch-midcom-archive@core3.amsl.com
Delivered-To: ietfarch-midcom-archive@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 72FA628C4FD; Tue, 25 Mar 2008 14:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.375
X-Spam-Status: No, score=-100.375 tagged_above=-999 required=5 tests=[AWL=-0.538, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id G5ui5-vBSPe9; Tue, 25 Mar 2008 14:50:40 -0700 (PDT)
Received: from core3.amsl.com (localhost []) by core3.amsl.com (Postfix) with ESMTP id 565EC3A6E9E; Tue, 25 Mar 2008 14:50:39 -0700 (PDT)
X-Original-To: midcom@core3.amsl.com
Delivered-To: midcom@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 305CF3A6DCA; Tue, 25 Mar 2008 14:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id wwdShS5eG57c; Tue, 25 Mar 2008 14:50:37 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 32B7A3A6B59; Tue, 25 Mar 2008 14:49:48 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 3D58C12105B; Tue, 25 Mar 2008 14:47:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20080325214729.3D58C12105B@bosco.isi.edu>
Date: Tue, 25 Mar 2008 14:47:29 -0700 (PDT)
Cc: midcom@ietf.org, rfc-editor@rfc-editor.org
Subject: [midcom] RFC 5189 on Middlebox Communication (MIDCOM) Protocol Semantics
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <midcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:midcom@ietf.org>
List-Help: <mailto:midcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: midcom-bounces@ietf.org
Errors-To: midcom-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        RFC 5189

        Title:      Middlebox Communication (MIDCOM) Protocol Semantics 
        Author:     M. Stiemerling, J. Quittek, T. Taylor
        Status:     Standards Track
        Date:       March 2008
        Mailbox:    stiemerling@nw.neclab.eu, 
        Pages:      70
        Characters: 161167
        Obsoletes:  RFC3989

        I-D Tag:    draft-ietf-midcom-rfc3989-bis-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5189.txt

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]

This document is a product of the Middlebox Communication Working Group 
of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


midcom mailing list