[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for March 12, 2009

[IESG Secretary <[e-mail]>]

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the March 12, 2009 IESG Teleconference

This agenda was generated at 16:4:27 EDT, March 5, 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-behave-turn-13.txt
    Traversal Using Relays around NAT (TURN): Relay Extensions to Session 
    Traversal Utilities for NAT (STUN) (Proposed Standard) - 1 of 9 
    Token: Magnus Westerlund
  o draft-ietf-avt-rtp-uemclip-04.txt
    RTP payload format for mU-law EMbedded Codec for Low-delay IP communication 
    (UEMCLIP) speech codec (Proposed Standard) - 2 of 9 
    Note: The document shepherd is Roni Even. 
    Token: Cullen Jennings
  o draft-ietf-btns-connection-latching-08.txt
    IPsec Channels: Connection Latching (Proposed Standard) - 3 of 9 
    Token: Tim Polk
  o draft-ietf-softwire-security-requirements-06.txt
    Softwire Security Analysis and Requirements (Proposed Standard) - 4 of 9 
    Token: Mark Townsley
  o draft-ietf-netconf-tls-07.txt
    NETCONF Over Transport Layer Security (TLS) (Proposed Standard) - 5 of 9 
    Note: Mehmet Ersue is the PROTO-shepherd 
    Token: Dan Romascanu
  o draft-ietf-ntp-ntpv4-proto-11.txt
    Network Time Protocol Version 4 Protocol And Algorithms Specification 
    (Proposed Standard) - 6 of 9 
    Token: Mark Townsley
  o draft-ietf-ntp-ntpv4-mib-05.txt
    Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) 
    (Proposed Standard) - 7 of 9 
    Token: Mark Townsley
  o draft-ietf-lemonade-profile-bis-12.txt
    The Lemonade Profile (Proposed Standard) - 8 of 9 
    Note: Glenn Parsons is the Document Shepherd 
    Token: Chris Newman
  o draft-ietf-netlmm-pmipv6-heartbeat-05.txt
    Heartbeat Mechanism for Proxy Mobile IPv6 (Proposed Standard) - 9 of 9 
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-usefor-usepro-14.txt
    Netnews Architecture and Protocols (Proposed Standard) - 1 of 1 
    Token: Lisa Dusseault


2.2 Individual Submissions
2.2.1 New Item
  o draft-farrel-rtg-common-bnf-08.txt
    Reduced Backus-Naur Form (RBNF) A Syntax Used in Various Protocol 
    Specifications (Proposed Standard) - 1 of 2 
    Token: Ross Callon
  o draft-gulbrandsen-imap-response-codes-07.txt
    IMAP Response Codes (Proposed Standard) - 2 of 2 
    Note: Alexey Melnikov is 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
NONE
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-jones-dime-3gpp-eps-command-codes-01.txt
    Diameter Command Code Registration for Third Generation Partnership Project 
    (3GPP) Evolved Packet System (EPS) (Informational) - 1 of 1 
    Note: IETF LC ends on 3/5. A new revised I-D will be available immediatly 
    after the Last Call. 
    Token: Dan Romascanu

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
  o Locator/ID Separation Protocol (lisp) - 1 of 3
    Token: Jari
  o Session Initiation Protocol Core (sipcore) - 2 of 3
    Token: Cullen
  o Dispatch (dispatch) - 3 of 3
    Token: Cullen
4.1.2 Proposed for Approval
    NONE
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Network File System Version 4 (nfsv4) - 1 of 3
    Token: Lars
  o Ad-Hoc Network Autoconfiguration (autoconf) - 2 of 3
    Token: Jari
  o Routing Over Low power and Lossy networks (roll) - 3 of 3
    Token: David

5. IAB News We can use

6. Management Issue

7. Agenda Working Group News