Fwd: PRELIMINARY Agenda and Package for May 27, 2004 Telechat
Alex Zinin <zinin@psg.com> Fri, 21 May 2004 02:07 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12878 for <rtg-dir-archive@ietf.org>; Thu, 20 May 2004 22:07:23 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQzRT-0006o9-O6 for rtg-dir-archive@ietf.org; Thu, 20 May 2004 22:07:23 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQzQa-0006i2-00 for rtg-dir-archive@ietf.org; Thu, 20 May 2004 22:06:29 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BQzPz-0006bf-00 for rtg-dir-archive@ietf.org; Thu, 20 May 2004 22:05:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQzPA-000098-4n; Thu, 20 May 2004 22:05:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BQzMU-0007xG-Rj for rtg-dir@optimus.ietf.org; Thu, 20 May 2004 22:02:14 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12632 for <rtg-dir@ietf.org>; Thu, 20 May 2004 22:02:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BQzMR-0006IM-Nj for rtg-dir@ietf.org; Thu, 20 May 2004 22:02:11 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BQzLX-0006Dn-00 for rtg-dir@ietf.org; Thu, 20 May 2004 22:01:16 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1BQzL8-00068j-00 for rtg-dir@ietf.org; Thu, 20 May 2004 22:00:50 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1BQzL8-000Fkp-OG for rtg-dir@ietf.org; Fri, 21 May 2004 02:00:50 +0000
Date: Thu, 20 May 2004 19:00:49 -0700
From: Alex Zinin <zinin@psg.com>
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1077175362.20040520190049@psg.com>
To: rtg-dir@ietf.org
Subject: Fwd: PRELIMINARY Agenda and Package for May 27, 2004 Telechat
In-Reply-To: <200405202133.RAA27477@ietf.org>
References: <200405202133.RAA27477@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: rtg-dir-admin@ietf.org
Errors-To: rtg-dir-admin@ietf.org
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL,PRIORITY_NO_NAME autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Guys, FYI below. -- Alex http://www.psg.com/~zinin/ This is a forwarded message From: IESG Secretary <iesg-secretary@ietf.org> To: iesg@ietf.org Cc: bfuller@foretec.com, amyk@foretec.com Date: Thursday, May 20, 2004, 2:33:44 PM Subject: PRELIMINARY Agenda and Package for May 27, 2004 Telechat ===8<==============Original message text=============== INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the May 27, 2004 IESG Teleconference This agenda was generated at 16:51:28 EDT, May 20, 2004 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes 1.4 Review of Action Items 1.5 Review of Projects http://www.unreason.com/jfp/iesg-projects 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-dnsop-ipv6-transport-guidelines-02.txt DNS IPv6 transport operational guidelines (BCP) - 1 of 5 Note: WG Last Call issued on Nov 21st.. Participant in PROTO Team pilot:. Workgroup Chair Followup of AD Evaluation Comments. http://www.ietf.org/internet-drafts/draft-ietf-proto-ad-comments-pilot-00.txt Token: David Kessens o draft-ietf-enum-pres-00.txt Enumservice Registration for Presence Services (Proposed Standard) - 2 of 5 Note: 01 draft expected for a few nits - short document, so hold off reading. Token: Allison Mankin o draft-ietf-sip-join-03.txt The Session Inititation Protocol (SIP) 'Join' Header (Proposed Standard) - 3 of 5 Note: Note - security considerations details also in Section 4. . Participant in PROTO Team pilot:. Working Group Chair Followup of DISCUSS Comments. http://www.ietf.org/internet-drafts/draft-ietf-proto-wgchair-discuss-pilot-01.txt Token: Allison Mankin o draft-ietf-dnsext-nsec-rdata-06.txt DNSSEC NSEC RDATA Format (Proposed Standard) - 4 of 5 Note: 2004-05-20: On agenda for next IESG telechat. Token: Thomas Narten o draft-ietf-smime-rfc3369bis-03.txt Cryptographic Message Syntax (CMS) (Proposed Standard) - 5 of 5 Token: Steve Bellovin 2.1.2 Returning Item o draft-ietf-mpls-in-ip-or-gre-07.txt Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) (Proposed Standard) - 1 of 1 Note: The WG discussed comments from Pekka (add mandatory to implement source-address checking). The WG consensus was not in favor of them. My personal review of the technical arguements did not yield a solid reason to request the WG to add this feature to the spec. Token: Alex Zinin 2.2 Individual Submissions 2.2.1 New Item o draft-ietf-ops-rfc3291bis-04.txt Textual Conventions for Internet Network Addresses (Proposed Standard) - 1 of 3 Token: Bert Wijnen o draft-hollenbeck-epp-rgp-04.txt Redemption Grace Period Mapping for the Extensible Provisioning Protocol (Proposed Standard) - 2 of 3 Token: Ted Hardie o draft-daigle-snaptr-00.txt Domain-based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS) (Proposed Standard) - 3 of 3 Note: successor to daigle-naptsr-04.txt Token: Ted Hardie 2.2.2 Returning Item NONE 2.2.3 For Action o draft-riikonen-silc-spec-08.txt Secure Internet Live Conferencing (SILC), Protocol Specification (Proposed Standard) - 1 of 4 Token: Harald Alvestrand o draft-riikonen-silc-pp-08.txt SILC Packet Protocol (Proposed Standard) - 2 of 4 Token: Harald Alvestrand o draft-riikonen-silc-ke-auth-08.txt SILC Key Exchange and Authentication Protocols (Proposed Standard) - 3 of 4 Token: Harald Alvestrand o draft-riikonen-silc-commands-06.txt SILC Commands (Proposed Standard) - 4 of 4 Token: Harald Alvestrand 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-v6ops-isp-scenarios-analysis-02.txt Scenarios and Analysis for Introducing IPv6 into ISP Networks (Informational) - 1 of 2 Token: David Kessens o draft-ietf-v6ops-v6onbydefault-02.txt Issues with Dual Stack IPv6 on by Default (Informational) - 2 of 2 Token: David Kessens 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-baker-soap-media-reg-06.txt The 'application/soap+xml' media type (Informational) - 1 of 2 Token: Scott Hollenbeck o draft-friend-tls-lzs-compression-03.txt Transport Layer Security Protocol Compression Using LZS (Informational) - 2 of 2 Token: Steve Bellovin 3.2.2 Returning Item NONE 3.2.3 For Action o draft-riikonen-presence-attrs-03.txt User Online Presence and Information Attributes (Informational) - 1 of 2 Token: Harald Alvestrand o draft-riikonen-flags-payloads-04.txt SILC Message Flag Payloads (Informational) - 2 of 2 Token: Harald Alvestrand 3.3 Individual Submissions Via RFC Editor Reviews should focus on these questions: "Does this document represent an end run around the IETF's working groups or its procedures? Does this document present an incompatible change to IETF technologies as if it were compatible?" Other matters may be sent to the RFC Editor in private review. 3.3.1 New Item NONE 3.3.2 Returning Item o draft-turk-bgp-dos-06.txt Configuring BGP to Block Denial-of-Service Attacks (Informational) - 1 of 1 Note: Information for the write-up requested by the IESG has been missing for a few weeks. Token: Alex Zinin 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval o RADIUS EXTensions (radext) - 1 of 2 Token: David Kessens o Bidirectional Forwarding Detection (bfd) - 2 of 2 Token: Alex Zinin 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE