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

IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 07 August 2008 22:38 UTC

Return-Path: <iesg-agenda-dist-bounces@iesg.org>
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 <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Mime-Version: 1.0
Message-Id: <20080807223823.3E6693A6A7D@core3.amsl.com>
Date: Thu, 07 Aug 2008 15:38:23 -0700
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 <iesg-agenda-dist.iesg.org>
List-Unsubscribe: <http://www.iesg.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@iesg.org?subject=unsubscribe>
List-Archive: <http://www.iesg.org/pipermail/iesg-agenda-dist>
List-Post: <mailto:iesg-agenda-dist@iesg.org>
List-Help: <mailto:iesg-agenda-dist-request@iesg.org?subject=help>
List-Subscribe: <http://www.iesg.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@iesg.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1899268064=="
Sender: iesg-agenda-dist-bounces@iesg.org
Errors-To: iesg-agenda-dist-bounces@iesg.org

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
http://www.ietf.org/internet-drafts/draft-ietf-ippm-storetraceroutes-10.txt" rel="nofollow">draft-ietf-ippm-storetraceroutes-10.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2228&filename=draft-ietf-ippm-storetraceroutes" rel="nofollow">[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
http://www.ietf.org/internet-drafts/draft-ietf-syslog-transport-tls-13.txt" rel="nofollow">draft-ietf-syslog-transport-tls-13.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2334&filename=draft-ietf-syslog-transport-tls" rel="nofollow">[Open Web Ballot]
Token: Pasi Eronen
INTDefinitions of Textual Conventions for Pseudowires (PW) Management (Proposed Standard) - 3 of 6
http://www.ietf.org/internet-drafts/draft-ietf-pwe3-pw-tc-mib-14.txt" rel="nofollow">draft-ietf-pwe3-pw-tc-mib-14.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2577&filename=draft-ietf-pwe3-pw-tc-mib" rel="nofollow">[Open Web Ballot]
Token: Mark Townsley
TSVGuidelines for Application Designers on Using Unicast UDP (BCP) - 4 of 6
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udp-guidelines-09.txt" rel="nofollow">draft-ietf-tsvwg-udp-guidelines-09.txt
Token: Magnus Westerlund
OPSSimple Network Management Protocol (SNMP) Context EngineID Discovery (Proposed Standard) - 5 of 6
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
APPInternet Message Store Events (Proposed Standard) - 6 of 6
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-msgevent-06.txt" rel="nofollow">draft-ietf-lemonade-msgevent-06.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2760&filename=draft-ietf-lemonade-msgevent" rel="nofollow">[Open Web Ballot]
Token: Lisa Dusseault
2.1.2 Returning Item
      AreaDate
TSVA Two-way Active Measurement Protocol (TWAMP) (Proposed Standard) - 1 of 1
http://www.ietf.org/internet-drafts/draft-ietf-ippm-twamp-09.txt" rel="nofollow">draft-ietf-ippm-twamp-09.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2229&filename=draft-ietf-ippm-twamp" rel="nofollow">[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
http://www.ietf.org/internet-drafts/draft-manner-router-alert-iana-03.txt" rel="nofollow">draft-manner-router-alert-iana-03.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2665&filename=draft-manner-router-alert-iana" rel="nofollow">[Open Web Ballot]
Token: Jari Arkko
SECExtensions to the IODEF-Document Class for Reporting Phishing, Fraud, and Other Crimeware (Proposed Standard) - 2 of 2
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
      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
http://www.ietf.org/internet-drafts/draft-zhou-emu-fast-gtc-04.txt" rel="nofollow">draft-zhou-emu-fast-gtc-04.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2683&filename=draft-zhou-emu-fast-gtc" rel="nofollow">[Open Web Ballot]
Token: Tim Polk
GENDynamic Provisioning using Flexible Authentication via Secure Tunneling Extensible Authentication Protocol (EAP-FAST) (Informational) - 2 of 3
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
RAIMedia Gateway Control Protocol Fax Package (Informational) - 3 of 3
http://www.ietf.org/internet-drafts/draft-andreasen-mgcp-fax-08.txt" rel="nofollow">draft-andreasen-mgcp-fax-08.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2812&filename=draft-andreasen-mgcp-fax" rel="nofollow">[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

_______________________________________________
IESG-AGENDA-DIST mailing list
IESG-AGENDA-DIST@iesg.org
http://www.iesg.org/mailman/listinfo/iesg-agenda-dist