From iesg-agenda-dist-bounces@ietf.org Thu Oct 2 15:17:00 2008 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 BBFB33A6994; Thu, 2 Oct 2008 15:17:00 -0700 (PDT) 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 921DB3A6994; Thu, 2 Oct 2008 15:16:59 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081002221659.921DB3A6994@core3.amsl.com> Date: Thu, 2 Oct 2008 15:16:59 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for October 9, 2008 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="===============0770791737==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0770791737== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2008-10-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
RAITransmission Time offsets in RTP streams (Proposed Standard) - 1 of 6
draft-ietf-avt-rtp-toffset-07.txt [Open Web Ballot]
Note: Tom Taylor is the PROTO Shepherd
Token: Cullen Jennings
RAIExample calls flows of race conditions in the Session Initiation Protocol (SIP) (BCP) - 2 of 6
draft-ietf-sipping-race-examples-06.txt
Token: Jon Peterson
RTGForCES Forwarding Element Model (Proposed Standard) - 3 of 6
draft-ietf-forces-model-15.txt [Open Web Ballot]
Token: Ross Callon
OPSCAPWAP Protocol Specification (Proposed Standard) - 4 of 6
draft-ietf-capwap-protocol-specification-13.txt [Open Web Ballot]
Token: Dan Romascanu
OPSCAPWAP Protocol Binding for IEEE 802.11 (Proposed Standard) - 5 of 6
draft-ietf-capwap-protocol-binding-ieee80211-10.txt [Open Web Ballot]
Token: Dan Romascanu
RAIRTP Payload Format for ITU-T Recommendation G.711.1 (Proposed Standard) - 6 of 6
draft-ietf-avt-rtp-g711wb-03.txt [Open Web Ballot]
Note: Roni Even is the document shepherd.
Token: Cullen Jennings
2.1.2 Returning Item
      NONE

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
      NONE
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
GENJWT Report on MPLS Architectural Considerations for a Transport Profile (Informational) - 1 of 1
draft-bryant-mpls-tp-jwt-report-00.txt [Open Web Ballot]
Token: David Ward
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
SECSyntax for binding documents with time stamps (Informational) - 1 of 2
draft-santoni-timestampeddata-04.txt [Open Web Ballot]
Token: Tim Polk
GENMANET Autoconfiguration using Virtual Enterprise Traversal (VET) (Informational) - 2 of 2
draft-templin-autoconf-dhcp-16.txt [Open Web Ballot]
Token: Ross Callon
3.3.3 For Action
      AreaDate
GENPPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1
draft-bberry-rfc4938bis-00.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
                    NONE

5. IAB News We Can Use

6. Management Issues

6.1 Referencing Non-Standardized Technology in IETF Documents (Dave Ward)
6.2 Expert Review for tel reg (Cullen Jennings)

7. Working Group News

