IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2005-01-20).

Updated 18:21:13 EDT, January 13, 2005


         

2.1 WG Submissions

         

2.1.1 New Item

     

Area

Date

INT

Internet Control Message Protocol (ICMPv6)for the Internet Protocol Version 6 (IPv6) Specification (Draft Standard) - 1 of 6

draft-ietf-ipngwg-icmp-v3-06.txt

Token

Margaret Wasserman

Review

Elwyn Davies (Same version reviewed for LC)



SEC

Addition of Camellia Ciphersuites to Transport Layer Security (TLS) (Proposed Standard) - 2 of 6

draft-ietf-tls-camellia-06.txt

Token:

Russ Housley

Review

John Loughney (Assigned during IETF Last Call)



TSV

RTP Payload Format for Uncompressed Video (Proposed Standard) - 3 of 6

draft-ietf-avt-uncomp-video-06.txt

Note: - Magnus.Westerlund@Ericsson.com is WG Chair Shepherd
- The writeup has an RFC Editor note with revisions of the Media Type (so it doesn't imply
  video/raw will also be a file format in future) - this rev was aired on types list.
- i-d was not rev'd after Feb.  I was holding during long congestion control debate.  MUST
  it have updated ipr boilerplate?? 

Token:

Allison Mankin

Review

Elwyn Davies (Assigned during IETF Last Call)



RTG

Three-Document ballot: - 4 of 6

Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional Specification (Proposed Standard) - 4 of 6

draft-ietf-ccamp-gmpls-recovery-functional-03.txt

Note: Target Category is PS, not INFO as the doc says

Recovery (Protection and Restoration) Terminology for Generalized Multi-Protocol Label Switching (GMPLS) (Informational)

draft-ietf-ccamp-gmpls-recovery-terminology-05.txt

Note: Target Category is INFO, not PS as the doc says

Analysis of Generalized Multi-Protocol Label Switching (GMPLS)-based Recovery Mechanisms (including Protection and Restoration) (Informational)

draft-ietf-ccamp-gmpls-recovery-analysis-04.txt

Token:

Alex Zinin

Review

Lucy Lynch (Assigned during IETF Last Call)



SEC

GSAKMP (Proposed Standard) - 5 of 6

draft-ietf-msec-gsakmp-sec-07.txt

Token:

Russ Housley

Review

Mark Allman



APP

LDAP: Uniform Resource Locator (Proposed Standard) - 6 of 6

draft-ietf-ldapbis-url-09.txt

Token:

Ted Hardie

Review

Scott Brim (updated since LC review was done)



2.1.2 Returning Item

     

Area

Date

APP

SMTP and MIME Extensions For Content Conversion (Proposed Standard) - 1 of 1

draft-ietf-fax-esmtp-conneg-12.txt

Note: Returning to (hopefully) clear the last discuss and to secure the additional ballots needed for approval.

Token:

Scott Hollenbeck

Review

Joel Halpern (Return review)



2.2 Individual Submissions

         

2.2.1 New Item

     

Area

Date

GEN

Structure of the IETF Administrative Support Activity (IASA) (BCP) - 1 of 1

draft-ietf-iasa-bcp-03.txt

Note: This document is still under discussion on the IETF list.
A revision (-04) is expected on Friday, Jan 14.
I (Harald) am putting it before the IESG on Jan 20 to make sure formal IESG processing does not cause delay that is not warranted. I will hold a DISCUSS on the document until it is clear that the IETF discussion is finished.

Token:

Harald Alvestrand

Review

Joel Halpern (was assigned to Lucy Lynch during IETF LC – she is overloaded this week)



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

Requirements for Internet Media Guides (Informational) - 1 of 6

draft-ietf-mmusic-img-req-07.txt

Token:

Jon Peterson

Review

Spencer Dawkins



TSV

A Framework for the Usage of Internet Media Guides (Informational) - 2 of 6

draft-ietf-mmusic-img-framework-08.txt

Token:

Jon Peterson

Review

Spencer Dawkins



APP

Goals for Internet Messaging to Support Diverse Service Environments (Informational) - 3 of 6

draft-ietf-lemonade-goals-05.txt

Token:

Ted Hardie

Review

Mark Allman (Reviewed Already for 05-01-20)



OPS

IPv4 Multihoming Motivation, Practices and Limitations (Informational) - 4 of 6

draft-ietf-multi6-v4-multihoming-03.txt

Token:

David Kessens

Review

John Loughney



OPS

Architectural Approaches to Multi-Homing for IPv6 (Informational) - 5 of 6

draft-ietf-multi6-architecture-03.txt

Token:

David Kessens

Review

Mark Allman



OPS

Things MULTI6 Developers should think about (Informational) - 6 of 6

draft-ietf-multi6-things-to-think-about-01.txt

Token:

David Kessens

Review

Suzanne Woolf



3.1.2 Returning Item

     

Area

Date

INT

State Machines for Extensible Authentication Protocol (EAP) Peer and Authenticator (Informational) - 1 of 1

draft-ietf-eap-statemachine-06.txt

Note: Went back to  the WG to address late issues raised while in RFC Editor queue that resulted in substantive changes.  Back on IESG agenda to be checked before being sent to the RFC Editor (again).

Token:

Margaret Wasserman

Review

Suzanne Woolf



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

APP

Simple New Mail Notification (Informational) - 1 of 3

draft-gellens-notify-mail-01.txt

Token:

Scott Hollenbeck

Review

Scott Brim



APP

A URN Namespace for the TV-Anytime Forum (Informational) - 2 of 3

draft-kameyama-tv-anytime-urn-02.txt

Note: Reviewed by the URN Nid list some time ago, but expired before it was seen by IESG.  Recently re-issued.

Token:

Ted Hardie

Review

Scott Brim



INT

Proposed changes to the format of the IANA IPv6 Registry (Informational) - 3 of 3

draft-huston-ip6-iana-registry-04.txt

Note: Has been reviewed by the IPv6 and v6ops WG (there were minor comments).

Token:

Thomas Narten

Review

Michael Patton



3.2.2 Returning Item
      NONE

3.3 Individual Submissions Via RFC Editor

Reviews should focus on these questions: "Does this document
represent an end run around the IETF's working groups
or its procedures? Does this document present an incompatible
change to IETF technologies as if it were compatible?" Other
matters may be sent to the RFC Editor in private review.

         

3.3.1 New Item
      NONE
3.3.2 Returning Item
      NONE