From midcom-bounces@ietf.org Mon Dec 04 10:15:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrFXc-0007Fu-W0; Mon, 04 Dec 2006 10:15:36 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrFXZ-0007FF-NB; Mon, 04 Dec 2006 10:15:33 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrFXZ-0002T0-Fz; Mon, 04 Dec 2006 10:15:33 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 406FA26E18; Mon, 4 Dec 2006 15:15:33 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GrFXZ-0002jl-57; Mon, 04 Dec 2006 10:15:33 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 04 Dec 2006 10:15:33 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Cc: midcom@ietf.org Subject: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) X-BeenThere: midcom@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: midcom.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: midcom-bounces@ietf.org The IESG has received a request from the midcom WG to consider the following document: - 'MIDCOM Protocol Semantics ' RFC 3989 as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-12-21. The file can be obtained via http://www.ietf.org/rfc/rfc3989.txt Please note that this document contains 4 normative references: [MDC-FRM] Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A., and A. Rayhan, "Middlebox communication architecture and framework", RFC 3303, August 2002. [MDC-REQ] Swale, R., Mart, P., Sijben, P., Brim, S., and M. Shore, "Middlebox Communications (midcom) Protocol Requirements", RFC 3304, August 2002. [NAT-TERM] Srisuresh, P. and M. Holdrege, "IP Network Address Translator (NAT) Terminology and Considerations", RFC 2663, August 1999. [NAT-TRAD] Srisuresh, P. and K. Egevang, "Traditional IP Network Address Translator (Traditional NAT)", RFC 3022, January 2001. These 4 references to informational documents are not what would be normally considered normative references in a standards track documents. This is a result of the propsed reclassification from informational to proposed standard. Therefore this last call explicitly identifies these as downrefs. This downref last call according to RFC 3967 shall not be considred a precedence for using the above reference in the future as normative references without an last call. _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom From midcom-bounces@ietf.org Thu Dec 14 14:11:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Guvys-0002sx-O0; Thu, 14 Dec 2006 14:10:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Guvyr-0002sn-9F for midcom@ietf.org; Thu, 14 Dec 2006 14:10:57 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Guvyo-0005zD-TQ for midcom@ietf.org; Thu, 14 Dec 2006 14:10:57 -0500 Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-5.cisco.com with ESMTP; 14 Dec 2006 11:10:54 -0800 Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-6.cisco.com (8.12.11/8.12.11) with ESMTP id kBEJAsce017379 for ; Thu, 14 Dec 2006 11:10:54 -0800 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id kBEJAl6h014275 for ; Thu, 14 Dec 2006 11:10:54 -0800 (PST) Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Dec 2006 14:10:51 -0500 Received: from 10.86.115.66 ([10.86.115.66]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([64.102.31.21]) with Microsoft Exchange Server HTTP-DAV ; Thu, 14 Dec 2006 19:10:51 +0000 User-Agent: Microsoft-Entourage/11.2.3.060209 Date: Thu, 14 Dec 2006 14:10:52 -0500 Subject: Reminder: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) From: Melinda Shore To: Message-ID: Thread-Topic: Reminder: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) Thread-Index: Accfs5Jz0MMi5YumEduo6gAKleNSdA== In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 14 Dec 2006 19:10:51.0329 (UTC) FILETIME=[920D2310:01C71FB3] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2327; t=1166123454; x=1166987454; c=relaxed/simple; s=sjdkim6002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshore@cisco.com; z=From:=20Melinda=20Shore=20 |Subject:=20Reminder=3A=20[midcom]=20Last=20Call=3A=20'MIDCOM=20Protocol= 20Semantics'=20to=0A=20Proposed=20Standard=20(rfc3989)=20 |Sender:=20; bh=StffGyGFS2gHLJ1HwyCmTWgQMlvo7FB+xjHAbRwoG7k=; b=aa07AbVFPJLZWviFb4U7+AD2wAoC8A5ExD8Fx15c/MDJ4zVCQ41NCZDublkgKCMt8lbZbv1e ItIKWg4NlTvxbfHYxpCfYsNzwTlkmjINHuGirqFlKAh5cZqjuvMO3PG5; Authentication-Results: sj-dkim-6; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/sjdkim6002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 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 This is a reminder that the midcom mib is in IETF last call and that comments should be sent to the IESG by next Thursday (21 December). Thanks, Melinda ------ Forwarded Message From: The IESG Reply-To: Date: Mon, 04 Dec 2006 10:15:33 -0500 To: IETF-Announce Cc: Subject: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) The IESG has received a request from the midcom WG to consider the following document: - 'MIDCOM Protocol Semantics ' RFC 3989 as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-12-21. The file can be obtained via http://www.ietf.org/rfc/rfc3989.txt Please note that this document contains 4 normative references: [MDC-FRM] Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A., and A. Rayhan, "Middlebox communication architecture and framework", RFC 3303, August 2002. [MDC-REQ] Swale, R., Mart, P., Sijben, P., Brim, S., and M. Shore, "Middlebox Communications (midcom) Protocol Requirements", RFC 3304, August 2002. [NAT-TERM] Srisuresh, P. and M. Holdrege, "IP Network Address Translator (NAT) Terminology and Considerations", RFC 2663, August 1999. [NAT-TRAD] Srisuresh, P. and K. Egevang, "Traditional IP Network Address Translator (Traditional NAT)", RFC 3022, January 2001. These 4 references to informational documents are not what would be normally considered normative references in a standards track documents. This is a result of the propsed reclassification from informational to proposed standard. Therefore this last call explicitly identifies these as downrefs. This downref last call according to RFC 3967 shall not be considred a precedence for using the above reference in the future as normative references without an last call. _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom ------ End of Forwarded Message _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom From midcom-bounces@ietf.org Mon Dec 18 10:08:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwK5n-0006TX-7b; Mon, 18 Dec 2006 10:07:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwK5l-0006Rg-QX for midcom@ietf.org; Mon, 18 Dec 2006 10:07:49 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwK5k-0004z0-E8 for midcom@ietf.org; Mon, 18 Dec 2006 10:07:49 -0500 Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-4.cisco.com with ESMTP; 18 Dec 2006 07:07:48 -0800 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id kBIF7ldJ030266 for ; Mon, 18 Dec 2006 07:07:47 -0800 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id kBIF7jAC018104 for ; Mon, 18 Dec 2006 07:07:47 -0800 (PST) Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 18 Dec 2006 10:07:27 -0500 Received: from 10.86.115.66 ([10.86.115.66]) by xmb-rtp-205.amer.cisco.com ([64.102.31.59]) via Exchange Front-End Server email.cisco.com ([64.102.31.21]) with Microsoft Exchange Server HTTP-DAV ; Mon, 18 Dec 2006 15:07:27 +0000 User-Agent: Microsoft-Entourage/11.2.3.060209 Date: Mon, 18 Dec 2006 10:07:32 -0500 Subject: FW: Reminder: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) From: Melinda Shore To: Message-ID: Thread-Topic: Reminder: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) Thread-Index: Accfs5Jz0MMi5YumEduo6gAKleNSdADAqtj2 In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-OriginalArrivalTime: 18 Dec 2006 15:07:27.0439 (UTC) FILETIME=[3B1B5DF0:01C722B6] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2814; t=1166454467; x=1167318467; c=relaxed/simple; s=sjdkim5002; 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=20Reminder=3A=20[midcom]=20Last=20Call=3A=20'MIDCOM=20P rotocol=20Semantics'=20to=0A=20Proposed=20Standard=20(rfc3989)=20 |Sender:=20; bh=YrevIsBG5Md9cwMfSUaXXwb+MKqVz4lJJHorTGIwZF0=; b=i7BPYF8SS83OU29ZTxkIDP1CsKs7rl7/MMMER3jzBu+iSVcbwc+FX1vedA25QRkVp+J7HWAh TXRtXa4ML2GAkk7R00jgDNTXDwmTHEmgID+y8wp0vle7F1Kd4lj28ylR; Authentication-Results: sj-dkim-5; header.From=mshore@cisco.com; dkim=pass ( sig from cisco.com/sjdkim5002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 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 This was a brain poot on my part. It's actually the semantics document in IETF last call. Thanks, Melinda ------ Forwarded Message From: Melinda Shore Date: Thu, 14 Dec 2006 14:10:52 -0500 To: Conversation: Reminder: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) Subject: Reminder: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) This is a reminder that the midcom mib is in IETF last call and that comments should be sent to the IESG by next Thursday (21 December). Thanks, Melinda ------ Forwarded Message From: The IESG Reply-To: Date: Mon, 04 Dec 2006 10:15:33 -0500 To: IETF-Announce Cc: Subject: [midcom] Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) The IESG has received a request from the midcom WG to consider the following document: - 'MIDCOM Protocol Semantics ' RFC 3989 as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-12-21. The file can be obtained via http://www.ietf.org/rfc/rfc3989.txt Please note that this document contains 4 normative references: [MDC-FRM] Srisuresh, P., Kuthan, J., Rosenberg, J., Molitor, A., and A. Rayhan, "Middlebox communication architecture and framework", RFC 3303, August 2002. [MDC-REQ] Swale, R., Mart, P., Sijben, P., Brim, S., and M. Shore, "Middlebox Communications (midcom) Protocol Requirements", RFC 3304, August 2002. [NAT-TERM] Srisuresh, P. and M. Holdrege, "IP Network Address Translator (NAT) Terminology and Considerations", RFC 2663, August 1999. [NAT-TRAD] Srisuresh, P. and K. Egevang, "Traditional IP Network Address Translator (Traditional NAT)", RFC 3022, January 2001. These 4 references to informational documents are not what would be normally considered normative references in a standards track documents. This is a result of the propsed reclassification from informational to proposed standard. Therefore this last call explicitly identifies these as downrefs. This downref last call according to RFC 3967 shall not be considred a precedence for using the above reference in the future as normative references without an last call. _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom ------ End of Forwarded Message ------ End of Forwarded Message _______________________________________________ midcom mailing list midcom@ietf.org https://www1.ietf.org/mailman/listinfo/midcom