--===============0770791737== 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 --===============0770791737==-- From iesg-agenda-dist-bounces@ietf.org Thu Oct 2 15:17:00 2008 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 E08A428C154; Thu, 2 Oct 2008 15:17:00 -0700 (PDT) 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 98E303A69B2; Thu, 2 Oct 2008 15:16:59 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081002221659.98E303A69B2@core3.amsl.com> Date: Thu, 2 Oct 2008 15:16:59 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for October 9, 2008 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 October 9, 2008 IESG Teleconference This agenda was generated at 15:16:59 EDT, October 2, 2008 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-avt-rtp-toffset-07.txt Transmission Time offsets in RTP streams (Proposed Standard) - 1 of 6 Note: Tom Taylor is the PROTO Shepherd Token: Cullen Jennings o draft-ietf-sipping-race-examples-06.txt Example calls flows of race conditions in the Session Initiation Protocol (SIP) (BCP) - 2 of 6 Token: Jon Peterson o draft-ietf-forces-model-15.txt ForCES Forwarding Element Model (Proposed Standard) - 3 of 6 Token: Ross Callon o draft-ietf-capwap-protocol-specification-13.txt CAPWAP Protocol Specification (Proposed Standard) - 4 of 6 Token: Dan Romascanu o draft-ietf-capwap-protocol-binding-ieee80211-10.txt CAPWAP Protocol Binding for IEEE 802.11 (Proposed Standard) - 5 of 6 Token: Dan Romascanu o draft-ietf-avt-rtp-g711wb-03.txt RTP Payload Format for ITU-T Recommendation G.711.1 (Proposed Standard) - 6 of 6 Note: Roni Even is the document shepherd. Token: Cullen Jennings 2.1.2 Returning Item NONE 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 NONE 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-bryant-mpls-tp-jwt-report-00.txt JWT Report on MPLS Architectural Considerations for a Transport Profile (Informational) - 1 of 1 Token: David Ward 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-santoni-timestampeddata-04.txt Syntax for binding documents with time stamps (Informational) - 1 of 2 Token: Tim Polk o draft-templin-autoconf-dhcp-16.txt MANET Autoconfiguration using Virtual Enterprise Traversal (VET) (Informational) - 2 of 2 Token: Ross Callon 3.3.3 For Action o draft-bberry-rfc4938bis-00.txt PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1 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 NONE 5. IAB News We can use 6. Management Issue 6.1 Referencing Non-Standardized Technology in IETF Documents (Dave Ward) 6.2 Expert Review for tel reg (Cullen Jennings) 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 Oct 3 08:08:35 2008 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 391B128C28A; Fri, 3 Oct 2008 08:08:35 -0700 (PDT) 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 3D80528C247; Fri, 3 Oct 2008 08:08:33 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081003150833.3D80528C247@core3.amsl.com> Date: Fri, 3 Oct 2008 08:08:33 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for October 9, 2008 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="===============0764888878==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0764888878== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2008-10-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
RAITransmission Time offsets in RTP streams (Proposed Standard) - 1 of 6
draft-ietf-avt-rtp-toffset-07.txt [Open Web Ballot]
Note: Tom Taylor is the PROTO Shepherd
Token: Cullen Jennings
RAIExample calls flows of race conditions in the Session Initiation Protocol (SIP) (BCP) - 2 of 6
draft-ietf-sipping-race-examples-06.txt
Token: Jon Peterson
RTGForCES Forwarding Element Model (Proposed Standard) - 3 of 6
draft-ietf-forces-model-15.txt [Open Web Ballot]
Token: Ross Callon
OPSCAPWAP Protocol Specification (Proposed Standard) - 4 of 6
draft-ietf-capwap-protocol-specification-13.txt [Open Web Ballot]
Token: Dan Romascanu
OPSCAPWAP Protocol Binding for IEEE 802.11 (Proposed Standard) - 5 of 6
draft-ietf-capwap-protocol-binding-ieee80211-10.txt [Open Web Ballot]
Token: Dan Romascanu
RAIRTP Payload Format for ITU-T Recommendation G.711.1 (Proposed Standard) - 6 of 6
draft-ietf-avt-rtp-g711wb-03.txt [Open Web Ballot]
Note: Roni Even is the document shepherd.
Token: Cullen Jennings
2.1.2 Returning Item
      NONE

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
      NONE
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
GENJWT Report on MPLS Architectural Considerations for a Transport Profile (Informational) - 1 of 1
draft-bryant-mpls-tp-jwt-report-00.txt [Open Web Ballot]
Token: David Ward
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
SECSyntax for binding documents with time stamps (Informational) - 1 of 1
draft-santoni-timestampeddata-04.txt [Open Web Ballot]
Token: Tim Polk
3.3.2 Returning Item
      AreaDate
GENGuidelines for Using the Privacy Mechanism for SIP (Informational) - 1 of 2
draft-munakata-sip-privacy-guideline-04.txt [Open Web Ballot]
Note: Proposing that this use RFC3932 Note 2:       This RFC is not a candidate for any level of Internet Standard.
      The IETF disclaims any knowledge of the fitness of this RFC for
      any purpose and in particular notes that the decision to publish
      is not based on IETF review for such things as security,
      congestion control, or inappropriate interaction with deployed
      protocols.  The RFC Editor has chosen to publish this document at
      its discretion.  Readers of this document should exercise caution
      in evaluating its value for implementation and deployment.  See
      RFC 3932 for more information.
