Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for April 24, 2008

From: IESG Secretary <[email-masked]>
Date: Thu, 17 Apr 2008 15:14:50 -0700 (PDT)

INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the April 24, 2008 IESG Teleconference

This agenda was generated at 15:14:50 EDT, April 17, 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-nfsv4-nfsdirect-08.txt
    NFS Direct Data Placement (Proposed Standard) - 1 of 4 
    Note: Document Shepherd: Spencer Shepler ([email-masked]) 
    Token: Lars Eggert
  o draft-ietf-nfsv4-rpcrdma-08.txt
    Remote Direct Memory Access Transport for Remote Procedure Call (Proposed 
    Standard) - 2 of 4 
    Note: Document Shepherd: Spencer Shepler ([email-masked]) 
    Token: Lars Eggert
  o draft-ietf-mipshop-4140bis-02.txt
    Hierarchical Mobile IPv6 Mobility Management (HMIPv6) (Proposed Standard) - 
    3 of 4 
    Note: Document shepherd is Vijay Devarapalli 
    Token: Jari Arkko
  o draft-ietf-dccp-dtls-06.txt
    Datagram Transport Layer Security (DTLS) over the Datagram Congestion 
    Control Protocol (DCCP) (Proposed Standard) - 4 of 4 
    Note: Document Shepherd: Gorry Fairhurst ([email-masked]) - DCCP WG 
    Chair 
    Token: Lars Eggert

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-hansen-4468upd-mailesc-registry-04.txt
    A Registry for SMTP Enhanced Mail System Status Codes (BCP) - 1 of 2 
    Note: Harald Alvestrand is document shepherd 
    Token: Chris Newman
  o draft-freed-sieve-environment-05.txt
    Sieve Email Filtering: Environment Extension (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
  o draft-ietf-pce-policy-enabled-path-comp-03.txt
    Policy-Enabled Path Computation Framework (Informational) - 1 of 1 
    Token: Ross Callon

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-funk-eap-ttls-v0-04.txt
    EAP Tunneled TLS Authentication Protocol Version 0 (EAP-TTLSv0) 
    (Informational) - 1 of 1 
    Note: Laksminath Dondeti is the Document Shepherd 
    Token: Jari Arkko

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 NETCONF Data Modeling Language (netmod) - 1 of 1
    Token: Dan
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

_______________________________________________
IESG-AGENDA-DIST mailing list
[email-masked]
http://www.iesg.org/mailman/listinfo/iesg-agenda-dist