[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for May 7, 2009

[IESG Secretary <[e-mail]>]

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the May 7, 2009 IESG Teleconference

This agenda was generated at 15:34:22 EDT, April 30, 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-tcpm-tcpsecure-11.txt
    Improving TCP's Robustness to Blind In-Window Attacks (Proposed Standard) - 
    1 of 11 
    Note: IESG: Please read the Document Shepherd Writeup, we need to discuss 
    the "Updates: 793" issue. 
    Token: Lars Eggert
  o draft-ietf-tsvwg-rsvp-proxy-proto-08.txt
    RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) 
    - 2 of 11 
    Note: Please read the informational document 
    draft-ietf-tsvwg-rsvp-proxy-approaches before this one! 
    Token: Magnus Westerlund
  o draft-ietf-mpls-p2mp-te-mib-09.txt
    Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic 
    Engineering (TE) Management Information Base (MIB) module (Proposed 
    Standard) - 3 of 11 
    Token: Ross Callon
  o draft-ietf-radext-design-07.txt
    RADIUS Design Guidelines (BCP) - 4 of 11 
    Token: Dan Romascanu
  o draft-ietf-mipshop-mos-dhcp-options-13.txt
    Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 
    802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 of 11 
    Token: Jari Arkko
  o draft-ietf-isms-tmsm-17.txt
    Transport Subsystem for the Simple Network Management Protocol (SNMP) 
    (Proposed Standard) - 6 of 11 
    Token: Pasi Eronen
  o draft-ietf-isms-transport-security-model-13.txt
    Transport Security Model for SNMP (Proposed Standard) - 7 of 11 
    Token: Pasi Eronen
  o draft-ietf-isms-secshell-16.txt
    Secure Shell Transport Model for SNMP (Proposed Standard) - 8 of 11 
    Token: Pasi Eronen
  o draft-ietf-isms-radius-usage-06.txt
    Remote Authentication Dial-In User Service (RADIUS) Usage for Simple 
    Network Management Protocol (SNMP) Transport Models (Proposed Standard) - 9 
    of 11 
    Token: Pasi Eronen
  o draft-ietf-dccp-serv-codes-09.txt
    The DCCP Service Code (Proposed Standard) - 10 of 11 
    Token: Lars Eggert
  o draft-ietf-mipshop-rfc5268bis-01.txt
    Mobile IPv6 Fast Handovers (Proposed Standard) - 11 of 11 
    Note: 
    http://www.arkko.com/ietf/mipshop/draft-ietf-mipshop-rfc5268bis-01-from-rfc5268.diff.html 
    Token: Jari Arkko

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-thomson-beep-async-02.txt
    Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP) 
    (Proposed Standard) - 1 of 2 
    Note: Chris Newman is the document shepherd.. 
    Token: Alexey Melnikov
  o draft-ncook-urlauth-accessid-02.txt
    Internet Message Access Protocol (IMAP) - URL Access Identifier Extension 
    (Proposed Standard) - 2 of 2 
    Note: Eric Burger is the document shepherd. This document is a Normative 
    dependency for a Lemonade WG document, updating another Lemonade document.. 
    Token: Alexey Melnikov

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-tcpm-ecnsyn-08.txt
    Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK 
    Packets (Experimental) - 1 of 5 
    Token: Lars Eggert
  o draft-ietf-lemonade-notifications-10.txt
    Lemonade Notifications Architecture (Informational) - 2 of 5 
    Note: Eric Burger is the document shepherd. 
    Token: Alexey Melnikov
  o draft-ietf-openpgp-camellia-04.txt
    The Camellia Cipher in OpenPGP (Informational) - 3 of 5 
    Note: Derek Atkins has agreed to shepherd 
    Token: Tim Polk
  o draft-ietf-roll-indus-routing-reqs-05.txt
    Industrial Routing Requirements in Low Power and Lossy Networks 
    (Informational) - 4 of 5 
    Note: This I-D was updated after IETF last call to synchronise with IESG 
    review comments made for draft-ietf-roll-urban-routing-reqs. It also pickes 
    up GenArt review coments. 
    Token: Adrian Farrel
  o draft-ietf-tsvwg-rsvp-proxy-approaches-06.txt
    RSVP Proxy Approaches (Informational) - 5 of 5 
    Note: Read this before the Protocol document 
    Token: Magnus Westerlund

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-p2pi-cooper-workshop-report-01.txt
    Report from the IETF workshop on P2P Infrastructure, May 28, 2008 
    (Informational) - 1 of 1 
    Token: Cullen Jennings

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
  o draft-brusilovsky-pak-10.txt
    Password-Authenticated Diffie-Hellman Exchange (PAK) (Informational) - 1 of 
    2 
    Token: Tim Polk
  o draft-templin-isatapv4-02.txt
    Transmission of IPv4 Packets over ISATAP Interfaces (Informational) - 2 of 
    2 
    Token: Jari Arkko

3.3.2 Returning Item
  o draft-saleem-msml-08.txt
    Media Server Markup Language (MSML) (Informational) - 1 of 1 
    Token: Robert Sparks


4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o Yet Another Mail (yam) - 1 of 3
    Token: Alexey
  o STORage Maintenance (storm) - 2 of 3
    Token: Lars
  o Extensible Messaging and Presence Protocol (xmpp) - 3 of 3
    Token: Cullen
4.1.2 Proposed for Approval
  o Open Authentication Protocol (oauth) - 1 of 1
    Token: Lisa
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
    NONE

5. IAB News We can use

6. Management Issue

7. Agenda Working Group News