From rtg-dir-bounces@ietf.org Mon Nov 12 07:02:37 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrXzw-0001U1-Jv; Mon, 12 Nov 2007 07:02:36 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IrXzv-0001SZ-21 for rtg-dir@ietf.org; Mon, 12 Nov 2007 07:02:35 -0500 Received: from [206.197.161.144] (helo=runaway.fenron.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IrXzr-0007xC-TI for rtg-dir@ietf.org; Mon, 12 Nov 2007 07:02:35 -0500 Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id lACC1G6W099308 for ; Mon, 12 Nov 2007 04:01:16 -0800 (PST) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id lACC1G9R099307 for rtg-dir@ietf.org; Mon, 12 Nov 2007 04:01:16 -0800 (PST) (envelope-from fenner) Date: Mon, 12 Nov 2007 04:01:16 -0800 (PST) Message-Id: <200711121201.lACC1G9R099307@runaway.fenron.com> From: fenner@research.att.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) X-Spam-Score: 0.3 (/) X-Scan-Signature: 681e62a2ce9b0804b459fe780d892beb Subject: IESG agenda for 2007-11-15 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2007-11-15). ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item Area Date RAI A Framework for Centralized Conferencing (Proposed Standard) - 1 of 6 draft-ietf-xcon-framework-10.txt [Open Web Ballot] Note: Adam Roach is proto shepherd Token: Cullen Jennings Session Initiation Protocol (SIP) User Agent RAI Capability Extension to Presence Information Data Format (PIDF) (Proposed Standard) - 2 of 6 draft-ietf-simple-prescaps-ext-08.txt [Open Web Ballot] Token: Jon Peterson TSV NAT Behavioral Requirements for ICMP protocol (BCP) - 3 of 6 draft-ietf-behave-nat-icmp-06.txt [Open Web Ballot] Token: Magnus Westerlund TSV Explicit Congestion Marking in MPLS (Proposed Standard) - 4 of 6 draft-ietf-tsvwg-ecn-mpls-02.txt [Open Web Ballot] Note: Lars Eggert (lars.eggert@nokia.com) is document shepherd. Token: Lars Eggert RAI TEI Query Request Number Change (Proposed Standard) - 5 of 6 draft-ietf-sigtran-rfc4233update-02.txt [Open Web Ballot] Token: Jon Peterson INT Distributing a Symmetric FMIPv6 Handover Key using SEND (Proposed Standard) - 6 of 6 draft-ietf-mipshop-handover-key-03.txt [Open Web Ballot] Note: Document Shepherd is Vijay Devarapalli Token: Jari Arkko 2.1.2 Returning Item Area Date INT Transmission of IPv6 via the IPv6 CS over IEEE 802.16 Networks (Proposed Standard) - 1 of 1 draft-ietf-16ng-ipv6-over-ipv6cs-10.txt [Open Web Ballot] Note: Bringing back to the agenda now that a new version exists. Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item Area Date The Presence-Specific Static Dictionary for GEN Signaling Compression (Sigcomp) (Proposed Standard) - 1 of 1 draft-garcia-simple-presence-dictionary-06.txt [Open Web Ballot] Token: Jon Peterson 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 Area Date TSV NFS RDMA Problem Statement (Informational) - 1 of 5 draft-ietf-nfsv4-nfs-rdma-problem-statement-07.txt [Open Web Ballot] Note: Document Shepherd: Spencer Shepler (spencer.shepler@sun.com) Token: Lars Eggert Session Initiation Protocol (SIP) Torture Test RAI Messages for Internet Protocol Version 6 (IPv6) (Informational) - 2 of 5 draft-ietf-sipping-ipv6-torture-tests-04.txt [Open Web Ballot] Token: Jon Peterson INT Network Discovery and Selection Problem (Informational) - 3 of 5 draft-ietf-eap-netsel-problem-08.txt [Open Web Ballot] Token: Mark Townsley State of Peer-to-Peer(P2P) Communication Across TSV Network Address Translators(NATs) (Informational) - 4 of 5 draft-ietf-behave-p2p-state-05.txt [Open Web Ballot] Token: Magnus Westerlund SEC CMS Advanced Electronic Signatures (CAdES) (Informational) - 5 of 5 draft-ietf-smime-cades-06.txt [Open Web Ballot] Token: Tim Polk 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 Area Date SEC Additional Diffie-Hellman Groups for use with IETF Standards (Informational) - 1 of 1 draft-lepinski-dh-groups-03.txt [Open Web Ballot] Token: Tim Polk 3.2.2 Returning Item Area Date A Uniform Resource Name Namespace For The APP Dec 1 EPCglobal Electronic Product Code (EPC) and Related Standards (Informational) - 1 of 1 draft-mealling-epc-urn-02.txt [Open Web Ballot] Token: Lisa Dusseault 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 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 Area Date TSV Metrics for the Evaluation of Congestion Control Mechanisms (Informational) - 1 of 1 draft-irtf-tmrg-metrics-11.txt [Open Web Ballot] Note: To be published according to draft-irtf-rfcs-01.txt Based on the Working Group Summary, I believe that the second variant suggested in Appendix A of draft-irtf-rfcs-0 is appropriate for this document: "This document in not an IETF Internet Standard. It represents the individual opinion(s) of one or more members of the TMRG Research Group of the Internet Research Task Force. It may be considered for standardization by the IETF or adoption as a IRTF Research Group consensus document in the future." Token: Lars Eggert 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval Area Date OPS Oct 17 IP Flow Information Export (ipfix) - 1 of 2 Token: Dan OPS Oct 16 Network Configuration (netconf) - 2 of 2 Token: Dan 5. IAB News We Can Use 6. Management Issues 6.1 Expert for RFC 3340 APEX Parameters [IANA #121073] (Michelle Cotton) 6.2 New IANA expert for AVP Codes (RFC 3588) (Dan Romascanu) 6.3 CARP protocol number allocation situation (Jari Arkko) 6.4 Review of Atom Link Relation request [IANA #123284] (Michelle Cotton) 6.5 Approval of IESG Policy on Autoresponse Messages Sent to IETF Mailing Lists (Chris Newman) 7. Working Group News From rtg-dir-bounces@ietf.org Mon Nov 26 07:00:15 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwcdL-0000As-Lq; Mon, 26 Nov 2007 07:00:15 -0500 Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwcdK-0000Ak-Se for rtg-dir@ietf.org; Mon, 26 Nov 2007 07:00:15 -0500 Received: from [206.197.161.144] (helo=rtg.ietf.org) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IwcdJ-0006ld-Rt for rtg-dir@ietf.org; Mon, 26 Nov 2007 07:00:14 -0500 Received: from runaway.fenron.com (localhost [127.0.0.1]) by rtg.ietf.org (8.13.8/8.13.8) with ESMTP id lAQC05Q7063925 for ; Mon, 26 Nov 2007 04:00:05 -0800 (PST) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id lAQC05LK063924 for rtg-dir@ietf.org; Mon, 26 Nov 2007 04:00:05 -0800 (PST) (envelope-from fenner) Date: Mon, 26 Nov 2007 04:00:05 -0800 (PST) Message-Id: <200711261200.lAQC05LK063924@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on runaway.fenron.com X-Spam-Score: 0.1 (/) X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e Subject: IESG agenda for 2007-11-29 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2007-11-29). ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item Area Date TSV Session Traversal Utilities for (NAT) (STUN) (Proposed Standard) - 1 of 9 draft-ietf-behave-rfc3489bis-13.txt [Open Web Ballot] Token: Magnus Westerlund RAI Revised Civic Location Format for PIDF-LO (Proposed Standard) - 2 of 9 draft-ietf-geopriv-revised-civic-lo-06.txt [Open Web Ballot] Note: Robert is proto shepherd Token: Cullen Jennings Low Density Parity Check (LDPC) Staircase and TSV Triangle Forward Error Correction (FEC) Schemes (Proposed Standard) - 3 of 9 draft-ietf-rmt-bb-fec-ldpc-07.txt [Open Web Ballot] Token: Magnus Westerlund TSV Reed-Solomon Forward Error Correction (FEC) Schemes (Proposed Standard) - 4 of 9 draft-ietf-rmt-bb-fec-rs-05.txt [Open Web Ballot] Token: Magnus Westerlund Using the Boneh-Franklin and Boneh-Boyen SEC Oct 15 identity-based encryption algorithms with the Cryptographic Message Syntax (CMS) (Proposed Standard) - 5 of 9 draft-ietf-smime-bfibecms-08.txt [Open Web Ballot] Token: Tim Polk SEC Oct 15 Identity-based Encryption Architecture (Proposed Standard) - 6 of 9 draft-ietf-smime-ibearch-06.txt [Open Web Ballot] Token: Tim Polk RAI A More Loss-Tolerant RTP Payload Format for MP3 Audio (Proposed Standard) - 7 of 9 draft-ietf-avt-rfc3119bis-05.txt [Open Web Ballot] Note: Colin Perkins is the document shepherd. Token: Cullen Jennings Definition of Events For Channel-Oriented RAI Telephony Signalling (Proposed Standard) - 8 of 9 draft-ietf-avt-rfc2833biscas-05.txt [Open Web Ballot] Note: Proto shepherd is Roni Even Token: Cullen Jennings INT Mobile IPv4 Traversal Across IPsec-based VPN Gateways (BCP) - 9 of 9 draft-ietf-mip4-vpn-problem-solution-03.txt [Open Web Ballot] Note: Document Shepherd is Henrik Levkowetz Token: Jari Arkko 2.1.2 Returning Item Area Date INT Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE (BCP) - 1 of 1 draft-ietf-mip4-mobike-connectivity-03.txt [Open Web Ballot] Note: Document Shepherd is Token: Jari Arkko 2.2 Individual Submissions 2.2.1 New Item Area Date APP ASCII Escaping of Unicode Characters (BCP) - 1 of 1 draft-klensin-unicode-escapes-07.txt [Open Web Ballot] Token: Chris Newman 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 Area Date RTG Jitter considerations in Mobile Ad Hoc Networks (MANETs) (Informational) - 1 of 1 draft-ietf-manet-jitter-03.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 Area Date INT Service Selection for Mobile IPv6 (Informational) - 1 of 2 draft-korhonen-mip6-service-05.txt [Open Web Ballot] Note: No document shepherd Token: Jari Arkko INT Unified L2 Abstractions for L3-Driven Fast Handover (Experimental) - 2 of 2 draft-irtf-mobopts-l2-abstractions-04.txt [Open Web Ballot] Note: This is an IRTF submission Token: Jari Arkko 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item Area Date Reorder Density and Reorder Buffer-occupancy GEN Density - Metrics for Packet Reordering Measurements (Informational) - 1 of 1 draft-jayasumana-reorder-density-08.txt [Open Web Ballot] Note: Suggest to respond to the RFC Editor with RFC 3932, Section 3, Option 2: "The IESG thinks that this work is related to IETF work done in the IPPM WG, but this does not prevent publishing." Token: Lars Eggert 3.3.2 Returning Item Area Date TSV Metrics for the Evaluation of Congestion Control Mechanisms (Informational) - 1 of 1 draft-irtf-tmrg-metrics-11.txt [Open Web Ballot] Note: To be published according to draft-irtf-rfcs-01.txt Based on the Working Group Summary, I believe that the second variant suggested in Appendix A of draft-irtf-rfcs-0 is appropriate for this document: "This document in not an IETF Internet Standard. It represents the individual opinion(s) of one or more members of the TMRG Research Group of the Internet Research Task Force. It may be considered for standardization by the IETF or adoption as a IRTF Research Group consensus document in the future." Token: Lars Eggert 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 Approval of IESG Policy on Autoresponse Messages Sent to IETF Mailing Lists (Chris Newman) 7. Working Group News From rtg-dir-bounces@ietf.org Thu Nov 29 16:03:21 2007 Return-path: Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxqXZ-0005nb-Ko; Thu, 29 Nov 2007 16:03:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IxqXZ-0005nR-08 for rtg-dir@ietf.org; Thu, 29 Nov 2007 16:03:21 -0500 Received: from asmtp1.iomartmail.com ([62.128.201.248]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IxqXY-0000wh-IU for rtg-dir@ietf.org; Thu, 29 Nov 2007 16:03:20 -0500 Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id lATL3J4Z007099 for ; Thu, 29 Nov 2007 21:03:19 GMT Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id lATL3HIY007079 for ; Thu, 29 Nov 2007 21:03:19 GMT Message-ID: <0c4b01c832cb$427876c0$0200a8c0@your029b8cecfe> From: "Adrian Farrel" To: "Routing Area Directorate" Date: Thu, 29 Nov 2007 21:01:51 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: Discussion of distribution of TE information from outside the AS X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org Hi, Various recent drafts have been floated at CCAMP that propose different mechanisms for distributing TE information from outside the AS within the AS. We plan a chunk of our time at our Vancouver meeting (Tuesday, 9.00-11.30) to discuss this topic and look at the I-Ds. The objective is to clarify what is in scope and what is out of scope before moving further forward with anything. Please see our agenda at http://www3.ietf.org/proceedings/07dec/agenda/ccamp.htm to see a full list of the relevant I-Ds. And have a look at a set of overview slides I have written and placed at http://www3.ietf.org/proceedings/07dec/slides/ccamp-2.ppt You are all very welcome to attend CCAMP to throw peanuts (or speak at the mic). And, of course, contributions on the CCAMP mailing list before, during, or after, will be valued. Thanks, Adrian