[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for May 8, 2008
IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 01 May 2008 22:35 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1FD43A69A4; Thu, 1 May 2008 15:35:45 -0700 (PDT)
X-Original-To: iesg-agenda-dist@ietf.org
Delivered-To: tmdaiesgagen@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 862263A68E7; Thu, 1 May 2008 15:35:41 -0700 (PDT)
Mime-Version: 1.0
To: iesg-agenda-dist@ietf.org
From: IESG Secretary <iesg-secretary-reply@ietf.org>
Message-Id: <20080501223541.862263A68E7@core3.amsl.com>
Date: Thu, 01 May 2008 15:35:41 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for May 8, 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 May 8, 2008 IESG Teleconference This agenda was generated at 15:35:41 EDT, May 1, 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-iptel-tel-reg-05.txt The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry (Proposed Standard) - 1 of 11 Note: Jonathan Rosenberg is Proto Shepherd Token: Jon Peterson o draft-ietf-simple-imdn-07.txt Instant Message Disposition Notification (Proposed Standard) - 2 of 11 Token: Jon Peterson o draft-ietf-pim-bsr-mib-05.txt PIM Bootstrap Router MIB (Proposed Standard) - 3 of 11 Token: David Ward o draft-ietf-l1vpn-basic-mode-04.txt Layer 1 VPN Basic Mode (Proposed Standard) - 4 of 11 Token: David Ward o draft-ietf-mpls-upstream-label-05.txt MPLS Upstream Label Assignment and Context-Specific Label Space (Proposed Standard) - 5 of 11 Token: Ross Callon o draft-ietf-mpls-multicast-encaps-09.txt MPLS Multicast Encapsulations (Proposed Standard) - 6 of 11 Token: Ross Callon o draft-ietf-l1vpn-ospf-auto-discovery-05.txt OSPF Based Layer 1 VPN Auto-Discovery (Proposed Standard) - 7 of 11 Token: David Ward o draft-ietf-l1vpn-bgp-auto-discovery-04.txt BGP-based Auto-Discovery for Layer-1 VPNs (Proposed Standard) - 8 of 11 Token: David Ward o draft-ietf-mpls-ldp-interarea-03.txt LDP extension for Inter-Area LSP (Proposed Standard) - 9 of 11 Token: Ross Callon o draft-ietf-lemonade-convert-18.txt IMAP CONVERT extension (Proposed Standard) - 10 of 11 Note: Eric Burger is the document shepherd Token: Chris Newman o draft-ietf-tsvwg-rsvp-user-error-spec-07.txt User-Defined Errors for RSVP (Proposed Standard) - 11 of 11 Token: Magnus Westerlund 2.1.2 Returning Item o draft-ietf-ospf-ospfv3-update-21.txt OSPF for IPv6 (Proposed Standard) - 1 of 1 Token: David Ward 2.2 Individual Submissions 2.2.1 New Item o draft-klensin-rfc2821bis-10.txt Simple Mail Transfer Protocol (Draft Standard) - 1 of 1 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 o draft-ietf-ipfix-testing-05.txt Guidelines for IP Flow Information eXport (IPFIX) Testing (Informational) - 1 of 2 Note: Nevil Brownlee is the PROTO shepherd Token: Dan Romascanu o draft-ietf-v6ops-addcon-07.txt IPv6 Unicast Address Assignment Considerations (Informational) - 2 of 2 Token: Ron Bonica 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-vanelburg-sipping-served-user-05.txt The Session Initiation Protocol (SIP) P-Served-User Private-Header (P-Header) (Informational) - 1 of 2 Token: Jon Peterson o draft-iijima-netconf-soap-implementation-07.txt Experience of implementing NETCONF over SOAP (Informational) - 2 of 2 Token: Dan Romascanu 3.2.2 Returning Item o draft-wu-sava-testbed-experience-04.txt SAVA Testbed and Experiences to Date (Experimental) - 1 of 1 Token: Jari Arkko 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 o Three-document ballot: - 1 of 1 - draft-irtf-dtnrg-ltp-09.txt Licklider Transmission Protocol - Specification (Experimental) Note: Recommend RFC 3932 response #1: The IESG has not found any. conflict between this document and IETF work. - draft-irtf-dtnrg-ltp-extensions-07.txt Licklider Transmission Protocol - Security Extensions (Experimental) Note: Recommend RFC 3932 response #1: The IESG has not found any. conflict between this document and IETF work. - draft-irtf-dtnrg-ltp-motivation-06.txt Licklider Transmission Protocol - Motivation (Informational) Note: Recommend RFC 3932 response #1: The IESG has not found any. conflict between this document and IETF work. Token: Russ Housley 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Source Address Validation Improvements (savi) - 1 of 2 Token: Jari o Data for Reachability of Inter/tra-NetworK SIP (drinks) - 2 of 2 Token: Jon 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review o RADIUS EXTensions (radext) - 1 of 1 Token: Dan 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 6.1 Should default welcome message for IETF lists have the Note Well (Cullen Jennings) 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