Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for October 22, 2009

From: IESG Secretary <[email-masked]>
Date: Thu, 15 Oct 2009 15:02:46 -0700 (PDT)

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2009-10-22).

1. Administrivia

1.1 Roll Call

1.2 Bash the Agenda

1.3 Approval of the Minutes of the past telechat

1.4 List of Remaining Action Items from Last Telechat

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

Area
Date

SEC

Signed syslog Messages (Proposed Standard) - 1 of 13

draft-ietf-syslog-sign-28.txt
[Open Web Ballot]

Token:

Pasi Eronen

TSV

Asynchronous Layered Coding (ALC) Protocol Instantiation (Proposed Standard) - 2 of 13

draft-ietf-rmt-pi-alc-revised-08.txt
[Open Web Ballot]

Note: WG Shepherd: Brian Adamson ([email-masked])

Token:

Magnus Westerlund

RAI

Certificate Management Service for The Session Initiation Protocol (SIP) (Proposed Standard) - 3 of 13

draft-ietf-sip-certs-09.txt
[Open Web Ballot]

Token:

Robert Sparks

SEC

Distribution of EAP based keys for handover and re-authentication (Proposed Standard) - 4 of 13

draft-ietf-hokey-key-mgm-09.txt
[Open Web Ballot]

Note: Glen Zorn ([email-masked]) is the document shepherd.

Token:

Tim Polk

INT

Fast Handovers for Proxy Mobile IPv6 (Proposed Standard) - 5 of 13

draft-ietf-mipshop-pfmipv6-09.txt
[Open Web Ballot]

Note: Vijay Devarapalli ([email-masked]) is the document shepherd.

Token:

Jari Arkko

APP

vCard Extensions to WebDAV (CardDAV) (Proposed Standard) - 6 of 13

draft-ietf-vcarddav-carddav-09.txt
[Open Web Ballot]

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

RTG

BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs (Proposed Standard) - 7 of 13

draft-ietf-l3vpn-2547bis-mcast-bgp-08.txt
[Open Web Ballot]

Token:

Ross Callon

SEC

Salted Challenge Response (SCRAM) SASL and GSS-API Mechanism (Proposed Standard) - 8 of 13

draft-ietf-sasl-scram-10.txt
[Open Web Ballot]

Note: Simon Josefsson ([email-masked]) is the document shepherd

Token:

Pasi Eronen

APP

Preliminary Evaluation of RFC 1652 for Advancement to Full Standard (Standard) - 9 of 13

draft-ietf-yam-rfc1652bis-pre-evaluation-00.txt
[Open Web Ballot]

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 <[email-masked]> has agreed to serve as the document shepherd, but note that there is no shepherding write-up for this document.

Token:

Alexey Melnikov

SEC

Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA (Proposed Standard) - 10 of 13

draft-ietf-pkix-sha2-dsa-ecdsa-10.txt
[Open Web Ballot]

Note: Document shepherd is Stephen Kent (WG chair).

Token:

Pasi Eronen

INT

Virtual Subnet Selection Options for DHCPv4 and DHCPv6 (Proposed Standard) - 11 of 13

draft-ietf-dhc-vpn-option-11.txt
[Open Web Ballot]

Note: John Jason Brzozowski ([email-masked]) is the document shepherd.

Token:

Ralph Droms

RTG

An Inband Data Communication Network For the MPLS Transport Profile (Proposed Standard) - 12 of 13

draft-ietf-mpls-tp-gach-dcn-06.txt
[Open Web Ballot]

Note: Loa Andersson ([email-masked]) is the document shepherd.

Token:

Ross Callon

INT

The DHCPv4 Relay Agent Identifier Suboption (Proposed Standard) - 13 of 13

draft-ietf-dhc-relay-id-suboption-07.txt
[Open Web Ballot]

Note: John Jason Brzozowski ([email-masked]) is the document shepherd.

Token:

Ralph Droms

2.1.2 Returning Item

Area
Date

RAI

Post-Repair Loss RLE Report Block Type for RTCP XR (Proposed Standard) - 1 of 1

draft-ietf-avt-post-repair-rtcp-xr-06.txt
[Open Web Ballot]

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

Area
Date

APP

URI Scheme for GSM Short Message Service (Proposed Standard) - 1 of 1

draft-wilde-sms-uri-19.txt
[Open Web Ballot]

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

Area
Date

APP

POP3 Support for UTF-8 (Experimental) - 1 of 2

draft-ietf-eai-pop-07.txt
[Open Web Ballot]

Note: Harald Alvestrand is the document shepherd.

Token:

Alexey Melnikov

SEC

IPv6 Configuration in IKEv2 (Experimental) - 2 of 2

draft-ietf-ipsecme-ikev2-ipv6-config-02.txt
[Open Web Ballot]

Note: Paul Hoffman ([email-masked]) is the document shepherd.

Token:

Tim Polk

3.1.2 Returning Item

Area
Date

SEC

Dec 4

Problem statement on the cross-realm operation of Kerberos (Informational) - 1 of 1

draft-ietf-krb-wg-cross-problem-statement-04.txt

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

Area
Date

INT

Sep 30

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 Issues

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

6.2 Planned boilerplate changes in xml2rfc (Alexey Melnikov)

7. Working Group News