From rtg-dir-bounces@ietf.org Mon Apr 7 04:02:22 2008 Return-Path: X-Original-To: rtg-dir-archive@megatron.ietf.org Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 565293A6BA1; Mon, 7 Apr 2008 04:02:22 -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 C09553A69BA for ; Mon, 7 Apr 2008 04:02:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 Cqlm4gB4NPqm for ; Mon, 7 Apr 2008 04:02:20 -0700 (PDT) Received: from runaway.fenron.com (runaway.fenron.com [206.197.161.144]) by core3.amsl.com (Postfix) with ESMTP id 9FE7C3A69CA for ; Mon, 7 Apr 2008 04:02:20 -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 m37B1FhY063527 for ; Mon, 7 Apr 2008 04:01:15 -0700 (PDT) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id m37B1FWl063526 for rtg-dir@ietf.org; Mon, 7 Apr 2008 04:01:15 -0700 (PDT) (envelope-from fenner) Date: Mon, 7 Apr 2008 04:01:15 -0700 (PDT) Message-Id: <200804071101.m37B1FWl063526@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) Subject: IESG agenda for 2008-04-10 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , 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-04-10). ----------------------------------------------------------------------- 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 INT Proxy Mobile IPv6 (Proposed Standard) - 1 of 1 draft-ietf-netlmm-proxymip6-11.txt [Open Web Ballot] Note: Document Shepherd is Jonne Soininen Token: Jari Arkko 2.1.2 Returning Item Area Date INT Mobile IPv4 Traversal Across IPsec-based VPN Gateways (Proposed Standard) - 1 of 1 draft-ietf-mip4-vpn-problem-solution-05.txt [Open Web Ballot] Note: Document Shepherd is Henrik Levkowetz Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item NONE 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 RAI ENUM Implementation Issues and Experiences (Informational) - 1 of 2 draft-ietf-enum-experiences-09.txt [Open Web Ballot] Token: Jon Peterson Requirements from SIP (Session Initiation RAI Protocol) Session Border Control Deployments (Informational) - 2 of 2 draft-ietf-sipping-sbc-funcs-05.txt [Open Web Ballot] Token: Jon Peterson 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 NONE 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 Area Date OPS Apr 3 NETCONF Data Modeling Language (netmod) - 1 of 1 Token: Dan 4.1.2 Proposed for Approval Area Date Internationalized Domain Names in APP Mar 31 Applications (Revised) (idnabis) - 1 of 1 Token: Lisa 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval Area Date RAI Feb 14 Multiparty Multimedia Session Control (mmusic) - 1 of 1 Token: Cullen 5. IAB News We Can Use 6. Management Issues 6.1 ISOC BoT Candidate Confirmation (Executive Session) (Russ Housley) 6.2 Approval of expert team for IANA port number allocations (Lars Eggert) 6.3 Confirm results of IETF LC on draft-irtf-nmrg-snmp-measure-04.txt (Dan Romascanu) 7. Working Group News From rtg-dir-bounces@ietf.org Mon Apr 21 04:00:31 2008 Return-Path: X-Original-To: rtg-dir-archive@megatron.ietf.org Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 362803A6F12; Mon, 21 Apr 2008 04:00:31 -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 6A2BE28C1D6 for ; Mon, 21 Apr 2008 04:00:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 cJGlhy7jqzUl for ; Mon, 21 Apr 2008 04:00:29 -0700 (PDT) Received: from runaway.fenron.com (runaway.fenron.com [206.197.161.144]) by core3.amsl.com (Postfix) with ESMTP id 468F83A6F12 for ; Mon, 21 Apr 2008 04:00:29 -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 m3LB0I6G071413 for ; Mon, 21 Apr 2008 04:00:18 -0700 (PDT) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id m3LB0ISv071412 for rtg-dir@ietf.org; Mon, 21 Apr 2008 04:00:18 -0700 (PDT) (envelope-from fenner) Date: Mon, 21 Apr 2008 04:00:18 -0700 (PDT) Message-Id: <200804211100.m3LB0ISv071412@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) Subject: IESG agenda for 2008-04-24 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , 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-04-24). ----------------------------------------------------------------------- 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 TSV NFS Direct Data Placement (Proposed Standard) - 1 of 4 draft-ietf-nfsv4-nfsdirect-08.txt [Open Web Ballot] Note: Document Shepherd: Spencer Shepler (spencer.shepler@sun.com) Token: Lars Eggert Remote Direct Memory Access Transport for TSV Remote Procedure Call (Proposed Standard) - 2 of 4 draft-ietf-nfsv4-rpcrdma-08.txt [Open Web Ballot] Note: Document Shepherd: Spencer Shepler (spencer.shepler@sun.com) Token: Lars Eggert INT Hierarchical Mobile IPv6 Mobility Management (HMIPv6) (Proposed Standard) - 3 of 4 draft-ietf-mipshop-4140bis-02.txt [Open Web Ballot] Note: Document shepherd is Vijay Devarapalli Token: Jari Arkko Datagram Transport Layer Security (DTLS) over TSV the Datagram Congestion Control Protocol (DCCP) (Proposed Standard) - 4 of 4 draft-ietf-dccp-dtls-06.txt [Open Web Ballot] Note: Document Shepherd: Gorry Fairhurst (gorry@erg.abdn.ac.uk) - DCCP WG Chair Token: Lars Eggert 2.1.2 Returning Item Area Date RTG OSPF Multi-Area Adjacency (Proposed Standard) - 1 of 3 draft-ietf-ospf-multi-area-adj-08.txt Token: David Ward RTG OSPFv3 Graceful Restart (Proposed Standard) - 2 of 3 draft-ietf-ospf-ospfv3-graceful-restart-07.txt Token: David Ward RTG The OSPF Opaque LSA Option (Proposed Standard) - 3 of 3 draft-ietf-ospf-rfc2370bis-02.txt Token: David Ward 2.2 Individual Submissions 2.2.1 New Item Area Date APP A Registry for SMTP Enhanced Mail System Status Codes (BCP) - 1 of 2 draft-hansen-4468upd-mailesc-registry-04.txt [Open Web Ballot] Note: Harald Alvestrand is document shepherd Token: Chris Newman APP Sieve Email Filtering: Environment Extension (Proposed Standard) - 2 of 2 draft-freed-sieve-environment-05.txt [Open Web Ballot] Note: Alexey Melnikov is document shepherd Token: Chris Newman 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 RTG Policy-Enabled Path Computation Framework (Informational) - 1 of 1 draft-ietf-pce-policy-enabled-path-comp-03.txt [Open Web Ballot] Token: Ross Callon 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 EAP Tunneled TLS Authentication Protocol INT Version 0 (EAP-TTLSv0) (Informational) - 1 of 2 draft-funk-eap-ttls-v0-04.txt [Open Web Ballot] Note: Laksminath Dondeti is the Document Shepherd Token: Jari Arkko PKCS #8: Private-Key Information Syntax GEN Standard Version 1.2 (Informational) - 2 of 2 draft-kaliski-pkcs8-00.txt [Open Web Ballot] Token: Russ Housley 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 Area Date OPS Apr 3 NETCONF Data Modeling Language (netmod) - 1 of 1 Token: Dan 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 7. Working Group News