From iesg-agenda-dist-bounces@iesg.org Thu Aug 7 15:38:24 2008 Return-Path: X-Original-To: iesg-agenda-dist-archive@optimus.ietf.org Delivered-To: ietfarch-iesg-agenda-dist-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9EF53A6A7D; Thu, 7 Aug 2008 15:38:24 -0700 (PDT) X-Original-To: iesg-agenda-dist@ietf.org Delivered-To: iesg-agenda-dist@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 3E6693A6A7D; Thu, 7 Aug 2008 15:38:23 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20080807223823.3E6693A6A7D@core3.amsl.com> Date: Thu, 7 Aug 2008 15:38:23 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for August 14, 2008 X-BeenThere: iesg-agenda-dist@iesg.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1899268064==" Sender: iesg-agenda-dist-bounces@iesg.org Errors-To: iesg-agenda-dist-bounces@iesg.org --===============1899268064== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

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

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
      AreaDate
TSVInformation Model and XML Data Model for Traceroute Measurements (Proposed Standard) - 1 of 6
draft-ietf-ippm-storetraceroutes-10.txt [Open Web Ballot]
Note: Document sheperd is Henk Uijterwaal (henk@ripe.net)
Token: Lars Eggert
SECTLS Transport Mapping for Syslog (Proposed Standard) - 2 of 6
draft-ietf-syslog-transport-tls-13.txt [Open Web Ballot]
Token: Pasi Eronen
INTDefinitions of Textual Conventions for Pseudowires (PW) Management (Proposed Standard) - 3 of 6
draft-ietf-pwe3-pw-tc-mib-14.txt [Open Web Ballot]
Token: Mark Townsley
TSVGuidelines for Application Designers on Using Unicast UDP (BCP) - 4 of 6
draft-ietf-tsvwg-udp-guidelines-09.txt
Token: Magnus Westerlund
OPSSimple Network Management Protocol (SNMP) Context EngineID Discovery (Proposed Standard) - 5 of 6
draft-ietf-opsawg-snmp-engineid-discovery-03.txt [Open Web Ballot]
Token: Dan Romascanu
APPInternet Message Store Events (Proposed Standard) - 6 of 6
draft-ietf-lemonade-msgevent-06.txt [Open Web Ballot]
Token: Lisa Dusseault
2.1.2 Returning Item
      AreaDate
