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

From: IESG Secretary <[email-masked]>
Date: Thu, 18 Sep 2008 22:04:17 -0700 (PDT)

INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the September 25, 2008 IESG Teleconference

This agenda was generated at 22:4:17 EDT, September 18, 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-sipping-race-examples-05.txt
    Example calls flows of race conditions in the Session Initiation Protocol 
    (SIP) (BCP) - 1 of 8 
    Token: Jon Peterson
  o draft-ietf-forces-model-15.txt
    ForCES Forwarding Element Model (Proposed Standard) - 2 of 8 
    Token: Ross Callon
  o draft-ietf-capwap-protocol-specification-12.txt
    CAPWAP Protocol Specification (Proposed Standard) - 3 of 8 
    Token: Dan Romascanu
  o draft-ietf-capwap-dhc-ac-option-01.txt
    CAPWAP Access Controller DHCP Option (Proposed Standard) - 4 of 8 
    Token: Dan Romascanu
  o draft-ietf-ccamp-isis-interas-te-extension-04.txt
    ISIS Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) 
    and Generalized MPLS (GMPLS) Traffic Engineering (Proposed Standard) - 5 of 
    8 
    Token: Ross Callon
  o draft-ietf-nfsv4-rpcsec-gss-v2-05.txt
    RPCSEC_GSS Version 2 (Proposed Standard) - 6 of 8 
    Note: Document Shepherd: Spencer Shepler ([email-masked]). 
    Token: Lars Eggert
  o draft-ietf-mipshop-mstp-solution-06.txt
    Mobility Services Framework Design (MSFD) (Proposed Standard) - 7 of 8 
    Token: Jari Arkko
  o draft-ietf-capwap-protocol-binding-ieee80211-08.txt
    CAPWAP Protocol Binding for IEEE 802.11 (Proposed Standard) - 8 of 8 
    Token: Dan Romascanu

2.1.2 Returning Item
  o draft-ietf-manet-packetbb-15.txt
    Generalized MANET Packet/Message Format (Proposed Standard) - 1 of 2 
    Token: Ross Callon
  o draft-ietf-manet-timetlv-07.txt
    Representing multi-value time in MANETs (Proposed Standard) - 2 of 2 
    Token: Ross Callon

2.2 Individual Submissions
2.2.1 New Item
  o draft-sanchez-webdav-current-principal-01.txt
    WebDAV Current Principal Extension (Proposed Standard) - 1 of 1 
    Token: Lisa Dusseault

2.2.2 Returning Item
  o draft-wilde-sms-uri-16.txt
    URI Scheme for GSM Short Message Service (Proposed Standard) - 1 of 1 
    Token: Lisa Dusseault

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-capwap-threat-analysis-04.txt
    CAPWAP Threat Analysis for IEEE 802.11 Deployments (Informational) - 1 of 1 
    Token: Dan Romascanu

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-templin-autoconf-dhcp-16.txt
    MANET Autoconfiguration using Virtual Enterprise Traversal (VET) 
    (Informational) - 1 of 1 
    Token: Ross Callon

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o Application-Layer Traffic Optimization (alto) - 1 of 1
    Token: Lisa
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 Softwires (softwire) - 1 of 1
    Token: Mark

5. IAB News We can use

6. Management Issue

 6.1 Review of arp-parameters request 2 of 2 [IANA #183428] (Michelle Cotton)

 6.2 Large Interim Mtgs (Russ Housley)

7. Agenda Working Group News

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