IESG agenda for 2008-06-05 telechat.
fenner@fenron.com (Bill Fenner) Mon, 02 June 2008 11:00 UTC
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D74BA3A6C99; Mon, 2 Jun 2008 04:00:28 -0700 (PDT)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 76C3F3A67B2 for <rtg-dir@core3.amsl.com>; Mon, 2 Jun 2008 04:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6r188ACnlnz for <rtg-dir@core3.amsl.com>; Mon, 2 Jun 2008 04:00:26 -0700 (PDT)
Received: from runaway.fenron.com (unknown [IPv6:2001:470:117:128:230:48ff:fe92:8e81]) by core3.amsl.com (Postfix) with ESMTP id D37CD3A6844 for <rtg-dir@ietf.org>; Mon, 2 Jun 2008 04:00:04 -0700 (PDT)
Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id m52B02xM016838 for <rtg-dir@ietf.org>; Mon, 2 Jun 2008 04:00:02 -0700 (PDT) (envelope-from fenner@runaway.fenron.com)
Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id m52B02eY016831 for rtg-dir@ietf.org; Mon, 2 Jun 2008 04:00:02 -0700 (PDT) (envelope-from fenner)
Date: Mon, 02 Jun 2008 04:00:02 -0700
Message-Id: <200806021100.m52B02eY016831@runaway.fenron.com>
From: fenner@fenron.com
To: rtg-dir@ietf.org
Subject: IESG agenda for 2008-06-05 telechat.
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.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 (2008-06-05).
-----------------------------------------------------------------------
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
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
RTG Traffic Engineering Extensions to OSPF
version 3 (Proposed Standard) - 1 of 12
draft-ietf-ospf-ospfv3-traffic-11.txt [Open
Web Ballot]
Token: David Ward
RTG Two-Document ballot: [Open Web Ballot] - 2
of 12
Outbound Route Filtering Capability for
BGP-4 (Proposed Standard) - 2 of 12
draft-ietf-idr-route-filter-16.txt
Address Prefix Based Outbound Route Filter
for BGP-4 (Proposed Standard)
draft-ietf-idr-bgp-prefix-orf-04.txt
Token: David Ward
RTG Format for using TLVs in PIM messages
(Proposed Standard) - 3 of 12
draft-ietf-pim-join-attributes-03.txt [Open
Web Ballot]
Token: David Ward
SEC Textual Conventions for Syslog Management
(Proposed Standard) - 4 of 12
draft-ietf-syslog-tc-mib-08.txt [Open Web
Ballot]
Token: Pasi Eronen
GEN Two-Document ballot: [Open Web Ballot] - 5
of 12
Rights Contributors provide to the IETF
Trust (BCP) - 5 of 12
draft-ietf-ipr-3978-incoming-09.txt
Advice to the Trustees of the IETF Trust on
Rights to be Granted in IETF Documents
(Informational)
draft-ietf-ipr-outbound-rights-06.txt
Token: Russ Housley
Basic Specification for IP Fast-Reroute:
RTG Loop-free Alternates (Proposed Standard) - 6
of 12
draft-ietf-rtgwg-ipfrr-spec-base-12.txt
[Open Web Ballot]
Token: David Ward
RTG Bidirectional Forwarding Detection (Proposed
Standard) - 7 of 12
draft-ietf-bfd-base-08.txt [Open Web Ballot]
Token: Ross Callon
RTG BFD for Multihop Paths (Proposed Standard) -
8 of 12
draft-ietf-bfd-multihop-06.txt [Open Web
Ballot]
Token: Ross Callon
RTG BFD for IPv4 and IPv6 (Single Hop) (Proposed
Standard) - 9 of 12
draft-ietf-bfd-v4v6-1hop-08.txt [Open Web
Ballot]
Token: Ross Callon
RTG Generic Application of BFD (Proposed
Standard) - 10 of 12
draft-ietf-bfd-generic-04.txt [Open Web
Ballot]
Token: Ross Callon
RTG BFD For MPLS LSPs (Proposed Standard) - 11
of 12
draft-ietf-bfd-mpls-05.txt [Open Web Ballot]
Token: Ross Callon
Resource ReSerVation Protovol (RSVP)
TSV Extensions for Emergency Services (Proposed
Standard) - 12 of 12
draft-ietf-tsvwg-emergency-rsvp-08.txt [Open
Web Ballot]
Token: Magnus Westerlund
2.1.2 Returning Item
NONE
2.2 Individual Submissions
2.2.1 New Item
Area Date
APP Contexts for IMAP4 (Proposed Standard) - 1
of 2
draft-cridland-imap-context-05.txt [Open
Web Ballot]
Note: Alexey Melnikov
<alexey.melnikov@isode.com> is the
document shepherd
Token: Chris Newman
GEN Sieve Email Filtering: Date and Index
Extensions (Proposed Standard) - 2 of 2
draft-freed-sieve-date-index-12.txt [Open
Web Ballot]
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
Area Date
TSV Four-Document ballot: [Open Web Ballot] - 1
of 4
Aggregate Server Access Protocol (ASAP)
(Experimental) - 1 of 4
draft-ietf-rserpool-asap-20.txt
Note: Before reading this ballot set please
read draft-ietf-rserpool-overview
Endpoint Handlespace Redundancy Protocol
(ENRP) (Experimental)
draft-ietf-rserpool-enrp-20.txt
Note: Before reading this ballot set please
read draft-ietf-rserpool-overview
Aggregate Server Access Protocol (ASAP) and
Endpoint Handlespace Redundancy Protocol
(ENRP) Parameters (Experimental)
draft-ietf-rserpool-common-param-17.txt
Note: Before reading this ballot set please
read draft-ietf-rserpool-overview
Reliable Server Pooling Policies
(Experimental)
draft-ietf-rserpool-policies-09.txt
Note: Before reading this ballot set please
read draft-ietf-rserpool-overview
Token: Magnus Westerlund
TSV An Overview of Reliable Server Pooling
Protocols (Informational) - 2 of 4
draft-ietf-rserpool-overview-06.txt [Open
Web Ballot]
Note: Doc Shepherd: Maureen Stillman
Token: Magnus Westerlund
RTG Host Threats to Protocol Independent
Multicast (PIM) (Informational) - 3 of 4
draft-ietf-pim-lasthop-threats-04.txt [Open
Web Ballot]
Token: David Ward
SEC ECC Support for PKINIT (Informational) - 4
of 4
draft-zhu-pkinit-ecc-04.txt [Open Web
Ballot]
Token: Tim Polk
3.1.2 Returning Item
Area Date
Threats Introduced by RSerPool and
TSV Requirements for Security in Response to
Threats (Informational) - 1 of 1
draft-ietf-rserpool-threats-12.txt [Open Web
Ballot]
Note: PROTO Shepherd: Maureen Stillman
Please read RSERPOOL Overview document and
the protocol specifications first.
Token: Magnus Westerlund
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
APP Atom Bidirectional Attribute (Experimental) -
1 of 2
draft-snell-atompub-bidi-06.txt [Open Web
Ballot]
Token: Lisa Dusseault
A Uniform Resource Name (URN) Namespace for
GEN the 3rd Generation Partnership Project (3GPP)
(Informational) - 2 of 2
draft-monrad-sipping-3gpp-urn-namespace-02.txt
[Open Web Ballot]
Token: Lisa Dusseault
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
4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
NONE
4.1.2 Proposed for Approval
Area Date
RAI May 1 Data for Reachability of Inter/
tra-NetworK SIP (drinks) - 1 of 1
Token: Jon
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
Area Date
RTG May 28 Common Control and Measurement
Plane (ccamp) - 1 of 3
Token: Ross
RTG May 16 Path Computation Element (pce) - 2
of 3
Token: Ross
RTG May 28 Multiprotocol Label Switching
(mpls) - 3 of 3
Token: Ross
4.2.2 Proposed for Approval
Area Date
SEC May 5 EAP Method Update (emu) - 1 of
1
Token: Pasi
5. IAB News We Can Use
6. Management Issues
7. Working Group News
- IESG agenda for 2008-06-05 telechat. Bill Fenner