IESG agenda for 2006-02-02 telechat.
fenner@research.att.com (Bill Fenner) Mon, 30 January 2006 12:02 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3XjP-0001Pc-I0; Mon, 30 Jan 2006 07:02:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F3XjL-0001Ia-R6 for rtg-dir@megatron.ietf.org; Mon, 30 Jan 2006 07:02:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17044 for <rtg-dir@ietf.org>; Mon, 30 Jan 2006 07:00:17 -0500 (EST)
Received: from [192.20.225.110] (helo=mail-white.research.att.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F3Xu0-000149-32 for rtg-dir@ietf.org; Mon, 30 Jan 2006 07:13:00 -0500
Received: from frogbits.attlabs.att.com (frogbits.attlabs.att.com [135.197.129.116]) by mail-green.research.att.com (Postfix) with ESMTP id D7DBE88E5 for <rtg-dir@ietf.org>; Mon, 30 Jan 2006 07:01:38 -0500 (EST)
Received: from frogbits.attlabs.att.com (localhost [127.0.0.1]) by frogbits.attlabs.att.com (8.13.4/8.13.4) with ESMTP id k0UC0Tbm031736 for <rtg-dir@ietf.org>; Mon, 30 Jan 2006 04:00:29 -0800 (PST) (envelope-from fenner@frogbits.attlabs.att.com)
Received: (from fenner@localhost) by frogbits.attlabs.att.com (8.13.4/8.13.4/Submit) id k0UC0Ti0031735 for rtg-dir@ietf.org; Mon, 30 Jan 2006 04:00:29 -0800 (PST) (envelope-from fenner)
Date: Mon, 30 Jan 2006 04:00:29 -0800
Message-Id: <200601301200.k0UC0Ti0031735@frogbits.attlabs.att.com>
From: fenner@research.att.com
To: rtg-dir@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1924de3f9fb68e58c31920136007eb1
Subject: IESG agenda for 2006-02-02 telechat.
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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
IESG Agenda
Good approximation of what will be included in the Agenda of next
Telechat (2006-02-02).
Updated 2:2:39 EDT, January 30, 2006
-----------------------------------------------------------------------
1. Administrivia
1.1 Roll Call
1.2 Bash the Agenda
1.3 Approval of the Minutes of the past telechat
1.4 List of Remaining Action Items from Last Telechat
1.5 Review of 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
Area Date
APP LDAP: Authentication Methods and Security
Mechanisms (Proposed Standard) - 1 of 12
draft-ietf-ldapbis-authmeth-18.txt [Open Web
Ballot]
Token: Ted Hardie
RTG Definition of an RRO node-id subobject
(Proposed Standard) - 2 of 12
draft-ietf-mpls-nodeid-subobject-07.txt [Open
Web Ballot]
Token: Alex Zinin
RTG Anycast-RP using PIM (Proposed Standard) - 3
of 12
draft-ietf-pim-anycast-rp-04.txt [Open Web
Ballot]
Note: A -05 is coming to fix the Security
Considerations to point just to pim-sm-v2-new
and to fix some minor reference issues.
Token: Bill Fenner
INT Virtual Private LAN Service (Proposed
Standard) - 4 of 12
draft-ietf-l2vpn-vpls-bgp-06.txt [Open Web
Ballot]
Note: This document and
draft-ietf-l2vpn-vpls-ldp are different
solutions to similar problems. L2VPN agreed to
advance both and essentially "let the market
decide."
Token: Mark Townsley
INT Virtual Private LAN Services over MPLS
(Proposed Standard) - 5 of 12
draft-ietf-l2vpn-vpls-ldp-08.txt [Open Web
Ballot]
Note: This document and
draft-ietf-l2vpn-vpls-bgp are different
solutions to similar problems. L2VPN agreed to
advance both and essentially "let the market
decide."
Token: Mark Townsley
APP Lemonade Profile (Proposed Standard) - 6 of 12
draft-ietf-lemonade-profile-07.txt [Open Web
Ballot]
Token: Ted Hardie
INT The Role of Wildcards in the Domain Name
System (Proposed Standard) - 7 of 12
draft-ietf-dnsext-wcard-clarify-10.txt [Open
Web Ballot]
Note: The PROTO shepherd for this document is
Olaf Kolkman <olaf@nlnetlabs.nl>.
Token: Margaret Wasserman
A Resource Reservation Protocol Extension for
TSV the Reduction of Bandwidth of a Reservation
Flow (Proposed Standard) - 8 of 12
draft-ietf-tsvwg-rsvp-bw-reduction-02.txt
[Open Web Ballot]
Token: Allison Mankin
Using the GOST 28147-89, GOST R 34.11-94, GOST
SEC R 34.10-94 and GOST R 34.10-2001 algorithms
with the Cryptographic Message Syntax (CMS)
(Proposed Standard) - 9 of 12
draft-ietf-smime-gost-07.txt [Open Web Ballot]
Token: Russ Housley
Lightweight Directory Access Protocol (LDAP):
APP Technical Specification Road Map (Proposed
Standard) - 10 of 12
draft-ietf-ldapbis-roadmap-08.txt [Open Web
Ballot]
Token: Ted Hardie
SEC Kerberos Cryptosystem Negotiation Extension
(Proposed Standard) - 11 of 12
draft-zhu-kerb-enctype-nego-04.txt [Open Web
Ballot]
Note: Proto shepherd: jhutz@cmu.edu
Token: Sam Hartman
RAI RTP Payload Format for Video Codec 1 (VC-1)
(Proposed Standard) - 12 of 12
draft-ietf-avt-rtp-vc1-06.txt [Open Web
Ballot]
Note: PROTO shepherd Colin Perkins
csp@csperkins.org
Token: Allison Mankin
2.1.2 Returning Item
NONE
2.2 Individual Submissions
2.2.1 New Item
Area Date
SEC The AES-CMAC-96 Algorithm and its use with
IPsec (Proposed Standard) - 1 of 3
draft-songlee-aes-cmac-96-03.txt [Open Web
Ballot]
Token: Russ Housley
APP Collected extensions to IMAP4 ABNF
(Proposed Standard) - 2 of 3
draft-melnikov-imap-ext-abnf-08.txt [Open
Web Ballot]
Token: Scott Hollenbeck
APP COSINE LDAP/X.500 Schema (Proposed
Standard) - 3 of 3
draft-zeilenga-ldap-cosine-01.txt [Open Web
Ballot]
Token: Ted Hardie
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
NONE
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
Area Date
SEC US Secure Hash Algorithms (SHA)
(Informational) - 1 of 1
draft-eastlake-sha2-01.txt [Open Web
Ballot]
Token: Russ Housley
3.2.2 Returning Item
NONE
3.3 Individual 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.
Other matters may be recorded in comments to 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
Area Date
TSV Jan 13 Session PEERing for Multimedia
INTerconnect (speermint) - 1 of 1
Token: Allison
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
Area Date
GEN Jan 26 Intellectual Property Rights (ipr)
- 1 of 1
Token: Brian
4.2.2 Proposed for Approval
NONE
5. IAB News We Can Use
6. Management Issues
7. Working Group News
- IESG agenda for 2006-02-02 telechat. Bill Fenner