From midcom-bounces@ietf.org Tue Jan 08 17:49:32 2008 Return-path: Received: from [127.0.0.1] (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 [10.91.34.44] (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 [10.31.47.10]) 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 To: IETF-Announce Message-Id: Date: Tue, 08 Jan 2008 17:49:17 -0500 X-Spam-Score: -1.4 (-) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: midcom mailing list , midcom chair , Internet Architecture Board , RFC Editor 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: , List-Post: List-Help: List-Subscribe: , Errors-To: midcom-bounces@ietf.org The IESG has approved the following document: - 'Definitions of Managed Objects for Middlebox Communication ' as a Proposed Standard This document is the product of the Middlebox Communication Working Group. The IESG contact persons are Magnus Westerlund and Lars Eggert. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-midcom-mib-11.txt 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 midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom From midcom-bounces@ietf.org Tue Jan 08 17:50:36 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCNHH-0000t4-QE; Tue, 08 Jan 2008 17:50:35 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCNHE-0000sB-Uf; Tue, 08 Jan 2008 17:50:32 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCNHE-0000WY-Ks; Tue, 08 Jan 2008 17:50:32 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 6FBCA2AC5D; Tue, 8 Jan 2008 22:50:32 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JCNHE-0002I1-72; Tue, 08 Jan 2008 17:50:32 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Tue, 08 Jan 2008 17:50:32 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: midcom mailing list , midcom chair , Internet Architecture Board , RFC Editor Subject: [midcom] Protocol Action: 'Middlebox Communications (MIDCOM) Protocol Semantics' to Proposed Standard X-BeenThere: midcom@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: midcom.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: midcom-bounces@ietf.org The IESG has approved the following document: - 'Middlebox Communications (MIDCOM) Protocol Semantics ' as a Proposed Standard This document is the product of the Middlebox Communication Working Group. The IESG contact persons are Magnus Westerlund and Lars Eggert. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-midcom-rfc3989-bis-02.txt Technical Summary 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 the implementation of the sematics in draft-ietf-midcom-mib does require the sematics description as normative reference. Therefore the semantics declaration is reclassified from informational to proposed standard. Working Group Summary There is consensus in the WG to reclassify this document to proposed standard to provide the necessary normative language for draft-ietf-midcom-mib. Protocol Quality Magnus Westerlund reveiwed the document for IESG. The memo was published as RFC 3989 with informational status and has then been somewhat modified to make it more suitable as proposed standard. Note to RFC Editor OLD: Tom Taylor Nortel 1852 Lorraine Ave. Ottawa, Ontario Canada K1H 6Z8 Phone: +1 613 763 1496 EMail: taylor@nortel.com NEW: Tom Taylor Nortel 1852 Lorraine Ave. Ottawa, Ontario Canada K1H 6Z8 Phone: +1 613 763 1496 EMail: tom.taylor@rogers.com _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom From midcom-bounces@ietf.org Tue Jan 08 18:08:05 2008 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCNYA-0004AK-3F; Tue, 08 Jan 2008 18:08:02 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCNY9-0004AF-FU for midcom@ietf.org; Tue, 08 Jan 2008 18:08:01 -0500 Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JCNY9-0000zn-2g for midcom@ietf.org; Tue, 08 Jan 2008 18:08:01 -0500 Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 08 Jan 2008 18:08:01 -0500 Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m08N80FX020081 for ; Tue, 8 Jan 2008 18:08:00 -0500 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id m08N80Gu023480 for ; Tue, 8 Jan 2008 23:08:00 GMT Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 8 Jan 2008 18:08:00 -0500 Received: from 10.86.115.68 ([10.86.115.68]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) with Microsoft Exchange Server HTTP-DAV ; Tue, 8 Jan 2008 23:08:00 +0000 User-Agent: Microsoft-Entourage/11.3.3.061214 Date: Tue, 08 Jan 2008 18:08:09 -0500 From: Melinda Shore To: Message-ID: Thread-Topic: Protocol Action: 'Middlebox Communications (MIDCOM) Protocol Semantics' to Proposed Standard Thread-Index: AchSS1V3lE8RlL4+EdyySgAKleNSdA== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 08 Jan 2008 23:08:00.0905 (UTC) FILETIME=[50A49F90:01C8524B] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2333; t=1199833680; x=1200697680; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshore@cisco.com; z=From:=20Melinda=20Shore=20 |Subject:=20FW=3A=20Protocol=20Action=3A=20'Middlebox=20Com munications=20(MIDCOM)=20=20Protocol=0A=20Semantics'=20to=20 Proposed=20Standard=20 |Sender:=20 |To:=20; bh=KZCVyb+vmwA4Dr0XHqBevVEpbi9RoLKC92850hgXFns=; b=Kar5RgAAK8D8rvIU1o8QcBtIn52T1lm1jlqNUmLC4XM7N9o+/49saDE+DC ElLgoa2Pdo5elGTAmvMXuZZK0J8+dLXQjnRC6irs2C9jnQCtP/X2BPBdr+qy gysxLpIZK3; Authentication-Results: rtp-dkim-1; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Subject: [midcom] FW: Protocol Action: 'Middlebox Communications (MIDCOM) Protocol Semantics' to Proposed Standard X-BeenThere: midcom@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: midcom.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: midcom-bounces@ietf.org FYI. Many thanks to Martin, Juergen, and Tom for their work on this document. Melinda ------ Forwarded Message From: The IESG Date: Tue, 08 Jan 2008 17:50:32 -0500 To: IETF-Announce Cc: Internet Architecture Board , RFC Editor , midcom mailing list , midcom chair Subject: Protocol Action: 'Middlebox Communications (MIDCOM) Protocol Semantics' to Proposed Standard The IESG has approved the following document: - 'Middlebox Communications (MIDCOM) Protocol Semantics ' as a Proposed Standard This document is the product of the Middlebox Communication Working Group. The IESG contact persons are Magnus Westerlund and Lars Eggert. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-midcom-rfc3989-bis-02.txt Technical Summary 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 the implementation of the sematics in draft-ietf-midcom-mib does require the sematics description as normative reference. Therefore the semantics declaration is reclassified from informational to proposed standard. Working Group Summary There is consensus in the WG to reclassify this document to proposed standard to provide the necessary normative language for draft-ietf-midcom-mib. Protocol Quality Magnus Westerlund reveiwed the document for IESG. The memo was published as RFC 3989 with informational status and has then been somewhat modified to make it more suitable as proposed standard. Note to RFC Editor OLD: Tom Taylor Nortel 1852 Lorraine Ave. Ottawa, Ontario Canada K1H 6Z8 Phone: +1 613 763 1496 EMail: taylor@nortel.com NEW: Tom Taylor Nortel 1852 Lorraine Ave. Ottawa, Ontario Canada K1H 6Z8 Phone: +1 613 763 1496 EMail: tom.taylor@rogers.com ------ End of Forwarded Message _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom