[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 29, 2009
IESG Secretary <iesg-secretary-reply@ietf.org> Fri, 23 January 2009 14:58 UTC
Return-Path: <iesg-agenda-dist-bounces@ietf.org>
X-Original-To: iesg-agenda-dist-archive@optimus.ietf.org
Delivered-To: ietfarch-iesg-agenda-dist-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70C7328C1D1; Fri, 23 Jan 2009 06:58:26 -0800 (PST)
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 61CA33A6ABF; Fri, 23 Jan 2009 06:58:24 -0800 (PST)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Mime-Version: 1.0
Message-Id: <20090123145825.61CA33A6ABF@core3.amsl.com>
Date: Fri, 23 Jan 2009 06:58:25 -0800
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 29, 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/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://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: iesg-agenda-dist-bounces@ietf.org
Errors-To: iesg-agenda-dist-bounces@ietf.org INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the January 29, 2009 IESG Teleconference This agenda was generated at 6:58:25 EDT, January 23, 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-mext-nemo-mib-04.txt NEMO Management Information Base (Proposed Standard) - 1 of 10 Token: Jari Arkko o draft-ietf-radext-management-authorization-06.txt Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management (Proposed Standard) - 2 of 10 Token: Dan Romascanu o draft-ietf-pkix-rfc4055-update-01.txt Update for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3 of 10 Token: Pasi Eronen o draft-ietf-softwire-mesh-framework-05.txt Softwire Mesh Framework (Proposed Standard) - 4 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-safi-04.txt BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute (Proposed Standard) - 5 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-ipsec-01.txt BGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 6 of 10 Token: Mark Townsley o draft-ietf-softwire-bgp-te-attribute-04.txt BGP Traffic Engineering Attribute (Proposed Standard) - 7 of 10 Token: Mark Townsley o draft-ietf-softwire-v4nlri-v6nh-01.txt Advertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) - 8 of 10 Token: Mark Townsley o draft-ietf-tls-psk-new-mac-aes-gcm-05.txt Pre-Shared Key Cipher Suites for Transport Layer Security (TLS) with SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 9 of 10 Note: Document Shepherd is jsalowey@cisco.com Token: Pasi Eronen o draft-ietf-idr-flow-spec-04.txt Dissemination of flow specification rules (Proposed Standard) - 10 of 10 Token: David Ward 2.1.2 Returning Item o draft-ietf-mipshop-mstp-solution-11.txt IEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed Standard) - 1 of 1 Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item o draft-stjohns-sipso-06.txt Common Architecture Label IPv6 Security Option (CALIPSO) (Proposed Standard) - 1 of 4 Token: Tim Polk o draft-hoffman-dac-vbr-05.txt Vouch By Reference (Proposed Standard) - 2 of 4 Token: Russ Housley o draft-loreto-simple-im-srv-label-03.txt Internet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) (Proposed Standard) - 3 of 4 Token: Jon Peterson o draft-melnikov-sieve-imapext-metadata-08.txt The Sieve mail filtering language - extensions for checking mailbox status and accessing mailbox metadata (Proposed Standard) - 4 of 4 Token: Lisa Dusseault 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-speermint-terminology-17.txt SPEERMINT Terminology (Informational) - 1 of 4 Token: Jon Peterson o draft-ietf-trill-prob-05.txt Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (Informational) - 2 of 4 Token: Mark Townsley o draft-ietf-pim-rpf-vector-08.txt The RPF Vector TLV (Informational) - 3 of 4 Token: David Ward o draft-ietf-tls-ecdhe-psk-05.txt ECDHE_PSK Ciphersuites for Transport Layer Security (TLS) (Informational) - 4 of 4 Token: Pasi Eronen 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 3.3.3 For Action o draft-irtf-routing-history-09.txt Analysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2 Token: Russ Housley o draft-irtf-routing-reqs-10.txt A Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2 Token: Russ Housley 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 o Network Configuration (netconf) - 1 of 2 Token: Dan o IP Performance Metrics (ippm) - 2 of 2 Token: Lars 5. IAB News We can use 6. Management Issue 6.1 IESG Statement regarding chartered work overcome by events before IESG consideration (Ron Bonica) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist
- [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Te… IESG Secretary
- [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Te… IESG Secretary