[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for February 26, 2009
IESG Secretary <iesg-secretary-reply@ietf.org> Fri, 20 February 2009 00:38 UTC
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: iesg-agenda-dist@ietf.org
Delivered-To: iesg-agenda-dist@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id EF1AB3A68D4; Thu, 19 Feb 2009 16:38:40 -0800 (PST)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090220003840.EF1AB3A68D4@core3.amsl.com>
Date: Thu, 19 Feb 2009 16:38:40 -0800
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for February 26, 2009
X-BeenThere: iesg-agenda-dist@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distribution of IESG agendas <iesg-agenda-dist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iesg-agenda-dist>
List-Post: <mailto:iesg-agenda-dist@ietf.org>
List-Help: <mailto:iesg-agenda-dist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2009 00:38:41 -0000
INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the February 26, 2009 IESG Teleconference This agenda was generated at 16:38:40 EDT, February 19, 2009 Web version of this agenda can be found at: http://www.ietf.org/IESG/agenda.html 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes 1.4 Review of Action Items 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 o draft-ietf-mediactrl-vxml-04.txt SIP Interface to VoiceXML Media Services (Proposed Standard) - 1 of 2 Token: Jon Peterson o draft-ietf-dime-qos-parameters-09.txt Quality of Service Parameters for Usage with Diameter (Proposed Standard) - 2 of 2 Token: Dan Romascanu 2.1.2 Returning Item NONE 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 o draft-ietf-rserpool-mib-11.txt Reliable Server Pooling MIB Module Definition (Experimental) - 1 of 3 Token: Magnus Westerlund o draft-ietf-mediactrl-architecture-04.txt An Architectural Framework for Media Server Control (Informational) - 2 of 3 Token: Jon Peterson o draft-ietf-pcn-architecture-09.txt Pre-Congestion Notification (PCN) Architecture (Informational) - 3 of 3 Note: Scott Bradner (sob@harvard.edu) is the Document Shepherd. Token: Lars Eggert 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 <X>, but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG <X> and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for <X> 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 o Network File System Version 4 (nfsv4) - 1 of 1 Token: Lars 4.2.2 Proposed for Approval o IP Performance Metrics (ippm) - 1 of 1 Token: Lars 5. IAB News We can use 6. Management Issue 6.1 Document Submission cutoff for IETF 74 (Tim Polk) 6.2 Second Nomcom appointment to the IAOC (Ross Callon) 7. Agenda Working Group News
- [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Te… IESG Secretary