[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for December 3, 2009

IESG Secretary <iesg-secretary-reply@ietf.org> Fri, 27 November 2009 23:03 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 DEA433A67A1; Fri, 27 Nov 2009 15:03:12 -0800 (PST)
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: <20091127230312.DEA433A67A1@core3.amsl.com>
Date: Fri, 27 Nov 2009 15:03:12 -0800
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for December 3, 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: Fri, 27 Nov 2009 23:03:13 -0000

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the December 3, 2009 IESG Teleconference

This agenda was generated at 15:3:12 EDT, November 27, 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-sasl-gs2-18.txt
    Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family (Proposed 
    Standard) - 1 of 8 
    Note: Alexey Melnikov (alexey.melnikov@isode.com) is the document shepherd 
    Token: Pasi Eronen
  o draft-ietf-ipfix-mib-08.txt
    Definitions of Managed Objects for IP Flow Information Export (Proposed 
    Standard) - 2 of 8 
    Token: Dan Romascanu
  o draft-ietf-tsvwg-rsvp-l3vpn-05.txt
    Support for RSVP in Layer 3 VPNs (Proposed Standard) - 3 of 8 
    Token: Magnus Westerlund
  o draft-ietf-pim-sm-linklocal-09.txt
    Authentication and Confidentiality in PIM-SM Link-local Messages (Proposed 
    Standard) - 4 of 8 
    Note: Document shepherd is Stig Venaas &lt;stig@venaas.com&gt; 
    Token: Adrian Farrel
  o draft-ietf-ospf-af-alt-09.txt
    Support of address families in OSPFv3 (Proposed Standard) - 5 of 8 
    Token: Ross Callon
  o draft-ietf-ospf-te-node-addr-06.txt
    Advertising a Router's Local Addresses in OSPF TE Extensions (Proposed 
    Standard) - 6 of 8 
    Note: Acee Lindem (acee@redback.com) is the document shepherd. 
    Token: Ross Callon
  o draft-ietf-ccamp-lsp-dppm-10.txt
    Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in 
    Generalized MPLS Networks (Proposed Standard) - 7 of 8 
    Note: Lou Berger (lberger@labn.net) is the document shepherd. 
    Token: Adrian Farrel
  o draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06.txt
    Transmission of IPv4 packets over IEEE 802.16's IP Convergence Sublayer 
    (Proposed Standard) - 8 of 8 
    Note: Gabriel Montenegro (g_e_montenegro@yahoo.com) is the document 
    shepherd. 
    Token: Ralph Droms

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-dusseault-http-patch-16.txt
    PATCH Method for HTTP (Proposed Standard) - 1 of 4 
    Note: Mark Nottingham &lt;mnot@mnot.net&gt; agreed to be the document 
    shepherd.. 
    Token: Alexey Melnikov
  o draft-klensin-ftp-registry-02.txt
    FTP Extension Registry (Proposed Standard) - 2 of 4 
    Note: Barry Leiba &lt;barryleiba@computer.org&gt; is the document 
    shepherd.. 
    Token: Alexey Melnikov
  o draft-nottingham-site-meta-04.txt
    Defining Well-Known URIs (Proposed Standard) - 3 of 4 
    Token: Lisa Dusseault
  o draft-melnikov-imap-keywords-07.txt
    IMAP4 Keyword Registry (Proposed Standard) - 4 of 4 
    Note: Barry Leiba &lt;barryleiba@computer.org&gt; is the document shepherd. 
    Token: Lisa Dusseault

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-hip-native-api-09.txt
    Basic Socket Interface Extensions for Host Identity Protocol (HIP) 
    (Experimental) - 1 of 1 
    Note: Gonzalo Camarillo (Gonzalo.Camarillo@ericsson.com) is the document 
    shepherd. 
    Token: Ralph Droms

3.1.2 Returning Item
  o draft-ietf-csi-sndp-prob-03.txt
    Securing Neighbor Discovery Proxy Problem Statement (Informational) - 1 of 
    1 
    Note: The document shepherd is Marcelo Bagnulo (marcelo@it.uc3m.es) 
    Token: Ralph Droms


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-combes-ipdvb-mib-rcs-08.txt
    The SatLabs Group DVB-RCS MIB (Informational) - 1 of 3 
    Note: Document Shepherd is Gorry Fairhurst &lt;gorry@erg.abdn.ac.uk&gt; 
    Token: Jari Arkko
  o draft-reschke-rfc2731bis-04.txt
    RFC 2731 ("Encoding Dublin Core Metadata in HTML") is Obsolete 
    (Informational) - 2 of 3 
    Note: Bernard Desruisseaux &lt;bernard.desruisseaux@oracle.com&gt; is the 
    document shepherd.. RFC Editor seems to be fine with the idea of obsoleting 
    an RFC submitted directly to RFC Editor (e.g. RFC 2731) with an AD 
    sponsored document. 
    Token: Alexey Melnikov
  o draft-hammer-oauth-07.txt
    The OAuth Core 1.0 Protocol (Informational) - 3 of 3 
    Token: Lisa Dusseault

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-wu-softwire-4over6-03.txt
    4over6 Transit Solution using IP Encapsulation and MP-BGP Extensions 
    (Experimental) - 1 of 1 
    Token: Ralph Droms


4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
  o HTTP State Management Mechanism (httpstate) - 1 of 1
    Token: Lisa
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 RIM IPR disclosure and application/3gpp-ims+xml media type registration (Alexey Melnikov)

7. Working Group News