[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for October 22, 2009

[IESG Secretary <[e-mail]>]

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the October 22, 2009 IESG Teleconference

This agenda was generated at 15:2:46 EDT, October 15, 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-syslog-sign-28.txt
    Signed syslog Messages (Proposed Standard) - 1 of 13 
    Token: Pasi Eronen
  o draft-ietf-rmt-pi-alc-revised-08.txt
    Asynchronous Layered Coding (ALC) Protocol Instantiation (Proposed 
    Standard) - 2 of 13 
    Note: WG Shepherd: Brian Adamson ([e-mail]) 
    Token: Magnus Westerlund
  o draft-ietf-sip-certs-09.txt
    Certificate Management Service for The Session Initiation Protocol (SIP) 
    (Proposed Standard) - 3 of 13 
    Token: Robert Sparks
  o draft-ietf-hokey-key-mgm-09.txt
    Distribution of EAP based keys for handover and re-authentication (Proposed 
    Standard) - 4 of 13 
    Note: Glen Zorn ([e-mail]) is the document shepherd. 
    Token: Tim Polk
  o draft-ietf-mipshop-pfmipv6-09.txt
    Fast Handovers for Proxy Mobile IPv6 (Proposed Standard) - 5 of 13 
    Note: Vijay Devarapalli ([e-mail]) is the document shepherd. 
    Token: Jari Arkko
  o draft-ietf-vcarddav-carddav-09.txt
    vCard Extensions to WebDAV (CardDAV) (Proposed Standard) - 6 of 13 
    Note: Due to WG chairs being busy I didn't get the write-up in time. 
    (Chairs were happy for the document to be sent to IESG review though.). So 
    I've decided to do the shepherding write-up myself.. . Note that security 
    related comments from Brian Carpenter's GenArt review are addressed using 
    RFC Editor notes.. 
    Token: Alexey Melnikov
  o draft-ietf-l3vpn-2547bis-mcast-bgp-08.txt
    BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs (Proposed 
    Standard) - 7 of 13 
    Token: Ross Callon
  o draft-ietf-sasl-scram-10.txt
    Salted Challenge Response (SCRAM) SASL and GSS-API Mechanism (Proposed 
    Standard) - 8 of 13 
    Note: Simon Josefsson ([e-mail]) is the document shepherd 
    Token: Pasi Eronen
  o draft-ietf-yam-rfc1652bis-pre-evaluation-00.txt
    Preliminary Evaluation of RFC 1652 for Advancement to Full Standard 
    (Standard) - 9 of 13 
    Note: This draft contains the list of changes planned by the YAM WG to move 
    RFC 1652 to Full Standard. There is no intention to publish this document 
    as an RFC, so IESG should vote on this document as if RFC 1652 is advancing 
    to Full Standard.. S Moonesamy <[e-mail]> has agreed to 
    serve as the document shepherd, but note that there is no shepherding 
    write-up for this document. 
    Token: Alexey Melnikov
  o draft-ietf-pkix-sha2-dsa-ecdsa-10.txt
    Internet X.509 Public Key Infrastructure: Additional Algorithms and 
    Identifiers for DSA and ECDSA (Proposed Standard) - 10 of 13 
    Note: Document shepherd is Stephen Kent (WG chair). 
    Token: Pasi Eronen
  o draft-ietf-dhc-vpn-option-11.txt
    Virtual Subnet Selection Options for DHCPv4 and DHCPv6 (Proposed Standard) 
    - 11 of 13 
    Note: John Jason Brzozowski ([e-mail]) is the 
    document shepherd. 
    Token: Ralph Droms
  o draft-ietf-mpls-tp-gach-dcn-06.txt
    An Inband Data Communication Network For the MPLS Transport Profile 
    (Proposed Standard) - 12 of 13 
    Note: Loa Andersson ([e-mail]) is the document shepherd. 
    Token: Ross Callon
  o draft-ietf-dhc-relay-id-suboption-07.txt
    The DHCPv4 Relay Agent Identifier Suboption (Proposed Standard) - 13 of 13 
    Note: John Jason Brzozowski ([e-mail]) is the 
    document shepherd. 
    Token: Ralph Droms

2.1.2 Returning Item
  o draft-ietf-avt-post-repair-rtcp-xr-06.txt
    Post-Repair Loss RLE Report Block Type for RTCP XR (Proposed Standard) - 1 
    of 1 
    Note: This draft still needs to be put on an IESG agenda 
    Token: Cullen Jennings


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
  o draft-wilde-sms-uri-19.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-eai-pop-07.txt
    POP3 Support for UTF-8 (Experimental) - 1 of 2 
    Note: Harald Alvestrand is the document shepherd. 
    Token: Alexey Melnikov
  o draft-ietf-ipsecme-ikev2-ipv6-config-02.txt
    IPv6 Configuration in IKEv2 (Experimental) - 2 of 2 
    Note: Paul Hoffman ([e-mail]) is the document shepherd. 
    Token: Tim Polk

3.1.2 Returning Item
  o draft-ietf-krb-wg-cross-problem-statement-04.txt
    Problem statement on the cross-realm operation of Kerberos (Informational) 
    - 1 of 1 
    Token: Tim Polk


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 Internet Area Working Group (intareawg) - 1 of 1
    Token: Jari
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
    NONE

5. IAB News We can use

6. Management Issue

 6.1 Link Relations Request [IANA #259813] (Lisa Dusseault)

 6.2 Planned boilerplate changes in xml2rfc (Alexey Melnikov)

7. Working Group News