Fwd: UPDATED Agenda and Package for June 10, 2004 Telechat
Alex Zinin <zinin@psg.com> Mon, 07 June 2004 23:22 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 TAA02387 for <rtg-dir-archive@ietf.org>; Mon, 7 Jun 2004 19:22:55 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXTSA-0001cH-P4 for rtg-dir-archive@ietf.org; Mon, 07 Jun 2004 19:22:54 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXTRA-00011G-00 for rtg-dir-archive@ietf.org; Mon, 07 Jun 2004 19:21:53 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BXTQZ-0000QN-00 for rtg-dir-archive@ietf.org; Mon, 07 Jun 2004 19:21:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXTJn-0003WY-3I; Mon, 07 Jun 2004 19:14:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BXTCf-0000pU-1z for rtg-dir@megatron.ietf.org; Mon, 07 Jun 2004 19:06:53 -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 TAA01618 for <rtg-dir@ietf.org>; Mon, 7 Jun 2004 19:06:49 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BXTCd-00005w-Bk for rtg-dir@ietf.org; Mon, 07 Jun 2004 19:06:51 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BXTBr-0007KU-00 for rtg-dir@ietf.org; Mon, 07 Jun 2004 19:06:04 -0400
Received: from psg.com ([147.28.0.62] ident=mailnull) by ietf-mx with esmtp (Exim 4.12) id 1BXTB5-0006ks-00 for rtg-dir@ietf.org; Mon, 07 Jun 2004 19:05:15 -0400
Received: from psg.com ([147.28.0.62] helo=[127.0.0.1]) by psg.com with esmtp (Exim 4.30; FreeBSD) id 1BXTB5-000OPC-NR for rtg-dir@ietf.org; Mon, 07 Jun 2004 23:05:15 +0000
Date: Mon, 07 Jun 2004 16:05:15 -0700
From: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <3110651711.20040607160515@psg.com>
To: rtg-dir@ietf.org
In-Reply-To: <200406072229.SAA29969@ietf.org>
References: <200406072229.SAA29969@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: Fwd: UPDATED Agenda and Package for June 10, 2004 Telechat
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Alex Zinin <zinin@psg.com>
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
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>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org
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
FYI. Comments /if any/ by Wed, please. -- 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: Monday, June 7, 2004, 3:29:18 PM Subject: UPDATED Agenda and Package for June 10, 2004 Telechat ===8<==============Original message text=============== INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the June 10, 2004 IESG Teleconference This agenda was generated at 17:23:6 EDT, June 7, 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 Two-document ballot: - 1 of 7 - draft-ietf-l3vpn-rfc2547bis-01.txt BGP/MPLS IP VPNs (Proposed Standard) - draft-ietf-l3vpn-as2547-05.txt Applicability Statement for BGP/MPLS IP VPNs (Informational) Token: Thomas Narten o draft-ietf-iptel-rfc2806bis-08.txt The tel URI for Telephone Numbers (Proposed Standard) - 2 of 7 Token: Jon Peterson o draft-ietf-ipsec-ikev2-14.txt Internet Key Exchange (IKEv2) Protocol (Proposed Standard) - 3 of 7 Token: Russ Housley o draft-ietf-tewg-mib-08.txt A Traffic Engineering MIB (Proposed Standard) - 4 of 7 Note: 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: Bert Wijnen o draft-iesg-rfced-documents-02.txt The IESG and RFC Editor documents: Procedures (BCP) - 5 of 7 Token: David Kessens o draft-ietf-send-ndopt-05.txt SEcure Neighbor Discovery (SEND) (Proposed Standard) - 6 of 7 Token: Margaret Wasserman o draft-ietf-smime-rfc2632bis-07.txt S/MIME Version 3.1 Certificate Handling (Proposed Standard) - 7 of 7 Token: Russ Housley 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-ietf-nat-natmib-09.txt Definitions of Managed Objects for Network Address Translators (NAT) (Proposed Standard) - 1 of 3 Note: Had careful MIB doctor review. Wrt function, allowed to configure. only the NAT's address range and not NAT/firewall binds or. firewall policies. This means no conflict with MIDCOM. Token: Allison Mankin o draft-ymbk-downref-02.txt Clarifying when Standards Track Documents may Refer Normatively to Documents at a Lower Level (BCP) - 2 of 3 Token: Harald Alvestrand o draft-klensin-process-july14-02.txt A model for IETF Process Experiments (BCP) - 3 of 3 Token: Harald Alvestrand 2.2.2 Returning Item NONE 2.2.3 For Action o draft-duerst-iri-08.txt Internationalized Resource Identifiers (IRIs) (Proposed Standard) - 1 of 1 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-ieprep-framework-09.txt Framework for Supporting ETS in IP Telephony (Informational) - 1 of 7 Token: Jon Peterson o draft-ietf-l3vpn-ppvpn-terminology-02.txt PPVPN terminology (Informational) - 2 of 7 Note: 2004-06-07: on IESG agenda for review; needed by other ppvpn documents. Token: Thomas Narten o draft-ietf-v6ops-application-transition-02.txt Application Aspects of IPv6 Transition (Informational) - 3 of 7 Note: 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: David Kessens o draft-ietf-dnsop-ipv6-dns-issues-07.txt Operational Considerations and Issues with IPv6 DNS (Informational) - 4 of 7 Note: 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-dnsop-misbehavior-against-aaaa-01.txt Common Misbehavior against DNS Queries for IPv6 Addresses (Informational) - 5 of 7 Note: 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-mboned-mroutesec-01.txt PIM-SM Multicast Routing Security Issues and Enhancements (Informational) - 6 of 7 Token: David Kessens o draft-ietf-rtgwg-igp-shortcut-01.txt Calculating IGP Routes Over Traffic Engineering Tunnels (Informational) - 7 of 7 Token: Alex Zinin 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-walker-ieee802-req-01.txt EAP Method Requirements for Wireless LANs (Informational) - 1 of 1 Note: To be reviewed by the IESG BLUE TEAM! Token: Margaret Wasserman 3.2.2 Returning Item NONE 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 o draft-wlai-tewg-bcmodel-04.txt Bandwidth Constraints Models for Diffserv-aware MPLS Traffic Engineering: Performance Evaluation (Informational) - 1 of 1 Token: Bert Wijnen 3.3.2 Returning Item o draft-dfncis-netnews-admin-sys-06.txt Netnews Administration System (NAS) (Experimental) - 1 of 1 Note: Re-review in light of new procedures for individual submissions via the RFC Editor. This one has been in the IESG's hands for two years! Token: Scott Hollenbeck 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 Protocol for carrying Authentication for Network Access (pana) - 1 of 3 Token: Thomas Narten o Extensible Authentication Protocol (eap) - 2 of 3 Token: Margaret Wasserman o Multiprotocol Label Switching (mpls) - 3 of 3 Token: Alex Zinin 4.2.2 Proposed for Approval NONE 5. Agenda Working Group News 6. IAB News We can use 7. Management Issue 7.1 PERM - Protected Entertainment Rights Management (Harald Alvestrand) 7.2 3667/3668 fix (Steve Bellovin)