From iesg-agenda-dist-bounces@ietf.org Fri Jan 2 09:19:47 2009 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 453CF3A6A11; Fri, 2 Jan 2009 09:19:47 -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 3A6E23A6937; Fri, 2 Jan 2009 09:19:46 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090102171946.3A6E23A6937@core3.amsl.com> Date: Fri, 2 Jan 2009 09:19:46 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for January 8, 2009 X-BeenThere: iesg-agenda-dist@ietf.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="===============0298885193==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0298885193== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

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

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
RTGSimplified Extension of LSP Space for IS-IS (Proposed Standard) - 1 of 3
draft-ietf-isis-wg-extlsp-05.txt [Open Web Ballot]
Token: Ross Callon
RAIA Framework for Session Initiation Protocol (SIP) Session Policies (Proposed Standard) - 2 of 3
draft-ietf-sip-session-policy-framework-05.txt [Open Web Ballot]
Token: Cullen Jennings
RTGCapabilities Advertisement with BGP-4 (Proposed Standard) - 3 of 3
draft-ietf-idr-rfc3392bis-03.txt [Open Web Ballot]
Token: David Ward
2.1.2 Returning Item
      AreaDate
SECSecure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification (Proposed Standard) - 1 of 2
draft-ietf-smime-3851bis-08.txt [Open Web Ballot]
Token: Tim Polk
SECSecure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling (Proposed Standard) - 2 of 2
draft-ietf-smime-3850bis-08.txt [Open Web Ballot]
Token: Tim Polk

2.2 Individual Submissions

          2.2.1 New Item
      NONE
2.2.2 Returning Item
      AreaDate
GENIESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1
draft-housley-iesg-rfc3932bis-06.txt [Open Web Ballot]
Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html
Token: Jari Arkko

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
SECDES and IDEA Cipher Suites for Transport Layer Security (TLS) (Informational) - 1 of 2
draft-ietf-tls-des-idea-02.txt [Open Web Ballot]
Token: Tim Polk
TSVPacket Delay Variation Applicability Statement (Informational) - 2 of 2
draft-ietf-ippm-delay-var-as-01.txt [Open Web Ballot]
Token: Lars Eggert
3.1.2 Returning Item
      AreaDate
RTGThe RPF Vector TLV (Informational) - 1 of 1
draft-ietf-pim-rpf-vector-06.txt [Open Web Ballot]
Token: David Ward

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
RTGPerformance Analysis of Inter-Domain Path Computation Methodologies (Informational) - 1 of 3
draft-dasgupta-ccamp-path-comp-analysis-02.txt [Open Web Ballot]
Token: Ross Callon
INTVoIP Configuration Server Address Option (Informational) - 2 of 3
draft-raj-dhc-tftp-addr-option-04.txt [Open Web Ballot]
Token: Jari Arkko
INTService Selection for Mobile IPv4 (Informational) - 3 of 3
draft-korhonen-mip4-service-07.txt
Token: Jari Arkko
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
         
AreaDate
APPDec 11Message Organization (morg) - 1 of 1
Token:Chris
         

4.2 WG Rechartering

          4.2.1 Under evaluation for IETF Review
         
AreaDate
OPSDec 17Network Configuration (netconf) - 1 of 2
Token:Dan
TSVDec 19IP Performance Metrics (ippm) - 2 of 2
Token:Lars
          4.2.2 Proposed for Approval
                    NONE

5. IAB News We Can Use

6. Management Issues

6.1 Nomcom appointment to the IAOC (Ross Callon)

7. Working Group News

