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

From: IESG Secretary <[email-masked]>
Date: Thu, 5 Mar 2009 16:04:27 -0800 (PST)

IESG Agenda

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

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

TSV

Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) (Proposed Standard) - 1 of 9

draft-ietf-behave-turn-13.txt
[Open Web Ballot]

Token:

Magnus Westerlund

RAI

RTP payload format for mU-law EMbedded Codec for Low-delay IP communication (UEMCLIP) speech codec (Proposed Standard) - 2 of 9

draft-ietf-avt-rtp-uemclip-04.txt
[Open Web Ballot]

Note: The document shepherd is Roni Even.

Token:

Cullen Jennings

SEC

IPsec Channels: Connection Latching (Proposed Standard) - 3 of 9

draft-ietf-btns-connection-latching-08.txt
[Open Web Ballot]

Token:

Tim Polk

INT

Softwire Security Analysis and Requirements (Proposed Standard) - 4 of 9

draft-ietf-softwire-security-requirements-06.txt
[Open Web Ballot]

Token:

Mark Townsley

OPS

NETCONF Over Transport Layer Security (TLS) (Proposed Standard) - 5 of 9

draft-ietf-netconf-tls-07.txt
[Open Web Ballot]

Note: Mehmet Ersue is the PROTO-shepherd

Token:

Dan Romascanu

INT

Network Time Protocol Version 4 Protocol And Algorithms Specification (Proposed Standard) - 6 of 9

draft-ietf-ntp-ntpv4-proto-11.txt
[Open Web Ballot]

Token:

Mark Townsley

INT

Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) (Proposed Standard) - 7 of 9

draft-ietf-ntp-ntpv4-mib-05.txt
[Open Web Ballot]

Token:

Mark Townsley

APP

The Lemonade Profile (Proposed Standard) - 8 of 9

draft-ietf-lemonade-profile-bis-12.txt
[Open Web Ballot]

Note: Glenn Parsons is the Document Shepherd

Token:

Chris Newman

INT

Heartbeat Mechanism for Proxy Mobile IPv6 (Proposed Standard) - 9 of 9

draft-ietf-netlmm-pmipv6-heartbeat-05.txt
[Open Web Ballot]

Token:

Jari Arkko

2.1.2 Returning Item

Area
Date

APP

Netnews Architecture and Protocols (Proposed Standard) - 1 of 1

draft-ietf-usefor-usepro-14.txt
[Open Web Ballot]

Token:

Lisa Dusseault

2.2 Individual Submissions

2.2.1 New Item

Area
Date

GEN

Reduced Backus-Naur Form (RBNF) A Syntax Used in Various Protocol Specifications (Proposed Standard) - 1 of 2

draft-farrel-rtg-common-bnf-08.txt
[Open Web Ballot]

Token:

Ross Callon

APP

IMAP Response Codes (Proposed Standard) - 2 of 2

draft-gulbrandsen-imap-response-codes-07.txt

Note: Alexey Melnikov is document shepherd

Token:

Chris Newman

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

NONE

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

Area
Date

GEN

Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS) (Informational) - 1 of 1

draft-jones-dime-3gpp-eps-command-codes-01.txt
[Open Web Ballot]

Note: IETF LC ends on 3/5. A new revised I-D will be available immediatly after the Last Call.

Token:

Dan Romascanu

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

Mar 5

Locator/ID Separation Protocol (lisp) - 1 of 3

Token:

Jari

RAI

Feb 27

Session Initiation Protocol Core (sipcore) - 2 of 3

Token:

Cullen

RAI

Feb 27

Dispatch (dispatch) - 3 of 3

Token:

Cullen

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

Area
Date

INT

Feb 18

Ad-Hoc Network Autoconfiguration (autoconf) - 1 of 2

Token:

Jari

RTG

Feb 20

Routing Over Low power and Lossy networks (roll) - 2 of 2

Token:

David

5. IAB News We Can Use

6. Management Issues

7. Working Group News