[IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for April 9, 2009

IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 02 April 2009 21:54 UTC

Return-Path: <wwwrun@core3.amsl.com>
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 348913A6950; Thu, 2 Apr 2009 14:54:09 -0700 (PDT)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Content-Type: text/html; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090402215410.348913A6950@core3.amsl.com>
Date: Thu, 02 Apr 2009 14:54:10 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for April 9, 2009
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/mail-archive/web/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>
X-List-Received-Date: Thu, 02 Apr 2009 21:54:10 -0000

IESG Agenda

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2009-04-09).


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
TSVGIST: General Internet Signalling Transport (Proposed Standard) - 1 of 9
http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-19.txt" rel="nofollow">draft-ietf-nsis-ntlp-19.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=1546&filename=draft-ietf-nsis-ntlp" rel="nofollow">[Open Web Ballot]
Note: Please check your comment field so that it doesn't contain old text! RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please indicate in the comment field that you have performed this re-evaluation. Pleas also include some motivation behind your decision.
Token: Magnus Westerlund
TSVTraversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) (Proposed Standard) - 2 of 9
http://www.ietf.org/internet-drafts/draft-ietf-behave-turn-13.txt" rel="nofollow">draft-ietf-behave-turn-13.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2322&filename=draft-ietf-behave-turn" rel="nofollow">[Open Web Ballot]
Token: Magnus Westerlund
RTGLDP Capabilities (Proposed Standard) - 3 of 9
http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-capabilities-03.txt" rel="nofollow">draft-ietf-mpls-ldp-capabilities-03.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2751&filename=draft-ietf-mpls-ldp-capabilities" rel="nofollow">[Open Web Ballot]
Token: Ross Callon
SECOct 3Clarifications and Extensions to the GSS-API for the Use of Channel Bindings (Proposed Standard) - 4 of 9
http://www.ietf.org/internet-drafts/draft-ietf-kitten-gssapi-channel-bindings-06.txt" rel="nofollow">draft-ietf-kitten-gssapi-channel-bindings-06.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2861&filename=draft-ietf-kitten-gssapi-channel-bindings" rel="nofollow">[Open Web Ballot]
Note: proto writeup received...
Token: Tim Polk
INTSoftwire Security Analysis and Requirements (Proposed Standard) - 5 of 9
http://www.ietf.org/internet-drafts/draft-ietf-softwire-security-requirements-07.txt" rel="nofollow">draft-ietf-softwire-security-requirements-07.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2935&filename=draft-ietf-softwire-security-requirements" rel="nofollow">[Open Web Ballot]
Token: Mark Townsley
INTNetwork Time Protocol Version 4 Protocol And Algorithms Specification (Proposed Standard) - 6 of 9
http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-proto-11.txt" rel="nofollow">draft-ietf-ntp-ntpv4-proto-11.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2973&filename=draft-ietf-ntp-ntpv4-proto" rel="nofollow">[Open Web Ballot]
Token: Mark Townsley
INTDefinitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) (Proposed Standard) - 7 of 9
http://www.ietf.org/internet-drafts/draft-ietf-ntp-ntpv4-mib-05.txt" rel="nofollow">draft-ietf-ntp-ntpv4-mib-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2974&filename=draft-ietf-ntp-ntpv4-mib" rel="nofollow">[Open Web Ballot]
Token: Mark Townsley
RTGRSVP Extensions for Path Key Support (Proposed Standard) - 8 of 9
http://www.ietf.org/internet-drafts/draft-ietf-ccamp-path-key-ero-04.txt" rel="nofollow">draft-ietf-ccamp-path-key-ero-04.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=3000&filename=draft-ietf-ccamp-path-key-ero" rel="nofollow">[Open Web Ballot]
Token: Ross Callon
RTGPath Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions In Support of Global Concurrent Optimization (Proposed Standard) - 9 of 9
http://www.ietf.org/internet-drafts/draft-ietf-pce-global-concurrent-optimization-10.txt" rel="nofollow">draft-ietf-pce-global-concurrent-optimization-10.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=3001&filename=draft-ietf-pce-global-concurrent-optimization" rel="nofollow">[Open Web Ballot]
Token: Ross Callon
2.1.2 Returning Item
      AreaDate
TSVA One-Way Packet Duplication Metric (Proposed Standard) - 1 of 1
http://www.ietf.org/internet-drafts/draft-ietf-ippm-duplicate-07.txt" rel="nofollow">draft-ietf-ippm-duplicate-07.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=3007&filename=draft-ietf-ippm-duplicate" rel="nofollow">[Open Web Ballot]
Token: Lars Eggert

2.2 Individual Submissions

          2.2.1 New Item
      NONE
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
APPStreaming Internet Messaging Attachments (Informational) - 1 of 1
http://www.ietf.org/internet-drafts/draft-ietf-lemonade-streaming-10.txt" rel="nofollow">draft-ietf-lemonade-streaming-10.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2855&filename=draft-ietf-lemonade-streaming" rel="nofollow">[Open Web Ballot]
Note: Glenn Parsons is document shepherd
Token: Alexey Melnikov
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
      AreaDate
INTIPv6 Rapid Deployment on IPv4 infrastructures (6rd) (Informational) - 1 of 1
http://www.ietf.org/internet-drafts/draft-despres-6rd-02.txt" rel="nofollow">draft-despres-6rd-02.txt
Token: Jari Arkko
3.3.2 Returning Item
      NONE

4. Working Group Actions

         

4.1 WG Creation

          4.1.1 Proposed for IETF Review
         
AreaDate
INTApr 2Multiple Interfaces (mif) - 1 of 1
Token:Jari
          4.1.2 Proposed for Approval
         
AreaDate
INTMar 5Locator/ID Separation Protocol (lisp) - 1 of 3
Token:Jari
RAIMar 12Session Initiation Protocol Core (sipcore) - 2 of 3
Token:Cullen
RAIFeb 27Dispatch (dispatch) - 3 of 3
Token:Cullen
         

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

6.1 Request for expert designation for RFC5415 [IANA #229023] (Michelle Cotton)
6.2 Approve IANA expert for CAPWAP (Russ Housley)
6.3 Assignment of media type action point to Alexey (Magnus Westerlund)
6.4 ISOC BoT Appointment Confirmation (Executive Session) (Russ Housley)

7. Working Group News