[IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for August 28, 2008

[IESG Secretary <[e-mail]>]

IESG Agenda

IESG Agenda

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

---

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 RTG A Link-Type sub-TLV to convey the number of Traffic Engineering Label Switched Paths signalled with zero reserved bandwidth across a link (Proposed Standard) - 1 of 1 http://www.ietf.org/internet-drafts/draft-ietf-mpls-number-0-bw-te-lsps-11.txt" rel="nofollow">draft-ietf-mpls-number-0-bw-te-lsps-11.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2771&filename=draft-ietf-mpls-number-0-bw-te-lsps" rel="nofollow">[Open Web Ballot] Token: Ross Callon 2.1.2 Returning Item       NONE 2.1.3 For Action       Area Date OPS Simple Network Management Protocol (SNMP) Context EngineID Discovery (Proposed Standard) - 1 of 1 http://www.ietf.org/internet-drafts/draft-ietf-opsawg-snmp-engineid-discovery-03.txt" rel="nofollow">draft-ietf-opsawg-snmp-engineid-discovery-03.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2739&filename=draft-ietf-opsawg-snmp-engineid-discovery" rel="nofollow">[Open Web Ballot] Token: Dan Romascanu 2.2 Individual Submissions           2.2.1 New Item       Area Date SEC Extensions to the IODEF-Document Class for Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 1 of 1 http://www.ietf.org/internet-drafts/draft-cain-post-inch-phishingextns-05.txt" rel="nofollow">draft-cain-post-inch-phishingextns-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2744&filename=draft-cain-post-inch-phishingextns" rel="nofollow">[Open Web Ballot] Token: Tim Polk 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 INT Why Authentication Data suboption is needed for MIP6 (Informational) - 1 of 1 http://www.ietf.org/internet-drafts/draft-ietf-mip6-whyauthdataoption-06.txt" rel="nofollow">draft-ietf-mip6-whyauthdataoption-06.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2588&filename=draft-ietf-mip6-whyauthdataoption" rel="nofollow">[Open Web Ballot] Note: No document shepherd -- old MIP6 document Token: Jari Arkko 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 Dynamic Provisioning using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 2 http://www.ietf.org/internet-drafts/draft-cam-winget-eap-fast-provisioning-09.txt" rel="nofollow">draft-cam-winget-eap-fast-provisioning-09.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2776&filename=draft-cam-winget-eap-fast-provisioning" rel="nofollow">[Open Web Ballot] Token: Tim Polk OPS Diameter ITU-T Rw Policy Enforcement Interface Application (Informational) - 2 of 2 http://www.ietf.org/internet-drafts/draft-sun-dime-itu-t-rw-01.txt" rel="nofollow">draft-sun-dime-itu-t-rw-01.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2818&filename=draft-sun-dime-itu-t-rw" rel="nofollow">[Open Web Ballot] 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       Area Date OPS SNMP Traffic Measurements and Trace Exchange Formats (Informational) - 1 of 1 http://www.ietf.org/internet-drafts/draft-irtf-nmrg-snmp-measure-05.txt" rel="nofollow">draft-irtf-nmrg-snmp-measure-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2723&filename=draft-irtf-nmrg-snmp-measure" rel="nofollow">[Open Web Ballot] Note: Proposed IESG Note: The IESG thinks that this work is related to IETF work done in the Operations and Management Area related to SNMP, but this does not prevent publishing. This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and notes that the decision to publish is not based on IETF review apart from the IETF Last Call on the allocation of an URI by IANA and the IESG review for conflict with IETF work. The RFC Editor has chosen to publish this document at its discretion.  See RFC 3932 for more information. Token: Dan Romascanu 3.3.2 Returning Item       NONE

4. Working Group Actions

4.1 WG Creation           4.1.1 Proposed for IETF Review                     NONE           4.1.2 Proposed for Approval                     NONE

4.2 WG Rechartering           4.2.1 Under evaluation for IETF Review           Area Date OPS Aug 18 Operational Security Capabilities for IP Network Infrastructure (opsec) - 1 of 1 Token: Ron           4.2.2 Proposed for Approval           Area Date APP Jul 2 Sieve Mail Filtering Language (sieve) - 1 of 1 Token: Lisa

5. IAB News We Can Use

6. Management Issues

6.1 No New Ballot Sets (Pasi Eronen)
6.2 IESG Requirements for NomCom (UPDATED) (Russ Housley)
6.3 Friday Meetings in Minneapolis (Russ Housley)
6.4 Registration procedures for arp-parameters (hardware types) [IANA #183428] (Michelle Cotton)
6.5 Revised guidance for interim meetings (UPDATED) (Russ Housley)
6.6 Executive Session: First draft of appeal response (Lisa Dusseault)

7. Working Group News

_______________________________________________
IESG-AGENDA-DIST mailing list
[e-mail]
http://www.iesg.org/mailman/listinfo/iesg-agenda-dist