--===============0298885193== 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@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist --===============0298885193==-- From iesg-agenda-dist-bounces@ietf.org Fri Jan 2 09:19:47 2009 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 6061828C11E; Fri, 2 Jan 2009 09:19:47 -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 424413A6825; Fri, 2 Jan 2009 09:19:46 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090102171946.424413A6825@core3.amsl.com> Date: Fri, 2 Jan 2009 09:19:46 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 8, 2009 X-BeenThere: iesg-agenda-dist@ietf.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@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the January 8, 2009 IESG Teleconference This agenda was generated at 9:19:46 EDT, January 2, 2009 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-isis-wg-extlsp-05.txt Simplified Extension of LSP Space for IS-IS (Proposed Standard) - 1 of 3 Token: Ross Callon o draft-ietf-sip-session-policy-framework-05.txt A Framework for Session Initiation Protocol (SIP) Session Policies (Proposed Standard) - 2 of 3 Token: Cullen Jennings o draft-ietf-idr-rfc3392bis-03.txt Capabilities Advertisement with BGP-4 (Proposed Standard) - 3 of 3 Token: David Ward 2.1.2 Returning Item o draft-ietf-smime-3851bis-08.txt Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification (Proposed Standard) - 1 of 2 Token: Tim Polk o draft-ietf-smime-3850bis-08.txt Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling (Proposed Standard) - 2 of 2 Token: Tim Polk 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item o draft-housley-iesg-rfc3932bis-06.txt IESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1 Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html Token: Jari Arkko 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-tls-des-idea-02.txt DES and IDEA Cipher Suites for Transport Layer Security (TLS) (Informational) - 1 of 2 Token: Tim Polk o draft-ietf-ippm-delay-var-as-01.txt Packet Delay Variation Applicability Statement (Informational) - 2 of 2 Token: Lars Eggert 3.1.2 Returning Item o draft-ietf-pim-rpf-vector-06.txt The RPF Vector TLV (Informational) - 1 of 1 Token: David Ward 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-dasgupta-ccamp-path-comp-analysis-02.txt Performance Analysis of Inter-Domain Path Computation Methodologies (Informational) - 1 of 3 Token: Ross Callon o draft-raj-dhc-tftp-addr-option-04.txt VoIP Configuration Server Address Option (Informational) - 2 of 3 Token: Jari Arkko o draft-korhonen-mip4-service-07.txt Service Selection for Mobile IPv4 (Informational) - 3 of 3 Token: Jari Arkko 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 o Message Organization (morg) - 1 of 1 Token: Chris 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review o Network Configuration (netconf) - 1 of 2 Token: Dan o IP Performance Metrics (ippm) - 2 of 2 Token: Lars 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 6.1 Nomcom appointment to the IAOC (Ross Callon) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist From iesg-agenda-dist-bounces@ietf.org Thu Jan 8 15:04:54 2009 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 B3A183A6A47; Thu, 8 Jan 2009 15:04:54 -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 732EE3A6A47; Thu, 8 Jan 2009 15:04:53 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090108230453.732EE3A6A47@core3.amsl.com> Date: Thu, 8 Jan 2009 15:04:53 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for January 15, 2009 X-BeenThere: iesg-agenda-dist@ietf.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="===============0942898975==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0942898975== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

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

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
RTGEncoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) (Proposed Standard) - 1 of 3
draft-ietf-pce-of-06.txt [Open Web Ballot]
Token: Ross Callon
RTGDiff-Serv Aware Class Type Object for Path Computation Element Communication Protocol (Proposed Standard) - 2 of 3
draft-ietf-pce-dste-02.txt [Open Web Ballot]
Token: Ross Callon
APPA Protocol for Remotely Managing Sieve Scripts (Proposed Standard) - 3 of 3
draft-ietf-sieve-managesieve-06.txt [Open Web Ballot]
Token: Lisa Dusseault
2.1.2 Returning Item
      AreaDate
SECDomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP) (Proposed Standard) - 1 of 1
draft-ietf-dkim-ssp-08.txt
Note: Document shepherd is Stephen Farrell (stephen.farrell@cs.tcd.ie)
Token: Pasi Eronen

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
GENVouch By Reference (Proposed Standard) - 1 of 1
draft-hoffman-dac-vbr-05.txt [Open Web Ballot]
Token: Russ Housley
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
RTGMANET Extension of OSPF using CDS Flooding (Experimental) - 1 of 3
draft-ietf-ospf-manet-mdr-04.txt [Open Web Ballot]
Token: David Ward
RTGOSPF MPR Extension for Ad Hoc Networks (Experimental) - 2 of 3
draft-ietf-ospf-manet-mpr-03.txt [Open Web Ballot]
Token: David Ward
RTGExtensions to OSPF to Support Mobile Ad Hoc Networking (Experimental) - 3 of 3
draft-ietf-ospf-manet-or-01.txt [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

6.1 Draft Statement on BCP Status for Examples (Dan Romascanu)

7. Working Group News

--===============0942898975== 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@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist --===============0942898975==-- From iesg-agenda-dist-bounces@ietf.org Thu Jan 8 15:04:54 2009 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 D00313A6AFD; Thu, 8 Jan 2009 15:04:54 -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 750193A67F8; Thu, 8 Jan 2009 15:04:53 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090108230453.750193A67F8@core3.amsl.com> Date: Thu, 8 Jan 2009 15:04:53 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 15, 2009 X-BeenThere: iesg-agenda-dist@ietf.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@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the January 15, 2009 IESG Teleconference This agenda was generated at 15:4:53 EDT, January 8, 2009 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-pce-of-06.txt Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) (Proposed Standard) - 1 of 3 Token: Ross Callon o draft-ietf-pce-dste-02.txt Diff-Serv Aware Class Type Object for Path Computation Element Communication Protocol (Proposed Standard) - 2 of 3 Token: Ross Callon o draft-ietf-sieve-managesieve-06.txt A Protocol for Remotely Managing Sieve Scripts (Proposed Standard) - 3 of 3 Token: Lisa Dusseault 2.1.2 Returning Item o draft-ietf-dkim-ssp-08.txt DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP) (Proposed Standard) - 1 of 1 Note: Document shepherd is Stephen Farrell (stephen.farrell@cs.tcd.ie) Token: Pasi Eronen 2.2 Individual Submissions 2.2.1 New Item o draft-hoffman-dac-vbr-05.txt Vouch By Reference (Proposed Standard) - 1 of 1 Token: Russ Housley 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-ospf-manet-mdr-04.txt MANET Extension of OSPF using CDS Flooding (Experimental) - 1 of 3 Token: David Ward o draft-ietf-ospf-manet-mpr-03.txt OSPF MPR Extension for Ad Hoc Networks (Experimental) - 2 of 3 Token: David Ward o draft-ietf-ospf-manet-or-01.txt Extensions to OSPF to Support Mobile Ad Hoc Networking (Experimental) - 3 of 3 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 , 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 NONE 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 6.1 Draft Statement on BCP Status for Examples (Dan Romascanu) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist From iesg-agenda-dist-bounces@ietf.org Thu Jan 22 14:40:26 2009 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 016AA3A68F4; Thu, 22 Jan 2009 14:40:26 -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 6E0483A68B2; Thu, 22 Jan 2009 14:40:24 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090122224024.6E0483A68B2@core3.amsl.com> Date: Thu, 22 Jan 2009 14:40:24 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for January 29, 2009 X-BeenThere: iesg-agenda-dist@ietf.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="===============0381359213==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0381359213== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

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

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
INTNEMO Management Information Base (Proposed Standard) - 1 of 6
draft-ietf-mext-nemo-mib-04.txt [Open Web Ballot]
Token: Jari Arkko
OPSRemote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management (Proposed Standard) - 2 of 6
draft-ietf-radext-management-authorization-06.txt [Open Web Ballot]
Token: Dan Romascanu
SECUpdate for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3 of 6
draft-ietf-pkix-rfc4055-update-01.txt [Open Web Ballot]
Token: Pasi Eronen
INTBGP Traffic Engineering Attribute (Proposed Standard) - 4 of 6
draft-ietf-softwire-bgp-te-attribute-04.txt [Open Web Ballot]
Token: Mark Townsley
SECPre-Shared Key Cipher Suites for Transport Layer Security (TLS) with SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 5 of 6
draft-ietf-tls-psk-new-mac-aes-gcm-05.txt [Open Web Ballot]
Note: Document Shepherd is jsalowey@cisco.com
Token: Pasi Eronen
RTGDissemination of flow specification rules (Proposed Standard) - 6 of 6
draft-ietf-idr-flow-spec-03.txt [Open Web Ballot]
Token: David Ward
2.1.2 Returning Item
      AreaDate
INTIEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed Standard) - 1 of 5
draft-ietf-mipshop-mstp-solution-11.txt [Open Web Ballot]
Token: Jari Arkko
INTSoftwire Mesh Framework (Proposed Standard) - 2 of 5
draft-ietf-softwire-mesh-framework-05.txt [Open Web Ballot]
Token: Mark Townsley
INTBGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute (Proposed Standard) - 3 of 5
draft-ietf-softwire-encaps-safi-04.txt [Open Web Ballot]
Token: Mark Townsley
INTBGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 4 of 5
draft-ietf-softwire-encaps-ipsec-01.txt [Open Web Ballot]
Token: Mark Townsley
INTAdvertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) - 5 of 5
draft-ietf-softwire-v4nlri-v6nh-01.txt [Open Web Ballot]
Token: Mark Townsley

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
SECCommon Architecture Label IPv6 Security Option (CALIPSO) (Proposed Standard) - 1 of 3
draft-stjohns-sipso-06.txt [Open Web Ballot]
Token: Tim Polk
GENVouch By Reference (Proposed Standard) - 2 of 3
draft-hoffman-dac-vbr-05.txt [Open Web Ballot]
Token: Russ Housley
APPThe Sieve mail filtering language - extensions for checking mailbox status and accessing mailbox metadata (Proposed Standard) - 3 of 3
draft-melnikov-sieve-imapext-metadata-08.txt [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
INTTransparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (Informational) - 1 of 2
draft-ietf-trill-prob-05.txt [Open Web Ballot]
Token: Mark Townsley
SECECDHE_PSK Ciphersuites for Transport Layer Security (TLS) (Informational) - 2 of 2
draft-ietf-tls-ecdhe-psk-05.txt [Open Web Ballot]
Token: Pasi Eronen
3.1.2 Returning Item
      AreaDate
RTGThe RPF Vector TLV (Informational) - 1 of 1
draft-ietf-pim-rpf-vector-08.txt [Open Web Ballot]
Token: David Ward

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
3.3.3 For Action
      AreaDate
GENAnalysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2
draft-irtf-routing-history-09.txt
Token: Russ Housley
GENA Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2
draft-irtf-routing-reqs-10.txt
Token: Russ Housley

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
         
AreaDate
OPSDec 17Network Configuration (netconf) - 1 of 2
Token:Dan
TSVDec 19IP Performance Metrics (ippm) - 2 of 2
Token:Lars

5. IAB News We Can Use

6. Management Issues

6.1 IESG Statement regarding chartered work overcome by events before IESG consideration (Ron Bonica)

7. Working Group News

--===============0381359213== 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@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist --===============0381359213==-- From iesg-agenda-dist-bounces@ietf.org Thu Jan 22 14:40:26 2009 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 2335028C17F; Thu, 22 Jan 2009 14:40:26 -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 750973A6828; Thu, 22 Jan 2009 14:40:24 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090122224024.750973A6828@core3.amsl.com> Date: Thu, 22 Jan 2009 14:40:24 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 29, 2009 X-BeenThere: iesg-agenda-dist@ietf.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@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the January 29, 2009 IESG Teleconference This agenda was generated at 14:40:24 EDT, January 22, 2009 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-mext-nemo-mib-04.txt NEMO Management Information Base (Proposed Standard) - 1 of 10 Token: Jari Arkko o draft-ietf-radext-management-authorization-06.txt Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management (Proposed Standard) - 2 of 10 Token: Dan Romascanu o draft-ietf-pkix-rfc4055-update-01.txt Update for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3 of 10 Token: Pasi Eronen o draft-ietf-softwire-mesh-framework-05.txt Softwire Mesh Framework (Proposed Standard) - 4 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-safi-04.txt BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute (Proposed Standard) - 5 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-ipsec-01.txt BGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 6 of 10 Token: Mark Townsley o draft-ietf-softwire-bgp-te-attribute-04.txt BGP Traffic Engineering Attribute (Proposed Standard) - 7 of 10 Token: Mark Townsley o draft-ietf-softwire-v4nlri-v6nh-01.txt Advertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) - 8 of 10 Token: Mark Townsley o draft-ietf-tls-psk-new-mac-aes-gcm-05.txt Pre-Shared Key Cipher Suites for Transport Layer Security (TLS) with SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 9 of 10 Note: Document Shepherd is jsalowey@cisco.com Token: Pasi Eronen o draft-ietf-idr-flow-spec-03.txt Dissemination of flow specification rules (Proposed Standard) - 10 of 10 Token: David Ward 2.1.2 Returning Item o draft-ietf-mipshop-mstp-solution-11.txt IEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed Standard) - 1 of 1 Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item o draft-stjohns-sipso-06.txt Common Architecture Label IPv6 Security Option (CALIPSO) (Proposed Standard) - 1 of 3 Token: Tim Polk o draft-hoffman-dac-vbr-05.txt Vouch By Reference (Proposed Standard) - 2 of 3 Token: Russ Housley o draft-melnikov-sieve-imapext-metadata-08.txt The Sieve mail filtering language - extensions for checking mailbox status and accessing mailbox metadata (Proposed Standard) - 3 of 3 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 o draft-ietf-trill-prob-05.txt Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (Informational) - 1 of 3 Token: Mark Townsley o draft-ietf-pim-rpf-vector-08.txt The RPF Vector TLV (Informational) - 2 of 3 Token: David Ward o draft-ietf-tls-ecdhe-psk-05.txt ECDHE_PSK Ciphersuites for Transport Layer Security (TLS) (Informational) - 3 of 3 Token: Pasi Eronen 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 , 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 3.3.3 For Action o draft-irtf-routing-history-09.txt Analysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2 Token: Russ Housley o draft-irtf-routing-reqs-10.txt A Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2 Token: Russ Housley 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 o Network Configuration (netconf) - 1 of 2 Token: Dan o IP Performance Metrics (ippm) - 2 of 2 Token: Lars 5. IAB News We can use 6. Management Issue 6.1 IESG Statement regarding chartered work overcome by events before IESG consideration (Ron Bonica) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist From iesg-agenda-dist-bounces@ietf.org Fri Jan 23 06:58:26 2009 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 5584E3A6AC0; Fri, 23 Jan 2009 06:58:26 -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 5B50128C1A7; Fri, 23 Jan 2009 06:58:24 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090123145825.5B50128C1A7@core3.amsl.com> Date: Fri, 23 Jan 2009 06:58:25 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for January 29, 2009 X-BeenThere: iesg-agenda-dist@ietf.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="===============0090334235==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0090334235== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

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

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
INTNEMO Management Information Base (Proposed Standard) - 1 of 10
draft-ietf-mext-nemo-mib-04.txt [Open Web Ballot]
Token: Jari Arkko
OPSRemote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management (Proposed Standard) - 2 of 10
draft-ietf-radext-management-authorization-06.txt [Open Web Ballot]
Token: Dan Romascanu
SECUpdate for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3 of 10
draft-ietf-pkix-rfc4055-update-01.txt [Open Web Ballot]
Token: Pasi Eronen
INTSoftwire Mesh Framework (Proposed Standard) - 4 of 10
draft-ietf-softwire-mesh-framework-05.txt [Open Web Ballot]
Token: Mark Townsley
INTBGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute (Proposed Standard) - 5 of 10
draft-ietf-softwire-encaps-safi-04.txt [Open Web Ballot]
Token: Mark Townsley
INTBGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 6 of 10
draft-ietf-softwire-encaps-ipsec-01.txt [Open Web Ballot]
Token: Mark Townsley
INTBGP Traffic Engineering Attribute (Proposed Standard) - 7 of 10
draft-ietf-softwire-bgp-te-attribute-04.txt [Open Web Ballot]
Token: Mark Townsley
INTAdvertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) - 8 of 10
draft-ietf-softwire-v4nlri-v6nh-01.txt [Open Web Ballot]
Token: Mark Townsley
SECPre-Shared Key Cipher Suites for Transport Layer Security (TLS) with SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 9 of 10
draft-ietf-tls-psk-new-mac-aes-gcm-05.txt [Open Web Ballot]
Note: Document Shepherd is jsalowey@cisco.com
Token: Pasi Eronen
RTGDissemination of flow specification rules (Proposed Standard) - 10 of 10
draft-ietf-idr-flow-spec-04.txt [Open Web Ballot]
Token: David Ward
2.1.2 Returning Item
      AreaDate
INTIEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed Standard) - 1 of 1
draft-ietf-mipshop-mstp-solution-11.txt [Open Web Ballot]
Token: Jari Arkko

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
SECCommon Architecture Label IPv6 Security Option (CALIPSO) (Proposed Standard) - 1 of 4
draft-stjohns-sipso-06.txt [Open Web Ballot]
Token: Tim Polk
GENVouch By Reference (Proposed Standard) - 2 of 4
draft-hoffman-dac-vbr-05.txt [Open Web Ballot]
Token: Russ Housley
RAIInternet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) (Proposed Standard) - 3 of 4
draft-loreto-simple-im-srv-label-03.txt [Open Web Ballot]
Token: Jon Peterson
APPThe Sieve mail filtering language - extensions for checking mailbox status and accessing mailbox metadata (Proposed Standard) - 4 of 4
draft-melnikov-sieve-imapext-metadata-08.txt [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
RAISPEERMINT Terminology (Informational) - 1 of 4
draft-ietf-speermint-terminology-17.txt [Open Web Ballot]
Token: Jon Peterson
INTTransparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (Informational) - 2 of 4
draft-ietf-trill-prob-05.txt [Open Web Ballot]
Token: Mark Townsley
RTGThe RPF Vector TLV (Informational) - 3 of 4
draft-ietf-pim-rpf-vector-08.txt [Open Web Ballot]
Token: David Ward
SECECDHE_PSK Ciphersuites for Transport Layer Security (TLS) (Informational) - 4 of 4
draft-ietf-tls-ecdhe-psk-05.txt [Open Web Ballot]
Token: Pasi Eronen
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
3.3.3 For Action
      AreaDate
GENAnalysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2
draft-irtf-routing-history-09.txt
Token: Russ Housley
GENA Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2
draft-irtf-routing-reqs-10.txt
Token: Russ Housley

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
         
AreaDate
OPSDec 17Network Configuration (netconf) - 1 of 2
Token:Dan
TSVDec 19IP Performance Metrics (ippm) - 2 of 2
Token:Lars

5. IAB News We Can Use

6. Management Issues

6.1 IESG Statement regarding chartered work overcome by events before IESG consideration (Ron Bonica)

7. Working Group News

--===============0090334235== 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@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist --===============0090334235==-- From iesg-agenda-dist-bounces@ietf.org Fri Jan 23 06:58:26 2009 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 70C7328C1D1; Fri, 23 Jan 2009 06:58:26 -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 61CA33A6ABF; Fri, 23 Jan 2009 06:58:24 -0800 (PST) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20090123145825.61CA33A6ABF@core3.amsl.com> Date: Fri, 23 Jan 2009 06:58:25 -0800 (PST) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for January 29, 2009 X-BeenThere: iesg-agenda-dist@ietf.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@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the January 29, 2009 IESG Teleconference This agenda was generated at 6:58:25 EDT, January 23, 2009 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-mext-nemo-mib-04.txt NEMO Management Information Base (Proposed Standard) - 1 of 10 Token: Jari Arkko o draft-ietf-radext-management-authorization-06.txt Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management (Proposed Standard) - 2 of 10 Token: Dan Romascanu o draft-ietf-pkix-rfc4055-update-01.txt Update for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3 of 10 Token: Pasi Eronen o draft-ietf-softwire-mesh-framework-05.txt Softwire Mesh Framework (Proposed Standard) - 4 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-safi-04.txt BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute (Proposed Standard) - 5 of 10 Token: Mark Townsley o draft-ietf-softwire-encaps-ipsec-01.txt BGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 6 of 10 Token: Mark Townsley o draft-ietf-softwire-bgp-te-attribute-04.txt BGP Traffic Engineering Attribute (Proposed Standard) - 7 of 10 Token: Mark Townsley o draft-ietf-softwire-v4nlri-v6nh-01.txt Advertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) - 8 of 10 Token: Mark Townsley o draft-ietf-tls-psk-new-mac-aes-gcm-05.txt Pre-Shared Key Cipher Suites for Transport Layer Security (TLS) with SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 9 of 10 Note: Document Shepherd is jsalowey@cisco.com Token: Pasi Eronen o draft-ietf-idr-flow-spec-04.txt Dissemination of flow specification rules (Proposed Standard) - 10 of 10 Token: David Ward 2.1.2 Returning Item o draft-ietf-mipshop-mstp-solution-11.txt IEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed Standard) - 1 of 1 Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item o draft-stjohns-sipso-06.txt Common Architecture Label IPv6 Security Option (CALIPSO) (Proposed Standard) - 1 of 4 Token: Tim Polk o draft-hoffman-dac-vbr-05.txt Vouch By Reference (Proposed Standard) - 2 of 4 Token: Russ Housley o draft-loreto-simple-im-srv-label-03.txt Internet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) (Proposed Standard) - 3 of 4 Token: Jon Peterson o draft-melnikov-sieve-imapext-metadata-08.txt The Sieve mail filtering language - extensions for checking mailbox status and accessing mailbox metadata (Proposed Standard) - 4 of 4 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 o draft-ietf-speermint-terminology-17.txt SPEERMINT Terminology (Informational) - 1 of 4 Token: Jon Peterson o draft-ietf-trill-prob-05.txt Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement (Informational) - 2 of 4 Token: Mark Townsley o draft-ietf-pim-rpf-vector-08.txt The RPF Vector TLV (Informational) - 3 of 4 Token: David Ward o draft-ietf-tls-ecdhe-psk-05.txt ECDHE_PSK Ciphersuites for Transport Layer Security (TLS) (Informational) - 4 of 4 Token: Pasi Eronen 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 , 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 3.3.3 For Action o draft-irtf-routing-history-09.txt Analysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2 Token: Russ Housley o draft-irtf-routing-reqs-10.txt A Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2 Token: Russ Housley 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 o Network Configuration (netconf) - 1 of 2 Token: Dan o IP Performance Metrics (ippm) - 2 of 2 Token: Lars 5. IAB News We can use 6. Management Issue 6.1 IESG Statement regarding chartered work overcome by events before IESG consideration (Ron Bonica) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist