From ietf-announce-bounces@ietf.org Mon Dec 04 10:30:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrFXb-0007Fb-QJ; Mon, 04 Dec 2006 10:15:35 -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: Last Call: 'MIDCOM Protocol Semantics' to Proposed Standard (rfc3989) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-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. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 04 15:52:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKZe-0006b6-CL; Mon, 04 Dec 2006 15:38:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKZc-0006Zm-9Z for ietf-announce@ietf.org; Mon, 04 Dec 2006 15:38:00 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrKZK-0001Rh-Kn for ietf-announce@ietf.org; Mon, 04 Dec 2006 15:37:42 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 963D032897; Mon, 4 Dec 2006 20:37:42 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GrKZK-0006oI-GD; Mon, 04 Dec 2006 15:37:42 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 04 Dec 2006 15:37:42 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: ietf-pkix@imc.org Subject: Last Call: 'Internet X.509 Public Key Infrastructure Subject Alternative Name for expression of service name' to Proposed Standard (draft-ietf-pkix-srvsan) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Public-Key Infrastructure (X.509) WG to consider the following document: - 'Internet X.509 Public Key Infrastructure Subject Alternative Name for expression of service name ' 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-18. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-pkix-srvsan-03.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 04 19:06:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrNdd-0007x4-4e; Mon, 04 Dec 2006 18:54:21 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrNdb-0007wg-Ah; Mon, 04 Dec 2006 18:54:19 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GrNdZ-0005ax-1m; Mon, 04 Dec 2006 18:54:19 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns4.neustar.com (Postfix) with ESMTP id F0D012AC6B; Mon, 4 Dec 2006 23:53:46 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GrNd4-00067O-OQ; Mon, 04 Dec 2006 18:53:46 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list From: Leslie Daigle Message-Id: Date: Mon, 04 Dec 2006 18:53:46 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: iab@ietf.org Subject: Second call for nominations: IAOC position selected by the IAB X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iab@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IAB is making a call for nominations for the IETF Administrative Oversight Committee (IAOC), as described in BCP 101 (RFC 4071) and BCP 113 (RFC 4333). The IESG and the IAB each select one person for a two-year IAOC term in alternate years. This year, the IAB will select one person for a term ending in spring 2009. The incumbent is Lucy Lynch, who was selected by the IAB for an initial two year term expiring in spring 2007. Candidates for these IAOC positions should have knowledge of the IETF, knowledge of contracts and financial procedures, and familiarity with the administrative support needs of the IAB, the IESG, and the IETF standards process. The candidates are also expected to be able to understand the respective roles and responsibilities of the IETF and ISOC in this activity, and be able to articulate these roles within the IETF community. The candidates will also be expected to exercise all the duties of an IAOC member, including being prepared to undertake any associated responsibilities. These include, but are not limited to, the setting of administrative support policies, oversight of the administrative operations of the IETF, and representing the interests of the IETF to the IAOC. The candidates must be able to undertake full participation in all Committee meetings and Committee activities. The IAB-selected member of the IAOC does not directly represent the IAB. The IAB and IESG selected members are accountable directly to the IETF community. Candidates do not need to be current members of the IAB or IESG, and in fact we prefer nominations and volunteers from the rest of the community. If you are interested in one of these positions, or know of someone who may be a good fit for this position, please send the name and email address to Phil Roberts, Executive Director of the IAB at . The IAB will respond with a questionnaire, asking for the candidates' qualifications and willingness to serve. The names of all people who declare themselves willing to serve will be made public on the ietf-announce@ietf.org list after the end of the solicitation period (December 22). The IAB expects to make a decision on or before January 29 (prior to the expected date at which the Nomcom will select its IAOC nominee). Leslie Daigle, for the IAB. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 04 19:19:02 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO1U-0004Gu-9N; Mon, 04 Dec 2006 19:19:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO1S-0004Gj-Uf for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:18:58 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrO1R-0007fb-Nj for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:18:58 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id AC4F332899; Tue, 5 Dec 2006 00:18:57 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GrO1R-0005hK-JO; Mon, 04 Dec 2006 19:18:57 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 04 Dec 2006 19:18:57 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: Internet Architecture Board , hubmib chair , RFC Editor Subject: Protocol Action: 'Managed Objects of Ethernet Passive Optical Networks (EPON)' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Managed Objects of Ethernet Passive Optical Networks (EPON) ' as a Proposed Standard This document is the product of the Ethernet Interfaces and Hub MIB Working Group. The IESG contact persons are Dan Romascanu and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-epon-mib-06.txt Technical Summary This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing interfaces that conform to the Ethernet Passive Optical Networks (EPON) standard as defined in the IEEE Std 802.3ah-2004, which are extended capabilities to the Ethernet like interfaces. Working Group Summary The working Group has consensus to publish this document as a Proposed Standard RFC. Protocol Quality The document has been reviewed by various WG members (and chairs) of the HUBMIB WG. IEEE802.3ah did various reviews and comments throughout the development of this document. MIB Doctor review was done by David Perkins. IETF Last Call also resulted in some comments. All review comments have been addressed. We are not aware of any current implementations. Bert Wijnen (WG chair of hubmib) is the PROTO SHEPHERD. Dan Romascanu is the Responsible Area Director. Note to RFC Editor 1. Page 99, pls move reference [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. from the informative to the normative section. 2. Replace all citations/references to rfc3636 and with the new rfc3636bis-to-be (which has been approved by IESG already, and which obsoletes RFC3636). _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 04 19:22:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO4p-00086y-6d; Mon, 04 Dec 2006 19:22:27 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO4m-00085v-A4 for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:22:24 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GrO4g-00007j-RE for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:22:24 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id C56BC32899; Tue, 5 Dec 2006 00:22:18 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GrO4g-0004T1-Me; Mon, 04 Dec 2006 19:22:18 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 04 Dec 2006 19:22:18 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: Internet Architecture Board , netlmm chair , RFC Editor Subject: Document Action: 'Problem Statement for Network-based Localized Mobility Management' to Informational RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Problem Statement for Network-based Localized Mobility Management ' as an Informational RFC This document is the product of the Network-based Localized Mobility Management Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-netlmm-nohost-ps-05.txt Technical Summary This is a problem statement relating to the area of the NETLMM WG, discussing the need for network-based local mobility management as well as some problems in existing solutions. Working Group Summary There has been substantial discussion and comments with regards to this document in the WG. The issues raised have been resolved as desired by the group, and there's consensus behind the end result. Note that concerns were raised earlier on the netlmm/int-area/ietf mailing lists about the validity of the problems that the group is attempting to solve, though not specifically of this document. However, these concerns were raised by only one individual and did not get agreement from the WG members or others. Protocol Quality Jari Arkko has reviewed this document for the IESG. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 04 19:22:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO3Z-0006e8-5a; Mon, 04 Dec 2006 19:21:09 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO3X-0006aL-5d for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:21:07 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GrO3W-0000Qy-Tp for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:21:07 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id D5F972AC34; Tue, 5 Dec 2006 00:20:36 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GrO32-0008KV-KQ; Mon, 04 Dec 2006 19:20:36 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 04 Dec 2006 19:20:36 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: nemo chair , Internet Architecture Board , RFC Editor Subject: Document Action: 'Network Mobility Support Terminology' to Informational RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Network Mobility Support Terminology ' as an Informational RFC This document is the product of the Network Mobility Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-nemo-terminology-06.txt Technical Summary This document defines a terminology for discussing network mobility (NEMO) issues and solution requirements. Working Group Summary There has been significant review and discussion of this document, and the consensus of the working group is solidly behind the document. Protocol Quality RFC 3963, NEMO Basic Support protocol employs these terms in its specification. There are multiple implementations of the protocol. This document has been reviewed by Jari Arkko for the IESG. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 04 19:24:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO75-0002H4-OM; Mon, 04 Dec 2006 19:24:47 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrO73-0002Gk-Tn for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:24:45 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GrO73-0000jx-Ld for ietf-announce@ietf.org; Mon, 04 Dec 2006 19:24:45 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 9725E2AC45; Tue, 5 Dec 2006 00:24:15 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GrO6Z-0004VM-CQ; Mon, 04 Dec 2006 19:24:15 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 04 Dec 2006 19:24:15 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: Internet Architecture Board , netlmm chair , RFC Editor Subject: Document Action: 'Goals for Network-based Localized Mobility Management (NETLMM)' to Informational RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Goals for Network-based Localized Mobility Management (NETLMM) ' as an Informational RFC This document is the product of the Network-based Localized Mobility Management Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-netlmm-nohost-req-05.txt Technical Summary This document discusses goals and requirements for network-based localized mobility management protocol. Working Group Summary There has been a lot of comments during the WG processing of the document. Three solicited reviews from Gabriel Montenegro, Vidya Naryanan, and Pete McCann. It is believed that the comments have been resolved to everyone's satisfaction. In addition, a call was made in the MIP6 and MIPSHOP WGs to verify that the gap analysis for existing solutions is correct. Protocol Quality Jari Arkko has reviewed this specification for the IESG. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Tue Dec 05 14:47:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrfyW-0000J0-8u; Tue, 05 Dec 2006 14:29:08 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GrfyU-0000It-Dd; Tue, 05 Dec 2006 14:29:06 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GrfyT-0004cv-6I; Tue, 05 Dec 2006 14:29:06 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id E27ED175BC; Tue, 5 Dec 2006 19:28:34 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Grfxy-0005QS-Gz; Tue, 05 Dec 2006 14:28:34 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: IETF Secretariat Message-Id: Date: Tue, 05 Dec 2006 14:28:34 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Subject: IETF IPv6 Site Maintenance X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf-secretariat-reply@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org On December 7, 2006 at around 8:00pm EST, the IETF Web site in the IPv6 network will encounter a brief downtime due to maintenance of the IPv6 firewall. NeuStar Secretariat Services will replace a piece of hardware to fix voltage fluctuations. The work will be completed in about an hour. Thank you. NeuStar Secretariat Services _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 07 09:56:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsKRj-00064z-Dx; Thu, 07 Dec 2006 09:41:59 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsKRh-00060G-9q; Thu, 07 Dec 2006 09:41:57 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GsKRg-0001wo-1e; Thu, 07 Dec 2006 09:41:57 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 0141E2AC5E; Thu, 7 Dec 2006 14:41:26 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GsKRB-0001fU-Og; Thu, 07 Dec 2006 09:41:25 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 07 Dec 2006 09:41:25 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: rohc@ietf.org Subject: Last Call: 'Implementer's Guide for SigComp' to Proposed Standard (draft-ietf-rohc-sigcomp-impl-guide) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Robust Header Compression WG to consider the following document: - 'Implementer's Guide for SigComp ' 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/internet-drafts/draft-ietf-rohc-sigcomp-impl-guide-09.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 07 18:50:47 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsT0k-0005Fs-GJ; Thu, 07 Dec 2006 18:50:42 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsT0i-0005Fm-Dh for ietf-announce@ietf.org; Thu, 07 Dec 2006 18:50:40 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GsT0i-0005kg-5d for ietf-announce@ietf.org; Thu, 07 Dec 2006 18:50:40 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id E27F017602 for ; Thu, 7 Dec 2006 23:50:09 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GsT0D-0000O6-G9 for ietf-announce@ietf.org; Thu, 07 Dec 2006 18:50:09 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 07 Dec 2006 18:50:09 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: Last Call: 'Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)' to Proposed Standard (draft-manral-ipsec-rfc4305-bis-errata) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following document: - 'Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH) ' as a Proposed Standard To provide security services, the IPsec protocols make use of various cryptographic algorithms. In particular, the Encapsulating Security Payload (ESP) and the Authentication Header (AH) protect data that is sent over an IPsec Security Association (SA). To ensure interoperability, it is necessary to specify a set of mandatory-to- implement algorithms. This document defines the current set of mandatory-to-implement algorithms for ESP and AH, as well as specifying algorithms that should be implemented because they may be promoted to mandatory at some future time. 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 2007-01-04. The file can be obtained via http://www.ietf.org/internet-drafts/draft-manral-ipsec-rfc4305-bis-errata-02.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 07 18:57:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsSxm-00047e-8h; Thu, 07 Dec 2006 18:47:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GsSxl-00047Z-2z for ietf-announce@ietf.org; Thu, 07 Dec 2006 18:47:37 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsSxk-0006iW-U4 for ietf-announce@ietf.org; Thu, 07 Dec 2006 18:47:37 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id DC45E329D1; Thu, 7 Dec 2006 23:47:36 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GsSxk-0000L4-Oz; Thu, 07 Dec 2006 18:47:36 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 07 Dec 2006 18:47:36 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: radiusext@ops.ietf.org Subject: Last Call: 'RADIUS Filter Rule Attribute' to Proposed Standard (draft-ietf-radext-filter) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the RADIUS EXTensions WG to consider the following document: - 'RADIUS Filter Rule Attribute ' 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/internet-drafts/draft-ietf-radext-filter-06.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 09:39:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtmIr-0004rk-4O; Mon, 11 Dec 2006 09:38:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtmIp-0004r9-81 for ietf-announce@ietf.org; Mon, 11 Dec 2006 09:38:47 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtmIp-0005YE-1n for ietf-announce@ietf.org; Mon, 11 Dec 2006 09:38:47 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id E2B6D26E28 for ; Mon, 11 Dec 2006 14:38:46 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GtmIo-0002jz-Qf for ietf-announce@ietf.org; Mon, 11 Dec 2006 09:38:46 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 11 Dec 2006 09:38:46 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: Last Call: 'Suite B Cryptographic Suites for IPsec' to Proposed Standard (draft-solinas-ui-suites) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following document: - 'Suite B Cryptographic Suites for IPsec ' as a Proposed Standard This document proposes four optional cryptographic user interface suites ("UI suites") for IPsec similar to the two suites specified in RFC 4308. The four new suites provide compatibility with the United States National Security Agency's Suite B specifications. 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 2007-01-08. The file can be obtained via http://www.ietf.org/internet-drafts/draft-solinas-ui-suites-00.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 10:19:54 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtmwN-0005sX-7g; Mon, 11 Dec 2006 10:19:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtmwK-0005rw-Rv for ietf-announce@ietf.org; Mon, 11 Dec 2006 10:19:36 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtmwJ-0004OX-MH for ietf-announce@ietf.org; Mon, 11 Dec 2006 10:19:36 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id A30FC328F2; Mon, 11 Dec 2006 15:19:35 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GtmwJ-00057a-Hs; Mon, 11 Dec 2006 10:19:35 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 11 Dec 2006 10:19:35 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: dna@eng.monash.edu.au Subject: Last Call: 'Link-layer Event Notifications for Detecting Network Attachments' to Informational RFC (draft-ietf-dna-link-information) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Detecting Network Attachment WG to consider the following document: - 'Link-layer Event Notifications for Detecting Network Attachments ' as an Informational RFC 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-31. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-dna-link-information-05.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 12:43:27 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtpBL-0001Wy-1x; Mon, 11 Dec 2006 12:43:15 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtpBJ-0001WX-01 for ietf-announce@ietf.org; Mon, 11 Dec 2006 12:43:13 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtpBI-0004rq-OY for ietf-announce@ietf.org; Mon, 11 Dec 2006 12:43:12 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 7C5AD26E6C; Mon, 11 Dec 2006 17:43:12 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GtpBI-0001XP-D7; Mon, 11 Dec 2006 12:43:12 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 11 Dec 2006 12:43:12 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Cc: pmtud chair , Internet Architecture Board , RFC Editor Subject: Protocol Action: 'Packetization Layer Path MTU Discovery' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Packetization Layer Path MTU Discovery ' as a Proposed Standard This document is the product of the Path MTU Discovery Working Group. The IESG contact persons are Lars Eggert and Magnus Westerlund. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pmtud-method-11.txt Technical Summary This document describes a robust method for Path MTU Discovery ("Packetization Layer Path MTU Discovery" or PLPMTUD) that relies on TCP or some other Packetization Layer to probe an Internet path with progressively larger packets. This method is described as an extension to RFC 1191 and RFC 1981, which specify ICMP based Path MTU Discovery for IP versions 4 and 6, respectively. The general strategy of the new algorithm is to start with a small MTU and search upward, testing successively larger MTUs by probing with single packets. If a probe is successfully delivered then the MTU can be raised. If the probe is lost, it is treated as an MTU limitation and not as a congestion signal. PLPMTUD introduces some flexibility in the implementation of classical Path MTU discovery. If can be configured to perform just ICMP black hole recovery to increase the robustness of classical Path MTU Discovery, or at the other extreme, all ICMP processing can be disabled and PLPMTUD can completely replace classical Path MTU Discovery. Working Group Summary The working group feels that an update to path MTU discovery is needed to rectify problems with current "classical" path MTU discovery that occur in today's network deployments (which result in Path MTU "black holes", and the failure of not only the algorithm but often the entire connection). The document has had considerable review by the working group over its eight revisions, and the comments have been incorporated in the current draft. Reviewers have had background in TCP, SCTP, DCCP, the use of tunnels (ipsec and other) and IPv6. The WGLC version has had four careful reviews that only revealed nits and clarifications that are fixed in this version. Protocol Quality The current protocol has one implementation in Linux, by a co-author, and another independent implementation in a user-space transport protocol. Previous versions have had implementation in Linux, NetBSD, and FreeBSD, by different people, resulting in comments that contributed to document changes. Other operating systems vendors and tunnel vendors have reviewed the document. Matt Zekauskas (matt@internet2.edu) acted as Document Shepherd. Lars Eggert (eggert@netlab.nec.de) has reviewed this document for the IESG. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 16:22:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtsW2-0003Xj-NL; Mon, 11 Dec 2006 16:16:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtsW1-0003XQ-0h; Mon, 11 Dec 2006 16:16:49 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtsW0-00016P-Re; Mon, 11 Dec 2006 16:16:49 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id ABD5326E3F; Mon, 11 Dec 2006 21:16:48 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GtsW0-0002mS-J0; Mon, 11 Dec 2006 16:16:48 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 11 Dec 2006 16:16:48 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: widex@ietf.org Subject: Last Call: 'Widget Description Exchange Service (WIDEX) Requirements' to Informational RFC (draft-ietf-widex-requirements) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Widget Description Exchange Service WG to consider the following document: - 'Widget Description Exchange Service (WIDEX) Requirements ' as an Informational RFC 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-25. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-widex-requirements-03.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 16:58:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9p-0004Lk-0K; Mon, 11 Dec 2006 16:57:57 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9n-0004LV-Iu; Mon, 11 Dec 2006 16:57:55 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtt9j-0000dx-3C; Mon, 11 Dec 2006 16:57:55 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBBLvmPY017196; Mon, 11 Dec 2006 13:57:48 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBBLvmoX017195; Mon, 11 Dec 2006 13:57:48 -0800 Date: Mon, 11 Dec 2006 13:57:48 -0800 Message-Id: <200612112157.kBBLvmoX017195@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.3 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: iptel@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4759 on The ENUM Dip Indicator Parameter for the "tel" URI X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4759 Title: The ENUM Dip Indicator Parameter for the "tel" URI Author: R. Stastny, R. Shockey, L. Conroy Status: Standards Track Date: December 2006 Mailbox: Richard.stastny@oefeg.at, richard.shockey@neustar.biz, lconroy@insensate.co.uk Pages: 8 Characters: 15062 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-iptel-tel-enumdi-05.txt URL: http://www.rfc-editor.org/rfc/rfc4759.txt This document defines a new parameter "enumdi" for the "tel" Uniform Resource Identifier (URI) to support the handling of ENUM queries in Voice over Internet Protocol (VoIP) network elements. A VoIP network element may receive a URI containing an E.164 number, where that URI contains an "enumdi" parameter. The presence of the "enumdi" parameter indicates that an ENUM query has already been performed on the E.164 number by a previous VoIP network element. Equally, if a VoIP network element sends such a URI, it asserts that an ENUM query has been carried out on this number. [STANDARDS TRACK] This document is a product of the IP Telephony 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 16:58:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9q-0004Me-MP; Mon, 11 Dec 2006 16:57:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9o-0004Le-FJ for ietf-announce@ietf.org; Mon, 11 Dec 2006 16:57:56 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtt9l-0000gD-Bb for ietf-announce@ietf.org; Mon, 11 Dec 2006 16:57:56 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBBLvq5G017201; Mon, 11 Dec 2006 13:57:52 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBBLvqvT017200; Mon, 11 Dec 2006 13:57:52 -0800 Date: Mon, 11 Dec 2006 13:57:52 -0800 Message-Id: <200612112157.kBBLvqvT017200@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: rfc-editor@rfc-editor.org Subject: RFC 4794 on RFC 1264 Is Obsolete X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4794 Title: RFC 1264 Is Obsolete Author: B. Fenner Status: Informational Date: December 2006 Mailbox: fenner@research.att.com Pages: 4 Characters: 7554 Obsoletes: RFC1264 See-Also: I-D Tag: draft-fenner-obsolete-1264-03.txt URL: http://www.rfc-editor.org/rfc/rfc4794.txt RFC 1264 was written during what was effectively a completely different time in the life of the Internet. It prescribed rules to protect the Internet against new routing protocols that may have various undesirable properties. In today's Internet, there are so many other pressures against deploying unreasonable protocols that we believe that existing controls suffice, and the RFC 1264 rules just get in the way. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 16:58:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9p-0004Lk-0K; Mon, 11 Dec 2006 16:57:57 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9n-0004LV-Iu; Mon, 11 Dec 2006 16:57:55 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtt9j-0000dx-3C; Mon, 11 Dec 2006 16:57:55 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBBLvmPY017196; Mon, 11 Dec 2006 13:57:48 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBBLvmoX017195; Mon, 11 Dec 2006 13:57:48 -0800 Date: Mon, 11 Dec 2006 13:57:48 -0800 Message-Id: <200612112157.kBBLvmoX017195@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.3 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: iptel@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4759 on The ENUM Dip Indicator Parameter for the "tel" URI X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4759 Title: The ENUM Dip Indicator Parameter for the "tel" URI Author: R. Stastny, R. Shockey, L. Conroy Status: Standards Track Date: December 2006 Mailbox: Richard.stastny@oefeg.at, richard.shockey@neustar.biz, lconroy@insensate.co.uk Pages: 8 Characters: 15062 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-iptel-tel-enumdi-05.txt URL: http://www.rfc-editor.org/rfc/rfc4759.txt This document defines a new parameter "enumdi" for the "tel" Uniform Resource Identifier (URI) to support the handling of ENUM queries in Voice over Internet Protocol (VoIP) network elements. A VoIP network element may receive a URI containing an E.164 number, where that URI contains an "enumdi" parameter. The presence of the "enumdi" parameter indicates that an ENUM query has already been performed on the E.164 number by a previous VoIP network element. Equally, if a VoIP network element sends such a URI, it asserts that an ENUM query has been carried out on this number. [STANDARDS TRACK] This document is a product of the IP Telephony 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 16:58:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9q-0004Me-MP; Mon, 11 Dec 2006 16:57:58 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9o-0004Le-FJ for ietf-announce@ietf.org; Mon, 11 Dec 2006 16:57:56 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtt9l-0000gD-Bb for ietf-announce@ietf.org; Mon, 11 Dec 2006 16:57:56 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBBLvq5G017201; Mon, 11 Dec 2006 13:57:52 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBBLvqvT017200; Mon, 11 Dec 2006 13:57:52 -0800 Date: Mon, 11 Dec 2006 13:57:52 -0800 Message-Id: <200612112157.kBBLvqvT017200@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: rfc-editor@rfc-editor.org Subject: RFC 4794 on RFC 1264 Is Obsolete X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4794 Title: RFC 1264 Is Obsolete Author: B. Fenner Status: Informational Date: December 2006 Mailbox: fenner@research.att.com Pages: 4 Characters: 7554 Obsoletes: RFC1264 See-Also: I-D Tag: draft-fenner-obsolete-1264-03.txt URL: http://www.rfc-editor.org/rfc/rfc4794.txt RFC 1264 was written during what was effectively a completely different time in the life of the Internet. It prescribed rules to protect the Internet against new routing protocols that may have various undesirable properties. In today's Internet, there are so many other pressures against deploying unreasonable protocols that we believe that existing controls suffice, and the RFC 1264 rules just get in the way. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 11 16:58:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9u-0004Oe-9U; Mon, 11 Dec 2006 16:58:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtt9s-0004O8-VF for ietf-announce@ietf.org; Mon, 11 Dec 2006 16:58:00 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtt9r-0000hE-JS for ietf-announce@ietf.org; Mon, 11 Dec 2006 16:58:00 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBBLvxeD017206; Mon, 11 Dec 2006 13:57:59 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBBLvxOT017205; Mon, 11 Dec 2006 13:57:59 -0800 Date: Mon, 11 Dec 2006 13:57:59 -0800 Message-Id: <200612112157.kBBLvxOT017205@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Cc: rfc-editor@rfc-editor.org Subject: RFC 4757 on The RC4-HMAC Kerberos Encryption Types Used by Microsoft Windows X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4757 Title: The RC4-HMAC Kerberos Encryption Types Used by Microsoft Windows Author: K. Jaganathan, L. Zhu, J. Brezak Status: Informational Date: December 2006 Mailbox: karthikj@microsoft.com, lzhu@microsoft.com, jbrezak@microsoft.com Pages: 18 Characters: 36562 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-jaganathan-rc4-hmac-03.txt URL: http://www.rfc-editor.org/rfc/rfc4757.txt The Microsoft Windows 2000 implementation of Kerberos introduces a new encryption type based on the RC4 encryption algorithm and using an MD5 HMAC for checksum. This is offered as an alternative to using the existing DES-based encryption types. The RC4-HMAC encryption types are used to ease upgrade of existing Windows NT environments, provide strong cryptography (128-bit key lengths), and provide exportable (meet United States government export restriction requirements) encryption. This document describes the implementation of those encryption types. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 13 09:59:53 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuVZX-0005Sl-05; Wed, 13 Dec 2006 09:59:03 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuVZW-0005SW-54; Wed, 13 Dec 2006 09:59:02 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GuVZT-0007Ji-RN; Wed, 13 Dec 2006 09:59:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id C2A3F2ACF3; Wed, 13 Dec 2006 14:58:29 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GuVYz-0002U1-H5; Wed, 13 Dec 2006 09:58:29 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Wed, 13 Dec 2006 09:58:29 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: rohc@ietf.org Subject: Last Call: 'Formal Notation for Robust Header Compression (ROHC-FN)' to Proposed Standard (draft-ietf-rohc-formal-notation) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Robust Header Compression WG to consider the following document: - 'Formal Notation for Robust Header Compression (ROHC-FN) ' 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 2007-01-03. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-rohc-formal-notation-13.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 13 10:13:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuVmu-0003oC-NT; Wed, 13 Dec 2006 10:12:52 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuVmt-0003na-Iq for ietf-announce@ietf.org; Wed, 13 Dec 2006 10:12:51 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GuVmt-0001kf-9w for ietf-announce@ietf.org; Wed, 13 Dec 2006 10:12:51 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 095071776C; Wed, 13 Dec 2006 15:12:21 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GuVm9-0004Wm-Kc; Wed, 13 Dec 2006 10:12:10 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Wed, 13 Dec 2006 10:12:05 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: idr chair , Internet Architecture Board , RFC Editor Subject: Protocol Action: 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE)' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Connecting IPv6 Islands over IPv4 MPLS using IPv6 Provider Edge Routers (6PE) ' as a Proposed Standard This document is the product of the Inter-Domain Routing Working Group. The IESG contact persons are Bill Fenner and Ross Callon. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ooms-v6ops-bgp-tunnel-07.txt Technical Summary This document explains how to interconnect IPv6 islands over a Multi-Protocol Label Switching (MPLS)-enabled IPv4 cloud. This approach relies on IPv6 Provider Edge routers (6PE) which are Dual Stack in order to connect to IPv6 islands and to the MPLS core which is only required to run IPv4 MPLS. The 6PE routers exchange the IPv6 reachability information transparently over the core using the Multi-Protocol Border Gateway Protocol (MP-BGP) over IPv4. In doing so, the BGP Next Hop field is used to convey the IPv4 address of the 6PE router so that dynamically established IPv4-signaled MPLS Label Switched Paths (LSPs) can be used without explicit tunnel configuration. Working Group Summary The v6ops working group had consensus to develop this approach, and handed the document off to the idr working group for its BGP expertise. There were no comments on the document during the idr WG Last Call. Protocol Quality There are multiple implementations of this specification. Specifically there are two implementations by the router vendors, and three implementations by the network test equipment vendors. The full implementation report is available (see http://www.ietf.org/IESG/Implementations/Implementation_draft-levy-idr-6pe-survey.txt). Note to RFC Editor Please publish this version, instead of the previously approved version 06. This version includes the changes described in the previous approval message's RFC Editor Note. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 13 13:33:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuF-0005cu-8m; Wed, 13 Dec 2006 13:32:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuA-0005Ym-Ku for ietf-announce@ietf.org; Wed, 13 Dec 2006 13:32:34 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuYnE-0002lT-H4 for ietf-announce@ietf.org; Wed, 13 Dec 2006 13:25:25 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBDIPOCp024900; Wed, 13 Dec 2006 10:25:24 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBDIPN7Y024899; Wed, 13 Dec 2006 10:25:24 -0800 Date: Wed, 13 Dec 2006 10:25:24 -0800 Message-Id: <200612131825.kBDIPN7Y024899@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Cc: ccamp@ops.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4783 on GMPLS - Communication of Alarm Information X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4783 Title: GMPLS - Communication of Alarm Information Author: L. Berger, Ed. Status: Standards Track Date: December 2006 Mailbox: lberger@labn.net Pages: 19 Characters: 42068 Updates: RFC3473 See-Also: I-D Tag: draft-ietf-ccamp-gmpls-alarm-spec-06.txt URL: http://www.rfc-editor.org/rfc/rfc4783.txt This document describes an extension to Generalized MPLS (Multi-Protocol Label Switching) signaling to support communication of alarm information. GMPLS signaling already supports the control of alarm reporting, but not the communication of alarm information. This document presents both a functional description and GMPLS-RSVP specifics of such an extension. This document also proposes modification of the RSVP ERROR_SPEC object. This document updates RFC 3473, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", through the addition of new, optional protocol elements. It does not change, and is fully backward compatible with, the procedures specified in RFC 3473. [STANDADS TRACK] This document is a product of the Common Control and Measurement Plane 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 13 13:46:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuI-0005eq-9s; Wed, 13 Dec 2006 13:32:42 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuE-0005cO-Qe for ietf-announce@ietf.org; Wed, 13 Dec 2006 13:32:38 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuYlU-0002d8-ET for ietf-announce@ietf.org; Wed, 13 Dec 2006 13:23:37 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBDINZgP024891; Wed, 13 Dec 2006 10:23:35 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBDINZsC024890; Wed, 13 Dec 2006 10:23:35 -0800 Date: Wed, 13 Dec 2006 10:23:35 -0800 Message-Id: <200612131823.kBDINZsC024890@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Cc: rfc-editor@rfc-editor.org Subject: BCP0125 RFC 4775 on Procedures for Protocol Extensions and Variations X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. BCP 125 RFC 4775 Title: Procedures for Protocol Extensions and Variations Author: S. Bradner, B. Carpenter, Ed., T. Narten Status: Best Current Practice Date: December 2006 Mailbox: sob@harvard.edu, brc@zurich.ibm.com, narten@us.ibm.com Pages: 14 Characters: 32797 Updates: See-Also: BCP0125 I-D Tag: draft-carpenter-protocol-extensions-04.txt URL: http://www.rfc-editor.org/rfc/rfc4775.txt This document discusses procedural issues related to the extensibility of IETF protocols, including when it is reasonable to extend IETF protocols with little or no review, and when extensions or variations need to be reviewed by the IETF community. Experience has shown that extension of protocols without early IETF review can carry risk. The document also recommends that major extensions to or variations of IETF protocols only take place through normal IETF processes or in coordination with the IETF. This document is directed principally at other Standards Development Organizations (SDOs) and vendors considering requirements for extensions to IETF protocols. It does not modify formal IETF processes. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 13 13:46:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuZ-0005pl-H0; Wed, 13 Dec 2006 13:32:59 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuE-0005Ym-Rc; Wed, 13 Dec 2006 13:32:38 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuYlP-0002cl-Vb; Wed, 13 Dec 2006 13:23:33 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBDINVFh024886; Wed, 13 Dec 2006 10:23:31 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBDINVHe024885; Wed, 13 Dec 2006 10:23:31 -0800 Date: Wed, 13 Dec 2006 10:23:31 -0800 Message-Id: <200612131823.kBDINVHe024885@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Cc: ospf@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4750 on OSPF Version 2 Management Information Base X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4750 Title: OSPF Version 2 Management Information Base Author: D. Joyal, Ed., P. Galecki, Ed., S. Giacalone, Ed., R. Coltun, F. Baker Status: Standards Track Date: December 2006 Mailbox: djoyal@nortel.com, pgalecki@airvana.com, spencer.giacalone@gmail.com, fred@cisco.com Pages: 121 Characters: 222459 Obsoletes: RFC1850 See-Also: I-D Tag: draft-ietf-ospf-mib-update-11.txt URL: http://www.rfc-editor.org/rfc/rfc4750.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing version 2 of the Open Shortest Path First Routing Protocol. Version 2 of the OSPF protocol is specific to the IPv4 address family. Version 3 of the OSPF protocol is specific to the IPv6 address family. This memo obsoletes RFC 1850; however, it is designed to be backwards compatible. The functional differences between this memo and RFC 1850 are explained in Appendix B. [STANDARDS TRACK] This document is a product of the Open Shortest Path First IGP 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 13 13:46:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuF-0005cu-G0; Wed, 13 Dec 2006 13:32:39 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYuA-0005Ym-Ku for ietf-announce@ietf.org; Wed, 13 Dec 2006 13:32:34 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuYnE-0002lT-H4 for ietf-announce@ietf.org; Wed, 13 Dec 2006 13:25:25 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBDIPOCp024900; Wed, 13 Dec 2006 10:25:24 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBDIPN7Y024899; Wed, 13 Dec 2006 10:25:24 -0800 Date: Wed, 13 Dec 2006 10:25:24 -0800 Message-Id: <200612131825.kBDIPN7Y024899@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 Cc: ccamp@ops.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4783 on GMPLS - Communication of Alarm Information X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4783 Title: GMPLS - Communication of Alarm Information Author: L. Berger, Ed. Status: Standards Track Date: December 2006 Mailbox: lberger@labn.net Pages: 19 Characters: 42068 Updates: RFC3473 See-Also: I-D Tag: draft-ietf-ccamp-gmpls-alarm-spec-06.txt URL: http://www.rfc-editor.org/rfc/rfc4783.txt This document describes an extension to Generalized MPLS (Multi-Protocol Label Switching) signaling to support communication of alarm information. GMPLS signaling already supports the control of alarm reporting, but not the communication of alarm information. This document presents both a functional description and GMPLS-RSVP specifics of such an extension. This document also proposes modification of the RSVP ERROR_SPEC object. This document updates RFC 3473, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions", through the addition of new, optional protocol elements. It does not change, and is fully backward compatible with, the procedures specified in RFC 3473. [STANDADS TRACK] This document is a product of the Common Control and Measurement Plane 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 15 05:03:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv9uv-0004zL-Th; Fri, 15 Dec 2006 05:03:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv9uu-0004zD-UQ; Fri, 15 Dec 2006 05:03:48 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv9uu-0007Lb-PD; Fri, 15 Dec 2006 05:03:48 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id A12CE26E83; Fri, 15 Dec 2006 10:03:48 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Gv9uu-0000UZ-IQ; Fri, 15 Dec 2006 05:03:48 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: Brian Carpenter Message-Id: Date: Fri, 15 Dec 2006 05:03:48 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: ion-ion-store open for public comment X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org An ION (IETF Operational Note, see RFC 4693) is open for public comment on the ietf@ietf.org list. Comments should be sent by 2006-12-31. Please see http://www.ietf.org/IESG/content/ions/drafts/ion-ion-store.html _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 15 05:11:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv9uw-0004zL-2c; Fri, 15 Dec 2006 05:03:50 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv9uu-0004zD-UQ; Fri, 15 Dec 2006 05:03:48 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv9uu-0007Lb-PD; Fri, 15 Dec 2006 05:03:48 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id A12CE26E83; Fri, 15 Dec 2006 10:03:48 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Gv9uu-0000UZ-IQ; Fri, 15 Dec 2006 05:03:48 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: Brian Carpenter Message-Id: Date: Fri, 15 Dec 2006 05:03:48 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: ion-ion-store open for public comment X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org An ION (IETF Operational Note, see RFC 4693) is open for public comment on the ietf@ietf.org list. Comments should be sent by 2006-12-31. Please see http://www.ietf.org/IESG/content/ions/drafts/ion-ion-store.html _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 15 05:11:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv9tC-0004SC-PG; Fri, 15 Dec 2006 05:02:02 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv9tA-0004S3-7l; Fri, 15 Dec 2006 05:02:00 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv9tA-00072a-2c; Fri, 15 Dec 2006 05:02:00 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns1.neustar.com (Postfix) with ESMTP id ED5CD26E83; Fri, 15 Dec 2006 10:01:59 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Gv9t9-0000UF-SU; Fri, 15 Dec 2006 05:01:59 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: Brian Carpenter Message-Id: Date: Fri, 15 Dec 2006 05:01:59 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: ion-ion-format open for public comment X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org An ION (IETF Operational Note, see RFC 4693) is open for public comment on the ietf@ietf.org list. Comments should be sent by 2006-12-31. Please see http://www.ietf.org/IESG/content/ions/drafts/ion-ion-format.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 15 10:24:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GvElt-0007P3-Vt; Fri, 15 Dec 2006 10:14:49 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GvEls-0007Os-4e; Fri, 15 Dec 2006 10:14:48 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GvElq-000802-S3; Fri, 15 Dec 2006 10:14:48 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id CA2462AC7C; Fri, 15 Dec 2006 15:14:16 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GvElM-0001Ts-IX; Fri, 15 Dec 2006 10:14:16 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Fri, 15 Dec 2006 10:14:16 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: lemonade@ietf.org Subject: Last Call: 'The IMAP COMPRESS Extension' to Proposed Standard (draft-ietf-lemonade-compress) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Enhancements to Internet email to Support Diverse Service Environments WG to consider the following document: - 'The IMAP COMPRESS Extension ' 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 2007-01-06. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-lemonade-compress-06.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 15 17:10:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GvL8E-0001vu-NA; Fri, 15 Dec 2006 17:02:18 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GvL8D-0001vW-69; Fri, 15 Dec 2006 17:02:17 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GvL8B-0002ht-TH; Fri, 15 Dec 2006 17:02:17 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id 97BCB175A7; Fri, 15 Dec 2006 22:01:45 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GvL7h-00062x-6V; Fri, 15 Dec 2006 17:01:45 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list From: Leslie Daigle Message-Id: Date: Fri, 15 Dec 2006 17:01:45 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: iab@ietf.org Subject: FINAL call for nominations: IAOC position selected by the IAB X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iab@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IAB is making a call for nominations for the IETF Administrative Oversight Committee (IAOC), as described in BCP 101 (RFC 4071) and BCP 113 (RFC 4333). The IESG and the IAB each select one person for a two-year IAOC term in alternate years. This year, the IAB will select one person for a term ending in spring 2009. The incumbent is Lucy Lynch, who was selected by the IAB for an initial two year term expiring in spring 2007. Candidates for these IAOC positions should have knowledge of the IETF, knowledge of contracts and financial procedures, and familiarity with the administrative support needs of the IAB, the IESG, and the IETF standards process. The candidates are also expected to be able to understand the respective roles and responsibilities of the IETF and ISOC in this activity, and be able to articulate these roles within the IETF community. The candidates will also be expected to exercise all the duties of an IAOC member, including being prepared to undertake any associated responsibilities. These include, but are not limited to, the setting of administrative support policies, oversight of the administrative operations of the IETF, and representing the interests of the IETF to the IAOC. The candidates must be able to undertake full participation in all Committee meetings and Committee activities. The IAB-selected member of the IAOC does not directly represent the IAB. The IAB and IESG selected members are accountable directly to the IETF community. Candidates do not need to be current members of the IAB or IESG, and in fact we prefer nominations and volunteers from the rest of the community. If you are interested in one of these positions, or know of someone who may be a good fit for this position, please send the name and email address to Phil Roberts, Executive Director of the IAB at . The IAB will respond with a questionnaire, asking for the candidates' qualifications and willingness to serve. The names of all people who declare themselves willing to serve will be made public on the ietf-announce@ietf.org list after the end of the solicitation period (December 22). The IAB expects to make a decision on or before January 29 (prior to the expected date at which the Nomcom will select its IAOC nominee). Leslie Daigle, for the IAB. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 11:56:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwLcK-0002MW-JY; Mon, 18 Dec 2006 11:45:32 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwLcJ-0002ME-5X for ietf-announce@ietf.org; Mon, 18 Dec 2006 11:45:31 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwLcH-0007z8-RM for ietf-announce@ietf.org; Mon, 18 Dec 2006 11:45:31 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 8C574175D8; Mon, 18 Dec 2006 16:44:59 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwLbn-0004v3-5Q; Mon, 18 Dec 2006 11:44:59 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 18 Dec 2006 11:44:59 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 Cc: nemo chair , Internet Architecture Board , RFC Editor Subject: Document Action: 'Network Mobility Support Goals and Requirements' to Informational RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Network Mobility Support Goals and Requirements ' as an Informational RFC This document is the product of the Network Mobility Working Group. The IESG contact persons are Jari Arkko and Mark Townsley. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-nemo-requirements-06.txt Technical Summary Network mobility arises when a router connecting a network to the Internet dynamically changes its point of attachment to the Internet thereby causing the reachability of the said network to be changed in relation to the fixed Internet topology. Such kind of network is referred to as a mobile network. With appropriate mechanisms, sessions established between nodes in the mobile network and the global Internet can be maintained after the mobile router changes its point of attachment. This document outlines the goals expected from network mobility support and defines the requirements that must be met by the NEMO Basic Support solution. Working Group Summary There has been significant review and discussion of these documents, and the consensus of the working group is solidly behind the documents. Protocol Quality RFC 3963, NEMO Basic Support protocol was developed and published as an answer to these requirements. There are multiple implementations. This document has been reviewed by Jari Arkko for the IESG. Note to RFC Editor In Section 3.7, s/modidication/modification/ In Section 4, replace R10 with this: R10: The solution MUST be agnostic to the internal configuration. This means the solution will behave the same way if the NEMO is nested, comprises one or several subnets, comprises MNNs which are LFNs, VMNs, LFNs or a mixture of them. Add replace Section 5 with the following contents: Security consideration of the "NEMO Basic Support" solutions are addressed in RFC 3963. Section 3.9 of this document discusses the security goals for all forms of existing and forthcoming NEMO solutions. Please change MUST, MAY, etc in Section 4 to lower case. Please add a NEW Section 3.12: 3.12 Minimal Impact on Internet Routing Any NEMO solution(s) needs have minimal negative effect on the global Internet routing system. The solution must therefore limit both the amount of information that must be injected into Internet routing, as well as the dynamic changes in the information that is injected into the global routing system. As one example of why this is necessary, consider the approach of advertising each mobile network's connectivity into BGP, and for every movement withdrawing old routes and injecting new routes. If there were tens of thousands of mobile networks each advertising and withdrawing routes, for example, at the speed that an airplane can move from one ground station to another, the potential effect on BGP could be very unfortunate. In this example the total amount of routing information advertised into BGP may be acceptable, but the dynamic instability of the information (ie, the number of changes over time) would be unacceptable. And finally, add a NEW requirement to the end of Section 4: R17: The solution should have a minimal impact on the global Internet routing system. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 12:28:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwMHY-00030V-ET; Mon, 18 Dec 2006 12:28:08 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwLVl-0008Tc-LA; Mon, 18 Dec 2006 11:38:45 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwLVl-0007CB-Ee; Mon, 18 Dec 2006 11:38:45 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns4.neustar.com (Postfix) with ESMTP id 63F582ACFF; Mon, 18 Dec 2006 16:38:15 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GwLVH-0000qr-5m; Mon, 18 Dec 2006 11:38:15 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list From: Barbara Fuller Message-Id: Date: Mon, 18 Dec 2006 11:38:15 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad X-Mailman-Approved-At: Mon, 18 Dec 2006 12:28:02 -0500 Cc: iesg@ietf.org Subject: Secretariat Holiday Schedule X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org NeuStar Secretariat Services will be closed on Monday, December 25th and Tuesday, December 26th in observance of the Christmas holiday. In addition, most members of the Secretariat team will be on vacation for the rest of the week, and will return to work on Tuesday, January 2, 2007. Please be assured that even though they are on vacation, each staff member will check his or her e-mail on a regular basis and attend to any urgent or time-sensitive matters. Happy holidays and best wishes for the New Year. Barbara Fuller for the IETF Secretariat _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 14:18:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwNzv-0007m0-8A; Mon, 18 Dec 2006 14:18:03 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwNzu-0007ln-1N for ietf-announce@ietf.org; Mon, 18 Dec 2006 14:18:02 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwNzt-0006Nw-LK for ietf-announce@ietf.org; Mon, 18 Dec 2006 14:18:01 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 56766175E7; Mon, 18 Dec 2006 19:17:31 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwNzO-0002hI-Tz; Mon, 18 Dec 2006 14:17:30 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 18 Dec 2006 14:17:30 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 225414c974e0d6437992164e91287a51 Cc: dccp chair , Internet Architecture Board , RFC Editor Subject: Document Action: 'TCP Friendly Rate Control (TFRC): the Small-Packet (SP) Variant' to Experimental RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'TCP Friendly Rate Control (TFRC): the Small-Packet (SP) Variant ' as an Experimental RFC This document is the product of the Datagram Congestion Control Protocol Working Group. The IESG contact persons are Lars Eggert and Magnus Westerlund. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dccp-tfrc-voip-07.txt Technical Summary This document proposes a mechanism for further experimentation, but not for widespread deployment at this time in the global Internet. TCP-Friendly Rate Control (TFRC) is a congestion control mechanism for unicast flows operating in a best-effort Internet environment [RFC3448]. TFRC was intended for applications that use a fixed packet size, and was designed to be reasonably fair when competing for bandwidth with TCP connections using the same packet size. This document proposes TFRC-SP, a Small-Packet (SP) variant of TFRC, that is designed for applications that send small packets. The design goal for TFRC-SP is to achieve the same bandwidth in bps (bits per second) as a TCP flow using packets of up to 1500 bytes. TFRC-SP enforces a minimum interval of 10 ms between data packets, to prevent a single flow from sending small packets arbitrarily frequently. Flows using TFRC-SP compete reasonably fairly with large-packet TCP and TFRC flows in environments where large-packet flows and small- packet flows experience similar packet drop rates. However, in environments where small-packet flows experience lower packet drop rates than large-packet flows (e.g., with Drop-Tail queues in units of bytes), TFRC-SP can receive considerably more than its share of the bandwidth. Working Group Summary This document is a chartered item of the DCCP WG. The document provides a description of an experimental method to provide congestion control that is based on TFRC, but is adapted to sources that transmit small fixed-sized packets at a fixed rate. The document also provides simulation results to demonstrate the fairness with other IETF-defined transport protocols and may serve as a basis for future congestion control methods. Protocol Quality The document defines a new experimental algorithm. Further experimentation is required to understand the implications of implementation, its suitability to specific applications and the deployment within the general Internet. Gorry Fairhurst was the PROTO Document Shepherd and Lars Eggert has reviewed this document for the IESG. Note to RFC Editor Section 3 (feedback from Magnus): OLD: If the TFRC implementation knows that the IP layer is using IPv6 instead of IPv4, then the connection using TFRC-SP MAY use an estimate of 40 bytes instead of 60 bytes for H, for simplicity of implementation. NEW: However, if the TFRC implementation knows that the IP layer is using IPv6 instead of IPv4, then the connection using TFRC-SP MAY still use the default estimate of 40 bytes for H instead of the actual size of 60 bytes, for simplicity of implementation. Section 4.5.1 (from Miguel Garcia): OLD: this environments, the sending rate in bytes per RTT is roughly 1.2 NEW: these environments, the sending rate in bytes per RTT is roughly 1.2 ^^^^^ Section 4.5.3 (from Lars): OLD: bytes (becauses the path MTU is known to be less than 576 bytes), NEW: bytes (because the path MTU is known to be less than 576 bytes), ^^^^^^^ Section 12 (nit from Miguel Garcia): OLD: for feedback on earlier versions of this draft. NEW: for feedback on earlier versions of this document. ^^^^^^^^ Section 9 (from secdir review by Juergen Quittek): OLD: There are no security considerations introduced in this document. General security considerations for TFRC are discussed in RFC 3448. The security considerations for TFRC include the need to protect against spoofed feedback, and the need for protection mechanisms to protect the congestion control mechanisms against incorrect information from the receiver. Security considerations for DCCP's Congestion Control ID 3, TFRC Congestion Control, are discussed in [RFC4342]. That document extensively discussed the mechanisms the sender can use to verify the information sent by the receiver. NEW: There are no new security considerations introduced in this document. The issues of the fairness of TFRC-SP with standard TFRC and TCP in a range of environments, including those with byte-based queue management at the congested routers, are discussed extensively in the main body of this document. General security considerations for TFRC are discussed in RFC 3448. As with TFRC in RFC 3448, TFRC-SP is not a transport protocol in its own right, but a congestion control mechanism that is intended to be used in conjunction with a transport protocol. Therefore security primarily needs to be considered in the context of a specific transport protocol and its authentication mechanisms. As discussed for TFRC in RFC 3448, any transport protocol that uses TFRC-SP needs to protect against spoofed feedback, and to protect the congestion control mechanisms against incorrect information from the receiver. Again as discussed for TFRC in RFC 3448, we expect that protocols incorporating ECN with TFRC-SP will want to use the ECN nonce [RFC3540] to protect the sender from the accidental or malicious concealment of marked packets Security considerations for DCCP's Congestion Control ID 3, TFRC Congestion Control, the transport protocol that uses TFRC, are discussed in [RFC4342]. That document extensively discussed the mechanisms the sender can use to verify the information sent by the receiver, including the use of the ECN nonce. Section (adding acknowledgements): OLD: Eggert, Gorry Fairhurst, Mark Handley, Ladan Gharai, Richard Nelson, Colin Perkins, Pete Sholander, Magnus Westerlund, and Joerg Widmer NEW: Eggert, Gorry Fairhurst, Mark Handley, Miguel Garcia, Ladan Gharai, Richard Nelson, Colin Perkins, Juergen Quittek, Pete Sholander, Magnus Westerlund, and Joerg Widmer New Reference: NEW: [RFC3540] D. Wetherall, D. Ely, and N. Spring, Robust ECN Signaling with Nonces, RFC 3540, Experimental, June 2003. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 16:30:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ3u-0002aY-In; Mon, 18 Dec 2006 16:30:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ3t-0002ZY-5C for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:30:17 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwQ3s-0004VR-VK for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:30:17 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id B646726E8C; Mon, 18 Dec 2006 21:30:16 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwQ3s-0000hJ-Kj; Mon, 18 Dec 2006 16:30:16 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 18 Dec 2006 16:30:16 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: Internet Architecture Board , ccamp chair , RFC Editor Subject: Protocol Action: 'Exclude Routes - Extension to RSVP-TE' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Exclude Routes - Extension to RSVP-TE ' as a Proposed Standard This document is the product of the Common Control and Measurement Plane Working Group. The IESG contact persons are Ross Callon and Bill Fenner. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-te-exclude-route-06.txt Technical Summary In some networks where precise explicit paths are not computed at the head end it may be useful to specify and signal abstract nodes and resources that are to be explicitly excluded from routes. These exclusions may apply to the whole path, or to parts of a path between two abstract nodes specified in an explicit path. How Shared Risk Link Groups (SLRGs) can be excluded is also specified in this document. This document specifies ways to communicate route exclusions during path setup using RSVP-TE. Working Group Summary no reports of any dissent Protocol Quality Ross Callon has reviewed this for the IESG, and Eric Gray has provided Gen-ART review comments. The document has been updated in response to Eric's and Ross' comments. I know of at least one implementation with some deployment, and I suspect that there is more than one implementation. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 16:36:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ5u-0003PW-TP; Mon, 18 Dec 2006 16:32:22 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ5t-0003P3-2m for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:32:21 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwQ5s-0006KD-Qn for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:32:20 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id BF9602AD07; Mon, 18 Dec 2006 21:31:50 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwQ5O-0000jj-HX; Mon, 18 Dec 2006 16:31:50 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 18 Dec 2006 16:31:50 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: tsvwg chair , Internet Architecture Board , RFC Editor Subject: Protocol Action: 'Padding Chunk and Parameter for SCTP' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Padding Chunk and Parameter for SCTP ' as a Proposed Standard This document is the product of the Transport Area Working Group Working Group. The IESG contact persons are Lars Eggert and Magnus Westerlund. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-sctp-padding-02.txt Technical Summary This document defines a padding chunk and a padding parameter and describes the required receiver side procedures. The main purpose of the padding chunk and parameter are for path-MTU discovery. Working Group Summary There is strong consensus in the WG to publish this document. It has been reviewed by several people in the WG last call. Protocol Quality James Polk was the PROTO Document Shepherd for this document. Lars Eggert reviewed this document for the iESG. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 16:36:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ3u-0002aY-Nn; Mon, 18 Dec 2006 16:30:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ3t-0002ZY-5C for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:30:17 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwQ3s-0004VR-VK for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:30:17 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id B646726E8C; Mon, 18 Dec 2006 21:30:16 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwQ3s-0000hJ-Kj; Mon, 18 Dec 2006 16:30:16 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 18 Dec 2006 16:30:16 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: Internet Architecture Board , ccamp chair , RFC Editor Subject: Protocol Action: 'Exclude Routes - Extension to RSVP-TE' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'Exclude Routes - Extension to RSVP-TE ' as a Proposed Standard This document is the product of the Common Control and Measurement Plane Working Group. The IESG contact persons are Ross Callon and Bill Fenner. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ccamp-rsvp-te-exclude-route-06.txt Technical Summary In some networks where precise explicit paths are not computed at the head end it may be useful to specify and signal abstract nodes and resources that are to be explicitly excluded from routes. These exclusions may apply to the whole path, or to parts of a path between two abstract nodes specified in an explicit path. How Shared Risk Link Groups (SLRGs) can be excluded is also specified in this document. This document specifies ways to communicate route exclusions during path setup using RSVP-TE. Working Group Summary no reports of any dissent Protocol Quality Ross Callon has reviewed this for the IESG, and Eric Gray has provided Gen-ART review comments. The document has been updated in response to Eric's and Ross' comments. I know of at least one implementation with some deployment, and I suspect that there is more than one implementation. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 16:36:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ7E-0004XY-JP; Mon, 18 Dec 2006 16:33:44 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQ7C-0004VH-Ly for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:33:42 -0500 Received: from chsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.24.129] helo=ns0.neustar.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwQ7C-0006Xs-AS for ietf-announce@ietf.org; Mon, 18 Dec 2006 16:33:42 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 353683295E; Mon, 18 Dec 2006 21:33:42 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwQ7C-0000lv-3d; Mon, 18 Dec 2006 16:33:42 -0500 X-test-idtracker: no From: The IESG To: IETF-Announce Message-Id: Date: Mon, 18 Dec 2006 16:33:42 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a Cc: rohc chair , Internet Architecture Board , RFC Editor Subject: Protocol Action: 'The RObust Header Compression (ROHC) Framework' to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has approved the following document: - 'The RObust Header Compression (ROHC) Framework ' as a Proposed Standard This document is the product of the Robust Header Compression 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-rohc-rfc3095bis-framework-04.txt Technical Summary RFC 3095 defines the ROHC framework along with an initial set of compression profiles. When RFC 3095 was written, separating the framework specification from the profiles was never considered, but the lack of a clear and referential separation has become an inconvenience when defining additional or updated profiles. To improve and simplify the specifications, the framework and the profiles parts have now been split into separate documents, where this document explicitly defines the ROHC framework, and thus replaces the framework specification of RFC 3095. The ROHC Framework, as defined by this document, is technically identical to the framework defined by RFC 3095, and there are therefore no compatibility concerns with these two specifications. Working Group Summary This document has been based on the technical framework parts of RFC 3095, but significantly restructured and improved, based on the experiences previously documented in the RFC 3095 corrections and clarifications document. The final document has been thoroughly reviewed by the WG, and there is WG consensus that the document should now be published to form a new referential base for upcoming ROHC profiles. Protocol Quality Magnus Westerlund reviewed the document for the IESG. The document was also reviewed by the committed WG document reviewers, Carl Knutsson and Biplab Sarkar, appointed by the ROHC WG chair. Note to RFC Editor OLD Abstract: The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095. To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework separately, and thus replaces the framework specification of RFC 3095. NEW Abstract: The ROHC framework, along with a set of compression profiles, was initially defined in RFC 3095. To improve and simplify the ROHC specifications, this document explicitly defines the ROHC framework and the profile for uncompressed separately. More specifically, the definition of the framework does not modify or update the definition of the framework specified by RFC3095. OLD Intro: RFC 3095 [3] defines the ROHC framework along with an initial set of compression profiles. To improve and simplify the specification, the framework and the profiles parts have been split into separate documents. This document explicitly defines the ROHC framework, and thus replaces the framework specification of RFC 3095. NEW Intro: RFC 3095 [3] defines the ROHC framework along with an initial set of compression profiles. To improve and simplify the specification, the framework and the profiles parts have been split into separate documents. This document explicitly defines the ROHC framework, but it does not modify or update the definition of the framework specified by RFC3095; both documents can be used independently of each other. This also implies that implementations based on either definition will be compatible and interoperable with each other. However it is the intent to let this specification replace RFC 3095 as the base specification for all profiles defined in the future. Section 3. OLD: 3. Background (Informative) NEW: 3. Background Section OLD: Section 8, paragraph 3: Profile Identifier Usage Reference ------------------ ---------------------- --------- 0x0000 ROHC uncompressed RFC 3095 NEW: Section 8, paragraph 3: Profile Identifier Usage Reference ------------------ ---------------------- --------- 0x0000 ROHC uncompressed RFC YYYY Where YYYY is this document. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 17:16:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQmq-00027o-9I; Mon, 18 Dec 2006 17:16:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQmo-00027c-Fd for ietf-announce@ietf.org; Mon, 18 Dec 2006 17:16:42 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwQmo-0003vq-9v for ietf-announce@ietf.org; Mon, 18 Dec 2006 17:16:42 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 4557532956 for ; Mon, 18 Dec 2006 22:16:42 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwQmo-0005Bk-5W for ietf-announce@ietf.org; Mon, 18 Dec 2006 17:16:42 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 18 Dec 2006 17:16:42 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: Last Call: 'Telnet START-TLS Option' to Proposed Standard (draft-altman-telnet-starttls) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following documents: - 'Telnet Authentication Option' as a Proposed Standard - 'Telnet START-TLS Option' as a Proposed Standard - 'Telnet Authentication: Kerberos Version 5' as a Proposed Standard - 'Telnet Authentication: SRP' 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 2007-01-15. The file can be obtained via http://www.ietf.org/internet-drafts/draft-altman-telnet-rfc2941bis-02.txt http://www.ietf.org/internet-drafts/draft-altman-telnet-starttls-02.txt http://www.ietf.org/internet-drafts/draft-altman-telnet-rfc2942bis-02.txt http://www.ietf.org/internet-drafts/draft-altman-telnet-rfc2944bis-02.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 20:33:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTrU-0007yo-Sf; Mon, 18 Dec 2006 20:33:44 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTrT-0007yV-4x; Mon, 18 Dec 2006 20:33:43 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwTrR-0003ee-Di; Mon, 18 Dec 2006 20:33:43 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBJ1XeiB022538; Mon, 18 Dec 2006 17:33:40 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBJ1XeJm022537; Mon, 18 Dec 2006 17:33:40 -0800 Date: Mon, 18 Dec 2006 17:33:40 -0800 Message-Id: <200612190133.kBJ1XeJm022537@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: avt@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4734 on Definition of Events for Modem, Fax, and Text Telephony Signals X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4734 Title: Definition of Events for Modem, Fax, and Text Telephony Signals Author: H. Schulzrinne, T. Taylor Status: Standards Track Date: December 2006 Mailbox: schulzrinne@cs.columbia.edu, taylor@nortel.com Pages: 47 Characters: 116810 I-D Tag: draft-ietf-avt-rfc2833bisdata-08.txt URL: http://www.rfc-editor.org/rfc/rfc4734.txt This memo updates RFC 4733 to add event codes for modem, fax, and text telephony signals when carried in the telephony event RTP payload. It supersedes the assignment of event codes for this purpose in RFC 2833, and therefore obsoletes that part of RFC 2833. [STANDARDS TRACK] This document is a product of the Audio/Video Transport 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 20:33:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTrJ-0007td-QY; Mon, 18 Dec 2006 20:33:33 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTrI-0007tU-Kq; Mon, 18 Dec 2006 20:33:32 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwTrH-0003Zh-8F; Mon, 18 Dec 2006 20:33:32 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBJ1XSjW022533; Mon, 18 Dec 2006 17:33:28 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBJ1XSDj022532; Mon, 18 Dec 2006 17:33:28 -0800 Date: Mon, 18 Dec 2006 17:33:28 -0800 Message-Id: <200612190133.kBJ1XSDj022532@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: avt@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4733 on RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4733 Title: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals Author: H. Schulzrinne, T. Taylor Status: Standards Track Date: December 2006 Mailbox: schulzrinne@cs.columbia.edu, taylor@nortel.com Pages: 49 Characters: 115614 Obsoletes: RFC2833 See-Also: I-D Tag: draft-ietf-avt-rfc2833bis-15.txt URL: http://www.rfc-editor.org/rfc/rfc4733.txt This memo describes how to carry dual-tone multifrequency (DTMF) signalling, other tone signals, and telephony events in RTP packets. It obsoletes RFC 2833. This memo captures and expands upon the basic framework defined in RFC 2833, but retains only the most basic event codes. It sets up an IANA registry to which other event code assignments may be added. Companion documents add event codes to this registry relating to modem, fax, text telephony, and channel-associated signalling events. The remainder of the event codes defined in RFC 2833 are conditionally reserved in case other documents revive their use. This document provides a number of clarifications to the original document. However, it specifically differs from RFC 2833 by removing the requirement that all compliant implementations support the DTMF events. Instead, compliant implementations taking part in out-of-band negotiations of media stream content indicate what events they support. This memo adds three new procedures to the RFC 2833 framework: subdivision of long events into segments, reporting of multiple events in a single packet, and the concept and reporting of state events. [STANDARDS TRACK] This document is a product of the Audio/Video Transport 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 20:34:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTro-00082a-TR; Mon, 18 Dec 2006 20:34:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTro-00082T-2r for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:34:04 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwTrm-0003ht-NG for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:34:04 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBJ1Y2PJ022543; Mon, 18 Dec 2006 17:34:02 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBJ1Y1Ra022542; Mon, 18 Dec 2006 17:34:01 -0800 Date: Mon, 18 Dec 2006 17:34:01 -0800 Message-Id: <200612190134.kBJ1Y1Ra022542@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Cc: netconf@ops.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4741 on the NETCONF Configuration Protocol X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4741 Title: NETCONF Configuration Protocol Author: R. Enns, Ed. Status: Standards Track Date: December 2006 Mailbox: rpe@juniper.net Pages: 95 Characters: 173914 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netconf-prot-12.txt URL: http://www.rfc-editor.org/rfc/rfc4741.txt The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized on top of a simple Remote Procedure Call (RPC) layer. [STANDARDS TRACK] This document is a product of the Network Configuration 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 20:34:31 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTsC-0008Lx-K8; Mon, 18 Dec 2006 20:34:28 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTsA-0008Ke-TC for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:34:26 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwTs9-0003kT-HH for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:34:26 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBJ1YP6A022548; Mon, 18 Dec 2006 17:34:25 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBJ1YPXj022547; Mon, 18 Dec 2006 17:34:25 -0800 Date: Mon, 18 Dec 2006 17:34:25 -0800 Message-Id: <200612190134.kBJ1YPXj022547@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: netconf@ops.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4742 on Using the NETCONF Configuration Protocol over Secure SHell (SSH) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4742 Title: Using the NETCONF Configuration Protocol over Secure SHell (SSH) Author: M. Wasserman, T. Goddard Status: Standards Track Date: December 2006 Mailbox: margaret@thingmagic.com, ted.goddard@icesoft.com Pages: 10 Characters: 17807 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netconf-ssh-06.txt URL: http://www.rfc-editor.org/rfc/rfc4742.txt This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. [STANDARDS TRACK] This document is a product of the Network Configuration 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 20:34:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTsX-0000cH-Rc; Mon, 18 Dec 2006 20:34:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTsV-0000VW-Hj for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:34:47 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwTsU-0003nE-5g for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:34:47 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBJ1YjmV022553; Mon, 18 Dec 2006 17:34:45 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBJ1YjRq022552; Mon, 18 Dec 2006 17:34:45 -0800 Date: Mon, 18 Dec 2006 17:34:45 -0800 Message-Id: <200612190134.kBJ1YjRq022552@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Cc: netconf@ops.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4743 on Using NETCONF over the Simple Object Access Protocol (SOAP) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4743 Title: Using NETCONF over the Simple Object Access Protocol (SOAP) Author: T. Goddard Status: Standards Track Date: December 2006 Mailbox: ted.goddard@icesoft.com Pages: 20 Characters: 39734 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netconf-soap-08.txt URL: http://www.rfc-editor.org/rfc/rfc4743.txt The Network Configuration Protocol (NETCONF) is applicable to a wide range of devices in a variety of environments. Web Services is one such environment and is presently characterized by the use of the Simple Object Access Protocol (SOAP). NETCONF finds many benefits in this environment: from the reuse of existing standards, to ease of software development, to integration with deployed systems. Herein, we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible Protocol (BEEP) bindings for NETCONF. [STANDARDS TRACK] This document is a product of the Network Configuration 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Mon Dec 18 20:35:08 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTso-00015O-7M; Mon, 18 Dec 2006 20:35:06 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwTsn-00015A-H0 for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:35:05 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwTsm-0003sP-5O for ietf-announce@ietf.org; Mon, 18 Dec 2006 20:35:05 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBJ1Z3Cn022562; Mon, 18 Dec 2006 17:35:03 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBJ1Z3DC022561; Mon, 18 Dec 2006 17:35:03 -0800 Date: Mon, 18 Dec 2006 17:35:03 -0800 Message-Id: <200612190135.kBJ1Z3DC022561@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: netconf@ops.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4744 on Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4744 Title: Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) Author: E. Lear, K. Crozier Status: Standards Track Date: December 2006 Mailbox: lear@cisco.com, ken.crozier@gmail.com Pages: 10 Characters: 19287 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-netconf-beep-10.txt URL: http://www.rfc-editor.org/rfc/rfc4744.txt This document specifies an application protocol mapping for the Network Configuration Protocol (NETCONF) over the Blocks Extensible Exchange Protocol (BEEP). [STANDARDS TRACK] This document is a product of the Network Configuration 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Tue Dec 19 03:40:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwaVu-0002z8-Ry; Tue, 19 Dec 2006 03:39:54 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwaVs-0002yy-UV for ietf-announce@ietf.org; Tue, 19 Dec 2006 03:39:52 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwaVr-0002H6-Mf for ietf-announce@ietf.org; Tue, 19 Dec 2006 03:39:52 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id 705AD17604 for ; Tue, 19 Dec 2006 08:39:21 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GwaVN-0001Sz-1r for ietf-announce@ietf.org; Tue, 19 Dec 2006 03:39:21 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: IETF Chair Message-Id: Date: Tue, 19 Dec 2006 03:39:21 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: Preliminary BOF proposals due soon X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org As for the previous IETF, we're asking for preliminary BOF proposals to be sent to the appropriate Area Director a little earlier, by January 15. Even sooner would be better! Full list of dates: http://www.ietf.org/meetings/68-cutoff_dates.html BOF wiki: http://www1.tools.ietf.org/bof/trac/wiki Hints: http://tools.ietf.org/html/draft-narten-successful-bof Brian Carpenter _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Tue Dec 19 09:53:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwgLe-0007Tr-NF; Tue, 19 Dec 2006 09:53:42 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwgLd-0007R8-2F; Tue, 19 Dec 2006 09:53:41 -0500 Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwgLa-0000Av-SO; Tue, 19 Dec 2006 09:53:41 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id D0C5B32992; Tue, 19 Dec 2006 14:53:38 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GwgLa-00074j-O2; Tue, 19 Dec 2006 09:53:38 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Tue, 19 Dec 2006 09:53:38 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: dhcwg@ietf.org Subject: Last Call: 'DHCP options for PANA Authentication Agents' to Proposed Standard (draft-ietf-dhc-paa-option) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from the Dynamic Host Configuration WG to consider the following document: - 'DHCP options for PANA Authentication Agents ' 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 2007-01-07. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-dhc-paa-option-05.txt _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Tue Dec 19 10:31:08 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwgrs-000094-EH; Tue, 19 Dec 2006 10:27:00 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwgrq-00008v-Jb; Tue, 19 Dec 2006 10:26:58 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gwgrq-00015K-Aw; Tue, 19 Dec 2006 10:26:58 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns4.neustar.com (Postfix) with ESMTP id 485B92ACC6; Tue, 19 Dec 2006 15:26:28 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GwgrM-0004Mu-23; Tue, 19 Dec 2006 10:26:28 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list From: IETF Secretariat Message-Id: Date: Tue, 19 Dec 2006 10:26:28 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: irsg@isi.edu, wgchairs@ietf.org Subject: 68th IETF Registration X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org 68th IETF Meeting Prague, Czech Republic March 18-23, 2007 Registration is now open! Registration for the 68th IETF Meeting is at: http://www.ietf.org/meetings/68-IETF.html Registration Information: Early-Bird Registration - USD 600.00 If you register and pay for your attendance to the IETF-68 before NOON ET (17:00 UTC/GMT), Friday, 9 March 2007, then the price for registration is USD 600.00. After Early-Bird cutoff - USD 750.00 You can still register and pay online at USD 750.00 until 17:00 ET (21:00 UTC/GMT), Saturday, 17 March 2007. Full-time Student Registrations - USD 150.00 Full-time students with proper ID are eligible to receive a special USD 150.00 student rate. Student rate is no longer subject to any late-fees. Students will also be able to register on-site at the special student rate. Failure to provide valid student ID on-site will revoke the special student status. Cancellation The cut-off for registration cancellation is Monday, March 12 at 17:00 ET-US (21:00 UTC/GMT). Cancellations are subject to a 10% cancellation fee if requested by that date and time. Onsite Registration You can register onsite at the meeting in Prague, Czech Republic starting Sunday, March 18 at 12:00 noon (local time). The IETF meetings start Monday morning and run through Friday lunchtime, with late scheduling changes. Most training session take place on Sunday afternoon March 18th. Participants should plan their travel accordingly. The IETF Secretariat _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Tue Dec 19 21:24:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwquY-0002pq-9m; Tue, 19 Dec 2006 21:10:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwquW-0002pe-DY; Tue, 19 Dec 2006 21:10:24 -0500 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwquV-00036L-1F; Tue, 19 Dec 2006 21:10:24 -0500 Received: from adma.isi.edu (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id kBK2A62f014370; Tue, 19 Dec 2006 18:10:06 -0800 (PST) Received: (from rfc-ed@localhost) by adma.isi.edu (8.8.7/8.8.6) id CAA17595; Wed, 20 Dec 2006 02:10:06 GMT Date: Tue, 19 Dec 2006 18:10:05 -0800 From: RFC Editor To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Message-ID: <20061220021005.GD17275@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Score: -15.0 (---------------) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: iab@ietf.org, IESG , RFC Editor Subject: RFC Editor Holiday Schedule X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org Greetings All, The RFC Editor will be closed Monday, December 25 - January 1, 2007. We will be back in the office on Tuesday, January 2, 2007. Please note that memebers of the RFC Editor staff will check the RFC Editor mailbox periodically during this time, and we will respond to urgent and time-sensitive matters. Thank you, and happy holidays. RFC Editor _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 20 08:32:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx1Yd-0001bE-5j; Wed, 20 Dec 2006 08:32:31 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx1Yb-0001az-1p for ietf-announce@ietf.org; Wed, 20 Dec 2006 08:32:29 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gx1YX-00067m-Q8 for ietf-announce@ietf.org; Wed, 20 Dec 2006 08:32:28 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id 843B017622 for ; Wed, 20 Dec 2006 13:31:55 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1Gx1Y3-0006C9-4e for ietf-announce@ietf.org; Wed, 20 Dec 2006 08:31:55 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: Brian Carpenter Message-Id: Date: Wed, 20 Dec 2006 08:31:55 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Subject: Looking for another IESG scribe X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG's informal narrative minutes can be found at http://www.ietf.org/IESG/iesg-narrative.html These minutes rely on volunteer scribes, who join the IESG teleconferences to take notes. We would like to appoint a third scribe, to reduce the load on Spencer Dawkins and Marshall Eubanks. If you think you have the necessary skills, and a few hours per month available, please write to me at brc@zurich.ibm.com by January 12th. Brian Carpenter, for the IESG _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 20 13:34:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx66y-0002wj-Br; Wed, 20 Dec 2006 13:24:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx5Iy-0000LS-UH for ietf-announce@ietf.org; Wed, 20 Dec 2006 12:32:36 -0500 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx5Iu-0008HE-IL for ietf-announce@ietf.org; Wed, 20 Dec 2006 12:32:36 -0500 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kBKHWQSq021507 for ; Wed, 20 Dec 2006 12:32:27 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Received: from 300815erh2.post.avaya.com ([198.152.6.49]) by IS0004AVEXU1.global.avaya.com with Microsoft SMTPSVC(5.0.2195.6713); Mon, 18 Dec 2006 20:21:26 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Received: from co300216-ier2.net.avaya.com (co300216-ier2.net.avaya.com [198.152.13.103]) by 300815erh2.post.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kBIILPQF006458 for ; Mon, 18 Dec 2006 13:21:25 -0500 Received: from co300216-co-ierwest.avaya.com (h198-152-13-104.avaya.com [198.152.13.104]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kBIIGXTR006451 for ; Mon, 18 Dec 2006 13:21:24 -0500 Received: from odin.ietf.org (HELO megatron.ietf.org) ([156.154.16.145]) by co300216-co-ierwest.avaya.com with ESMTP; 18 Dec 2006 13:19:38 -0500 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwN3N-0007pN-7R; Mon, 18 Dec 2006 13:17:33 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GwN3L-0007nH-Aj for ietf@ietf.org; Mon, 18 Dec 2006 13:17:31 -0500 Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwN3J-00052B-UX for ietf@ietf.org; Mon, 18 Dec 2006 13:17:31 -0500 Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kBIIHO4k007072 for ; Mon, 18 Dec 2006 13:17:24 -0500 content-class: urn:content-classes:message Date: Wed, 20 Dec 2006 19:32:24 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: CAPWAP Interim Meeting, January 24th & 25th Thread-Index: Acci0MM4EzLKFWGaR/S8/2JdsCVTvg== From: "Romascanu, Dan \(Dan\)" To: X-Scanner: InterScan AntiVirus for Sendmail X-Spam-Score: 0.1 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 X-Mailman-Approved-At: Wed, 20 Dec 2006 13:24:13 -0500 Subject: CAPWAP Interim Meeting, January 24th & 25th X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The CAPWAP WG will hold a two-day interim meeting. Here are the details: CAPWAP WG Interim Meeting Wednesday & Thursday, January 24 & 25, 2007 9:00am - 5:00pm (PDT) 3750 Cisco Way (Building 15) San Jose, CA, USA More information about the CAPWAP WG can be found on our charter page: http://www.ietf.org/html.charters/capwap-charter.html More information about the CAPWAP interim meeting, including registration information and a full agenda, will be circulated on the CAPWAP WG mailing list. If you wish to join the CAPWAP mailing list, go to: http://lists.frascone.com/mailman/listinfo/capwap _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 20 15:50:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx8O4-0003pG-EX; Wed, 20 Dec 2006 15:50:04 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx8O2-0003p3-UZ; Wed, 20 Dec 2006 15:50:02 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx8O1-0001jG-SO; Wed, 20 Dec 2006 15:50:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id B50FB26EBE; Wed, 20 Dec 2006 20:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gx8O1-0002ZR-JM; Wed, 20 Dec 2006 15:50:01 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: ietf-announce@ietf.org From: IESG Secretary Message-Id: Date: Wed, 20 Dec 2006 15:50:01 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2 Cc: Pete McCann , mip4@ietf.org, Henrik Levkowetz Subject: WG Action: RECHARTER: Mobility for IPv4 (mip4) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The Mobility for IPv4 (mip4) working group in the Internet Area of the IETF has been rechartered. For additional information, please contact the Area Directors or the working group Chairs. +++ Mobility for IPv4 (mip4) ------------------------ Current Status: Active Working Group Chair(s): Henrik Levkowetz Pete McCann Internet Area Director(s): Jari Arkko Mark Townsley Internet Area Advisor: Jari Arkko Mailing Lists: General Discussion:mip4@ietf.org To Subscribe: mip4-request@ietf.org In Body: subscribe Archive: http://www.ietf.org/mail-archive/web/mip4/index.html Description of Working Group: IP mobility support for IPv4 nodes (hosts and routers) is specified in RFC3344. RFC 3344 mobility allows a node to continue using its "permanent" home address as it moves around the Internet. The Mobile IP protocols support transparency above the IP layer, including maintenance of active TCP connections and UDP port bindings. Besides the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal with concerns such as optimization, security, extensions, AAA support, and deployment issues. MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000 networks). The scope of the deployment is on a fairly large scale and accordingly, the MIP4 WG will focus on deployment issues and on addressing known deficiencies and shortcomings in the protocol that have come up as a result of deployment experience. Specifically, the working group will complete the work items to facilitate interactions with AAA environments, interactions with enterprise environments when MIPv4 is used therein, and updating existing protocol specifications in accordance with deployment needs and advancing those protocols that are on the standards track. Work expected to be done by the MIP4 WG as proposed by this charter is as follows: 1. MIPv4 has been a proposed standard for several years. It has been adopted by other standard development organizations and has been deployed commercially. One of the next steps for the WG is to advance the protocol to draft standard status. As part of advancing base Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to reflect implementation experience. 2. Work items that are pending from the previous Mobile IP WG, which will be completed by the MIP4 WG, are: - completion of the MIB for the revised base Mobile IP specification (2006bis) - regional registration draft. 3. The MIP4 WG will also complete the work on MIPv4 interactions in VPN scenarios. This work will involve identifying the requirements and a solution development for MIPv4 operation in the presence of IPsec VPNs. 4. Additionally, a proposal has been made for how MOBIKE could work together with MIPv4. This proposal does not describe any new protocol, but formulates a best current practice for deploying MOBIKE together with MIPv4. The working group will adopt and complete this document. 5. Some issues have been raised with respect to RFC3519. These will be identified and addressed as appropriate, through errata, revision of RFC 3519, and/or supplemental documents as needed. 6. It has been proposed that the FMIP protocol, which has been standardised for MIPv6 in the MIPSHOP working group, should also be published as an experimental protocol for MIPv4. A draft for this exists. The working group will take up and carry this work forward to publication 7. An extension to carry generic strings in the Registration Reply message has been proposed. The purpose is to supply supplemental human-readable information intended to the MN user. The working group will complete the specification and applicability statement of such an extension. 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been proposed for MIPv4. The working group will first produce a requirements specification, describing how the work differs from the requirements in RFC 2977 and the functionality provided by RFC 4004 (the MIPv4 Diameter App). The reason why this first step is required is that RFC 3127 shows that full RFC 2977 functionality can't be provided by even a considerably extended RADIUS, so we need to match the requirements to what can be done within RADIUS. Provided the requirements work finds approval with ADs and RADEXT WG, the workgroup will complete the specification of MIPv4 RADIUS attributes, solicit feedback from the RADEXT WG, adjust, and submit this for publication. Note that the work may require extensions to the RADIUS attribute space which will be handled outside the MIP4 WG. 9. MIPv4 Extension for Configuration Options. Several drafts have proposed extensions to help improve configuration of MIPv4 clients. The latest proposal is for a general configuration option extension which could carry information such as e.g., DNS address and DHCP server address. The working group will take on and complete one proposal for a configuration option extension. 10. Dual-stack Support There have been several proposals for how to enable an IPv6 connection over a network that supports Mobile IPv4. A protocol enhancement to MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has already been implemented and deployed. This would allow a dual stack mobile node to maintain IPv6 connectivity when using MIPv4. The solution would therefore be applicable only to networks that are not deploying Mobile IPv6. The working group will take on and complete one proposal for IPv6 over Mobile IPv4. This work is restricted to a small protocol extension similar to current Mobile IPv4 functionality. Support for advanced Mobile IPv6 functionality is strictly outside the scope. A problem statement covering both Mobile IPv4 and IPv6 dual-stack issues is expected to come out of MIP6 WG, and will not be developed in MIP4 WG. 11. MIPv4 Moving Network Support The Network Mobility (nemo) working group deals with the problem of mobility of a whole network, such as might exist inside a vehicle, train, or airplane. The nemo working group has developed draft specifications for both IPv6 and IPv4 mobile networks. However, it has been recognized that the IPv4 version of the protocol can be viewed as an extension of the basic Mobile IPv4 protocol, and there is good reason to do this extension in the mip4 working group. The working group will take on the MIPv4 network mobility internet draft and progress it along the standards track. In addition, the working group will take up extensions to the basic MIPv4 moving network support in the areas of dynamic prefix assignment and foreign agent support. 12. Asynchronous Notification Mechanism In some situations, there is a need for Mobile IPv4 entities, such as the home agent, foreign agent and mobile node to send and receive asynchronous notification events related to the operation of the MIPv4 protocol. A couple of examples of such events are registration revocation from a home agent to a foreign agent in order to terminate the service (to release resources and end charging), and notification of pending HA shutdown and indication of alternative serving HA, from a HA to the mobile node. The base Mobile IP Specification [RFC3344] does not have a provision for this. A new MIPv4 message pair which would support asynchronous notifications, and a notification model describing how to use these messages has been proposed. The working group will take on the existing MIPv4 notification message draft as a starting point, review and update it as needed, and progress it as a standards track document. In addition, the working group will also consider defining specific usages of the notification message based on the examples in the current document. Goals and Milestones: Done AAA Keys for MIPv4 to IESG Done MIPv4 VPN interaction problem statement to IESG Done Low latency handover to experimental Done Experimental MIPv4 message and extensions draft to IESG Done Dynamic Home Agent assignment protocol solution to IESG Done Revised MIPv4 Challenge/Response (3012bis) to IESG Done Regional registration document to IESG Jan 2007 MIPv4 Mobike interaction (BCP) to the IESG Feb 2007 MIPv4 Extension for Config. Options (Proposed Std.) to the IESG Dec 2006 MIPv4 VPN interaction (BCP) to the IESG May 2007 RADIUS Extensions for MIPv4 to the RADEXT WG for comment Jan 2007 Revised MIPv4 specification to IESG for Draft Std. Dec 2006 Generic Strings for MIPv4 (Proposed Std.) to the IESG Mar 2007 MIPv4 RADIUS Extensions Requirements to the IESG Dec 2006 FMIPv4 (Experimental) to the IESG Sep 2007 RADIUS Extensions for MIPv4 (Proposed Std.) to the IESG Nov 2007 Revised rfc2794bis (NAI extension) (Draft Std.) to the IESG Aug 2007 Revised MIB for MIPv4 (Proposed Std.) to IESG Apr 2007 Dual-stack MIPv4 (Draft Std.) to IESG Jul 2007 Notification Mechanism (Draft Std.) to IESG Sep 2007 Base MIPv4 Mobile Network Support (Draft Std.) to IESG Nov 2007 MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG Nov 2007 MIPv4 Mobile Network Support Dynamic Address Assignment (Draft Std.) to IESG _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 20 20:58:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxDCf-0003qh-Ql; Wed, 20 Dec 2006 20:58:37 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxDCe-0003pZ-GN; Wed, 20 Dec 2006 20:58:36 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GxDCe-0007Cl-5Y; Wed, 20 Dec 2006 20:58:36 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id D88A617618; Thu, 21 Dec 2006 01:58:05 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GxDC9-00052R-FQ; Wed, 20 Dec 2006 20:58:05 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list From: Leslie Daigle Message-Id: Date: Wed, 20 Dec 2006 20:58:05 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Cc: iab@ietf.org, iesg@ietf.org, ram@iab.org Subject: Routing & Addressing -- activities X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The recent IAB workshop (see draft-iab-raws-report-00) established that a significant fraction of the Internet operations community and their equipment vendors believe that we face a scaling problem for routing in the core of the Internet, on a worrying timescale. They further believe that timely action is needed. Enough evidence was available to the workshop to convince the IAB and IESG members present that the problem is real, even if the timescale and details are debatable, and that the solution will lie in certain specific areas mentioned below. It is also evident that the Internet community has everything to gain if efforts in the IETF and IRTF are closely coordinated with those in the operations and vendor communities, and much to lose otherwise. While these problems are pressing, we believe there is time for a coordinated approach. Therefore, the IAB & IESG have worked together to identify key paths for progress in discussing and resolving this problem, and have agreed to establish an advisory group for coordinating information flow and awareness of activities (more on this group, below). We note that although this topic is of primary concern to backbone network operators and their equipment makers, many other parts of the community have an interest. These include other ISPs, enterprise network operators, mobile operators, server and host software makers, and standards development organizations other than the IETF. KEY PATHS FOR PROGRESS Regarding possible solutions, the current understanding of the cause of the scaling problem is that it is driven not by growth of the size of the Internet as such, but by growth in the demand for routing of individual address prefixes that cannot be aggregated into coarser routes. This implies that the solution will lie in the direction of separating the usage of address prefixes to identify sites from their usage for wide-area routing. There is a variety of ways that such a separation could be achieved. Following various discussions at IETF67, we set out below the main lines of action that we propose, followed by a suggested arrangement to drive these actions forward in parallel. (1) Complete the problem statement, addressing the issues raised in the IAB workshop and others as applicable. (2) Determine applicable objective metrics and identify applicable trend analyses for them. (3) Document the underlying causes of perceived scaling problems. (4) Review proposed solution directions in terms of expected impact in addressing scaling issues as well as architectural soundness. (5) Encourage and nurture short term solution proposals, prototypes and appropriate standards activity. (6) Encourage and nurture relevant research activities directed towards long term solutions. INTEGRATION WITH EXISTING IETF FUNCTIONS The IAB and IESG intend to take their full part in these actions, but specifically as part of a broad community effort. The IAB would expect to focus on actions to promote (1), (2), (3) and (4), and expects the IRTF to work with other research entities on (6). The IAB in particular publishes informational documents, convenes workshops, and supports IRTF work as necessary and possible. The IESG will play its normal role in chartering BoFs and WGs and reviewing WG and individual submission (IETF stream) documents as appropriate and in particular for (5). To be as inclusive as possible, while sustaining the effort over a number of years, the IAB and IESG propose a tiered approach to project coordination: (A) We assume that detailed work will be carried out by ad hoc or chartered teams, and there is no grand plan for structuring these teams. As always in the development of the Internet, we expect analysis and solutions to come from the community at large. (B) IAB workshops, BOFs, IETF WGs and IRTF RGs can be organized in the normal way, as issues and proposals arise in the community. (C) General discussion is already proceeding on the ram@iab.org list. More specialized lists can be created as needed. COORDINATION The IETF and IAB Chairs will appoint a Directorate, including roughly ten people with different experience and expertise, to stay abreast of activities, provide coordinated updates, as well as input to the IESG and IAB about progress against the noted actions above. We use the name "Directorate" simply because it is a recognized term in the IETF; we expect it to focus on communication and coordination. It will not be charged with picking solutions or choosing a technical direction. That will be a community decision. This Directorate is expected to have a lifetime of about 5 years (with an annual review of membership). The Directorate will be organized and reviewed periodically to ensure it is running smoothly and reporting on overall progress. Specific objectives of the Directorate will be: (i) On a continuing basis, survey existing efforts on the lines of action listed above, and facilitate discussion of effectiveness and timeliness of proposals and problem statements, etc. (ii) Report to the IAB, IESG and the community regularly (at least once per IETF meeting) about those efforts, and highlight specific gaps or concerns about progress. (iii) Provide feedback to IESG, IAB and IRSG on any relevant proposed activities in the area (e.g., WG or RG charters, BOF or workshop proposals, etc). The Directorate will be charged with encouraging appropriate communication with all the identified constituencies. Leslie & Brian, for the IAB & IESG. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 02:52:11 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxIiW-0005fX-O2; Thu, 21 Dec 2006 02:51:52 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxIiT-0005e7-Ve; Thu, 21 Dec 2006 02:51:50 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GxIiS-0003UR-N1; Thu, 21 Dec 2006 02:51:49 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns4.neustar.com (Postfix) with ESMTP id A1D522ACA5; Thu, 21 Dec 2006 07:51:18 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GxIhy-00071x-E0; Thu, 21 Dec 2006 02:51:18 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: Brian Carpenter Message-Id: Date: Thu, 21 Dec 2006 02:51:18 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Subject: Re: Routing & Addressing -- activities (BOF) X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ram@iab.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org As part of the routing and addressing activities, a BOF is planned during IETF 68, as a plenary activity (day and time to be announced later). This will be tracked in the BOF wiki at http://www1.tools.ietf.org/bof/trac/wiki Details so far: * ROAP o ROuting and Addressing Problem BOF o Joint with Internet Area; will be a plenary session o Status: preliminary discussions o Background: RAWS report o Responsible ADs: Ross Callon, Mark Townsley Ross and Mark will be collecting proposals for the goals and content of the BOF. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjp-0003hv-DO; Thu, 21 Dec 2006 18:54:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjn-0003hi-Su; Thu, 21 Dec 2006 18:54:11 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXjm-0002Ey-Fa; Thu, 21 Dec 2006 18:54:11 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNs789002526; Thu, 21 Dec 2006 15:54:07 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNs7d6002525; Thu, 21 Dec 2006 15:54:07 -0800 Date: Thu, 21 Dec 2006 15:54:07 -0800 Message-Id: <200612212354.kBLNs7d6002525@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Cc: ipoverib@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4755 on IP over InfiniBand: Connected Mode X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4755 Title: IP over InfiniBand: Connected Mode Author: V. Kashyap Status: Standards Track Date: December 2006 Mailbox: vivk@us.ibm.com Pages: 13 Characters: 26314 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipoib-connected-mode-03.txt URL: http://www.rfc-editor.org/rfc/rfc4755.txt This document specifies transmission of IPv4/IPv6 packets and address resolution over the connected modes of InfiniBand. [STANDARDS TRACK] This document is a product of the IP over InfiniBand 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjp-0003hv-DO; Thu, 21 Dec 2006 18:54:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjn-0003hi-Su; Thu, 21 Dec 2006 18:54:11 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXjm-0002Ey-Fa; Thu, 21 Dec 2006 18:54:11 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNs789002526; Thu, 21 Dec 2006 15:54:07 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNs7d6002525; Thu, 21 Dec 2006 15:54:07 -0800 Date: Thu, 21 Dec 2006 15:54:07 -0800 Message-Id: <200612212354.kBLNs7d6002525@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Cc: ipoverib@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4755 on IP over InfiniBand: Connected Mode X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4755 Title: IP over InfiniBand: Connected Mode Author: V. Kashyap Status: Standards Track Date: December 2006 Mailbox: vivk@us.ibm.com Pages: 13 Characters: 26314 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipoib-connected-mode-03.txt URL: http://www.rfc-editor.org/rfc/rfc4755.txt This document specifies transmission of IPv4/IPv6 packets and address resolution over the connected modes of InfiniBand. [STANDARDS TRACK] This document is a product of the IP over InfiniBand 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXk2-0003oj-0u; Thu, 21 Dec 2006 18:54:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXk0-0003mj-Kr; Thu, 21 Dec 2006 18:54:24 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXjz-0002G0-8f; Thu, 21 Dec 2006 18:54:24 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNsMY9002541; Thu, 21 Dec 2006 15:54:22 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNsM0b002540; Thu, 21 Dec 2006 15:54:22 -0800 Date: Thu, 21 Dec 2006 15:54:22 -0800 Message-Id: <200612212354.kBLNsM0b002540@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4717 on Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4717 Title: Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks Author: L. Martini, J. Jayakumar, M. Bocci, N. El-Aawar, J. Brayley, G. Koleyni Status: Standards Track Date: December 2006 Mailbox: lmartini@cisco.com, jjayakum@cisco.com, matthew.bocci@alcatel.co.uk, nna@level3.net, jeremy.brayley@ecitele.com, ghassem@nortelnetworks.com Pages: 40 Characters: 86173 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-atm-encap-11.txt URL: http://www.rfc-editor.org/rfc/rfc4717.txt An Asynchronous Transfer Mode (ATM) Pseudowire (PW) is used to carry ATM cells over an MPLS network. This enables service providers to offer "emulated" ATM services over existing MPLS networks. This document specifies methods for the encapsulation of ATM cells within a pseudowire. It also specifies the procedures for using a PW to provide an ATM service. [STANDARDS TRACK] This document is a product of the Pseudo Wire Emulation Edge to Edge 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 eith.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXk2-0003oj-0u; Thu, 21 Dec 2006 18:54:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXk0-0003mj-Kr; Thu, 21 Dec 2006 18:54:24 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXjz-0002G0-8f; Thu, 21 Dec 2006 18:54:24 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNsMY9002541; Thu, 21 Dec 2006 15:54:22 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNsM0b002540; Thu, 21 Dec 2006 15:54:22 -0800 Date: Thu, 21 Dec 2006 15:54:22 -0800 Message-Id: <200612212354.kBLNsM0b002540@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Cc: pwe3@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4717 on Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4717 Title: Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks Author: L. Martini, J. Jayakumar, M. Bocci, N. El-Aawar, J. Brayley, G. Koleyni Status: Standards Track Date: December 2006 Mailbox: lmartini@cisco.com, jjayakum@cisco.com, matthew.bocci@alcatel.co.uk, nna@level3.net, jeremy.brayley@ecitele.com, ghassem@nortelnetworks.com Pages: 40 Characters: 86173 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pwe3-atm-encap-11.txt URL: http://www.rfc-editor.org/rfc/rfc4717.txt An Asynchronous Transfer Mode (ATM) Pseudowire (PW) is used to carry ATM cells over an MPLS network. This enables service providers to offer "emulated" ATM services over existing MPLS networks. This document specifies methods for the encapsulation of ATM cells within a pseudowire. It also specifies the procedures for using a PW to provide an ATM service. [STANDARDS TRACK] This document is a product of the Pseudo Wire Emulation Edge to Edge 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce er 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjy-0003la-Cl; Thu, 21 Dec 2006 18:54:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjw-0003kU-R1 for ietf-announce@ietf.org; Thu, 21 Dec 2006 18:54:20 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXju-0002Fl-E9 for ietf-announce@ietf.org; Thu, 21 Dec 2006 18:54:20 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNsHCx002536; Thu, 21 Dec 2006 15:54:17 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNsHhv002535; Thu, 21 Dec 2006 15:54:17 -0800 Date: Thu, 21 Dec 2006 15:54:17 -0800 Message-Id: <200612212354.kBLNsHhv002535@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: rfc-editor@rfc-editor.org Subject: RFC 4723 on Registration of Media Type audio/mobile-xmf X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4723 Title: Registration of Media Type audio/mobile-xmf Author: T. Kosonen, T. White Status: Informational Date: December 2006 Mailbox: timo.kosonen@nokia.com, twhite@midi.org Pages: 8 Characters: 12652 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-kosonen-mobile-xmf-mediatype-01.txt URL: http://www.rfc-editor.org/rfc/rfc4723.txt The MIDI Manufacturers Association (MMA) and the Association of Musical Electronics Industry (AMEI) have produced the Mobile XMF standard, which was developed particularly for mobile MIDI applications. Mobile XMF is a very compact media type providing high-quality synthetic audio content for music downloading and messaging applications that require MIME registration. This document registers the media type audio/mobile-xmf. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXju-0003jx-Ql; Thu, 21 Dec 2006 18:54:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjs-0003is-5m; Thu, 21 Dec 2006 18:54:16 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXjq-0002FN-0g; Thu, 21 Dec 2006 18:54:16 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNsDg7002531; Thu, 21 Dec 2006 15:54:13 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNsDWe002530; Thu, 21 Dec 2006 15:54:13 -0800 Date: Thu, 21 Dec 2006 15:54:13 -0800 Message-Id: <200612212354.kBLNsDWe002530@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: kitten@lists.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4768 on Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4768 Title: Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming Author: S. Hartman Status: Informational Date: December 2006 Mailbox: hartmans-ietf@mit.edu Pages: 12 Characters: 27205 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-kitten-gss-naming-05.txt URL: http://www.rfc-editor.org/rfc/rfc4768.txt The Generic Security Services API (GSS-API) provides a naming architecture that supports name-based authorization. GSS-API authenticates two named parties to each other. Names can be stored on access control lists (ACLs) to make authorization decisions. Advances in security mechanisms and the way implementers wish to use GSS-API require this model to be extended for the next version of GSS-API. As people move within an organization or change their names, the name authenticated by GSS-API may change. Using some sort of constant identifier would make ACLs more stable. Some mechanisms, such as public-key mechanisms, do not have a single name to be used across all environments. Other mechanisms, such as Kerberos, may include group membership or role information as part of authentication. This document motivates extensions to GSS-API naming and describes the extensions under discussion. This memo provides information for the Internet community. This document is a product of the Kitten (GSS-API Next Generation) Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjy-0003la-Cl; Thu, 21 Dec 2006 18:54:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjw-0003kU-R1 for ietf-announce@ietf.org; Thu, 21 Dec 2006 18:54:20 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXju-0002Fl-E9 for ietf-announce@ietf.org; Thu, 21 Dec 2006 18:54:20 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNsHCx002536; Thu, 21 Dec 2006 15:54:17 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNsHhv002535; Thu, 21 Dec 2006 15:54:17 -0800 Date: Thu, 21 Dec 2006 15:54:17 -0800 Message-Id: <200612212354.kBLNsHhv002535@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Cc: rfc-editor@rfc-editor.org Subject: RFC 4723 on Registration of Media Type audio/mobile-xmf X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4723 Title: Registration of Media Type audio/mobile-xmf Author: T. Kosonen, T. White Status: Informational Date: December 2006 Mailbox: timo.kosonen@nokia.com, twhite@midi.org Pages: 8 Characters: 12652 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-kosonen-mobile-xmf-mediatype-01.txt URL: http://www.rfc-editor.org/rfc/rfc4723.txt The MIDI Manufacturers Association (MMA) and the Association of Musical Electronics Industry (AMEI) have produced the Mobile XMF standard, which was developed particularly for mobile MIDI applications. Mobile XMF is a very compact media type providing high-quality synthetic audio content for music downloading and messaging applications that require MIME registration. This document registers the media type audio/mobile-xmf. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 21 18:54:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXju-0003jx-Ql; Thu, 21 Dec 2006 18:54:18 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxXjs-0003is-5m; Thu, 21 Dec 2006 18:54:16 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxXjq-0002FN-0g; Thu, 21 Dec 2006 18:54:16 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBLNsDg7002531; Thu, 21 Dec 2006 15:54:13 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBLNsDWe002530; Thu, 21 Dec 2006 15:54:13 -0800 Date: Thu, 21 Dec 2006 15:54:13 -0800 Message-Id: <200612212354.kBLNsDWe002530@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: kitten@lists.ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4768 on Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4768 Title: Desired Enhancements to Generic Security Services Application Program Interface (GSS-API) Version 3 Naming Author: S. Hartman Status: Informational Date: December 2006 Mailbox: hartmans-ietf@mit.edu Pages: 12 Characters: 27205 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-kitten-gss-naming-05.txt URL: http://www.rfc-editor.org/rfc/rfc4768.txt The Generic Security Services API (GSS-API) provides a naming architecture that supports name-based authorization. GSS-API authenticates two named parties to each other. Names can be stored on access control lists (ACLs) to make authorization decisions. Advances in security mechanisms and the way implementers wish to use GSS-API require this model to be extended for the next version of GSS-API. As people move within an organization or change their names, the name authenticated by GSS-API may change. Using some sort of constant identifier would make ACLs more stable. Some mechanisms, such as public-key mechanisms, do not have a single name to be used across all environments. Other mechanisms, such as Kerberos, may include group membership or role information as part of authentication. This document motivates extensions to GSS-API naming and describes the extensions under discussion. This memo provides information for the Internet community. This document is a product of the Kitten (GSS-API Next Generation) Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 04:48:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxgri-0007qx-7k; Fri, 22 Dec 2006 04:38:58 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxgrg-0007qq-19 for ietf-announce@ietf.org; Fri, 22 Dec 2006 04:38:56 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gxgre-0003Qf-O6 for ietf-announce@ietf.org; Fri, 22 Dec 2006 04:38:55 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns4.neustar.com (Postfix) with ESMTP id AA8772AD92 for ; Fri, 22 Dec 2006 09:38:24 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GxgrA-0004Ss-F7 for ietf-announce@ietf.org; Fri, 22 Dec 2006 04:38:24 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: IETF Announcement list Cc: From: IETF Administrative Director Message-Id: Date: Fri, 22 Dec 2006 04:38:24 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Subject: Network Services RFP for IETF Meetings X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org Network Services RFP for IETF Meetings The Internet Society and the IETF Administrative Oversight Committee (IAOC) are considering outsourcing the network communications infrastructure for Internet Engineering Task Force (IETF) meetings in 2007 and beyond, and to that end seek a partner to perform the appropriate services. Outsourced services would include: performing a pre-meeting site survey; developing a detailed network design; installing all equipment; conducting tests; and providing operations, systems management and user support functions during the meeting. The RFP can be found at this location: http://iaoc.ietf.org/ The IETF conducts three, one-week meetings a year throughout the world. Attendance is in the range of 1,200 to 1,500 per meeting. These meetings are in furtherance of the IETF's mission of standards development for the Internet. Attendees include engineers, computer scientists, and academicians who are always connected with one or more devices. The meetings are typically conducted in March, July and November. Changes to the IETF meeting hosting models and a need for greater consistency with the network services have motivated this approach to providing network infrastructure services. Should a decision be taken to outsource the network communications infrastructure for the Internet Engineering Task Force (IETF) meetings, it may include: a. IETF 68 at the Hilton Prague, Prague, Czech Republic, March 18 - 23, 2007 b. IETF 69 at the Palmer House Hilton, Chicago, IL, USA, July 22 - 27, 2007 c. IETF 70, at a location TBD, North America, December 2 - 7, 2007. Future meetings could be added to this Master Agreement from time to time by a mutually signed Supplemental Agreement. Specific quotes are requested for IETF 68 and IETF 69. The following timeline may lead to contract award: a. RFP Issued by email: December 22, 2006 b. RFP Response by email due no later than 5 PM EDT on January 5, 2007 c. Response Review Period: January 8 through January 12, 2007 d. Notification of selection: January 15, 2007 e. Contract Negotiation and Agreement: January 15 through January 19, 2007 f. Contract Signed and Accepted: January 22, 2007 Ray Pelletier IETF Administrative Director Internet Society _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 13:13:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxotg-00011F-6K; Fri, 22 Dec 2006 13:13:32 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxop1-0006DW-H4 for ietf-announce@ietf.org; Fri, 22 Dec 2006 13:08:43 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gxooz-00064S-8m for ietf-announce@ietf.org; Fri, 22 Dec 2006 13:08:43 -0500 Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42]) by ns3.neustar.com (Postfix) with ESMTP id 05F1917659 for ; Fri, 22 Dec 2006 18:08:11 +0000 (GMT) Received: from mirror by ietf.org with local (Exim 4.43) id 1GxooU-0007GS-Jk for ietf-announce@ietf.org; Fri, 22 Dec 2006 13:08:10 -0500 Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 To: ietf-announce@ietf.org Cc: From: Russ Housley Message-Id: Date: Fri, 22 Dec 2006 13:08:10 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 X-Mailman-Approved-At: Fri, 22 Dec 2006 13:13:29 -0500 Subject: HOKEY interim meeting on January 23rd, 2007 X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The HOKEY WG will hold a one-day interim meeting. Here are the details: HOKEY WG Interim Meeting Tuesday, January 23, 2007 9:00 AM - 5:00 PM (PDT) 3750 Cisco Way (Building 15) San Jose,CA More information about the HOKEY WG can be found on our charter page: http://www.ietf.org/html.charters/hokey-charter.html More information about the HOKEY interim meeting, including registration information and a full agenda, will be circulated on the HOKEY WG mailing list. If you wish to join the HOKEY mailing list, go to: https://www.ietf.org/mailman/listinfo/hokey _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 15:21:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxqtH-0001BI-Gq; Fri, 22 Dec 2006 15:21:15 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxqtG-0001A7-FF for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:21:14 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GxqtE-0000bW-Vn for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:21:14 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id B3944175EC for ; Fri, 22 Dec 2006 20:20:42 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gxqsk-00066T-9q for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:20:42 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Fri, 22 Dec 2006 15:20:42 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: Last Call: draft-barany-eap-gee (3GPP2 Generic EAP Encapsulation (GEE) Protocol) to Experimental RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following document: - '3GPP2 Generic EAP Encapsulation (GEE) Protocol ' as an Experimental RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-01-19. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-barany-eap-gee-04.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14299&rfc_flag=0 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 15:30:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxqud-0001f3-Ug; Fri, 22 Dec 2006 15:22:39 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxquc-0001ew-ID for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:22:38 -0500 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gxquc-0000fC-AM for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:22:38 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 43E632ACCE for ; Fri, 22 Dec 2006 20:22:08 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gxqu8-0001zd-1N for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:22:08 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Fri, 22 Dec 2006 15:22:08 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: Last Call: draft-bonica-internet-icmp (Modifying ICMP to Support Multi-part Messages) to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following document: - 'Modifying ICMP to Support Multi-part Messages ' 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 substantive comments to the ietf@ietf.org mailing lists by 2007-01-19. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-bonica-internet-icmp-14.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13675&rfc_flag=0 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 15:30:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxqtH-0001BI-Ln; Fri, 22 Dec 2006 15:21:15 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxqtG-0001A7-FF for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:21:14 -0500 Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GxqtE-0000bW-Vn for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:21:14 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id B3944175EC for ; Fri, 22 Dec 2006 20:20:42 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Gxqsk-00066T-9q for ietf-announce@ietf.org; Fri, 22 Dec 2006 15:20:42 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Fri, 22 Dec 2006 15:20:42 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: Last Call: draft-barany-eap-gee (3GPP2 Generic EAP Encapsulation (GEE) Protocol) to Experimental RFC X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following document: - '3GPP2 Generic EAP Encapsulation (GEE) Protocol ' as an Experimental RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2007-01-19. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-barany-eap-gee-04.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14299&rfc_flag=0 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 16:56:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNa-0001gs-5h; Fri, 22 Dec 2006 16:56:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNZ-0001gY-0J for ietf-announce@ietf.org; Fri, 22 Dec 2006 16:56:37 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxsNX-0006Sa-Ju for ietf-announce@ietf.org; Fri, 22 Dec 2006 16:56:36 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBMLuZeI006855; Fri, 22 Dec 2006 13:56:35 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBMLuZ6Y006854; Fri, 22 Dec 2006 13:56:35 -0800 Date: Fri, 22 Dec 2006 13:56:35 -0800 Message-Id: <200612222156.kBMLuZ6Y006854@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Cc: rfc-editor@rfc-editor.org Subject: RFC 4773 on Administration of the IANA Special Purpose IPv6 Address Block X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4773 Title: Administration of the IANA Special Purpose IPv6 Address Block Author: G. Huston Status: Informational Date: December 2006 Mailbox: gih@apnic.net Pages: 5 Characters: 10580 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-huston-ipv6-iana-specials-01.txt URL: http://www.rfc-editor.org/rfc/rfc4773.txt This is a direction to IANA concerning the management of the IANA Special Purpose IPv6 address assignment registry. This memo provides information for the Internet community. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 16:56:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNl-0001rj-Oz; Fri, 22 Dec 2006 16:56:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNj-0001q9-Ox; Fri, 22 Dec 2006 16:56:47 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxsNi-0006UR-Cq; Fri, 22 Dec 2006 16:56:47 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBMLujHW006865; Fri, 22 Dec 2006 13:56:45 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBMLujlL006864; Fri, 22 Dec 2006 13:56:45 -0800 Date: Fri, 22 Dec 2006 13:56:45 -0800 Message-Id: <200612222156.kBMLujlL006864@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.3 (--------------) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Cc: grow@ietf.org, rfc-editor@rfc-editor.org Subject: BCP 126, RFC 4786 on Operation of Anycast Services X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. BCP0126 RFC 4786 Title: Operation of Anycast Services Author: J. Abley, K. Lindqvist Status: Best Current Practice Date: December 2006 Mailbox: jabley@ca.afilias.info, kurtis@kurtis.pp.se Pages: 24 Characters: 56818 Updates: See-Also: BCP0126 I-D Tag: draft-ietf-grow-anycast-04.txt URL: http://www.rfc-editor.org/rfc/rfc4786.txt As the Internet has grown, and as systems and networked services within enterprises have become more pervasive, many services with high availability requirements have emerged. These requirements have increased the demands on the reliability of the infrastructure on which those services rely. Various techniques have been employed to increase the availability of services deployed on the Internet. This document presents commentary and recommendations for distribution of services using anycast. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document is a product of the Global Routing Operations Working Group of the IETF. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 16:56:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNU-0001cY-1m; Fri, 22 Dec 2006 16:56:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNS-0001aH-Tc; Fri, 22 Dec 2006 16:56:30 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxsNR-0006SB-HZ; Fri, 22 Dec 2006 16:56:30 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBMLuTmj006850; Fri, 22 Dec 2006 13:56:29 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBMLuTp0006849; Fri, 22 Dec 2006 13:56:29 -0800 Date: Fri, 22 Dec 2006 13:56:29 -0800 Message-Id: <200612222156.kBMLuTp0006849@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4639 on Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4639 Title: Cable Device Management Information Base for Data-Over-Cable Service Interface Specification (DOCSIS) Compliant Cable Modems and Cable Modem Termination Systems Author: R. Woundy, K. Marez Status: Standards Track Date: December 2006 Mailbox: richard_woundy@cable.comcast.com, kevin.marez@motorola.com Pages: 88 Characters: 188220 Obsoletes: RFC2669 See-Also: I-D Tag: draft-ietf-ipcdn-device-mibv2-11.txt URL: http://www.rfc-editor.org/rfc/rfc4639.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of Data Over Cable Service Interface Specification (DOCSIS)-compliant Cable Modems and Cable Modem Termination Systems. This memo obsoletes RFC 2669. [STANDARDS TRACK] This document is a product of the IP over Cable Data Network 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Fri Dec 22 16:56:56 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNq-0001y3-Bq; Fri, 22 Dec 2006 16:56:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxsNp-0001tv-2K; Fri, 22 Dec 2006 16:56:53 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxsNn-0006WB-JZ; Fri, 22 Dec 2006 16:56:53 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kBMLupeW006870; Fri, 22 Dec 2006 13:56:51 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kBMLupad006869; Fri, 22 Dec 2006 13:56:51 -0800 Date: Fri, 22 Dec 2006 13:56:51 -0800 Message-Id: <200612222156.kBMLupad006869@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Cc: ipcdn@ietf.org, rfc-editor@rfc-editor.org Subject: RFC 4682 on Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4682 Title: Multimedia Terminal Adapter (MTA) Management Information Base for PacketCable- and IPCablecom-Compliant Devices Author: E. Nechamkin, J-F. Mule Status: Standards Track Date: December 2006 Mailbox: enechamkin@broadcom.com, jf.mule@cablelabs.com Pages: 60 Characters: 137373 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ipcdn-pktc-mtamib-09.txt URL: http://www.rfc-editor.org/rfc/rfc4682.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines a basic set of managed objects for Simple Network Management Protocol (SNMP)-based management of PacketCable- and IPCablecom-compliant Multimedia Terminal Adapter devices. [STANDARDS TRACK] This document is a product of the IP over Cable Data Network 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 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 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 ... _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Wed Dec 27 15:52:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzfWX-0004SN-SL; Wed, 27 Dec 2006 15:37:17 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzfWV-0004SG-G8 for ietf-announce@ietf.org; Wed, 27 Dec 2006 15:37:15 -0500 Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GzfWV-0006CH-9k for ietf-announce@ietf.org; Wed, 27 Dec 2006 15:37:15 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id F002D26ED3 for ; Wed, 27 Dec 2006 20:37:14 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GzfWU-00036v-SF for ietf-announce@ietf.org; Wed, 27 Dec 2006 15:37:14 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Wed, 27 Dec 2006 15:37:14 -0500 X-Spam-Score: -2.8 (--) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: Last Call: draft-daigle-unaptr (Domain-based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)) to Proposed Standard X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ietf@ietf.org List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org The IESG has received a request from an individual submitter to consider the following document: - 'Domain-based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS) ' 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 substantive comments to the ietf@ietf.org mailing lists by 2007-01-25. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://www.ietf.org/internet-drafts/draft-daigle-unaptr-01.txt IESG discussion can be tracked via https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14866&rfc_flag=0 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce From ietf-announce-bounces@ietf.org Thu Dec 28 10:23:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzwyK-0008Rd-IY; Thu, 28 Dec 2006 10:15:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxy5h-0001bu-HK; Fri, 22 Dec 2006 23:02:33 -0500 Received: from smtp130.iad.emailsrvr.com ([207.97.245.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxy5g-0005xe-8l; Fri, 22 Dec 2006 23:02:33 -0500 Received: from [192.168.2.4] (c-71-62-81-159.hsd1.va.comcast.net [71.62.81.159]) (Authenticated sender: rpelletier@isoc.org) by relay3.r3.iad.emailsrvr.com (SMTP Server) with ESMTP id F266044C003; Fri, 22 Dec 2006 23:02:31 -0500 (EST) Message-ID: <458CAA57.10708@isoc.org> Date: Fri, 22 Dec 2006 23:02:31 -0500 From: Ray Pelletier User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw, ja MIME-Version: 1.0 To: IETF Administrative Director References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: OK X-Spam-Score: 0.0 (/) X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248 X-Mailman-Approved-At: Thu, 28 Dec 2006 10:15:03 -0500 Cc: IETF Announcement list Subject: Re: Network Services RFP for IETF Meetings X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ietf-announce.ietf.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ietf-announce-bounces@ietf.org Network Services RFP for IETF Meetings Schedule Modification The RFP response date is hereby changed to provide a greater period for response preparation. The RFP response is changed from 5 PM EST January 5, 2007 to 5 PM EST January 15, 2007. Ray Pelletier IETF Administrative Director Internet Society IETF Administrative Director wrote: >Network Services RFP for IETF Meetings > >The Internet Society and the IETF Administrative Oversight Committee >(IAOC) are considering outsourcing the network communications >infrastructure for Internet Engineering Task Force (IETF) meetings in 2007 >and beyond, and to that end seek a partner to perform the appropriate >services. Outsourced services would include: performing a pre-meeting >site survey; developing a detailed network design; installing all >equipment; conducting tests; and providing operations, systems management >and user support functions during the meeting. > >The RFP can be found at this location: http://iaoc.ietf.org/ > >The IETF conducts three, one-week meetings a year throughout the world. >Attendance is in the range of 1,200 to 1,500 per meeting. These meetings >are in furtherance of the IETF's mission of standards development for the >Internet. Attendees include engineers, computer scientists, and >academicians who are always connected with one or more devices. The >meetings are typically conducted in March, July and November. > >Changes to the IETF meeting hosting models and a need for greater >consistency with the network services have motivated this approach to >providing network infrastructure services. > >Should a decision be taken to outsource the network communications >infrastructure for the Internet Engineering Task Force (IETF) meetings, it >may include: > >a. IETF 68 at the Hilton Prague, Prague, Czech Republic, March 18 - 23, >2007 > >b. IETF 69 at the Palmer House Hilton, Chicago, IL, USA, July 22 - 27, >2007 > >c. IETF 70, at a location TBD, North America, December 2 - 7, 2007. > >Future meetings could be added to this Master Agreement from time to time >by a mutually signed Supplemental Agreement. > >Specific quotes are requested for IETF 68 and IETF 69. > >The following timeline may lead to contract award: > >a. RFP Issued by email: December 22, 2006 >b. RFP Response by email due no later than 5 PM EDT on January 5, 2007 >c. Response Review Period: January 8 through January 12, 2007 >d. Notification of selection: January 15, 2007 >e. Contract Negotiation and Agreement: January 15 through January 19, >2007 >f. Contract Signed and Accepted: January 22, 2007 > >Ray Pelletier >IETF Administrative Director >Internet Society > >_______________________________________________ >IETF-Announce mailing list >IETF-Announce@ietf.org >https://www1.ietf.org/mailman/listinfo/ietf-announce > > > > _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce