[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for August 27, 2009

IESG Secretary <iesg-secretary-reply@ietf.org> Fri, 21 August 2009 22:33 UTC

Return-Path: <wwwrun@core3.amsl.com>
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 B10B23A6C72; Fri, 21 Aug 2009 15:33:02 -0700 (PDT)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090821223302.B10B23A6C72@core3.amsl.com>
Date: Fri, 21 Aug 2009 15:33:02 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for August 27, 2009
X-BeenThere: iesg-agenda-dist@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distribution of IESG agendas <iesg-agenda-dist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iesg-agenda-dist>
List-Post: <mailto:iesg-agenda-dist@ietf.org>
List-Help: <mailto:iesg-agenda-dist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2009 22:33:02 -0000

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the August 27, 2009 IESG Teleconference

This agenda was generated at 15:33:2 EDT, August 21, 2009
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-simple-xcap-diff-13.txt
    An Extensible Markup Language (XML) Document Format for Indicating A Change 
    in XML Configuration Access Protocol (XCAP) Resources (Proposed Standard) - 
    1 of 7 
    Note: Ben Campbell is taking over as the document Shepherd 
    Token: Robert Sparks
  o draft-ietf-ippm-multimetrics-11.txt
    IP Performance Metrics (IPPM) for spatial and multicast (Proposed Standard) 
    - 2 of 7 
    Note: The document shepherd is Matt Zekauskas (matt@internet2.edu). 
    Token: Lars Eggert
  o draft-ietf-ospf-hmac-sha-06.txt
    OSPFv2 HMAC-SHA Cryptographic Authentication (Proposed Standard) - 3 of 7 
    Token: Ross Callon
  o draft-ietf-opsawg-syslog-alarm-02.txt
    Alarms in SYSLOG (Proposed Standard) - 4 of 7 
    Note: Scott Bradner (sob@harvard.edu) is the document shepherd. 
    Token: Dan Romascanu
  o draft-ietf-mext-binding-revocation-10.txt
    Binding Revocation for IPv6 Mobility (Proposed Standard) - 5 of 7 
    Note: Julien Laganier (julien.laganier.ietf@googlemail.com) is the document 
    shepherd. 
    Token: Jari Arkko
  o draft-ietf-vcarddav-webdav-mkcol-06.txt
    Extended MKCOL for WebDAV (Proposed Standard) - 6 of 7 
    Note: Julian Reschke &lt;julian.reschke@greenbytes.de&gt; agreed to 
    shepherd the document. 
    Token: Alexey Melnikov
  o draft-ietf-ntp-dhcpv6-ntp-opt-04.txt
    Network Time Protocol (NTP) Server Option for DHCPv6 (Proposed Standard) - 
    7 of 7 
    Note: Brian Haberman (brian@innovationslab.net) is the document shepherd. 
    Token: Ralph Droms

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
  o draft-green-secsh-ecc-08.txt
    Elliptic-Curve Algorithm Integration in the Secure Shell Transport Layer 
    (Proposed Standard) - 1 of 2 
    Note: Jeffrey Hutzelman (jhutz@cmu.edu) is document shepherd. 
    Token: Tim Polk
  o draft-housley-iesg-rfc3932bis-08.txt
    IESG Procedures for Handling of Independent and IRTF Stream Submissions 
    (BCP) - 2 of 2 
    Note: There is no document shepherd 
    Token: Jari Arkko


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-behave-nat-behavior-discovery-07.txt
    NAT Behavior Discovery Using STUN (Experimental) - 1 of 4 
    Token: Magnus Westerlund
  o draft-ietf-bmwg-mpls-forwarding-meth-05.txt
    MPLS Forwarding Benchmarking Methodology for IP Flows (Informational) - 2 
    of 4 
    Token: Ron Bonica
  o draft-ietf-mext-aero-reqs-04.txt
    Network Mobility Route Optimization Requirements for Operational Use in 
    Aeronautics and Space Exploration Mobile Networks (Informational) - 3 of 4 
    Note: Document Shepherd is Marcelo Bagnulo Braun &lt;marcelo@it.uc3m.es&gt; 
    Token: Jari Arkko
  o draft-ietf-pwe3-mpls-transport-04.txt
    Application of Ethernet Pseudowires to MPLS Transport Networks 
    (Informational) - 4 of 4 
    Note: Matthew Bocci (matthew.bocci@alcatel-lucent.com) is the document 
    shepherd 
    Token: Ralph Droms

3.1.2 Returning Item
  o draft-ietf-ospf-manet-or-02.txt
    Extensions to OSPF to Support Mobile Ad Hoc Networking (Experimental) - 1 
    of 1 
    Token: Ross Callon


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
NONE
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 Multicast Mobility (multimob) - 1 of 1
    Token: Jari
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Internationalized Domain Names in Applications, Revised (idnabis) - 1 of 2
    Token: Lisa
  o DNS Extensions (dnsext) - 2 of 2
    Token: Ralph

5. IAB News We can use

6. Management Issue

 6.1 Tracking changes to WG charters (Alexey Melnikov)

 6.2 Status of 128.66.0.0/16 [IANA #256883] (Michelle Cotton)

7. Working Group News