[midcom] Protocol Action: 'Definitions of Managed Objects for Middlebox Communication' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 08 January 2008 22:49 UTC

Return-path: <midcom-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCNG6-0000UT-Cp; Tue, 08 Jan 2008 17:49:22 -0500
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCNG3-0000R5-60; Tue, 08 Jan 2008 17:49:19 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCNG2-0001rh-Af; Tue, 08 Jan 2008 17:49:19 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com []) by ns1.neustar.com (Postfix) with ESMTP id DA55D26E78; Tue, 8 Jan 2008 22:49:17 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JCNG1-0002FO-NS; Tue, 08 Jan 2008 17:49:17 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1JCNG1-0002FO-NS@stiedprstage1.ietf.org>
Date: Tue, 08 Jan 2008 17:49:17 -0500
X-Spam-Score: -1.4 (-)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: midcom mailing list <midcom@ietf.org>, midcom chair <midcom-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [midcom] Protocol Action: 'Definitions of Managed Objects for Middlebox Communication' to Proposed Standard
X-BeenThere: midcom@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: midcom.ietf.org
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/midcom>, <mailto:midcom-request@ietf.org?subject=subscribe>
Errors-To: midcom-bounces@ietf.org

The IESG has approved the following document:

- 'Definitions of Managed Objects for Middlebox Communication '
   <draft-ietf-midcom-mib-11.txt> as a Proposed Standard

This document is the product of the Middlebox Communication Working 

The IESG contact persons are Magnus Westerlund and Lars Eggert.

A URL of this Internet-Draft is:

Technical summary:

The midcom working group was chartered to develop a protocol to
send requests from network endpoints/application participants to
network devices, initially focusing on firewalls and NATs.  The
charter required that the working group reuse an existing IETF
protocol if possible, and the working group followed an evaluation
process described in RFC 4097.  The protocol that best met
the evaluation criteria was SNMPv2.

The document being submitted for publication is the definition of
a MIB to be used to communicate pinhole requests to a firewall and
NAT table mapping requests to a NAT.

Working group summary:

There is working group consensus that this document is ready to
be published.

Protocol quality:

The protocol has received extensive review by applications experts
in the domain most likely to use a midcom protocol, by SNMP protocol
experts, and by middlebox experts.  We know of no existing
implementations, and it is not clear that it will be implemented given
the existence of competing protocols (for example, SIMCO).  This
protocol received particular attention in its early stages from
David Harrington, Wes Hardaker, and Mary Barnes, and recently from
its MIB Doctor, Juergen Shoenwaelder. 

The responsible AD was Magnus Westerlund and Melinda Shore the 
WG shepherd.

Note to RFC Editor
Section 13. Please move these 2 referneces to section 14. 

[RFC3303]   Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A. and A.
            Rayhan, "Middlebox communication architecture and
            framework", RFC 3303, August 2002.

[RFC3304]   Swale, R.P., Mart, P.A., Sijben, P., Brimm, S. and M. Shore,
            "Middlebox Communications (midcom) Protocol Requirements",
            RFC 3304, August 2002.

midcom mailing list