[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for April 23, 2009

IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 16 April 2009 21:29 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 9905B3A6946; Thu, 16 Apr 2009 14:29:08 -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: <20090416212908.9905B3A6946@core3.amsl.com>
Date: Thu, 16 Apr 2009 14:29:08 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for April 23, 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: Thu, 16 Apr 2009 21:29:08 -0000

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the April 23, 2009 IESG Teleconference

This agenda was generated at 14:29:8 EDT, April 16, 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 10 
    Note: IESG: Please read the Document Shepherd Writeup, we need to discuss 
    the "Updates: 793" issue. 
    Token: Lars Eggert
  o draft-ietf-radext-design-07.txt
    RADIUS Design Guidelines (BCP) - 2 of 10 
    Token: Dan Romascanu
  o draft-ietf-ipfix-exporting-type-03.txt
    Exporting Type Information for IPFIX Information Elements (Proposed 
    Standard) - 3 of 10 
    Token: Dan Romascanu
  o draft-ietf-ipfix-file-03.txt
    Specification of the IPFIX File Format (Proposed Standard) - 4 of 10 
    Token: Dan Romascanu
  o draft-ietf-dime-mip6-split-16.txt
    Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction 
    (Proposed Standard) - 5 of 10 
    Token: Dan Romascanu
  o draft-ietf-netlmm-grekey-option-06.txt
    GRE Key Option for Proxy Mobile IPv6 (Proposed Standard) - 6 of 10 
    Token: Jari Arkko
  o draft-ietf-dhc-container-opt-05.txt
    Container Option for Server Configuration (Proposed Standard) - 7 of 10 
    Token: Jari Arkko
  o draft-ietf-pkix-3281update-04.txt
    An Internet Attribute Certificate Profile for Authorization (Proposed 
    Standard) - 8 of 10 
    Token: Tim Polk
  o draft-ietf-dccp-serv-codes-08.txt
    The DCCP Service Code (Proposed Standard) - 9 of 10 
    Token: Lars Eggert
  o rfc3852.txt
    Cryptographic Message Syntax (CMS) (Draft Standard) - 10 of 10 
    Token: Tim Polk

2.1.2 Returning Item
  o draft-ietf-geopriv-radius-lo-23.txt
    Carrying Location Objects in RADIUS and Diameter (Proposed Standard) - 1 of 
    1 
    Note: Did new LC because previous one did not mention DOWNREF. 
    Token: Cullen Jennings


2.2 Individual Submissions
2.2.1 New Item
  o draft-atlas-icmp-unnumbered-06.txt
    Extending ICMP for Interface and Next-hop Identification (Proposed 
    Standard) - 1 of 1 
    Token: Jari Arkko

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 3 
    Token: Lars Eggert
  o draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt
    OSPFv2 Routing Protocols Extensions for ASON Routing (Experimental) - 2 of 
    3 
    Token: Adrian Farrel
  o draft-ietf-pana-statemachine-10.txt
    State Machines for Protocol for Carrying Authentication for Network Access 
    (PANA) (Informational) - 3 of 3 
    Token: Jari Arkko

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
  o draft-lochter-pkix-brainpool-ecc-03.txt
    ECC Brainpool Standard Curves and Curve Generation (Informational) - 1 of 2 
    Note: waiting for confirmation that no IPR disclosure is needed. 
    Token: Tim Polk
  o draft-bberry-rfc4938bis-00.txt
    PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics 
    (Informational) - 2 of 2 
    Token: Jari Arkko


4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o Open Web authentication (oauth) - 1 of 1
    Token: Lisa
4.1.2 Proposed for Approval
  o Multiple Interfaces (mif) - 1 of 3
    Token: Jari
  o Locator/ID Separation Protocol (lisp) - 2 of 3
    Token: Jari
  o Network-Based Mobility Extensions (netext) - 3 of 3
    Token: Jari
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

 6.1 LS response to ITU-T SG11 (Lars Eggert)

 6.2 Dean Anderson and tools.ietf.org (Russ Housley)

 6.3 Approve IANA expert for CAPWAP (Russ Housley)

 6.4 Assignment of media type action point to Alexey (Magnus Westerlund)

 6.5 ISOC BoT Appointment Confirmation (Executive Session) (Russ Housley)

 6.6 Last Call issue raised for draft-iana-rfc3330bis (Russ Housley)

7. Agenda Working Group News