[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for December 20, 2007
IESG Secretary <iesg-secretary-reply@ietf.org> Fri, 14 December 2007 00:12 UTC
Return-path: <iesg-agenda-dist-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2y9u-0007NP-8g; Thu, 13 Dec 2007 19:12:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J2y9t-0007NI-Pi for iesg-agenda-dist@ietf.org; Thu, 13 Dec 2007 19:12:05 -0500
Received: from ns3.neustar.com ([156.154.24.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J2y9t-0006X8-10 for iesg-agenda-dist@ietf.org; Thu, 13 Dec 2007 19:12:05 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id A447A175BD for <iesg-agenda-dist@ietf.org>; Fri, 14 Dec 2007 00:11:34 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1J2y9O-0007fk-6f for iesg-agenda-dist@ietf.org; Thu, 13 Dec 2007 19:11:34 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: iesg-agenda-dist@ietf.org
Cc:
From: IESG Secretary <iesg-secretary-reply@ietf.org>
Message-Id: <E1J2y9O-0007fk-6f@stiedprstage1.ietf.org>
Date: Thu, 13 Dec 2007 19:11:34 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for December 20, 2007
X-BeenThere: iesg-agenda-dist@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distribution of IESG agendas <iesg-agenda-dist.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/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://www1.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=subscribe>
Errors-To: iesg-agenda-dist-bounces@ietf.org
INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the December 20, 2007 IESG Teleconference This agenda was generated at 19:11:34 EDT, December 13, 2007 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 Three-document ballot: - 1 of 10 - draft-ietf-pkix-2797-bis-06.txt Certificate Management Messages over CMS (Proposed Standard) Note: PROTO Shepherd: Stefan Santesson <stefans@microsoft.com> - draft-ietf-pkix-cmc-compl-05.txt Certificate Managmement Messages over CMS (CMC): Complience Requirements (Proposed Standard) Note: PROTO Shepherd: Stefan Santesson <stefans@microsoft.com> - draft-ietf-pkix-cmc-trans-07.txt Certificate Management over CMS (CMC): Transport Protocols (Proposed Standard) Note: PROTO Shepherd: Stefan Santesson <stefans@microsoft.com> Token: Tim Polk o draft-ietf-shim6-hba-04.txt Hash Based Addresses (HBA) (Proposed Standard) - 2 of 10 Note: Please also read draft-ietf-shim6-applicability. Mark Townsley to handle any IPR questions in AD review/IETF LC/IESG, if any. Document Shepherd is Geoff Huston <gih@apnic.net>. Token: Jari Arkko o draft-ietf-shim6-failure-detection-09.txt Failure Detection and Locator Pair Exploration Protocol for IPv6 Multihoming (Proposed Standard) - 3 of 10 Note: Please also read draft-ietf-shim6-applicability. Mark is handling this for Jari as he is an author Token: Mark Townsley o draft-ietf-shim6-proto-09.txt Shim6: Level 3 Multihoming Shim Protocol for IPv6 (Proposed Standard) - 4 of 10 Note: Please also read draft-ietf-shim6-applicability. Document Shepherd is Geoff Huston <gih@apnic.net> Token: Jari Arkko o draft-ietf-dnsext-2929bis-06.txt Domain Name System (DNS) IANA Considerations (BCP) - 5 of 10 Token: Mark Townsley o draft-ietf-pkix-rfc3280bis-09.txt Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (Proposed Standard) - 6 of 10 Note: new version expected to be submitted Friday to address last call comments Token: Sam Hartman o draft-ietf-sieve-notify-11.txt SIEVE Email Filtering: Extension for Notifications (Proposed Standard) - 7 of 10 Token: Lisa Dusseault o draft-ietf-sieve-notify-xmpp-07.txt Sieve Notification Mechanism: xmpp (Proposed Standard) - 8 of 10 Token: Lisa Dusseault o draft-ietf-msec-ipsec-extensions-07.txt Multicast Extensions to the Security Architecture for the Internet Protocol (Proposed Standard) - 9 of 10 Note: Lakshminath Dondeti is the proto shepherd. Token: Tim Polk o draft-ietf-sip-consent-framework-03.txt A Framework for Consent-based Communications in the Session Initiation Protocol (SIP) (Proposed Standard) - 10 of 10 Note: Keith Drage is the document shepherd Token: Cullen Jennings 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-cheshire-ipv4-acd-05.txt IPv4 Address Conflict Detection (Proposed Standard) - 1 of 1 Note: -05 includes changes based on int-area review. Token: Mark Townsley 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-sipping-toip-08.txt Framework for real-time text over IP using the Session Initiation Protocol (SIP) (Informational) - 1 of 8 Token: Jon Peterson o draft-ietf-16ng-ps-goals-03.txt IP over 802.16 Problem Statement and Goals (Informational) - 2 of 8 Note: Document shepherd is Daniel Park <soohong.park@samsung.com> Token: Jari Arkko o draft-ietf-l2vpn-vpls-mcast-reqts-05.txt Requirements for Multicast Support in Virtual Private LAN Services (Informational) - 3 of 8 Token: Mark Townsley o draft-ietf-mipshop-mis-ps-05.txt Mobility Services Transport: Problem Statement (Informational) - 4 of 8 Note: Document Shepherd is Stefano Faccin Token: Jari Arkko o draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-04.txt Framework for MPLS-TE to GMPLS migration (Informational) - 5 of 8 Token: Ross Callon o draft-ietf-ccamp-mpls-gmpls-interwork-reqts-03.txt Interworking Requirements to Support operation of MPLS-TE over GMPLS Networks (Informational) - 6 of 8 Token: Ross Callon o draft-ietf-l2vpn-vpls-bridge-interop-02.txt VPLS Interoperability with CE Bridges (Informational) - 7 of 8 Token: Mark Townsley o draft-ietf-l2vpn-oam-req-frmk-09.txt L2VPN OAM Requirements and Framework (Informational) - 8 of 8 Token: Mark Townsley 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 o draft-creed-ogc-urn-03.txt A Uniform Resource Name (URN) namespace for the Open Geospatial Consortium (OGC) (Informational) - 1 of 3 Token: Lisa Dusseault o draft-korhonen-mip6-service-05.txt Service Selection for Mobile IPv6 (Informational) - 2 of 3 Note: No document shepherd Token: Jari Arkko o draft-sjdcox-cgi-urn-00.txt A URN namespace for the Commission for the Management and Application of Geoscience Information (CGI) (Informational) - 3 of 3 Token: Lisa Dusseault 3.2.2 Returning Item o draft-goodwin-iso-urn-02.txt A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) (Informational) - 1 of 1 Token: Lisa Dusseault 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 NONE 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www1.ietf.org/mailman/listinfo/iesg-agenda-dist
- [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Te… IESG Secretary