IESG agenda for 2005-07-21 telechat.

fenner@research.att.com (Bill Fenner) Mon, 18 July 2005 11:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00826 for <rtg-dir-archive@ietf.org>; Mon, 18 Jul 2005 07:04:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuTtW-0007mN-4V for rtg-dir-archive@ietf.org; Mon, 18 Jul 2005 07:34:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuTO7-0005JK-Ps; Mon, 18 Jul 2005 07:02:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuTO6-0005JD-Ft for rtg-dir@megatron.ietf.org; Mon, 18 Jul 2005 07:02:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00734 for <rtg-dir@ietf.org>; Mon, 18 Jul 2005 07:02:15 -0400 (EDT)
Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuTrW-0007ij-0c for rtg-dir@ietf.org; Mon, 18 Jul 2005 07:32:42 -0400
Received: from mango.attlabs.att.com (mango.attlabs.att.com [135.197.128.36]) by mail-green.research.att.com (Postfix) with ESMTP id 893A3A7BB0 for <rtg-dir@ietf.org>; Mon, 18 Jul 2005 07:02:08 -0400 (EDT)
Received: from mango.attlabs.att.com (localhost [127.0.0.1]) by mango.attlabs.att.com (8.12.10/8.12.10) with ESMTP id j6IB0l3h048624 for <rtg-dir@ietf.org>; Mon, 18 Jul 2005 04:01:12 -0700 (PDT) (envelope-from fenner@research.att.com)
Received: (from fenner@localhost) by mango.attlabs.att.com (8.12.10/8.12.10/Submit) id j6IB0auf048623 for rtg-dir@ietf.org; Mon, 18 Jul 2005 04:00:36 -0700 (PDT) (envelope-from fenner)
Date: Mon, 18 Jul 2005 04:00:36 -0700
Message-Id: <200507181100.j6IB0auf048623@mango.attlabs.att.com>
From: fenner@research.att.com
To: rtg-dir@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
Subject: IESG agenda for 2005-07-21 telechat.
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae

                              IESG Agenda

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

Updated 2:29:23 EDT, July 18, 2005
-----------------------------------------------------------------------

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
    1.5 Review of Projects

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         Graceful Restart Mechanism for BGP with MPLS
                         (Proposed Standard) - 1 of 6
                         draft-ietf-mpls-bgp-mpls-restart-04.txt [Open
                         Text Ballot]
                  Token: Alex Zinin
             APP         Two-Document ballot: [Open Web Ballot] - 2 of
                         6
                         NNTP Extension for Authentication (Proposed
                         Standard) - 2 of 6
                         draft-ietf-nntpext-authinfo-09.txt
                         Note: Document shepherd: Russ Allbery
                         <rra@stanford.edu>
                         Using TLS with NNTP (Proposed Standard)
                         draft-ietf-nntpext-tls-nntp-07.txt
                  Token: Scott Hollenbeck
             RTG         Virtual Router Redundancy Protocol for IPv6
                         (Proposed Standard) - 3 of 6
                         draft-ietf-vrrp-ipv6-spec-07.txt [Open Web
                         Ballot]
                  Token: Alex Zinin
                         Pseudowire Setup and Maintenance using the
             INT         Label Distribution Protocol (Proposed
                         Standard) - 4 of 6
                         draft-ietf-pwe3-control-protocol-17.txt [Open
                         Web Ballot]
                  Token: Mark Townsley
                         Certificate Extensions and Attributes
             SEC         Supporting Authentication in Point-to-Point
                         Protocol (PPP) and Wireless Local Area
                         Networks (WLAN) (Proposed Standard) - 5 of 6
                         draft-ietf-pkix-rfc3770bis-03.txt [Open Web
                         Ballot]
                         Note: proto shepherd: tim.polk@nist.gov
                  Token: Sam Hartman
             APP         NNTP Extension for Streaming Feeds (Proposed
                         Standard) - 6 of 6
                         draft-ietf-nntpext-streaming-06.txt [Open Web
                         Ballot]
                         Note: Document shepherd: Russ Allbery
                         <rra@stanford.edu>
                  Token: Scott Hollenbeck

          2.1.2 Returning Item


             Area  Date

                         Encoding of Attributes for Multiprotocol Label
             RTG         Switching (MPLS) Label Switched Path (LSP)
                         Establishment Using RSVP-TE (Proposed
                         Standard) - 1 of 2
                         draft-ietf-mpls-rsvpte-attributes-05.txt [Open
                         Web Ballot]
                  Token: Alex Zinin
                         Dynamic Host Configuration Protocol (DHCPv4
             APP         and DHCPv6) Option for Civic Addresses
                         Configuration Information (Proposed Standard)
                         - 2 of 2
                         draft-ietf-geopriv-dhcp-civil-06.txt [Open Web
                         Ballot]
                         Note: Back on to check RFC Editor notes
                  Token: Ted Hardie


     2.2 Individual Submissions

           2.2.1 New Item


              Area  Date

              TSV         MIME Type Registration for MPEG-4 (Proposed
                          Standard) - 1 of 3
                          draft-lim-mpeg4-mime-03.txt [Open Web Ballot]
                          Note: To IESG and I'll hold a Discuss until
                          Last Call ends (MPEG needs before end of
                          summer)
                   Token: Allison Mankin
              TSV         MIME Type Registrations for 3GPP2 Multimedia
                          files (Proposed Standard) - 2 of 3
                          draft-garudadri-avt-3gpp2-mime-02.txt [Open
                          Web Ballot]
                          Note: To IESG and I'll hold in Discuss until
                          Last Call ends (3GPP2 deadline this summer)
                   Token: Allison Mankin
                          Internet Message Access Protocol (IMAP) -
              APP         UIDPLUS extension (Proposed Standard) - 3 of
                          3
                          draft-crispin-imap-rfc2359bis-04.txt [Open
                          Web Ballot]
                   Token: Scott Hollenbeck

           2.2.2 Returning Item

               Area  Date

               APP         Media Type Specifications and Registration
                           Procedures (BCP) - 1 of 1
                           draft-freed-media-type-reg-04.txt [Open Web
                           Ballot]
                           Note: Returning to discuss the last
                           remaining discuss.
                    Token: Scott Hollenbeck


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         Session Description Protocol Offer/Answer
                         Examples (Informational) - 1 of 1
                         draft-ietf-mmusic-offer-answer-examples-06.txt
                         [Open Web Ballot]
                  Token: Jon Peterson

           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

                   Area  Date

                   APP         HTTP Header Field Registrations
                               (Informational) - 1 of 1
                               draft-nottingham-hdrreg-http-05.txt
                               [Open Web Ballot]
                        Token: Scott Hollenbeck


       3.3 Individual 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.

           Other matters may be recorded in comments to 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