Token: Jon Peterson
GENMANET Autoconfiguration using Virtual Enterprise Traversal (VET) (Informational) - 2 of 2
draft-templin-autoconf-dhcp-16.txt [Open Web Ballot]
Token: Ross Callon
3.3.3 For Action
      AreaDate
GENPPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1
draft-bberry-rfc4938bis-00.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
                    NONE

5. IAB News We Can Use

6. Management Issues

6.1 Referencing Non-Standardized Technology in IETF Documents (Dave Ward)
6.2 Expert Review for tel reg (Cullen Jennings)

7. Working Group News

--===============0764888878== 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 --===============0764888878==-- From iesg-agenda-dist-bounces@ietf.org Fri Oct 3 08:08:35 2008 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 51F0E28C290; Fri, 3 Oct 2008 08:08:35 -0700 (PDT) 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 432D028C28A; Fri, 3 Oct 2008 08:08:33 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081003150833.432D028C28A@core3.amsl.com> Date: Fri, 3 Oct 2008 08:08:33 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for October 9, 2008 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="===============2129404753==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============2129404753== Content-Type: text/plain; charset="utf-8" INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the October 9, 2008 IESG Teleconference This agenda was generated at 8:8:33 EDT, October 3, 2008 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-avt-rtp-toffset-07.txt Transmission Time offsets in RTP streams (Proposed Standard) - 1 of 6 Note: Tom Taylor is the PROTO Shepherd Token: Cullen Jennings o draft-ietf-sipping-race-examples-06.txt Example calls flows of race conditions in the Session Initiation Protocol (SIP) (BCP) - 2 of 6 Token: Jon Peterson o draft-ietf-forces-model-15.txt ForCES Forwarding Element Model (Proposed Standard) - 3 of 6 Token: Ross Callon o draft-ietf-capwap-protocol-specification-13.txt CAPWAP Protocol Specification (Proposed Standard) - 4 of 6 Token: Dan Romascanu o draft-ietf-capwap-protocol-binding-ieee80211-10.txt CAPWAP Protocol Binding for IEEE 802.11 (Proposed Standard) - 5 of 6 Token: Dan Romascanu o draft-ietf-avt-rtp-g711wb-03.txt RTP Payload Format for ITU-T Recommendation G.711.1 (Proposed Standard) - 6 of 6 Note: Roni Even is the document shepherd. Token: Cullen Jennings 2.1.2 Returning Item NONE 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 NONE 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-bryant-mpls-tp-jwt-report-00.txt JWT Report on MPLS Architectural Considerations for a Transport Profile (Informational) - 1 of 1 Token: David Ward 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-santoni-timestampeddata-04.txt Syntax for binding documents with time stamps (Informational) - 1 of 1 Token: Tim Polk 3.3.2 Returning Item o draft-munakata-sip-privacy-guideline-04.txt Guidelines for Using the Privacy Mechanism for SIP (Informational) - 1 of 2 Note: Proposing that this use RFC3932 Note 2:       This RFC is not a candidate for any level of Internet Standard..       The IETF disclaims any knowledge of the fitness of this RFC for.       any purpose and in particular notes that the decision to publish.       is not based on IETF review for such things as security,.       congestion control, or inappropriate interaction with deployed.       protocols.  The RFC Editor has chosen to publish this document at.       its discretion.  Readers of this document should exercise caution.       in evaluating its value for implementation and deployment.  See.       RFC 3932 for more information.. Token: Jon Peterson o draft-templin-autoconf-dhcp-16.txt MANET Autoconfiguration using Virtual Enterprise Traversal (VET) (Informational) - 2 of 2 Token: Ross Callon 3.3.3 For Action o draft-bberry-rfc4938bis-00.txt PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1 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 NONE 5. IAB News We can use 6. Management Issue 6.1 Referencing Non-Standardized Technology in IETF Documents (Dave Ward) 6.2 Expert Review for tel reg (Cullen Jennings) 7. Agenda Working Group News --===============2129404753== 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 --===============2129404753==-- From iesg-agenda-dist-bounces@ietf.org Thu Oct 16 16:11:41 2008 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 C2E7F3A67B3; Thu, 16 Oct 2008 16:11:41 -0700 (PDT) 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 4C9E93A67B3; Thu, 16 Oct 2008 16:11:39 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081016231140.4C9E93A67B3@core3.amsl.com> Date: Thu, 16 Oct 2008 16:11:40 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for October 23, 2008 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="===============1571598478==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============1571598478== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2008-10-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
RAIA Session Initiation Protocol (SIP) Event Package for Session-Specific Session Policies. (Proposed Standard) - 1 of 4
draft-ietf-sipping-policy-package-05.txt [Open Web Ballot]
Token: Jon Peterson
RTGEncoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE (Proposed Standard) - 2 of 4
draft-ietf-ccamp-rfc4420bis-03.txt [Open Web Ballot]
Token: Ross Callon
OPSDiameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (Proposed Standard) - 3 of 4
draft-ietf-dime-mip6-integrated-10.txt [Open Web Ballot]
Token: Dan Romascanu
RTGTextual Representation of AS Numbers (Proposed Standard) - 4 of 4
draft-ietf-idr-as-representation-01.txt [Open Web Ballot]
Token: David Ward
2.1.2 Returning Item
      NONE

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
RTGGMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) (Experimental) - 1 of 1
draft-ietf-ccamp-asymm-bw-bidir-lsps-01.txt [Open Web Ballot]
Token: Ross Callon
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
GENImproved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA') (Informational) - 1 of 1
draft-arkko-eap-aka-kdf-06.txt [Open Web Ballot]
Token: Russ Housley
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
GENVirtual Enterprise Traversal (VET) (Informational) - 1 of 1
draft-templin-autoconf-dhcp-17.txt [Open Web Ballot]
Token: Ross Callon
3.3.3 For Action
      AreaDate
