[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for June 5, 2008
IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 29 May 2008 23:06 UTC
Return-Path: <iesg-agenda-dist-bounces@iesg.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 3DAC43A6B95; Thu, 29 May 2008 16:06:25 -0700 (PDT)
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 4F6133A6B3C; Thu, 29 May 2008 16:06:23 -0700 (PDT)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Mime-Version: 1.0
Message-Id: <20080529230624.4F6133A6B3C@core3.amsl.com>
Date: Thu, 29 May 2008 16:06:24 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for June 5, 2008
X-BeenThere: iesg-agenda-dist@iesg.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distribution of IESG agendas <iesg-agenda-dist.iesg.org>
List-Unsubscribe: <http://www.iesg.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@iesg.org?subject=unsubscribe>
List-Archive: <http://www.iesg.org/pipermail/iesg-agenda-dist>
List-Post: <mailto:iesg-agenda-dist@iesg.org>
List-Help: <mailto:iesg-agenda-dist-request@iesg.org?subject=help>
List-Subscribe: <http://www.iesg.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@iesg.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: iesg-agenda-dist-bounces@iesg.org
Errors-To: iesg-agenda-dist-bounces@iesg.org
INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the June 5, 2008 IESG Teleconference This agenda was generated at 16:6:24 EDT, May 29, 2008 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-ospf-ospfv3-traffic-11.txt Traffic Engineering Extensions to OSPF version 3 (Proposed Standard) - 1 of 12 Token: David Ward o Two-document ballot: - 2 of 12 - draft-ietf-idr-route-filter-16.txt Outbound Route Filtering Capability for BGP-4 (Proposed Standard) - draft-ietf-idr-bgp-prefix-orf-04.txt Address Prefix Based Outbound Route Filter for BGP-4 (Proposed Standard) Token: David Ward o draft-ietf-pim-join-attributes-03.txt Format for using TLVs in PIM messages (Proposed Standard) - 3 of 12 Token: David Ward o draft-ietf-syslog-tc-mib-08.txt Textual Conventions for Syslog Management (Proposed Standard) - 4 of 12 Token: Pasi Eronen o Two-document ballot: - 5 of 12 - draft-ietf-ipr-3978-incoming-09.txt Rights Contributors provide to the IETF Trust (BCP) - draft-ietf-ipr-outbound-rights-06.txt Advice to the Trustees of the IETF Trust on Rights to be Granted in IETF Documents (Informational) Token: Russ Housley o draft-ietf-rtgwg-ipfrr-spec-base-12.txt Basic Specification for IP Fast-Reroute: Loop-free Alternates (Proposed Standard) - 6 of 12 Token: David Ward o draft-ietf-bfd-base-08.txt Bidirectional Forwarding Detection (Proposed Standard) - 7 of 12 Token: Ross Callon o draft-ietf-bfd-multihop-06.txt BFD for Multihop Paths (Proposed Standard) - 8 of 12 Token: Ross Callon o draft-ietf-bfd-v4v6-1hop-08.txt BFD for IPv4 and IPv6 (Single Hop) (Proposed Standard) - 9 of 12 Token: Ross Callon o draft-ietf-bfd-generic-04.txt Generic Application of BFD (Proposed Standard) - 10 of 12 Token: Ross Callon o draft-ietf-bfd-mpls-05.txt BFD For MPLS LSPs (Proposed Standard) - 11 of 12 Token: Ross Callon o draft-ietf-tsvwg-emergency-rsvp-08.txt Resource ReSerVation Protovol (RSVP) Extensions for Emergency Services (Proposed Standard) - 12 of 12 Token: Magnus Westerlund 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-cridland-imap-context-05.txt Contexts for IMAP4 (Proposed Standard) - 1 of 1 Note: Alexey Melnikov <alexey.melnikov@isode.com> is the document shepherd Token: Chris Newman 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-pim-lasthop-threats-04.txt Host Threats to Protocol Independent Multicast (PIM) (Informational) - 1 of 2 Token: David Ward o draft-zhu-pkinit-ecc-04.txt ECC Support for PKINIT (Informational) - 2 of 2 Token: Tim Polk 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-snell-atompub-bidi-06.txt Atom Bidirectional Attribute (Experimental) - 1 of 2 Token: Lisa Dusseault o draft-monrad-sipping-3gpp-urn-namespace-02.txt A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP) (Informational) - 2 of 2 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 o 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 o Common Control and Measurement Plane (ccamp) - 1 of 3 Token: Ross o Path Computation Element (pce) - 2 of 3 Token: Ross o Multiprotocol Label Switching (mpls) - 3 of 3 Token: Ross 4.2.2 Proposed for Approval o EAP Method Update (emu) - 1 of 1 Token: Pasi 5. IAB News We can use 6. Management Issue 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@iesg.org http://www.iesg.org/mailman/listinfo/iesg-agenda-dist
- [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Te… IESG Secretary