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

IESG Secretary <iesg-secretary-reply@ietf.org> Fri, 04 April 2008 01:22 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 04C853A6DE0; Thu, 3 Apr 2008 18:22:14 -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 506C13A6DE9; Thu, 3 Apr 2008 18:22:09 -0700 (PDT)
Mime-Version: 1.0
To: iesg-agenda-dist@ietf.org
From: IESG Secretary <iesg-secretary-reply@ietf.org>
Message-Id: <20080404012210.506C13A6DE9@core3.amsl.com>
Date: Thu, 03 Apr 2008 18:22:10 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for April 10, 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 April 10, 2008 IESG Teleconference

This agenda was generated at 18:22:10 EDT, April 3, 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-netlmm-proxymip6-11.txt
    Proxy Mobile IPv6 (Proposed Standard) - 1 of 1 
    Note: Document Shepherd is Jonne Soininen 
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-mip4-vpn-problem-solution-05.txt
    Mobile IPv4 Traversal Across IPsec-based VPN Gateways (Proposed Standard) - 
    1 of 1 
    Note: Document Shepherd is Henrik Levkowetz 
    Token: Jari Arkko


2.2 Individual Submissions
2.2.1 New Item
  o draft-mraihi-inch-thraud-05.txt
    How to Share Transaction Fraud (Thraud) Report Data (Proposed Standard) - 1 
    of 1 
    Token: Tim Polk

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-enum-experiences-09.txt
    ENUM Implementation Issues and Experiences (Informational) - 1 of 2 
    Token: Jon Peterson
  o draft-ietf-sipping-sbc-funcs-05.txt
    Requirements from SIP (Session Initiation Protocol) Session Border Control 
    Deployments (Informational) - 2 of 2 
    Token: Jon Peterson

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
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
  o NETCONF Data Modeling Language (netmod) - 1 of 1
    Token: Dan
4.1.2 Proposed for Approval
  o Internationalized Domain Names in Applications (Revised) (idnabis) - 1 of 1
    Token: Lisa
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Multiparty Multimedia Session Control (mmusic) - 1 of 1
    Token: Cullen

5. IAB News We can use

6. Management Issue

 6.1 ISOC BoT Candidate Confirmation (Executive Session) (Russ Housley)

 6.2 Confirm results of IETF LC on draft-irtf-nmrg-snmp-measure-04.txt (Dan Romascanu)

7. Agenda Working Group News


_______________________________________________
IESG-AGENDA-DIST mailing list
IESG-AGENDA-DIST@iesg.org
http://www.iesg.org/mailman/listinfo/iesg-agenda-dist