GENCongestion Control in the RFC Series (Informational) - 1 of 1
draft-irtf-iccrg-cc-rfcs-06.txt
Note: This document is an IRTF document. The IRSG is asking the IESG to perform a RFC3932bis review of draft-irtf-iccrg-cc-rfcs-06 [1] to be published an an Informational IRTF RFC. The document has been approved for publication by the IRSG.
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
         
AreaDate
RAISep 18Application-Layer Traffic Optimization (alto) - 1 of 1
Token:Lisa
         

4.2 WG Rechartering

          4.2.1 Under evaluation for IETF Review
         
AreaDate
TSVOct 15Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2
Token:Magnus
INTOct 16Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) - 2 of 2
Token:Jari
          4.2.2 Proposed for Approval
         
AreaDate
SECOct 3Simple Authentication and Security Layer (sasl) - 1 of 1
Token:Pasi

5. IAB News We Can Use

6. Management Issues

7. Working Group News

--===============1571598478== 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 --===============1571598478==-- From iesg-agenda-dist-bounces@ietf.org Thu Oct 16 16:11:41 2008 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 DFFC93A68B6; Thu, 16 Oct 2008 16:11:41 -0700 (PDT) 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 509603A6806; Thu, 16 Oct 2008 16:11:39 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081016231140.509603A6806@core3.amsl.com> Date: Thu, 16 Oct 2008 16:11:40 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for October 23, 2008 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 October 23, 2008 IESG Teleconference This agenda was generated at 16:11:39 EDT, October 16, 2008 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-sipping-policy-package-05.txt A Session Initiation Protocol (SIP) Event Package for Session-Specific Session Policies. (Proposed Standard) - 1 of 4 Token: Jon Peterson o draft-ietf-ccamp-rfc4420bis-03.txt Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE (Proposed Standard) - 2 of 4 Token: Ross Callon o draft-ietf-dime-mip6-integrated-10.txt Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction (Proposed Standard) - 3 of 4 Token: Dan Romascanu o draft-ietf-idr-as-representation-01.txt Textual Representation of AS Numbers (Proposed Standard) - 4 of 4 Token: David Ward 2.1.2 Returning Item NONE 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-ccamp-asymm-bw-bidir-lsps-01.txt GMPLS Asymmetric Bandwidth Bidirectional Label Switched Paths (LSPs) (Experimental) - 1 of 1 Token: Ross Callon 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-arkko-eap-aka-kdf-06.txt Improved Extensible Authentication Protocol Method for 3rd Generation Authentication and Key Agreement (EAP-AKA') (Informational) - 1 of 1 Token: Russ Housley 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-templin-autoconf-dhcp-17.txt Virtual Enterprise Traversal (VET) (Informational) - 1 of 1 Token: Ross Callon 3.3.3 For Action o draft-irtf-iccrg-cc-rfcs-06.txt Congestion Control in the RFC Series (Informational) - 1 of 1 Note: This document is an IRTF document. The IRSG is asking the IESG to perform a RFC3932bis review of draft-irtf-iccrg-cc-rfcs-06 [1] to be published an an Informational IRTF RFC. The document has been approved for publication by the IRSG. 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 o Application-Layer Traffic Optimization (alto) - 1 of 1 Token: Lisa 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2 Token: Magnus o Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) - 2 of 2 Token: Jari 4.2.2 Proposed for Approval o Simple Authentication and Security Layer (sasl) - 1 of 1 Token: Pasi 5. IAB News We can use 6. Management Issue 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 Oct 30 15:31:14 2008 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 8DF5F28C1A1; Thu, 30 Oct 2008 15:31:14 -0700 (PDT) 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 881BA28C1A0; Thu, 30 Oct 2008 15:31:13 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081030223113.881BA28C1A0@core3.amsl.com> Date: Thu, 30 Oct 2008 15:31:13 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for November 6, 2008 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="===============0833055581==" Sender: iesg-agenda-dist-bounces@ietf.org Errors-To: iesg-agenda-dist-bounces@ietf.org --===============0833055581== Content-Type: text/html; charset="utf-8" IESG Agenda

IESG Agenda

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

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
SECEAP Generalized Pre-Shared Key (EAP-GPSK) Method (Proposed Standard) - 1 of 7
draft-ietf-emu-eap-gpsk-16.txt [Open Web Ballot]
Note: document shepherd: Joe Salowey <jsalowey@cisco.com>
Token: Pasi Eronen
RAIThe use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) (Proposed Standard) - 2 of 7
draft-ietf-sip-sips-08.txt [Open Web Ballot]
Note: The proto Shepherd for this document is Dean Willis.
Token: Cullen Jennings
OPSInformation Model for Packet Sampling Exports (Proposed Standard) - 3 of 7
draft-ietf-psamp-info-11.txt [Open Web Ballot]
Note: Juergen Quittek is the PROTO shepherd
Token: Dan Romascanu
RAIDatagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP) (Proposed Standard) - 4 of 7
draft-ietf-avt-dtls-srtp-06.txt [Open Web Ballot]
Note: The document shepherd is Roni Even.
Token: Cullen Jennings
TSVNetwork Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol (BCP) - 5 of 7
draft-ietf-behave-dccp-04.txt [Open Web Ballot]
Token: Magnus Westerlund
RAIFramework for Establishing an SRTP Security Context using DTLS (Proposed Standard) - 6 of 7
draft-ietf-sip-dtls-srtp-framework-05.txt [Open Web Ballot]
Note: Last Call ends Oct 31. Dean Willis will act as the proto shepherd.
Token: Cullen Jennings
RTGVirtual Router Redundancy Protocol Version 3 for IPv4 and IPv6 (Proposed Standard) - 7 of 7
draft-ietf-vrrp-unified-spec-02.txt [Open Web Ballot]
Token: David Ward
2.1.2 Returning Item
      NONE

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
TSVTest vectors for STUN (Informational) - 1 of 2
draft-ietf-behave-stun-test-vectors-03.txt [Open Web Ballot]
Token: Magnus Westerlund
RTGAS Number Reservation for Documentation Use (Informational) - 2 of 2
draft-ietf-idr-as-documentation-reservation-00.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
      AreaDate
