From wwwrun@core3.amsl.com Thu Apr 2 14:54:10 2009 Return-Path: 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 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, 2 Apr 2009 14:54:10 -0700 (PDT) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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
draft-ietf-nsis-ntlp-19.txt [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
draft-ietf-behave-turn-13.txt [Open Web Ballot]
Token: Magnus Westerlund
RTGLDP Capabilities (Proposed Standard) - 3 of 9
draft-ietf-mpls-ldp-capabilities-03.txt [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
draft-ietf-kitten-gssapi-channel-bindings-06.txt [Open Web Ballot]
Note: proto writeup received...
Token: Tim Polk
INTSoftwire Security Analysis and Requirements (Proposed Standard) - 5 of 9
draft-ietf-softwire-security-requirements-07.txt [Open Web Ballot]
Token: Mark Townsley
INTNetwork Time Protocol Version 4 Protocol And Algorithms Specification (Proposed Standard) - 6 of 9
draft-ietf-ntp-ntpv4-proto-11.txt [Open Web Ballot]
Token: Mark Townsley
INTDefinitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) (Proposed Standard) - 7 of 9
draft-ietf-ntp-ntpv4-mib-05.txt [Open Web Ballot]
Token: Mark Townsley
RTGRSVP Extensions for Path Key Support (Proposed Standard) - 8 of 9
draft-ietf-ccamp-path-key-ero-04.txt [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
draft-ietf-pce-global-concurrent-optimization-10.txt [Open Web Ballot]
Token: Ross Callon
2.1.2 Returning Item
      AreaDate
TSVA One-Way Packet Duplication Metric (Proposed Standard) - 1 of 1
draft-ietf-ippm-duplicate-07.txt [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
draft-ietf-lemonade-streaming-10.txt [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
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

From wwwrun@core3.amsl.com Thu Apr 2 14:54:10 2009 Return-Path: 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 3E4C73A6B92; Thu, 2 Apr 2009 14:54:09 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090402215410.3E4C73A6B92@core3.amsl.com> Date: Thu, 2 Apr 2009 14:54:10 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2009 21:54:10 -0000 INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the April 9, 2009 IESG Teleconference This agenda was generated at 14:54:10 EDT, April 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-nsis-ntlp-19.txt GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 9 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 o draft-ietf-behave-turn-13.txt Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) (Proposed Standard) - 2 of 9 Token: Magnus Westerlund o draft-ietf-mpls-ldp-capabilities-03.txt LDP Capabilities (Proposed Standard) - 3 of 9 Token: Ross Callon o draft-ietf-kitten-gssapi-channel-bindings-06.txt Clarifications and Extensions to the GSS-API for the Use of Channel Bindings (Proposed Standard) - 4 of 9 Note: proto writeup received... Token: Tim Polk o draft-ietf-softwire-security-requirements-07.txt Softwire Security Analysis and Requirements (Proposed Standard) - 5 of 9 Token: Mark Townsley o draft-ietf-ntp-ntpv4-proto-11.txt Network Time Protocol Version 4 Protocol And Algorithms Specification (Proposed Standard) - 6 of 9 Token: Mark Townsley o draft-ietf-ntp-ntpv4-mib-05.txt Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) (Proposed Standard) - 7 of 9 Token: Mark Townsley o draft-ietf-ccamp-path-key-ero-04.txt RSVP Extensions for Path Key Support (Proposed Standard) - 8 of 9 Token: Ross Callon o draft-ietf-pce-global-concurrent-optimization-10.txt Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions In Support of Global Concurrent Optimization (Proposed Standard) - 9 of 9 Token: Ross Callon 2.1.2 Returning Item o draft-ietf-ippm-duplicate-07.txt A One-Way Packet Duplication Metric (Proposed Standard) - 1 of 1 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 o draft-ietf-lemonade-streaming-10.txt Streaming Internet Messaging Attachments (Informational) - 1 of 1 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 , 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 o draft-despres-6rd-02.txt IPv6 Rapid Deployment on IPv4 infrastructures (6rd) (Informational) - 1 of 1 Token: Jari Arkko 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Multiple Interfaces (mif) - 1 of 1 Token: Jari 4.1.2 Proposed for Approval o Locator/ID Separation Protocol (lisp) - 1 of 3 Token: Jari o Session Initiation Protocol Core (sipcore) - 2 of 3 Token: Cullen o Dispatch (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 Issue 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. Agenda Working Group News From wwwrun@core3.amsl.com Thu Apr 16 14:29:08 2009 Return-Path: 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 9129C3A69B4; Thu, 16 Apr 2009 14:29:08 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/html; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090416212908.9129C3A69B4@core3.amsl.com> Date: Thu, 16 Apr 2009 14:29:08 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for April 23, 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: , X-List-Received-Date: Thu, 16 Apr 2009 21:29:08 -0000 IESG Agenda

IESG Agenda

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


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
TSVImproving TCP's Robustness to Blind In-Window Attacks (Proposed Standard) - 1 of 10
draft-ietf-tcpm-tcpsecure-11.txt [Open Web Ballot]
Note: IESG: Please read the Document Shepherd Writeup, we need to discuss the "Updates: 793" issue.
Token: Lars Eggert
OPSRADIUS Design Guidelines (BCP) - 2 of 10
draft-ietf-radext-design-07.txt [Open Web Ballot]
Token: Dan Romascanu
OPSExporting Type Information for IPFIX Information Elements (Proposed Standard) - 3 of 10
draft-ietf-ipfix-exporting-type-03.txt [Open Web Ballot]
Token: Dan Romascanu
OPSSpecification of the IPFIX File Format (Proposed Standard) - 4 of 10
draft-ietf-ipfix-file-03.txt [Open Web Ballot]
Token: Dan Romascanu
OPSDiameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (Proposed Standard) - 5 of 10
draft-ietf-dime-mip6-split-16.txt [Open Web Ballot]
Token: Dan Romascanu
INTGRE Key Option for Proxy Mobile IPv6 (Proposed Standard) - 6 of 10
draft-ietf-netlmm-grekey-option-06.txt [Open Web Ballot]
Token: Jari Arkko
INTContainer Option for Server Configuration (Proposed Standard) - 7 of 10
draft-ietf-dhc-container-opt-05.txt [Open Web Ballot]
Token: Jari Arkko
SECAn Internet Attribute Certificate Profile for Authorization (Proposed Standard) - 8 of 10
draft-ietf-pkix-3281update-04.txt [Open Web Ballot]
Token: Tim Polk
TSVThe DCCP Service Code (Proposed Standard) - 9 of 10
draft-ietf-dccp-serv-codes-08.txt [Open Web Ballot]
Token: Lars Eggert
GENCryptographic Message Syntax (CMS) (Draft) - 10 of 10
rfc3852.txt [Open Web Ballot]
Token: Tim Polk
2.1.2 Returning Item
      AreaDate
RAICarrying Location Objects in RADIUS and Diameter (Proposed Standard) - 1 of 1
draft-ietf-geopriv-radius-lo-23.txt [Open Web Ballot]
Note: Did new LC because previous one did not mention DOWNREF.
Token: Cullen Jennings

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
INTExtending ICMP for Interface and Next-hop Identification (Proposed Standard) - 1 of 1
draft-atlas-icmp-unnumbered-06.txt [Open Web Ballot]
Token: Jari Arkko
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
TSVAdding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) - 1 of 3
draft-ietf-tcpm-ecnsyn-08.txt [Open Web Ballot]
Token: Lars Eggert
RTGOSPFv2 Routing Protocols Extensions for ASON Routing (Experimental) - 2 of 3
draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt [Open Web Ballot]
Token: Adrian Farrel
INTState Machines for Protocol for Carrying Authentication for Network Access (PANA) (Informational) - 3 of 3
draft-ietf-pana-statemachine-10.txt [Open Web Ballot]
Token: Jari Arkko
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
      AreaDate
GENECC Brainpool Standard Curves and Curve Generation (Informational) - 1 of 2
draft-lochter-pkix-brainpool-ecc-03.txt [Open Web Ballot]
Note: waiting for confirmation that no IPR disclosure is needed.
Token: Tim Polk
INTPPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 2 of 2
draft-bberry-rfc4938bis-00.txt [Open Web Ballot]
Token: Jari Arkko

4. Working Group Actions

         

4.1 WG Creation

          4.1.1 Proposed for IETF Review
         
AreaDate
APPApr 6Open Web authentication (oauth) - 1 of 1
Token:Lisa
          4.1.2 Proposed for Approval
         
AreaDate
INTApr 2Multiple Interfaces (mif) - 1 of 3
Token:Jari
INTMar 5Locator/ID Separation Protocol (lisp) - 2 of 3
Token:Jari
INTApr 3Network-Based Mobility Extensions (netext) - 3 of 3
Token:Jari
         

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 LS response to ITU-T SG11 (Lars Eggert)
6.2 Dean Anderson and tools.ietf.org (Russ Housley)
6.3 Approve IANA expert for CAPWAP (Russ Housley)
6.4 Assignment of media type action point to Alexey (Magnus Westerlund)
6.5 ISOC BoT Appointment Confirmation (Executive Session) (Russ Housley)
6.6 Last Call issue raised for draft-iana-rfc3330bis (Russ Housley)

7. Working Group News

From wwwrun@core3.amsl.com Thu Apr 16 14:29:08 2009 Return-Path: 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 9905B3A6946; Thu, 16 Apr 2009 14:29:08 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090416212908.9905B3A6946@core3.amsl.com> Date: Thu, 16 Apr 2009 14:29:08 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for April 23, 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: , X-List-Received-Date: Thu, 16 Apr 2009 21:29:08 -0000 INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the April 23, 2009 IESG Teleconference This agenda was generated at 14:29:8 EDT, April 16, 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-tcpm-tcpsecure-11.txt Improving TCP's Robustness to Blind In-Window Attacks (Proposed Standard) - 1 of 10 Note: IESG: Please read the Document Shepherd Writeup, we need to discuss the "Updates: 793" issue. Token: Lars Eggert o draft-ietf-radext-design-07.txt RADIUS Design Guidelines (BCP) - 2 of 10 Token: Dan Romascanu o draft-ietf-ipfix-exporting-type-03.txt Exporting Type Information for IPFIX Information Elements (Proposed Standard) - 3 of 10 Token: Dan Romascanu o draft-ietf-ipfix-file-03.txt Specification of the IPFIX File Format (Proposed Standard) - 4 of 10 Token: Dan Romascanu o draft-ietf-dime-mip6-split-16.txt Diameter Mobile IPv6: Support for Home Agent to Diameter Server Interaction (Proposed Standard) - 5 of 10 Token: Dan Romascanu o draft-ietf-netlmm-grekey-option-06.txt GRE Key Option for Proxy Mobile IPv6 (Proposed Standard) - 6 of 10 Token: Jari Arkko o draft-ietf-dhc-container-opt-05.txt Container Option for Server Configuration (Proposed Standard) - 7 of 10 Token: Jari Arkko o draft-ietf-pkix-3281update-04.txt An Internet Attribute Certificate Profile for Authorization (Proposed Standard) - 8 of 10 Token: Tim Polk o draft-ietf-dccp-serv-codes-08.txt The DCCP Service Code (Proposed Standard) - 9 of 10 Token: Lars Eggert o rfc3852.txt Cryptographic Message Syntax (CMS) (Draft Standard) - 10 of 10 Token: Tim Polk 2.1.2 Returning Item o draft-ietf-geopriv-radius-lo-23.txt Carrying Location Objects in RADIUS and Diameter (Proposed Standard) - 1 of 1 Note: Did new LC because previous one did not mention DOWNREF. Token: Cullen Jennings 2.2 Individual Submissions 2.2.1 New Item o draft-atlas-icmp-unnumbered-06.txt Extending ICMP for Interface and Next-hop Identification (Proposed Standard) - 1 of 1 Token: Jari Arkko 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-tcpm-ecnsyn-08.txt Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) - 1 of 3 Token: Lars Eggert o draft-ietf-ccamp-gmpls-ason-routing-ospf-08.txt OSPFv2 Routing Protocols Extensions for ASON Routing (Experimental) - 2 of 3 Token: Adrian Farrel o draft-ietf-pana-statemachine-10.txt State Machines for Protocol for Carrying Authentication for Network Access (PANA) (Informational) - 3 of 3 Token: Jari Arkko 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 o draft-lochter-pkix-brainpool-ecc-03.txt ECC Brainpool Standard Curves and Curve Generation (Informational) - 1 of 2 Note: waiting for confirmation that no IPR disclosure is needed. Token: Tim Polk o draft-bberry-rfc4938bis-00.txt PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 2 of 2 Token: Jari Arkko 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Open Web authentication (oauth) - 1 of 1 Token: Lisa 4.1.2 Proposed for Approval o Multiple Interfaces (mif) - 1 of 3 Token: Jari o Locator/ID Separation Protocol (lisp) - 2 of 3 Token: Jari o Network-Based Mobility Extensions (netext) - 3 of 3 Token: Jari 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 LS response to ITU-T SG11 (Lars Eggert) 6.2 Dean Anderson and tools.ietf.org (Russ Housley) 6.3 Approve IANA expert for CAPWAP (Russ Housley) 6.4 Assignment of media type action point to Alexey (Magnus Westerlund) 6.5 ISOC BoT Appointment Confirmation (Executive Session) (Russ Housley) 6.6 Last Call issue raised for draft-iana-rfc3330bis (Russ Housley) 7. Agenda Working Group News From wwwrun@core3.amsl.com Thu Apr 30 15:34:22 2009 Return-Path: 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 B545528C0D9; Thu, 30 Apr 2009 15:34:22 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/html; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090430223422.B545528C0D9@core3.amsl.com> Date: Thu, 30 Apr 2009 15:34:22 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for May 7, 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: , X-List-Received-Date: Thu, 30 Apr 2009 22:34:22 -0000 IESG Agenda

IESG Agenda

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


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
TSVImproving TCP's Robustness to Blind In-Window Attacks (Proposed Standard) - 1 of 11
draft-ietf-tcpm-tcpsecure-11.txt [Open Web Ballot]
Note: IESG: Please read the Document Shepherd Writeup, we need to discuss the "Updates: 793" issue.
Token: Lars Eggert
TSVRSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) - 2 of 11
draft-ietf-tsvwg-rsvp-proxy-proto-08.txt [Open Web Ballot]
Note: Please read the informational document draft-ietf-tsvwg-rsvp-proxy-approaches before this one!
Token: Magnus Westerlund
RTGPoint-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) module (Proposed Standard) - 3 of 11
draft-ietf-mpls-p2mp-te-mib-09.txt [Open Web Ballot]
Token: Ross Callon
OPSRADIUS Design Guidelines (BCP) - 4 of 11
draft-ietf-radext-design-07.txt [Open Web Ballot]
Token: Dan Romascanu
INTDynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 of 11
draft-ietf-mipshop-mos-dhcp-options-13.txt [Open Web Ballot]
Token: Jari Arkko
SECTransport Subsystem for the Simple Network Management Protocol (SNMP) (Proposed Standard) - 6 of 11
draft-ietf-isms-tmsm-17.txt [Open Web Ballot]
Token: Pasi Eronen
SECTransport Security Model for SNMP (Proposed Standard) - 7 of 11
draft-ietf-isms-transport-security-model-13.txt [Open Web Ballot]
Token: Pasi Eronen
SECSecure Shell Transport Model for SNMP (Proposed Standard) - 8 of 11
draft-ietf-isms-secshell-16.txt [Open Web Ballot]
Token: Pasi Eronen
SECRemote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models (Proposed Standard) - 9 of 11
draft-ietf-isms-radius-usage-06.txt [Open Web Ballot]
Token: Pasi Eronen
TSVThe DCCP Service Code (Proposed Standard) - 10 of 11
draft-ietf-dccp-serv-codes-09.txt [Open Web Ballot]
Token: Lars Eggert
INTMobile IPv6 Fast Handovers (Proposed Standard) - 11 of 11
draft-ietf-mipshop-rfc5268bis-01.txt [Open Web Ballot]
Note: http://www.arkko.com/ietf/mipshop/draft-ietf-mipshop-rfc5268bis-01-from-rfc5268.diff.html
Token: Jari Arkko
2.1.2 Returning Item
      NONE