TSVA Two-way Active Measurement Protocol (TWAMP) (Proposed Standard) - 1 of 1
draft-ietf-ippm-twamp-09.txt [Open Web Ballot]
Note: Document Shepherd: Henk Uijterwaal (henk@ripe.net)
Token: Lars Eggert

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
INTIANA Considerations for the IPv4 and IPv6 Router Alert Option (Proposed Standard) - 1 of 2
draft-manner-router-alert-iana-03.txt [Open Web Ballot]
Token: Jari Arkko
SECExtensions to the IODEF-Document Class for Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 2 of 2
draft-cain-post-inch-phishingextns-05.txt [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
      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
      AreaDate
GENBasic Password Exchange within the Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 3
draft-zhou-emu-fast-gtc-04.txt [Open Web Ballot]
Token: Tim Polk
GENDynamic Provisioning using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 2 of 3
draft-cam-winget-eap-fast-provisioning-09.txt [Open Web Ballot]
Token: Tim Polk
RAIMedia Gateway Control Protocol Fax Package (Informational) - 3 of 3
draft-andreasen-mgcp-fax-08.txt [Open Web Ballot]
Token: Cullen Jennings
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
                    NONE
          4.1.2 Proposed for Approval
                    NONE
         

4.2 WG Rechartering

          4.2.1 Under evaluation for IETF Review
         
AreaDate
INTAug 5Layer 2 Virtual Private Networks (l2vpn) - 1 of 1
Token:Mark
          4.2.2 Proposed for Approval
                    NONE

5. IAB News We Can Use

6. Management Issues

6.1 No New Ballot Sets (Pasi Eronen)
6.2 Printer designated experts (Chris Newman)
6.3 Updating the RFC Editor index? (Sandy Ginoza)
6.4 Designated expert for ethernet-numbers [IANA #182998] (Michelle Cotton)
6.5 IESG Requirements for NomCom (Russ Housley)
6.6 Friday Meetings in Minneapolis (Russ Housley)
6.7 Modification to a SASL Mechanism [IANA #178703] (Michelle Cotton)

7. Working Group News

--===============1899268064== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@iesg.org http://www.iesg.org/mailman/listinfo/iesg-agenda-dist --===============1899268064==-- From iesg-agenda-dist-bounces@iesg.org Thu Aug 7 15:38:24 2008 Return-Path: X-Original-To: iesg-agenda-dist-archive@optimus.ietf.org Delivered-To: ietfarch-iesg-agenda-dist-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C303F28C0FC; Thu, 7 Aug 2008 15:38:24 -0700 (PDT) X-Original-To: iesg-agenda-dist@ietf.org Delivered-To: iesg-agenda-dist@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 452F63A6AD7; Thu, 7 Aug 2008 15:38:23 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20080807223823.452F63A6AD7@core3.amsl.com> Date: Thu, 7 Aug 2008 15:38:23 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for August 14, 2008 X-BeenThere: iesg-agenda-dist@iesg.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: iesg-agenda-dist-bounces@iesg.org Errors-To: iesg-agenda-dist-bounces@iesg.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the August 14, 2008 IESG Teleconference This agenda was generated at 15:38:23 EDT, August 7, 2008 Web version of this agenda can be found at: http://www.ietf.org/IESG/agenda.html 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes 1.4 Review of Action Items 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 o draft-ietf-ippm-storetraceroutes-10.txt Information Model and XML Data Model for Traceroute Measurements (Proposed Standard) - 1 of 6 Note: Document sheperd is Henk Uijterwaal (henk@ripe.net) Token: Lars Eggert o draft-ietf-syslog-transport-tls-13.txt TLS Transport Mapping for Syslog (Proposed Standard) - 2 of 6 Token: Pasi Eronen o draft-ietf-pwe3-pw-tc-mib-14.txt Definitions of Textual Conventions for Pseudowires (PW) Management (Proposed Standard) - 3 of 6 Token: Mark Townsley o draft-ietf-tsvwg-udp-guidelines-09.txt Guidelines for Application Designers on Using Unicast UDP (BCP) - 4 of 6 Token: Magnus Westerlund o draft-ietf-opsawg-snmp-engineid-discovery-03.txt Simple Network Management Protocol (SNMP) Context EngineID Discovery (Proposed Standard) - 5 of 6 Token: Dan Romascanu o draft-ietf-lemonade-msgevent-06.txt Internet Message Store Events (Proposed Standard) - 6 of 6 Token: Lisa Dusseault 2.1.2 Returning Item o draft-ietf-ippm-twamp-09.txt A Two-way Active Measurement Protocol (TWAMP) (Proposed Standard) - 1 of 1 Note: Document Shepherd: Henk Uijterwaal (henk@ripe.net) Token: Lars Eggert 2.2 Individual Submissions 2.2.1 New Item o draft-manner-router-alert-iana-03.txt IANA Considerations for the IPv4 and IPv6 Router Alert Option (Proposed Standard) - 1 of 2 Token: Jari Arkko o draft-cain-post-inch-phishingextns-05.txt Extensions to the IODEF-Document Class for Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 2 of 2 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 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 o draft-zhou-emu-fast-gtc-04.txt Basic Password Exchange within the Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 3 Token: Tim Polk o draft-cam-winget-eap-fast-provisioning-09.txt Dynamic Provisioning using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 2 of 3 Token: Tim Polk o draft-andreasen-mgcp-fax-08.txt Media Gateway Control Protocol Fax Package (Informational) - 3 of 3 Token: Cullen Jennings 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review o Layer 2 Virtual Private Networks (l2vpn) - 1 of 1 Token: Mark 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 6.1 No New Ballot Sets (Pasi Eronen) 6.2 Printer designated experts (Chris Newman) 6.3 Updating the RFC Editor index? (Sandy Ginoza) 6.4 Designated expert for ethernet-numbers [IANA #182998] (Michelle Cotton) 6.5 IESG Requirements for NomCom (Russ Housley) 6.6 Friday Meetings in Minneapolis (Russ Housley) 6.7 Modification to a SASL Mechanism [IANA #178703] (Michelle Cotton) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@iesg.org http://www.iesg.org/mailman/listinfo/iesg-agenda-dist From iesg-agenda-dist-bounces@iesg.org Thu Aug 21 15:22:33 2008 Return-Path: X-Original-To: iesg-agenda-dist-archive@optimus.ietf.org Delivered-To: ietfarch-iesg-agenda-dist-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C9CA3A67BD; Thu, 21 Aug 2008 15:22:33 -0700 (PDT) X-Original-To: iesg-agenda-dist@ietf.org Delivered-To: iesg-agenda-dist@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 07B923A67BD; Thu, 21 Aug 2008 15:21:32 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20080821222133.07B923A67BD@core3.amsl.com> Date: Thu, 21 Aug 2008 15:21:33 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for August 28, 2008 X-BeenThere: iesg-agenda-dist@iesg.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1756952654==" Sender: iesg-agenda-dist-bounces@iesg.org Errors-To: iesg-agenda-dist-bounces@iesg.org --===============1756952654== Content-Type: text/html; charset="utf-8" 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
      AreaDate
RTGA 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
draft-ietf-mpls-number-0-bw-te-lsps-11.txt [Open Web Ballot]
Token: Ross Callon
2.1.2 Returning Item
      NONE
2.1.3 For Action
      AreaDate
OPSSimple Network Management Protocol (SNMP) Context EngineID Discovery (Proposed Standard) - 1 of 1
draft-ietf-opsawg-snmp-engineid-discovery-03.txt [Open Web Ballot]
Token: Dan Romascanu

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
SECExtensions to the IODEF-Document Class for Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 1 of 1
draft-cain-post-inch-phishingextns-05.txt [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
      AreaDate
INTWhy Authentication Data suboption is needed for MIP6 (Informational) - 1 of 1
draft-ietf-mip6-whyauthdataoption-06.txt [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
      AreaDate
GENDynamic Provisioning using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 2
draft-cam-winget-eap-fast-provisioning-09.txt [Open Web Ballot]
Token: Tim Polk
OPSDiameter ITU-T Rw Policy Enforcement Interface Application (Informational) - 2 of 2
draft-sun-dime-itu-t-rw-01.txt [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
      AreaDate
OPSSNMP Traffic Measurements and Trace Exchange Formats (Informational) - 1 of 1
draft-irtf-nmrg-snmp-measure-05.txt [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
         
AreaDate
OPSAug 18Operational Security Capabilities for IP Network Infrastructure (opsec) - 1 of 1
Token:Ron
          4.2.2 Proposed for Approval
         
AreaDate
APPJul 2Sieve 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

--===============1756952654== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@iesg.org http://www.iesg.org/mailman/listinfo/iesg-agenda-dist --===============1756952654==-- From iesg-agenda-dist-bounces@iesg.org Thu Aug 21 15:22:33 2008 Return-Path: X-Original-To: iesg-agenda-dist-archive@optimus.ietf.org Delivered-To: ietfarch-iesg-agenda-dist-archive@core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 267433A6881; Thu, 21 Aug 2008 15:22:33 -0700 (PDT) X-Original-To: iesg-agenda-dist@ietf.org Delivered-To: iesg-agenda-dist@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 099FC3A6783; Thu, 21 Aug 2008 15:21:33 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20080821222133.099FC3A6783@core3.amsl.com> Date: Thu, 21 Aug 2008 15:21:33 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for August 28, 2008 X-BeenThere: iesg-agenda-dist@iesg.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: iesg-agenda-dist-bounces@iesg.org Errors-To: iesg-agenda-dist-bounces@iesg.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the August 28, 2008 IESG Teleconference This agenda was generated at 15:21:32 EDT, August 21, 2008 Web version of this agenda can be found at: http://www.ietf.org/IESG/agenda.html 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes 1.4 Review of Action Items 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 o draft-ietf-mpls-number-0-bw-te-lsps-11.txt 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 Token: Ross Callon 2.1.2 Returning Item NONE 2.1.3 For Action o draft-ietf-opsawg-snmp-engineid-discovery-03.txt Simple Network Management Protocol (SNMP) Context EngineID Discovery (Proposed Standard) - 1 of 1 Token: Dan Romascanu 2.2 Individual Submissions 2.2.1 New Item o draft-cain-post-inch-phishingextns-05.txt Extensions to the IODEF-Document Class for Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 1 of 1 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 o draft-ietf-mip6-whyauthdataoption-06.txt Why Authentication Data suboption is needed for MIP6 (Informational) - 1 of 1 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 o draft-cam-winget-eap-fast-provisioning-09.txt Dynamic Provisioning using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 1 of 2 Token: Tim Polk o draft-sun-dime-itu-t-rw-01.txt Diameter ITU-T Rw Policy Enforcement Interface Application (Informational) - 2 of 2 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 o draft-irtf-nmrg-snmp-measure-05.txt SNMP Traffic Measurements and Trace Exchange Formats (Informational) - 1 of 1 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 o Operational Security Capabilities for IP Network Infrastructure (opsec) - 1 of 1 Token: Ron 4.2.2 Proposed for Approval o Sieve Mail Filtering Language (sieve) - 1 of 1 Token: Lisa 5. IAB News We can use 6. Management Issue 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. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@iesg.org http://www.iesg.org/mailman/listinfo/iesg-agenda-dist