From rtg-dir-bounces@ietf.org Mon Aug 11 04:00:16 2008 Return-Path: X-Original-To: rtg-dir-archive@megatron.ietf.org Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66F2D3A6BBB; Mon, 11 Aug 2008 04:00:16 -0700 (PDT) X-Original-To: rtg-dir@core3.amsl.com Delivered-To: rtg-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CC2F3A6CD8 for ; Mon, 11 Aug 2008 04:00:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.999 X-Spam-Level: X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CD87Imqp9fiv for ; Mon, 11 Aug 2008 04:00:14 -0700 (PDT) Received: from runaway.fenron.com (unknown [IPv6:2001:470:117:128:230:48ff:fe92:8e81]) by core3.amsl.com (Postfix) with ESMTP id DACE73A6BBB for ; Mon, 11 Aug 2008 04:00:13 -0700 (PDT) Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id m7BB023j037749 for ; Mon, 11 Aug 2008 04:00:02 -0700 (PDT) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id m7BB02oq037748 for rtg-dir@ietf.org; Mon, 11 Aug 2008 04:00:02 -0700 (PDT) (envelope-from fenner) Date: Mon, 11 Aug 2008 04:00:02 -0700 (PDT) Message-Id: <200808111100.m7BB02oq037748@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) Subject: IESG agenda for 2008-08-14 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: rtg-dir-bounces@ietf.org Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2008-08-14). ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item Area Date Information Model and XML Data Model for TSV Traceroute Measurements (Proposed Standard) - 1 of 6 draft-ietf-ippm-storetraceroutes-10.txt [Open Web Ballot] Note: Document sheperd is Henk Uijterwaal (henk@ripe.net) Token: Lars Eggert SEC TLS Transport Mapping for Syslog (Proposed Standard) - 2 of 6 draft-ietf-syslog-transport-tls-13.txt [Open Web Ballot] Token: Pasi Eronen Definitions of Textual Conventions for INT Pseudowires (PW) Management (Proposed Standard) - 3 of 6 draft-ietf-pwe3-pw-tc-mib-14.txt [Open Web Ballot] Token: Mark Townsley TSV Guidelines for Application Designers on Using Unicast UDP (BCP) - 4 of 6 draft-ietf-tsvwg-udp-guidelines-09.txt Token: Magnus Westerlund Simple Network Management Protocol (SNMP) OPS Context EngineID Discovery (Proposed Standard) - 5 of 6 draft-ietf-opsawg-snmp-engineid-discovery-03.txt [Open Web Ballot] Token: Dan Romascanu APP Internet Message Store Events (Proposed Standard) - 6 of 6 draft-ietf-lemonade-msgevent-06.txt [Open Web Ballot] Token: Lisa Dusseault 2.1.2 Returning Item Area Date TSV A Two-way Active Measurement Protocol (TWAMP) (Proposed Standard) - 1 of 1 draft-ietf-ippm-twamp-09.txt [Open Web Ballot] Note: Document Shepherd: Henk Uijterwaal (henk@ripe.net) Token: Lars Eggert 2.2 Individual Submissions 2.2.1 New Item Area Date IANA Considerations for the IPv4 and IPv6 INT Router Alert Option (Proposed Standard) - 1 of 2 draft-manner-router-alert-iana-03.txt [Open Web Ballot] Token: Jari Arkko Extensions to the IODEF-Document Class for SEC Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 2 of 2 draft-cain-post-inch-phishingextns-05.txt [Open Web Ballot] Token: Tim Polk 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item NONE 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item Area Date Basic Password Exchange within the Flexible GEN Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 3 draft-zhou-emu-fast-gtc-04.txt [Open Web Ballot] Token: Tim Polk Dynamic Provisioning using Flexible GEN Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 2 of 3 draft-cam-winget-eap-fast-provisioning-09.txt [Open Web Ballot] Token: Tim Polk RAI Media Gateway Control Protocol Fax Package (Informational) - 3 of 3 draft-andreasen-mgcp-fax-08.txt [Open Web Ballot] Token: Cullen Jennings 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review Area Date INT Aug 5 Layer 2 Virtual Private Networks (l2vpn) - 1 of 1 Token: Mark 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 6.1 No New Ballot Sets (Pasi Eronen) 6.2 Printer designated experts (Chris Newman) 6.3 Updating the RFC Editor index? (Sandy Ginoza) 6.4 Designated expert for ethernet-numbers [IANA #182998] (Michelle Cotton) 6.5 IESG Requirements for NomCom (Russ Housley) 6.6 Friday Meetings in Minneapolis (Russ Housley) 6.7 Modification to a SASL Mechanism [IANA #178703] (Michelle Cotton) 6.8 Register IMAP Child Mailbox Extension [IANA #111861] (Chris Newman) 7. Working Group News From rtg-dir-bounces@ietf.org Mon Aug 25 04:00:20 2008 Return-Path: X-Original-To: rtg-dir-archive@megatron.ietf.org Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 525873A683D; Mon, 25 Aug 2008 04:00:20 -0700 (PDT) X-Original-To: rtg-dir@core3.amsl.com Delivered-To: rtg-dir@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86FC23A683D for ; Mon, 25 Aug 2008 04:00:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.74 X-Spam-Level: X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qGVpCi9qHBhG for ; Mon, 25 Aug 2008 04:00:13 -0700 (PDT) Received: from runaway.fenron.com (unknown [IPv6:2001:470:117:128:230:48ff:fe92:8e81]) by core3.amsl.com (Postfix) with ESMTP id 62F7C3A689E for ; Mon, 25 Aug 2008 04:00:13 -0700 (PDT) Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id m7PB01AR046751 for ; Mon, 25 Aug 2008 04:00:01 -0700 (PDT) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id m7PB01Pf046747 for rtg-dir@ietf.org; Mon, 25 Aug 2008 04:00:01 -0700 (PDT) (envelope-from fenner) Date: Mon, 25 Aug 2008 04:00:01 -0700 (PDT) Message-Id: <200808251100.m7PB01Pf046747@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) Subject: IESG agenda for 2008-08-28 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: rtg-dir-bounces@ietf.org Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2008-08-28). ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item Area Date A Link-Type sub-TLV to convey the number of RTG Traffic Engineering Label Switched Paths signalled with zero reserved bandwidth across a link (Proposed Standard) - 1 of 1 draft-ietf-mpls-number-0-bw-te-lsps-11.txt [Open Web Ballot] Token: Ross Callon 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item Area Date Extensions to the IODEF-Document Class for SEC Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 1 of 1 draft-cain-post-inch-phishingextns-05.txt [Open Web Ballot] Token: Tim Polk 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item Area Date INT Why Authentication Data suboption is needed for MIP6 (Informational) - 1 of 1 draft-ietf-mip6-whyauthdataoption-06.txt [Open Web Ballot] Note: No document shepherd -- old MIP6 document Token: Jari Arkko 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item Area Date Dynamic Provisioning using Flexible GEN Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 2 draft-cam-winget-eap-fast-provisioning-09.txt [Open Web Ballot] Token: Tim Polk OPS Diameter ITU-T Rw Policy Enforcement Interface Application (Informational) - 2 of 2 draft-sun-dime-itu-t-rw-01.txt [Open Web Ballot] Token: Dan Romascanu 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item Area Date OPS SNMP Traffic Measurements and Trace Exchange Formats (Informational) - 1 of 1 draft-irtf-nmrg-snmp-measure-05.txt [Open Web Ballot] Note: Proposed IESG Note: The IESG thinks that this work is related to IETF work done in the Operations and Management Area related to SNMP, but this does not prevent publishing. This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and notes that the decision to publish is not based on IETF review apart from the IETF Last Call on the allocation of an URI by IANA and the IESG review for conflict with IETF work. The RFC Editor has chosen to publish this document at its discretion. See RFC 3932 for more information. Token: Dan Romascanu 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review Area Date OPS Aug 18 Operational Security Capabilities for IP Network Infrastructure (opsec) - 1 of 1 Token: Ron 4.2.2 Proposed for Approval Area Date APP Jul 2 Sieve Mail Filtering Language (sieve) - 1 of 2 Token: Lisa INT Aug 14 Layer 2 Virtual Private Networks (l2vpn) - 2 of 2 Token: Mark 5. IAB News We Can Use 6. Management Issues 6.1 IESG Requirements for NomCom (UPDATED) (Russ Housley) 6.2 Friday Meetings in Minneapolis (Russ Housley) 6.3 Registration procedures for arp-parameters (hardware types) [IANA # 183428] (Michelle Cotton) 6.4 Revised guidance for interim meetings (UPDATED) (Russ Housley) 6.5 Executive Session: First draft of appeal response (Lisa Dusseault) 7. Working Group News