2.2 Individual Submissions

          2.2.1 New Item
      AreaDate
APPAsynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP) (Proposed Standard) - 1 of 2
draft-thomson-beep-async-02.txt [Open Web Ballot]
Note: Chris Newman is the document shepherd.
Token: Alexey Melnikov
APPInternet Message Access Protocol (IMAP) - URL Access Identifier Extension (Proposed Standard) - 2 of 2
draft-ncook-urlauth-accessid-02.txt [Open Web Ballot]
Note: Eric Burger is the document shepherd. This document is a Normative dependency for a Lemonade WG document, updating another Lemonade document.
Token: Alexey Melnikov
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
TSVAdding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) - 1 of 5
draft-ietf-tcpm-ecnsyn-08.txt [Open Web Ballot]
Token: Lars Eggert
APPLemonade Notifications Architecture (Informational) - 2 of 5
draft-ietf-lemonade-notifications-10.txt [Open Web Ballot]
Note: Eric Burger is the document shepherd.
Token: Alexey Melnikov
SECThe Camellia Cipher in OpenPGP (Informational) - 3 of 5
draft-ietf-openpgp-camellia-04.txt [Open Web Ballot]
Note: Derek Atkins has agreed to shepherd
Token: Tim Polk
RTGIndustrial Routing Requirements in Low Power and Lossy Networks (Informational) - 4 of 5
draft-ietf-roll-indus-routing-reqs-05.txt [Open Web Ballot]
Note: This I-D was updated after IETF last call to synchronise with IESG review comments made for draft-ietf-roll-urban-routing-reqs. It also pickes up GenArt review coments.
Token: Adrian Farrel
TSVRSVP Proxy Approaches (Informational) - 5 of 5
draft-ietf-tsvwg-rsvp-proxy-approaches-06.txt [Open Web Ballot]
Note: Read this before the Protocol document
Token: Magnus Westerlund
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
RAIReport from the IETF workshop on P2P Infrastructure, May 28, 2008 (Informational) - 1 of 1
draft-p2pi-cooper-workshop-report-01.txt [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
      AreaDate
SECPassword-Authenticated Diffie-Hellman Exchange (PAK) (Informational) - 1 of 2
draft-brusilovsky-pak-10.txt [Open Web Ballot]
Token: Tim Polk
INTTransmission of IPv4 Packets over ISATAP Interfaces (Informational) - 2 of 2
draft-templin-isatapv4-02.txt [Open Web Ballot]
Token: Jari Arkko
3.3.2 Returning Item
      AreaDate
RAIMedia Server Markup Language (MSML) (Informational) - 1 of 1
draft-saleem-msml-08.txt [Open Web Ballot]
Token: Robert Sparks

4. Working Group Actions

         

4.1 WG Creation

          4.1.1 Proposed for IETF Review
         
AreaDate
APPApr 29Yet Another Mail (yam) - 1 of 3
Token:Alexey
TSVApr 25STORage Maintenance (storm) - 2 of 3
Token:Lars
APPApr 28Extensible Messaging and Presence Protocol (xmpp) - 3 of 3
Token:Cullen
          4.1.2 Proposed for Approval
         
AreaDate
APPApr 6Open Authentication Protocol (oauth) - 1 of 1
Token:Lisa
         

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

From wwwrun@core3.amsl.com Thu Apr 30 15:34:22 2009 Return-Path: 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 BF26C3A6EEC; Thu, 30 Apr 2009 15:34:22 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090430223422.BF26C3A6EEC@core3.amsl.com> Date: Thu, 30 Apr 2009 15:34:22 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for May 7, 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: , X-List-Received-Date: Thu, 30 Apr 2009 22:34:22 -0000 INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the May 7, 2009 IESG Teleconference This agenda was generated at 15:34:22 EDT, April 30, 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-tcpm-tcpsecure-11.txt Improving TCP's Robustness to Blind In-Window Attacks (Proposed Standard) - 1 of 11 Note: IESG: Please read the Document Shepherd Writeup, we need to discuss the "Updates: 793" issue. Token: Lars Eggert o draft-ietf-tsvwg-rsvp-proxy-proto-08.txt RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) - 2 of 11 Note: Please read the informational document draft-ietf-tsvwg-rsvp-proxy-approaches before this one! Token: Magnus Westerlund o draft-ietf-mpls-p2mp-te-mib-09.txt Point-to-Multipoint Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB) module (Proposed Standard) - 3 of 11 Token: Ross Callon o draft-ietf-radext-design-07.txt RADIUS Design Guidelines (BCP) - 4 of 11 Token: Dan Romascanu o draft-ietf-mipshop-mos-dhcp-options-13.txt Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery (Proposed Standard) - 5 of 11 Token: Jari Arkko o draft-ietf-isms-tmsm-17.txt Transport Subsystem for the Simple Network Management Protocol (SNMP) (Proposed Standard) - 6 of 11 Token: Pasi Eronen o draft-ietf-isms-transport-security-model-13.txt Transport Security Model for SNMP (Proposed Standard) - 7 of 11 Token: Pasi Eronen o draft-ietf-isms-secshell-16.txt Secure Shell Transport Model for SNMP (Proposed Standard) - 8 of 11 Token: Pasi Eronen o draft-ietf-isms-radius-usage-06.txt Remote Authentication Dial-In User Service (RADIUS) Usage for Simple Network Management Protocol (SNMP) Transport Models (Proposed Standard) - 9 of 11 Token: Pasi Eronen o draft-ietf-dccp-serv-codes-09.txt The DCCP Service Code (Proposed Standard) - 10 of 11 Token: Lars Eggert o draft-ietf-mipshop-rfc5268bis-01.txt Mobile IPv6 Fast Handovers (Proposed Standard) - 11 of 11 Note: http://www.arkko.com/ietf/mipshop/draft-ietf-mipshop-rfc5268bis-01-from-rfc5268.diff.html Token: Jari Arkko 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-thomson-beep-async-02.txt Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP) (Proposed Standard) - 1 of 2 Note: Chris Newman is the document shepherd.. Token: Alexey Melnikov o draft-ncook-urlauth-accessid-02.txt Internet Message Access Protocol (IMAP) - URL Access Identifier Extension (Proposed Standard) - 2 of 2 Note: Eric Burger is the document shepherd. This document is a Normative dependency for a Lemonade WG document, updating another Lemonade document.. Token: Alexey Melnikov 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-tcpm-ecnsyn-08.txt Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) - 1 of 5 Token: Lars Eggert o draft-ietf-lemonade-notifications-10.txt Lemonade Notifications Architecture (Informational) - 2 of 5 Note: Eric Burger is the document shepherd. Token: Alexey Melnikov o draft-ietf-openpgp-camellia-04.txt The Camellia Cipher in OpenPGP (Informational) - 3 of 5 Note: Derek Atkins has agreed to shepherd Token: Tim Polk o draft-ietf-roll-indus-routing-reqs-05.txt Industrial Routing Requirements in Low Power and Lossy Networks (Informational) - 4 of 5 Note: This I-D was updated after IETF last call to synchronise with IESG review comments made for draft-ietf-roll-urban-routing-reqs. It also pickes up GenArt review coments. Token: Adrian Farrel o draft-ietf-tsvwg-rsvp-proxy-approaches-06.txt RSVP Proxy Approaches (Informational) - 5 of 5 Note: Read this before the Protocol document Token: Magnus Westerlund 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 o draft-p2pi-cooper-workshop-report-01.txt Report from the IETF workshop on P2P Infrastructure, May 28, 2008 (Informational) - 1 of 1 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 , 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 o draft-brusilovsky-pak-10.txt Password-Authenticated Diffie-Hellman Exchange (PAK) (Informational) - 1 of 2 Token: Tim Polk o draft-templin-isatapv4-02.txt Transmission of IPv4 Packets over ISATAP Interfaces (Informational) - 2 of 2 Token: Jari Arkko 3.3.2 Returning Item o draft-saleem-msml-08.txt Media Server Markup Language (MSML) (Informational) - 1 of 1 Token: Robert Sparks 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Yet Another Mail (yam) - 1 of 3 Token: Alexey o STORage Maintenance (storm) - 2 of 3 Token: Lars o Extensible Messaging and Presence Protocol (xmpp) - 3 of 3 Token: Cullen 4.1.2 Proposed for Approval o Open Authentication Protocol (oauth) - 1 of 1 Token: Lisa 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 7. Agenda Working Group News