GENConsiderations for Having a Successful BOF (Informational) - 1 of 2
draft-narten-successful-bof-03.txt [Open Web Ballot]
Token: Russ Housley
GENSuite B Profile for Transport Layer Security (TLS) (Informational) - 2 of 2
draft-rescorla-tls-suiteb-09.txt [Open Web Ballot]
Token: Tim Polk
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
         
AreaDate
TSVOct 21Techniques for Advanced Networking Applications (tana) - 1 of 1
Token:Lars
          4.1.2 Proposed for Approval
         
AreaDate
APPSep 18Application-Layer Traffic Optimization (alto) - 1 of 1
Token:Lisa
         

4.2 WG Rechartering

          4.2.1 Under evaluation for IETF Review
                    NONE
          4.2.2 Proposed for Approval
         
AreaDate
TSVOct 15Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2
Token:Magnus
INTOct 16Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) - 2 of 2
Token:Jari

5. IAB News We Can Use

6. Management Issues

6.1 Message to IANA regarding address range reservation for IETF protocols (Russ Housley)
6.2 Large Interim Meeting Agenda (Russ Housley)

7. Working Group News

--===============0833055581== 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 --===============0833055581==-- From iesg-agenda-dist-bounces@ietf.org Thu Oct 30 15:31:14 2008 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 AA19D28C1AD; Thu, 30 Oct 2008 15:31:14 -0700 (PDT) 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 90FC428C1A1; Thu, 30 Oct 2008 15:31:13 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Mime-Version: 1.0 Message-Id: <20081030223113.90FC428C1A1@core3.amsl.com> Date: Thu, 30 Oct 2008 15:31:13 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for November 6, 2008 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 November 6, 2008 IESG Teleconference This agenda was generated at 15:31:13 EDT, October 30, 2008 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-emu-eap-gpsk-16.txt EAP Generalized Pre-Shared Key (EAP-GPSK) Method (Proposed Standard) - 1 of 7 Note: document shepherd: Joe Salowey <jsalowey@cisco.com> Token: Pasi Eronen o draft-ietf-sip-sips-08.txt The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) (Proposed Standard) - 2 of 7 Note: The proto Shepherd for this document is Dean Willis. Token: Cullen Jennings o draft-ietf-psamp-info-11.txt Information Model for Packet Sampling Exports (Proposed Standard) - 3 of 7 Note: Juergen Quittek is the PROTO shepherd Token: Dan Romascanu o draft-ietf-avt-dtls-srtp-06.txt Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP) (Proposed Standard) - 4 of 7 Note: The document shepherd is Roni Even. Token: Cullen Jennings o draft-ietf-behave-dccp-04.txt Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol (BCP) - 5 of 7 Token: Magnus Westerlund o draft-ietf-sip-dtls-srtp-framework-05.txt Framework for Establishing an SRTP Security Context using DTLS (Proposed Standard) - 6 of 7 Note: Last Call ends Oct 31. Dean Willis will act as the proto shepherd. Token: Cullen Jennings o draft-ietf-vrrp-unified-spec-02.txt Virtual Router Redundancy Protocol Version 3 for IPv4 and IPv6 (Proposed Standard) - 7 of 7 Token: David Ward 2.1.2 Returning Item NONE 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-behave-stun-test-vectors-03.txt Test vectors for STUN (Informational) - 1 of 2 Token: Magnus Westerlund o draft-ietf-idr-as-documentation-reservation-00.txt AS Number Reservation for Documentation Use (Informational) - 2 of 2 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 o draft-narten-successful-bof-03.txt Considerations for Having a Successful BOF (Informational) - 1 of 2 Token: Russ Housley o draft-rescorla-tls-suiteb-09.txt Suite B Profile for Transport Layer Security (TLS) (Informational) - 2 of 2 Token: Tim Polk 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 Application-Layer Traffic Optimization (alto) - 1 of 2 Token: Lisa o Low Extra Delay Background Transport (ledbat) - 2 of 2 Token: Lars 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2 Token: Magnus o Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) - 2 of 2 Token: Jari 5. IAB News We can use 6. Management Issue 6.1 Message to IANA regarding address range reservation for IETF protocols (Russ Housley) 6.2 Large Interim Meeting Agenda (Russ Housley) 7. Agenda Working Group News _______________________________________________ IESG-AGENDA-DIST mailing list IESG-AGENDA-DIST@ietf.org https://www.ietf.org/mailman/listinfo/iesg-agenda-dist