Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for November 6, 2008

From: IESG Secretary <[email-masked]>
Date: Thu, 30 Oct 2008 15:31:13 -0700 (PDT)

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2008-11-06).

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

EAP Generalized Pre-Shared Key (EAP-GPSK) Method (Proposed Standard) - 1 of 7

draft-ietf-emu-eap-gpsk-16.txt
[Open Web Ballot]

Note: document shepherd: Joe Salowey <[email-masked]>

Token:

Pasi Eronen

RAI

The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) (Proposed Standard) - 2 of 7

draft-ietf-sip-sips-08.txt
[Open Web Ballot]

Note: The proto Shepherd for this document is Dean Willis.

Token:

Cullen Jennings

OPS

Information Model for Packet Sampling Exports (Proposed Standard) - 3 of 7

draft-ietf-psamp-info-11.txt
[Open Web Ballot]

Note: Juergen Quittek is the PROTO shepherd

Token:

Dan Romascanu

RAI

Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP) (Proposed Standard) - 4 of 7

draft-ietf-avt-dtls-srtp-06.txt
[Open Web Ballot]

Note: The document shepherd is Roni Even.

Token:

Cullen Jennings

TSV

Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol (BCP) - 5 of 7

draft-ietf-behave-dccp-04.txt
[Open Web Ballot]

Token:

Magnus Westerlund

RAI

Framework for Establishing an SRTP Security Context using DTLS (Proposed Standard) - 6 of 7

draft-ietf-sip-dtls-srtp-framework-05.txt
[Open Web Ballot]

Note: Last Call ends Oct 31. Dean Willis will act as the proto shepherd.

Token:

Cullen Jennings

RTG

Virtual Router Redundancy Protocol Version 3 for IPv4 and IPv6 (Proposed Standard) - 7 of 7

draft-ietf-vrrp-unified-spec-02.txt
[Open Web Ballot]

Token:

David Ward

2.1.2 Returning Item

NONE

2.2 Individual Submissions

2.2.1 New Item

NONE

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

Area
Date

TSV

Test vectors for STUN (Informational) - 1 of 2

draft-ietf-behave-stun-test-vectors-03.txt
[Open Web Ballot]

Token:

Magnus Westerlund

RTG

AS Number Reservation for Documentation Use (Informational) - 2 of 2

draft-ietf-idr-as-documentation-reservation-00.txt
[Open Web Ballot]

Token:

David Ward

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

Considerations for Having a Successful BOF (Informational) - 1 of 2

draft-narten-successful-bof-03.txt
[Open Web Ballot]

Token:

Russ Housley

GEN

Suite B Profile for Transport Layer Security (TLS) (Informational) - 2 of 2

draft-rescorla-tls-suiteb-09.txt
[Open Web Ballot]

Token:

Tim Polk

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

TSV

Oct 21

Techniques for Advanced Networking Applications (tana) - 1 of 1

Token:

Lars

4.1.2 Proposed for Approval

Area
Date

APP

Sep 18

Application-Layer Traffic Optimization (alto) - 1 of 1

Token:

Lisa

4.2 WG Rechartering

4.2.1 Under evaluation for IETF Review

NONE

4.2.2 Proposed for Approval

Area
Date

TSV

Oct 15

Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2

Token:

Magnus

INT

Oct 16

Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) - 2 of 2

Token:

Jari

5. IAB News We Can Use

6. Management Issues

6.1 Message to IANA regarding address range reservation for IETF protocols (Russ Housley)

6.2 Large Interim Meeting Agenda (Russ Housley)

7. Working Group News

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