[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 10, 2008
IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 03 January 2008 23: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 1JAZEs-0006IR-0x; Thu, 03 Jan 2008 18:12:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JAZEq-0006HG-M6 for iesg-agenda-dist@ietf.org; Thu, 03 Jan 2008 18:12:36 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JAZEn-00027C-UE for iesg-agenda-dist@ietf.org; Thu, 03 Jan 2008 18:12:36 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id C00A526E91 for <iesg-agenda-dist@ietf.org>; Thu, 3 Jan 2008 23:12:33 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1JAZEn-00009O-Lv for iesg-agenda-dist@ietf.org; Thu, 03 Jan 2008 18:12:33 -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: <E1JAZEn-00009O-Lv@stiedprstage1.ietf.org>
Date: Thu, 03 Jan 2008 18:12:33 -0500
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 10, 2008
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 January 10, 2008 IESG Teleconference This agenda was generated at 18:12:33 EDT, January 3, 2008 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-psamp-sample-tech-10.txt Sampling and Filtering Techniques for IP Packet Selection (Proposed Standard) - 1 of 10 Token: Dan Romascanu o draft-ietf-enum-calendar-service-03.txt A Telephone Number Mapping (ENUM) Service Registration for Internet Calendaring Services (Proposed Standard) - 2 of 10 Token: Jon Peterson 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-sieve-body-07.txt Sieve Email Filtering: Body Extension (Proposed Standard) - 5 of 10 Token: Lisa Dusseault o draft-ietf-pkix-rfc3280bis-10.txt Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (Proposed Standard) - 6 of 10 Token: Sam Hartman o draft-ietf-psamp-protocol-09.txt Packet Sampling (PSAMP) Protocol Specifications (Proposed Standard) - 7 of 10 Token: Dan Romascanu o draft-simon-emu-rfc2716bis-12.txt The EAP TLS Authentication Protocol (Proposed Standard) - 8 of 10 Note: Joe Salowey is the proto shepherd Token: Sam Hartman 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-arkko-rfc2780-proto-update-01.txt IANA Allocation Guidelines for the Protocol Field (BCP) - 1 of 1 Token: Russ Housley 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-btns-prob-and-applic-06.txt Problem and Applicability Statement for Better Than Nothing Security (BTNS) (Informational) - 1 of 3 Token: Sam Hartman o draft-ietf-v6ops-802-16-deployment-scenarios-06.txt IPv6 Deployment Scenarios in 802.16 Networks (Informational) - 2 of 3 Token: Ron Bonica o draft-ietf-nea-requirements-05.txt Network Endpoint Assessment (NEA): Overview and Requirements (Informational) - 3 of 3 Token: Tim Polk 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 o draft-adolf-dvb-urn-03.txt A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB) (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 o vCard and CardDAV (vcarddav) - 1 of 3 Token: Chris o Routing Over Low power and Lossy networks (roll) - 2 of 3 Token: David o Cga & Send maIntenance (csi) - 3 of 3 Token: Jari 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 6.1 Approval of the IESG Policy on Autoresponse Messages Sent to IETF Mailing Lists (Chris Newman) 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