[IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for December 18, 2008

IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 11 December 2008 23:06 UTC

Return-Path: <iesg-agenda-dist-bounces@ietf.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 B43EF3A6A4F; Thu, 11 Dec 2008 15:06:22 -0800 (PST)
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 C899E28C0E5; Thu, 11 Dec 2008 15:06:21 -0800 (PST)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Mime-Version: 1.0
Message-Id: <20081211230621.C899E28C0E5@core3.amsl.com>
Date: Thu, 11 Dec 2008 15:06:21 -0800
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for December 18, 2008
X-BeenThere: iesg-agenda-dist@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distribution of IESG agendas <iesg-agenda-dist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/iesg-agenda-dist>
List-Post: <mailto:iesg-agenda-dist@ietf.org>
List-Help: <mailto:iesg-agenda-dist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1995679463=="
Sender: iesg-agenda-dist-bounces@ietf.org
Errors-To: iesg-agenda-dist-bounces@ietf.org

IESG Agenda

IESG Agenda

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


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
TSVTCP User Timeout Option (Proposed Standard) - 1 of 12
http://www.ietf.org/internet-drafts/draft-ietf-tcpm-tcp-uto-10.txt" rel="nofollow">draft-ietf-tcpm-tcp-uto-10.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2028&filename=draft-ietf-tcpm-tcp-uto" rel="nofollow">[Open Web Ballot]
Token: Magnus Westerlund
RTGForCES Protocol Specification (Proposed Standard) - 2 of 12
http://www.ietf.org/internet-drafts/draft-ietf-forces-protocol-19.txt" rel="nofollow">draft-ietf-forces-protocol-19.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2069&filename=draft-ietf-forces-protocol" rel="nofollow">[Open Web Ballot]
Token: Ross Callon
RTGForCES MIB (Proposed Standard) - 3 of 12
http://www.ietf.org/internet-drafts/draft-ietf-forces-mib-10.txt" rel="nofollow">draft-ietf-forces-mib-10.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2274&filename=draft-ietf-forces-mib" rel="nofollow">[Open Web Ballot]
Token: Ross Callon
APPInternet Calendaring and Scheduling Core Object Specification (iCalendar) (Proposed Standard) - 4 of 12
http://www.ietf.org/internet-drafts/draft-ietf-calsify-rfc2445bis-09.txt" rel="nofollow">draft-ietf-calsify-rfc2445bis-09.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2819&filename=draft-ietf-calsify-rfc2445bis" rel="nofollow">[Open Web Ballot]
Token: Lisa Dusseault
INTMobile IPv6 Support for Dual Stack Hosts and Routers (Proposed Standard) - 5 of 12
http://www.ietf.org/internet-drafts/draft-ietf-mext-nemo-v4traversal-06.txt" rel="nofollow">draft-ietf-mext-nemo-v4traversal-06.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2864&filename=draft-ietf-mext-nemo-v4traversal" rel="nofollow">[Open Web Ballot]
Token: Jari Arkko
TSVIANA Considerations for RPC Net Identifiers and Universal Address Formats (Proposed Standard) - 6 of 12
http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-rpc-netid-05.txt" rel="nofollow">draft-ietf-nfsv4-rpc-netid-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2869&filename=draft-ietf-nfsv4-rpc-netid" rel="nofollow">[Open Web Ballot]
Note: Document Shepherd: Spencer Shepler (shepler@storspeed.com)
Token: Lars Eggert
RTGOSPF Link-local Signaling (Proposed Standard) - 7 of 12
http://www.ietf.org/internet-drafts/draft-ietf-ospf-lls-05.txt" rel="nofollow">draft-ietf-ospf-lls-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2901&filename=draft-ietf-ospf-lls" rel="nofollow">[Open Web Ballot]
Token: David Ward
SECSecure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification (Proposed Standard) - 8 of 12
http://www.ietf.org/internet-drafts/draft-ietf-smime-3851bis-08.txt" rel="nofollow">draft-ietf-smime-3851bis-08.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2905&filename=draft-ietf-smime-3851bis" rel="nofollow">[Open Web Ballot]
Token: Tim Polk
SECSecure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling (Proposed Standard) - 9 of 12
http://www.ietf.org/internet-drafts/draft-ietf-smime-3850bis-08.txt" rel="nofollow">draft-ietf-smime-3850bis-08.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2906&filename=draft-ietf-smime-3850bis" rel="nofollow">[Open Web Ballot]
Token: Tim Polk
SECElliptic Curve Cryptography Subject Public Key Information (Proposed Standard) - 10 of 12
http://www.ietf.org/internet-drafts/draft-ietf-pkix-ecc-subpubkeyinfo-10.txt" rel="nofollow">draft-ietf-pkix-ecc-subpubkeyinfo-10.txt
Note: Document shepherd is stefans@microsoft.com
Token: Pasi Eronen
APPSieve Email Filtering: Ihave Extension (Proposed Standard) - 11 of 12
http://www.ietf.org/internet-drafts/draft-freed-sieve-ihave-03.txt" rel="nofollow">draft-freed-sieve-ihave-03.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2970&filename=draft-freed-sieve-ihave" rel="nofollow">[Open Web Ballot]
Token: Lisa Dusseault
RTGMulti-Protocol Label Switching (MPLS) label stack entry: "EXP" field renamed to "Traffic Class" field (Proposed Standard) - 12 of 12
http://www.ietf.org/internet-drafts/draft-ietf-mpls-cosfield-def-08.txt" rel="nofollow">draft-ietf-mpls-cosfield-def-08.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2976&filename=draft-ietf-mpls-cosfield-def" rel="nofollow">[Open Web Ballot]
Token: Ross Callon
2.1.2 Returning Item
      NONE

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
APPMessage Header Field for Indicating Message Authentication Status (Proposed Standard) - 1 of 1
http://www.ietf.org/internet-drafts/draft-kucherawy-sender-auth-header-18.txt" rel="nofollow">draft-kucherawy-sender-auth-header-18.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2899&filename=draft-kucherawy-sender-auth-header" rel="nofollow">[Open Web Ballot]
Token: Lisa Dusseault
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
RTGLDP IGP Synchronization (Informational) - 1 of 3
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-igp-sync-03.txt" rel="nofollow">draft-ietf-mpls-ldp-igp-sync-03.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2853&filename=draft-ietf-mpls-ldp-igp-sync" rel="nofollow">[Open Web Ballot]
Token: David Ward
RTGOSPFv3 Based Layer 1 VPN Auto-Discovery (Experimental) - 2 of 3
http://www.ietf.org/internet-drafts/draft-ietf-l1vpn-ospfv3-auto-discovery-02.txt" rel="nofollow">draft-ietf-l1vpn-ospfv3-auto-discovery-02.txt
Token: David Ward
RTGUrban WSNs Routing Requirements in Low Power and Lossy Networks (Informational) - 3 of 3
http://www.ietf.org/internet-drafts/draft-ietf-roll-urban-routing-reqs-02.txt" rel="nofollow">draft-ietf-roll-urban-routing-reqs-02.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2958&filename=draft-ietf-roll-urban-routing-reqs" rel="nofollow">[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
      NONE
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
                    NONE
          4.2.2 Proposed for Approval
                    NONE

5. IAB News We Can Use

6. Management Issues

7. Working Group News

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