From dromasca@avaya.com Mon Jan 3 09:38:15 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EE263A69BE; Mon, 3 Jan 2011 09:38:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.239 X-Spam-Level: X-Spam-Status: No, score=-102.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlS+riidTsld; Mon, 3 Jan 2011 09:38:12 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id E113E3A69BA; Mon, 3 Jan 2011 09:37:59 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAEqYIU2HCzI1/2dsb2JhbACkNHOlFwKWUYVKBI47 X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="257785447" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Jan 2011 12:40:05 -0500 X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="576242021" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Jan 2011 12:40:04 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 3 Jan 2011 18:39:55 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for the January 6, 2011 IESG Teleconference Thread-Index: Acuod8MjL0F3J88wRM6ifhfUcvMqaQC9SukQ From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for the January 6, 2011 IESG Teleconference X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2011 17:38:15 -0000 Please find below the preliminary agenda of the 1/6 telechat. Please send me your questions, comments and concerns before 1/5 COB.=20 Thanks and Regards, Dan 2. Protocol Actions 2.1 WG Submissions 2.1.1 New Items o draft-ietf-pkix-ocspagility-09 OCSP Algorithm Agility (Proposed Standard) Note: Stephen Kent is the document shepherd Token: Tim Polk o draft-ietf-httpstate-cookie-20 HTTP State Management Mechanism (Proposed Standard) Note: Jeff Hodges (chair of the HTTPSTATE WG) is the document shepherd. Token: Peter Saint-Andre Was deferred by Tim Polk on 2010-12-15 o draft-ietf-pim-group-rp-mapping-08 PIM Group-to-RP Mapping (Proposed Standard) Note: Mike McBride is the document shepherd (mmcbride@cisco.com). Token: Adrian Farrel o draft-ietf-roll-trickle-06 The Trickle Algorithm (Proposed Standard) Note: JP Vasseur (jpv@cisco.com) is the document shepherd. Token: Adrian Farrel Was deferred by Lars Eggert on 2010-12-16 o draft-ietf-pwe3-oam-msg-map-14 Pseudowire (PW) OAM Message Mapping (Proposed Standard) Note: Andrew Malis, andrew.g.malis@verizon.com is the document shepherd. Token: Stewart Bryant o draft-ietf-avt-rtcp-port-for-ssm-04 RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions (Proposed Standard) Note: The document shepherd for this document is Keith Drage (keith.drage@alcatel-lucent.com). Token: Robert Sparks o draft-ietf-avt-rtp-cnames-03 Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs) (Proposed Standard) Note: Keith Drage (keith.drage@alcatel-lucent.com) is the document shepherd. Token: Robert Sparks o draft-ietf-dnsext-5395bis-02 Domain Name System (DNS) IANA Considerations (BCP) Note: Olafur Gudmundsson (ogud@ogud.com) is the document shepherd. Token: Ralph Droms o draft-ietf-avt-srtp-big-aes-05 The use of AES-192 and AES-256 in Secure RTP (Proposed Standard) Note: Keith Drage (keith.drage@alcatel-lucent.com) is the document shepherd. Token: Robert Sparks 2.1.2 Returning Items o draft-ietf-mpls-ldp-upstream-09 MPLS Upstream Label Assignment for LDP (Proposed Standard) Note: Loa Andersson (loa@pi.nu) is the Document Shepherd. Token: Adrian Farrel 2.2 Individual Submissions 2.2.1 New Items o draft-cdmi-mediatypes-06 Cloud Data Management Interface (CDMI) Media Types (Proposed Standard) Token: Peter Saint-Andre o draft-melnikov-mailserver-uri-to-historic-00 Moving mailserver: URI scheme to historic (Proposed Standard) Token: Peter Saint-Andre o draft-kucherawy-authres-vbr-01 Authentication-Results Registration For Vouch By Reference Results (Proposed Standard) Note: Barry Leiba is the document shepherd. Token: Alexey Melnikov 2.2.2 Returning Items NONE 3. Document Actions 3.1 WG Submissions 3.1.1 New Items o draft-ietf-sieve-autoreply-03 Sieve Email Filtering: Use of Presence Information with Auto Responder functionality (Informational) Note: The Document Shepherd is Cyrus Daboo. Token: Peter Saint-Andre o draft-ietf-ecrit-lost-servicelistboundary-05 LoST Service List Boundary Extension (Experimental) Note: Richard Barnes (rbarnes@bbn.com) is the document shepherd. Token: Robert Sparks o draft-ietf-ipfix-anon-05 IP Flow Anonymisation Support (Experimental) Note: Nevil Brownlee is the Document Shepherd Token: Dan Romascanu Was deferred by Tim Polk on 2010-12-15 o draft-ietf-v6ops-tunnel-security-concerns-04 Security Concerns With IP Tunneling (Informational) Note: Joel Jaeggli (joelja@bogus.com) v6ops wg cochair is the document shepherd. Token: Ron Bonica o draft-ietf-roll-security-framework-03 A Security Framework for Routing over Low Power and Lossy Networks (Informational) Note: JP Vasseur (jpv@cisco.com) is the document shepherd. Token: Adrian Farrel o draft-ietf-v6ops-tunnel-loops-01 Routing Loop Attack using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations (Informational) Note: Joel Jaeggli (joelja@bogus.com) is the document shepherd. Token: Ron Bonica 3.1.2 Returning Items o draft-ietf-l2vpn-vpls-bridge-interop-06 VPLS Interoperability with CE Bridges (Informational) Note: Shane Amante is the document shepherd. Token: Stewart Bryant o draft-ietf-mpls-tp-oam-framework-10 Operations, Administration and Maintenance Framework for MPLS- based Transport Networks (Informational) Note: Loa Andersson (loa@pi.nu) is the Document Shepherd. Token: Adrian Farrel o draft-ietf-mpls-tp-uni-nni-02 MPLS Transport Profile User-to-Network and Network-to-Network Interfaces (Informational) Note: Loa Andersson (loa@pi.nu) is the Document Shepherd. Token: Adrian Farrel 3.2 Individual Submissions Via AD 3.2.1 New Items o draft-loreto-http-bidirectional-05 Known issues and best practices for the Use of Long Polling and Streaming in Bidirectional HTTP (Informational) Note: Martin Thomson is the document shepherd. Token: Alexey Melnikov o draft-turner-md5-seccon-update-08 Updated Security Considerations for the MD5 Message-Digest and the HMAC-MD5 Algorithms (Informational) Note: Sean Turner (turners@ieca.com) is the document shepherd. Token: Alexey Melnikov o draft-turner-md2-to-historic-10 MD2 to Historic Status (Informational) Note: Sean Turner (turners@ieca.com) is the document Shepherd. Token: Robert Sparks o draft-turner-md4-to-historic-10 MD4 to Historic Status (Informational) Note: Sean Turner (turners@ieca.com) is the document Shepherd. Token: Robert Sparks 3.2.2 Returning Items NONE 3.3 IRTF and Independent Submission Stream Documents 3.3.1 New Items NONE 3.3.2 Returning Items o draft-zorn-radius-keywrap-17 Cisco Vendor Specific RADIUS Attributes for the Delivery of Keying Material (Informational) Token: Dan Romascanu o draft-irtf-mobopts-mpa-framework-08 A Framework of Media-Independent Pre-Authentication (MPA) for Inter- domain Handover Optimization (Informational) Note: Rajeev Koodli (rkoodli@cisco.com) is the document shepherd. Token: Jari Arkko o draft-templin-iron-16 The Internet Routing Overlay Network (IRON) (Experimental) Note: Tony Li (tony.li@tony.li) is the document shepherd. Token: Jari Arkko 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Audio/Video Transport Payloads (payload) Token: Robert o Metric Blocks for use with RTCP's Extended Report Framework (xrblock) Token: Robert o Audio/Video Transport Core Maintenence (avtcore) Token: Robert o Audio/Video Transport Extensions (avtext) Token: Robert 4.1.2 Proposed for Approval o ControLling mUltiple streams for TElepresence (clue) Token: Gonzalo From dromasca@avaya.com Wed Jan 12 03:18:45 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 324F23A6A63; Wed, 12 Jan 2011 03:18:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.544 X-Spam-Level: X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZfALfZr-3Px; Wed, 12 Jan 2011 03:18:44 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 2E3723A6B0E; Wed, 12 Jan 2011 03:18:43 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAPIcLU2HCzI1/2dsb2JhbACkPnOlZAKWWoVMBI5K X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="227147833" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Jan 2011 06:21:00 -0500 X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="581297989" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 12 Jan 2011 06:20:59 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jan 2011 12:20:44 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Review: Audio/Video Transport Core Maintenence (avtcore) Thread-Index: Acuxv6ms2XE4wpE0RtuZJW5oP96tuAAirCZg From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , , "YANG Doctors" Subject: [AAA-DOCTORS] FW: WG Review: Audio/Video Transport Core Maintenence (avtcore) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 11:18:45 -0000 This is the first in a series of four messages announcing the review for four IETF Working Groups. Note that these WGs are not completely new, but rather the split of the current AVT (Audio/Video Transport) WG in the RAI Area.=20 Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Tuesday, January 11, 2011 8:43 PM To: new-work@ietf.org Subject: WG Review: Audio/Video Transport Core Maintenence (avtcore)=20 A new IETF working group has been proposed in the Real-Time Applications and Infrastructure Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. =20 Audio/Video Transport Core Maintenence (avtcore) ------------------------------------------- Current Status: Proposed Working Group Last modified: 2010-12-03 Chairs: TBD Real-Time Applications and Infrastructure Area Directors: Gonzalo Camarillo Robert Sparks Real-Time Applications and Infrastructure Area Advisor: Robert Sparks Mailing Lists: TBD Description of Working Group: The Real-time Transport Protocol, RTP, along with its associated profiles and payload formats provides for real-time transmission of audio and video over unicast and multicast transports. RTP itself has been shepherded to Full Standard. Its associated profiles, extensions, and payload formats are currently at various levels of standards maturity.=20 The AVTCORE working group is chartered to maintain the core RTP/RTCP protocols and the AVP, SAVP, AVPF, and SAVPF profiles. The group will provide architectural guidance for extending the protocols and guidelines for their proper use. While other working groups may be chartered to work on application-specific extensions to the protocols, extensions that are generally applicable will be developed in AVTCORE. The AVTCORE working group will coordinate closely with the Security Area while working on maintenance and enhancements to the SRTP Profile. In addition to the milestones called out below, the AVTCORE working group's initial tasks will include completing any remaining work identified in those drafts from the AVT working group already in IESG Evaluation, with the exception of the Rapid Acquisition of Multicast RTP sessions, which will complete in the AVTEXT working group. Goals and Milestones: Dec 2010 Submit Guideline for Choosing RTCP CNAME as Proposed Standard Dec 2010 Submit use of AES-192 and AES-256 in Secure RTP for Proposed=20 Standard Dec 2010 Submit Port Mapping Between Unicast and Multicast RTP Sessions for Proposed Standard Dec 2010 Submit Real-Time Transport Control Protocol (RTCP) in Overlay=20 Multicast for Proposed Standard Feb 2011 Submit Monitoring Architecture for RTP for Informational Feb 2011 Guidelines for the use of Variable Bit Rate Audio with Secure=20 RTP as informational (or possibly BCP) Apr 2011 Submit in band keying mechanism for SRTP draft for Proposed=20 Standard Apr 2011 Submit Explicit Congestion Notification (ECN) for RTP over UDP for Proposed Standard May 2011 RTCP indication for retransmission suppression as proposed=20 standard Sep 2011 Encryption of Header Extensions in the Secure Real-Time=20 Transport Protocol (SRTP) for Proposed Standard From dromasca@avaya.com Wed Jan 12 03:18:46 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61C403A6B23; Wed, 12 Jan 2011 03:18:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.544 X-Spam-Level: X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEzSWRMZVjgw; Wed, 12 Jan 2011 03:18:45 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 7ABEB3A6A5F; Wed, 12 Jan 2011 03:18:44 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAPIcLU2HCzI1/2dsb2JhbACkPnOlZAKWWoVMBI5K X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="227147835" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Jan 2011 06:21:01 -0500 X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="581297995" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 12 Jan 2011 06:21:00 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jan 2011 12:20:56 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Review: Audio/Video Transport Extensions (avtext) Thread-Index: AcuxwBfjEEYDB454S2WKDtnt5TSVfgAiq0JA From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , , "YANG Doctors" Subject: [AAA-DOCTORS] FW: WG Review: Audio/Video Transport Extensions (avtext) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 11:18:46 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Tuesday, January 11, 2011 8:46 PM To: new-work@ietf.org Subject: WG Review: Audio/Video Transport Extensions (avtext)=20 A new IETF working group has been proposed in the Real-Time Applications and Infrastructure Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. =20 Audio/Video Transport Extensions (avtext) ------------------------------------------- Current Status: Proposed Working Group Last modified: 2010-12-03 Chairs: TBD Real-Time Applications and Infrastructure Area Directors: Gonzalo Camarillo Robert Sparks Real-Time Applications and Infrastructure Area Advisor: Robert Sparks Mailing Lists: TBD Description of Working Group: The Full-Standard Real-time Transport Protocol, RTP [RFC 3550], along with its associated profiles and payload formats provides for real- time transmission of audio and video over unicast and multicast transports. RTP is widely implemented, and deployed for a wide range of applications, ranging from telephony to television over IP. As new applications have emerged, the need for guidelines for the use of the RTP/RTCP protocols and extensions specific to those applications has been identified. The AVTEXT working group is charted to develop application-specific guidelines for the use of RTP/RTCP protocols with the AVP, SAVP, AVPF, and SAVPF profiles, and extensions to those protocols that are driven by application-specific needs. Proposals for extensions with general applicability to many different RTP/RTCP usages should be taken to the AVTCORE working group.=20 The AVTEXT working group is constrained to use the protocol extension mechanisms defined in the core protocols (such as RTP Header extensions [RFC5285], AVPF Feedback Messages [RFC4585], and SDES Items [RFC3550]). If new ways to extend the core protocols are needed, they will be developed in the AVTCORE working group. In addition to the milestones called out below, the AVTEXT working group's initial tasks will include completing any new work identified during IESG evaluation for the Rapid Acquisition of Multicast RTP Sessions. Goals and Milestones: Dec 2010 Submit Considerations for RAMS Scenarios for Informational Oct 2011 Submit RTP Header extension for mixer to client audio level=20 indication as Proposed Standard Oct 2011 Submit RTP Header extension for client to mixer audio level=20 indication as proposed standard Dec 2011 Submit Support for multiple clock rates in an RTP session for=20 Proposed Standard Dec 2011 Submit SRTP Store-and-Forward Use Cases and Requirements for=20 Informational Dec 2011 Submit Use of the Secure Real-time Transport Protocol (SRTP)=20 in Store-and-Forward Applications for Proposed Standard From dromasca@avaya.com Wed Jan 12 03:19:16 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A6893A6B10; Wed, 12 Jan 2011 03:19:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.544 X-Spam-Level: X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyLlbU-iGLgW; Wed, 12 Jan 2011 03:19:15 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id B58BA3A6B0E; Wed, 12 Jan 2011 03:19:14 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAPIcLU3GmAcF/2dsb2JhbACkPnOlZAKWWoVMBI5K X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="227147908" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 12 Jan 2011 06:21:32 -0500 X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="569398335" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 12 Jan 2011 06:21:31 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jan 2011 12:21:08 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Review: Audio/Video Transport Payloads (payload) Thread-Index: AcuxvqEkRbDU/1H+SyGAlUpKw3fDjAAjCv6A From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , , "YANG Doctors" Subject: [AAA-DOCTORS] FW: WG Review: Audio/Video Transport Payloads (payload) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 11:19:16 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Tuesday, January 11, 2011 8:35 PM To: new-work@ietf.org Subject: WG Review: Audio/Video Transport Payloads (payload)=20 A new IETF working group has been proposed in the Real-Time Applications and Infrastructure Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. =20 Audio/Video Transport Payloads (payload) ------------------------------------------- Current Status: Proposed Working Group Last modified: 2010-12-03 Chairs: TBD Real-Time Applications and Infrastructure Area Directors: Gonzalo Camarillo Robert Sparks Real-Time Applications and Infrastructure Area Advisor: Robert Sparks Mailing Lists: TBD Description of Working Group: The PAYLOAD working group is tasked with the specification and maintenance of payload formats for use with the Real-Time Transport Protocol, RTP [RFC3550]. The group will follow the guidelines established in "Guidelines for Writers of RTP Payload Format Specifications" [BCP 36], the "How to Write an RTP Payload Format"=20 (under development) and is responsible for maintaining those guidelines. This working group will develop RTP payload formats for new media codecs, review and revise existing payload formats to advance those which are useful to Draft Standard or Standard, and declare others Historic. Goals and Milestones: Dec 2010 Submit RTP Payload Format for MIDI for Proposed Standard Feb 2011 Submit How to Write an RTP Payload Format for Informational Feb 2011 Submit RTP Payload Format for MPEG-4 Audio/Visual Streams for=20 Proposed Standard Mar 2011 Submit RTP Payload Format for EVBR/G.718 for Proposed Standard Mar 2011 Submit RTP Payload Format for Enhanced Variable Rate=20 Narrowband-Wideband Codec (EVRC-NW) for Proposed Standard Mar 2011 Submit RTP Payload Format for Bluetooth's SBC audio codec for=20 Proposed Standard Apr 2011 Submit RTP Payload Format for MPEG2-TS preamble for Proposed=20 Standard Apr 2011 Submit RTP Payload Format for DV (IEC 61834) Video for=20 Proposed Standard Apr 2011 Submit RTP Payload Format for the iSAC codec for Proposed=20 Standard Apr 2011 Submit RTP profile for the carriage of SMPTE 336M data for=20 Proposed Standard Jun 2011 Submit RTP Payload Format for MVC Video for Proposed Standard From dromasca@avaya.com Wed Jan 12 03:19:46 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7ECBD3A6A5F; Wed, 12 Jan 2011 03:19:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.544 X-Spam-Level: X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlU-Yba7idgo; Wed, 12 Jan 2011 03:19:45 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 0297C3A6B10; Wed, 12 Jan 2011 03:19:44 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAPIcLU3GmAcF/2dsb2JhbACkPnOlZAKWWoJ1glcEjko X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="259211509" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 12 Jan 2011 06:22:04 -0500 X-IronPort-AV: E=Sophos;i="4.60,312,1291611600"; d="scan'208";a="569398468" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 12 Jan 2011 06:22:03 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jan 2011 12:21:54 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) Thread-Index: AcuxvwtCiKy7IsiIT8e4vKMgHPx5pgAi9zuw From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , , "YANG Doctors" Subject: [AAA-DOCTORS] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 11:19:46 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Tuesday, January 11, 2011 8:38 PM To: new-work@ietf.org Subject: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock)=20 A new IETF working group has been proposed in the Real-Time Applications and Infrastructure Area. The IESG has not made any determination as yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. =20 Metric Blocks for use with RTCP's Extended Report Framework (xrblock) ------------------------------------------- Current Status: Proposed Working Group Last modified: 2010-12-03 Chairs: TBD Real-Time Applications and Infrastructure Area Directors: Gonzalo Camarillo Robert Sparks Real-Time Applications and Infrastructure Area Advisor: Robert Sparks Mailing Lists: TBD Description of Working Group: RFC3611, "RTP Control Protocol Extended Reports (RTCP XR)" established a framework to allow new information to be conveyed in RTCP, supplementing the original report blocks defined in RFC 3550, "RTP: A Transport Protocol for Real-Time Applications". The XRBLOCK working group is chartered to work within this framework, evaluating proposals for report block definitions containing new metrics. The group will follow the guidelines established in RFC5968, "Guidelines for Extending the RTP Control Protocol (RTCP)" and RTP Monitoring Architecture being developed in the RTPCORE working group. Goals and Milestones: Mar 2011 Submit RTCP XR Report Block for Measurement Identity Mar 2011 Submit RTCP XR Report Block for Burst/Gap Discard metric=20 Reporting Mar 2011 Submit RTCP XR Report Block for Burst/Gap Loss metric=20 Reporting Jun 2011 Submit RTCP XR Report Block for Concealed Seconds metric=20 Reporting Jun 2011 Submit RTCP XR Report Block for Delay metric Reporting Jun 2011 Submit RTCP XR Report Block for Discard metric Reporting Sep 2011 Submit RTCP XR Report Block for Jitter Buffer Metric Reporting Sep 2011 Submit RTCP XR Report Block for Loss Concealment metric=20 Reporting Sep 2011 Submit RTCP XR Report Block for Packet Delay Variation Metric=20 Reporting Dec 2011 Submit RTCP XR Report Block for Run Length Encodings of=20 Discarded Packets Dec 2011 Submit RTCP XR Report Block for QoE Metrics Reporting =20 From tme@americafree.tv Wed Jan 12 05:51:39 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6384B3A6B27; Wed, 12 Jan 2011 05:51:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.243 X-Spam-Level: X-Spam-Status: No, score=-102.243 tagged_above=-999 required=5 tests=[AWL=0.356, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Mr2rzFdnh6d; Wed, 12 Jan 2011 05:51:35 -0800 (PST) Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 653513A6A36; Wed, 12 Jan 2011 05:51:35 -0800 (PST) Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id AF5929A2C399; Wed, 12 Jan 2011 08:53:53 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=us-ascii From: Marshall Eubanks In-Reply-To: Date: Wed, 12 Jan 2011 08:53:49 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <824DCB12-4FC5-4573-A698-4887CD5D1785@americafree.tv> References: To: "Romascanu, Dan (Dan)" X-Mailer: Apple Mail (2.1081) X-Mailman-Approved-At: Wed, 12 Jan 2011 06:50:14 -0800 Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Audio/Video Transport Core Maintenence (avtcore) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 13:51:39 -0000 On Jan 12, 2011, at 6:20 AM, Romascanu, Dan (Dan) wrote: > This is the first in a series of four messages announcing the review = for > four IETF Working Groups. Note that these WGs are not completely new, > but rather the split of the current AVT (Audio/Video Transport) WG in > the RAI Area.=20 Dear Dan; In this case, what exactly is being reviewed : The desirability of splitting AVT ? The fault lines along which the split is being done ? The detailed charters of each new group & the energy available to do = each of the pieces ? In particular, 3 of the 4 seem like a fairly routine split of AVT, while = the fourth (XRBLOCK) seems like new work, and so it seems to me should be evaluated differently. Regards Marshall >=20 > Dan >=20 >=20 > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf = Of > IESG Secretary > Sent: Tuesday, January 11, 2011 8:43 PM > To: new-work@ietf.org > Subject: WG Review: Audio/Video Transport Core Maintenence (avtcore)=20= >=20 > A new IETF working group has been proposed in the Real-Time = Applications > and Infrastructure Area. The IESG has not made any determination as > yet. > The following draft charter was submitted, and is provided for > informational purposes only. Please send your comments to the IESG > mailing > list (iesg@ietf.org) by Tuesday, January 18, 2011. =20 >=20 > Audio/Video Transport Core Maintenence (avtcore) > ------------------------------------------- > Current Status: Proposed Working Group > Last modified: 2010-12-03 >=20 > Chairs: TBD >=20 > Real-Time Applications and Infrastructure Area Directors: > Gonzalo Camarillo > Robert Sparks >=20 > Real-Time Applications and Infrastructure Area Advisor: > Robert Sparks >=20 > Mailing Lists: TBD >=20 > Description of Working Group: >=20 > The Real-time Transport Protocol, RTP, along with its associated > profiles and payload formats provides for real-time transmission of > audio and video over unicast and multicast transports. RTP itself has > been shepherded to Full Standard. Its associated profiles, extensions, > and payload formats are currently at various levels of standards > maturity.=20 >=20 > The AVTCORE working group is chartered to maintain the core RTP/RTCP > protocols and the AVP, SAVP, AVPF, and SAVPF profiles. The group will > provide architectural guidance for extending the protocols and > guidelines for their proper use. While other working groups may be > chartered to work on application-specific extensions to the protocols, > extensions that are generally applicable will be developed in AVTCORE. >=20 > The AVTCORE working group will coordinate closely with the Security = Area > while working on maintenance and enhancements to the SRTP Profile. >=20 > In addition to the milestones called out below, the AVTCORE working > group's initial tasks will include completing any remaining work > identified in those drafts from the AVT working group already in IESG > Evaluation, with the exception of the Rapid Acquisition of Multicast = RTP > sessions, which will complete in the AVTEXT working group. >=20 > Goals and Milestones: > Dec 2010 Submit Guideline for Choosing RTCP CNAME as Proposed = Standard > Dec 2010 Submit use of AES-192 and AES-256 in Secure RTP for Proposed=20= > Standard > Dec 2010 Submit Port Mapping Between Unicast and Multicast RTP = Sessions >=20 > for Proposed Standard > Dec 2010 Submit Real-Time Transport Control Protocol (RTCP) in = Overlay=20 > Multicast for Proposed Standard Feb 2011 Submit Monitoring > Architecture for RTP for Informational Feb 2011 Guidelines for the = use > of Variable Bit Rate Audio with Secure=20 > RTP as informational (or possibly BCP) Apr 2011 Submit in > band keying mechanism for SRTP draft for Proposed=20 > Standard > Apr 2011 Submit Explicit Congestion Notification (ECN) for RTP over = UDP >=20 > for Proposed Standard > May 2011 RTCP indication for retransmission suppression as proposed=20= > standard > Sep 2011 Encryption of Header Extensions in the Secure Real-Time=20 > Transport Protocol (SRTP) for Proposed Standard >=20 > _______________________________________________ > OPS-DIR mailing list > OPS-DIR@ietf.org > https://www.ietf.org/mailman/listinfo/ops-dir >=20 From dromasca@avaya.com Wed Jan 12 06:55:41 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 923F228C126; Wed, 12 Jan 2011 06:55:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.545 X-Spam-Level: X-Spam-Status: No, score=-102.545 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgVGMetBMe5O; Wed, 12 Jan 2011 06:55:40 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 0F17928C108; Wed, 12 Jan 2011 06:55:39 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAIJQLU2HCzI1/2dsb2JhbACkPnOlcQKWMYVMBI5K X-IronPort-AV: E=Sophos;i="4.60,313,1291611600"; d="scan'208";a="259245157" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 12 Jan 2011 09:57:58 -0500 X-IronPort-AV: E=Sophos;i="4.60,313,1291611600"; d="scan'208";a="581402771" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 12 Jan 2011 09:57:57 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jan 2011 15:57:51 +0100 Message-ID: In-Reply-To: <824DCB12-4FC5-4573-A698-4887CD5D1785@americafree.tv> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPS-DIR] FW: WG Review: Audio/Video Transport Core Maintenence (avtcore) Thread-Index: AcuyYCkgdJJjgJY4QlaPzPohsstWvAACG2CQ References: <824DCB12-4FC5-4573-A698-4887CD5D1785@americafree.tv> From: "Romascanu, Dan (Dan)" To: "Marshall Eubanks" Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Audio/Video Transport Core Maintenence (avtcore) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 14:55:41 -0000 Marshall, Addressing all these questions seems to me valid - as the IESG will need to make a decision at the next telechat and input is appreciated. You may also want to read into the archives of AVT for the discussions that led to the proposal to split the WG - as some of these questions may have already been addressed and discussed. =20 Dan =20 > -----Original Message----- > From: Marshall Eubanks [mailto:tme@americafree.tv]=20 > Sent: Wednesday, January 12, 2011 3:54 PM > To: Romascanu, Dan (Dan) > Cc: ops-dir@ietf.org; IETF DNS Directorate;=20 > aaa-doctors@ietf.org; mib-doctors@ietf.org; YANG Doctors > Subject: Re: [OPS-DIR] FW: WG Review: Audio/Video Transport=20 > Core Maintenence (avtcore) >=20 >=20 > On Jan 12, 2011, at 6:20 AM, Romascanu, Dan (Dan) wrote: >=20 > > This is the first in a series of four messages announcing=20 > the review=20 > > for four IETF Working Groups. Note that these WGs are not=20 > completely=20 > > new, but rather the split of the current AVT (Audio/Video=20 > Transport)=20 > > WG in the RAI Area. >=20 > Dear Dan; >=20 > In this case, what exactly is being reviewed : >=20 > The desirability of splitting AVT ? >=20 > The fault lines along which the split is being done ? >=20 > The detailed charters of each new group & the energy=20 > available to do each of the pieces ? >=20 > In particular, 3 of the 4 seem like a fairly routine split of=20 > AVT, while the fourth (XRBLOCK) seems like new work, and so=20 > it seems to me should be evaluated differently. >=20 > Regards > Marshall >=20 >=20 > >=20 > > Dan > >=20 > >=20 > > -----Original Message----- > > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]=20 > On Behalf=20 > > Of IESG Secretary > > Sent: Tuesday, January 11, 2011 8:43 PM > > To: new-work@ietf.org > > Subject: WG Review: Audio/Video Transport Core Maintenence (avtcore) > >=20 > > A new IETF working group has been proposed in the Real-Time=20 > > Applications and Infrastructure Area. The IESG has not made any=20 > > determination as yet. > > The following draft charter was submitted, and is provided for=20 > > informational purposes only. Please send your comments to the IESG=20 > > mailing > > list (iesg@ietf.org) by Tuesday, January 18, 2011. =20 > >=20 > > Audio/Video Transport Core Maintenence (avtcore) > > ------------------------------------------- > > Current Status: Proposed Working Group Last modified: 2010-12-03 > >=20 > > Chairs: TBD > >=20 > > Real-Time Applications and Infrastructure Area Directors: > > Gonzalo Camarillo Robert Sparks=20 > > > >=20 > > Real-Time Applications and Infrastructure Area Advisor: > > Robert Sparks > >=20 > > Mailing Lists: TBD > >=20 > > Description of Working Group: > >=20 > > The Real-time Transport Protocol, RTP, along with its associated=20 > > profiles and payload formats provides for real-time transmission of=20 > > audio and video over unicast and multicast transports. RTP=20 > itself has=20 > > been shepherded to Full Standard. Its associated profiles,=20 > extensions,=20 > > and payload formats are currently at various levels of standards=20 > > maturity. > >=20 > > The AVTCORE working group is chartered to maintain the core=20 > RTP/RTCP=20 > > protocols and the AVP, SAVP, AVPF, and SAVPF profiles. The=20 > group will=20 > > provide architectural guidance for extending the protocols and=20 > > guidelines for their proper use. While other working groups may be=20 > > chartered to work on application-specific extensions to the=20 > protocols,=20 > > extensions that are generally applicable will be developed=20 > in AVTCORE. > >=20 > > The AVTCORE working group will coordinate closely with the Security=20 > > Area while working on maintenance and enhancements to the=20 > SRTP Profile. > >=20 > > In addition to the milestones called out below, the AVTCORE working=20 > > group's initial tasks will include completing any remaining work=20 > > identified in those drafts from the AVT working group=20 > already in IESG=20 > > Evaluation, with the exception of the Rapid Acquisition of=20 > Multicast=20 > > RTP sessions, which will complete in the AVTEXT working group. > >=20 > > Goals and Milestones: > > Dec 2010 Submit Guideline for Choosing RTCP CNAME as Proposed=20 > > Standard Dec 2010 Submit use of AES-192 and AES-256 in=20 > Secure RTP for Proposed > > Standard > > Dec 2010 Submit Port Mapping Between Unicast and Multicast RTP=20 > > Sessions > >=20 > > for Proposed Standard > > Dec 2010 Submit Real-Time Transport Control Protocol=20 > (RTCP) in Overlay=20 > > Multicast for Proposed Standard Feb 2011 Submit=20 > Monitoring=20 > > Architecture for RTP for Informational Feb 2011 Guidelines for the=20 > > use of Variable Bit Rate Audio with Secure > > RTP as informational (or possibly BCP) Apr 2011 Submit in=20 > > band keying mechanism for SRTP draft for Proposed > > Standard > > Apr 2011 Submit Explicit Congestion Notification (ECN) for=20 > RTP over=20 > > UDP > >=20 > > for Proposed Standard > > May 2011 RTCP indication for retransmission suppression as=20 > proposed=20 > > standard > > Sep 2011 Encryption of Header Extensions in the Secure Real-Time=20 > > Transport Protocol (SRTP) for Proposed Standard > >=20 > > _______________________________________________ > > OPS-DIR mailing list > > OPS-DIR@ietf.org > > https://www.ietf.org/mailman/listinfo/ops-dir > >=20 >=20 >=20 From dromasca@avaya.com Thu Jan 13 02:38:06 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A2173A6B60; Thu, 13 Jan 2011 02:38:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.54 X-Spam-Level: X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4fQu8sRMe4c; Thu, 13 Jan 2011 02:38:05 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 0A8F83A6A17; Thu, 13 Jan 2011 02:38:03 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEABNlLk3GmAcF/2dsb2JhbACkRnOmDAKWQ4J1glcEjkw X-IronPort-AV: E=Sophos;i="4.60,317,1291611600"; d="scan'208";a="227321823" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 13 Jan 2011 05:40:24 -0500 X-IronPort-AV: E=Sophos;i="4.60,317,1291611600"; d="scan'208";a="569809095" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Jan 2011 05:40:23 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Jan 2011 11:39:58 +0100 Message-ID: In-Reply-To: <4D2EBFD5.4030006@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) Thread-Index: AcuzAUJoyaTYsSjfRgWyqFsI1KM1twADNg/Q References: <4D2EBFD5.4030006@cisco.com> From: "Romascanu, Dan (Dan)" To: "Benoit Claise" Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2011 10:38:06 -0000 Hard to refer it in the charter as long as the RFC is not published.=20 Dan =20 > -----Original Message----- > From: Benoit Claise [mailto:bclaise@cisco.com]=20 > Sent: Thursday, January 13, 2011 11:03 AM > To: Romascanu, Dan (Dan) > Cc: ops-dir@ietf.org; IETF DNS Directorate;=20 > aaa-doctors@ietf.org; mib-doctors@ietf.org; YANG Doctors > Subject: Re: [OPS-DIR] FW: WG Review: Metric Blocks for use=20 > with RTCP's Extended Report Framework (xrblock) >=20 > Dan, >=20 > This one would be a good candidate for the PMOL guidelines. > Not sure if PMOL should be mentioned in the charter though... >=20 > Regards, Benoit. > > > > > > -----Original Message----- > > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]=20 > On Behalf=20 > > Of IESG Secretary > > Sent: Tuesday, January 11, 2011 8:38 PM > > To: new-work@ietf.org > > Subject: WG Review: Metric Blocks for use with RTCP's=20 > Extended Report=20 > > Framework (xrblock) > > > > A new IETF working group has been proposed in the Real-Time=20 > > Applications and Infrastructure Area. The IESG has not made any=20 > > determination as yet. > > The following draft charter was submitted, and is provided for=20 > > informational purposes only. Please send your comments to the IESG=20 > > mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. > > > > Metric Blocks for use with RTCP's Extended Report Framework=20 > (xrblock) > > ------------------------------------------- > > Current Status: Proposed Working Group Last modified: 2010-12-03 > > > > Chairs: TBD > > > > Real-Time Applications and Infrastructure Area Directors: > > Gonzalo Camarillo > > Robert Sparks > > > > Real-Time Applications and Infrastructure Area Advisor: > > Robert Sparks > > > > Mailing Lists: TBD > > > > Description of Working Group: > > > > RFC3611, "RTP Control Protocol Extended Reports (RTCP XR)"=20 > established=20 > > a framework to allow new information to be conveyed in RTCP,=20 > > supplementing the original report blocks defined in RFC=20 > 3550, "RTP: A=20 > > Transport Protocol for Real-Time Applications". > > > > The XRBLOCK working group is chartered to work within this=20 > framework,=20 > > evaluating proposals for report block definitions containing new=20 > > metrics. The group will follow the guidelines established=20 > in RFC5968,=20 > > "Guidelines for Extending the RTP Control Protocol (RTCP)" and RTP=20 > > Monitoring Architecture being developed in the RTPCORE=20 > working group. > > > > Goals and Milestones: > > > > Mar 2011 Submit RTCP XR Report Block for Measurement Identity Mar=20 > > 2011 Submit RTCP XR Report Block for Burst/Gap Discard metric > > Reporting > > Mar 2011 Submit RTCP XR Report Block for Burst/Gap Loss metric > > Reporting > > Jun 2011 Submit RTCP XR Report Block for Concealed Seconds metric > > Reporting > > Jun 2011 Submit RTCP XR Report Block for Delay metric Reporting Jun > > 2011 Submit RTCP XR Report Block for Discard metric Reporting Sep=20 > > 2011 Submit RTCP XR Report Block for Jitter Buffer Metric Reporting=20 > > Sep 2011 Submit RTCP XR Report Block for Loss Concealment metric > > Reporting > > Sep 2011 Submit RTCP XR Report Block for Packet Delay=20 > Variation Metric > > Reporting > > Dec 2011 Submit RTCP XR Report Block for Run Length Encodings of > > Discarded Packets > > Dec 2011 Submit RTCP XR Report Block for QoE Metrics Reporting=20 > > _______________________________________________ > > OPS-DIR mailing list > > OPS-DIR@ietf.org > > https://www.ietf.org/mailman/listinfo/ops-dir >=20 >=20 From bclaise@cisco.com Thu Jan 13 01:08:32 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B1A13A6AB7; Thu, 13 Jan 2011 01:08:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.48 X-Spam-Level: X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WwQf1ajd60C8; Thu, 13 Jan 2011 01:08:31 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id DC9F33A6AB3; Thu, 13 Jan 2011 01:08:30 -0800 (PST) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p0D93Lfi015195; Thu, 13 Jan 2011 10:03:21 +0100 (CET) Received: from [10.55.43.55] (ams-bclaise-8716.cisco.com [10.55.43.55]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p0D93HC4008156; Thu, 13 Jan 2011 10:03:17 +0100 (CET) Message-ID: <4D2EBFD5.4030006@cisco.com> Date: Thu, 13 Jan 2011 10:03:17 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 13 Jan 2011 02:42:44 -0800 Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2011 09:08:32 -0000 Dan, This one would be a good candidate for the PMOL guidelines. Not sure if PMOL should be mentioned in the charter though... Regards, Benoit. > > > -----Original Message----- > From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of > IESG Secretary > Sent: Tuesday, January 11, 2011 8:38 PM > To: new-work@ietf.org > Subject: WG Review: Metric Blocks for use with RTCP's Extended Report > Framework (xrblock) > > A new IETF working group has been proposed in the Real-Time Applications > and Infrastructure Area. The IESG has not made any determination as > yet. > The following draft charter was submitted, and is provided for > informational purposes only. Please send your comments to the IESG > mailing > list (iesg@ietf.org) by Tuesday, January 18, 2011. > > Metric Blocks for use with RTCP's Extended Report Framework (xrblock) > ------------------------------------------- > Current Status: Proposed Working Group > Last modified: 2010-12-03 > > Chairs: TBD > > Real-Time Applications and Infrastructure Area Directors: > Gonzalo Camarillo > Robert Sparks > > Real-Time Applications and Infrastructure Area Advisor: > Robert Sparks > > Mailing Lists: TBD > > Description of Working Group: > > RFC3611, "RTP Control Protocol Extended Reports (RTCP XR)" established a > framework to allow new information to be conveyed in RTCP, supplementing > the original report blocks defined in RFC 3550, "RTP: A Transport > Protocol for Real-Time Applications". > > The XRBLOCK working group is chartered to work within this framework, > evaluating proposals for report block definitions containing new > metrics. The group will follow the guidelines established in RFC5968, > "Guidelines for Extending the RTP Control Protocol (RTCP)" and RTP > Monitoring Architecture being developed in the RTPCORE working group. > > Goals and Milestones: > > Mar 2011 Submit RTCP XR Report Block for Measurement Identity Mar 2011 > Submit RTCP XR Report Block for Burst/Gap Discard metric > Reporting > Mar 2011 Submit RTCP XR Report Block for Burst/Gap Loss metric > Reporting > Jun 2011 Submit RTCP XR Report Block for Concealed Seconds metric > Reporting > Jun 2011 Submit RTCP XR Report Block for Delay metric Reporting Jun > 2011 Submit RTCP XR Report Block for Discard metric Reporting Sep 2011 > Submit RTCP XR Report Block for Jitter Buffer Metric Reporting Sep 2011 > Submit RTCP XR Report Block for Loss Concealment metric > Reporting > Sep 2011 Submit RTCP XR Report Block for Packet Delay Variation Metric > Reporting > Dec 2011 Submit RTCP XR Report Block for Run Length Encodings of > Discarded Packets > Dec 2011 Submit RTCP XR Report Block for QoE Metrics Reporting > _______________________________________________ > OPS-DIR mailing list > OPS-DIR@ietf.org > https://www.ietf.org/mailman/listinfo/ops-dir From bclaise@cisco.com Thu Jan 13 04:55:24 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEFA73A6B79; Thu, 13 Jan 2011 04:55:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.483 X-Spam-Level: X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZ+xlGx7VmtY; Thu, 13 Jan 2011 04:55:23 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 83ADD3A6B76; Thu, 13 Jan 2011 04:55:23 -0800 (PST) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p0DCoDmh003918; Thu, 13 Jan 2011 13:50:13 +0100 (CET) Received: from [10.55.43.55] (ams-bclaise-8716.cisco.com [10.55.43.55]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p0DCoCQR006846; Thu, 13 Jan 2011 13:50:12 +0100 (CET) Message-ID: <4D2EF504.20700@cisco.com> Date: Thu, 13 Jan 2011 13:50:12 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: "Romascanu, Dan (Dan)" References: <4D2EBFD5.4030006@cisco.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 13 Jan 2011 07:43:12 -0800 Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2011 12:55:24 -0000 Dan, Understood. Btw, interestingly, I was working on the PMOL framework this morning. The IETF last-call is not that far. However, I was thinking of a generic sentence that will point to PMOL without mentioning it. Something such as: "The definition of performance metrics should be consistent with the existing common practice in the IETF" Regards, Benoit. > Hard to refer it in the charter as long as the RFC is not published. > > Dan > > >> -----Original Message----- >> From: Benoit Claise [mailto:bclaise@cisco.com] >> Sent: Thursday, January 13, 2011 11:03 AM >> To: Romascanu, Dan (Dan) >> Cc: ops-dir@ietf.org; IETF DNS Directorate; >> aaa-doctors@ietf.org; mib-doctors@ietf.org; YANG Doctors >> Subject: Re: [OPS-DIR] FW: WG Review: Metric Blocks for use >> with RTCP's Extended Report Framework (xrblock) >> >> Dan, >> >> This one would be a good candidate for the PMOL guidelines. >> Not sure if PMOL should be mentioned in the charter though... >> >> Regards, Benoit. >>> >>> -----Original Message----- >>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] >> On Behalf >>> Of IESG Secretary >>> Sent: Tuesday, January 11, 2011 8:38 PM >>> To: new-work@ietf.org >>> Subject: WG Review: Metric Blocks for use with RTCP's >> Extended Report >>> Framework (xrblock) >>> >>> A new IETF working group has been proposed in the Real-Time >>> Applications and Infrastructure Area. The IESG has not made any >>> determination as yet. >>> The following draft charter was submitted, and is provided for >>> informational purposes only. Please send your comments to the IESG >>> mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. >>> >>> Metric Blocks for use with RTCP's Extended Report Framework >> (xrblock) >>> ------------------------------------------- >>> Current Status: Proposed Working Group Last modified: 2010-12-03 >>> >>> Chairs: TBD >>> >>> Real-Time Applications and Infrastructure Area Directors: >>> Gonzalo Camarillo >>> Robert Sparks >>> >>> Real-Time Applications and Infrastructure Area Advisor: >>> Robert Sparks >>> >>> Mailing Lists: TBD >>> >>> Description of Working Group: >>> >>> RFC3611, "RTP Control Protocol Extended Reports (RTCP XR)" >> established >>> a framework to allow new information to be conveyed in RTCP, >>> supplementing the original report blocks defined in RFC >> 3550, "RTP: A >>> Transport Protocol for Real-Time Applications". >>> >>> The XRBLOCK working group is chartered to work within this >> framework, >>> evaluating proposals for report block definitions containing new >>> metrics. The group will follow the guidelines established >> in RFC5968, >>> "Guidelines for Extending the RTP Control Protocol (RTCP)" and RTP >>> Monitoring Architecture being developed in the RTPCORE >> working group. >>> Goals and Milestones: >>> >>> Mar 2011 Submit RTCP XR Report Block for Measurement Identity Mar >>> 2011 Submit RTCP XR Report Block for Burst/Gap Discard metric >>> Reporting >>> Mar 2011 Submit RTCP XR Report Block for Burst/Gap Loss metric >>> Reporting >>> Jun 2011 Submit RTCP XR Report Block for Concealed Seconds metric >>> Reporting >>> Jun 2011 Submit RTCP XR Report Block for Delay metric Reporting Jun >>> 2011 Submit RTCP XR Report Block for Discard metric Reporting Sep >>> 2011 Submit RTCP XR Report Block for Jitter Buffer Metric Reporting >>> Sep 2011 Submit RTCP XR Report Block for Loss Concealment metric >>> Reporting >>> Sep 2011 Submit RTCP XR Report Block for Packet Delay >> Variation Metric >>> Reporting >>> Dec 2011 Submit RTCP XR Report Block for Run Length Encodings of >>> Discarded Packets >>> Dec 2011 Submit RTCP XR Report Block for QoE Metrics Reporting >>> _______________________________________________ >>> OPS-DIR mailing list >>> OPS-DIR@ietf.org >>> https://www.ietf.org/mailman/listinfo/ops-dir >> From dromasca@avaya.com Thu Jan 13 07:56:22 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37AB228C115; Thu, 13 Jan 2011 07:56:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.536 X-Spam-Level: X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nD9Xudu5NipU; Thu, 13 Jan 2011 07:56:20 -0800 (PST) Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id E4C7E28C112; Thu, 13 Jan 2011 07:56:19 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEABOwLk2HCzI1/2dsb2JhbACkSHOmVgKWLYJ1glcEjkw X-IronPort-AV: E=Sophos;i="4.60,318,1291611600"; d="scan'208";a="54190514" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 13 Jan 2011 10:56:49 -0500 X-IronPort-AV: E=Sophos;i="4.60,317,1291611600"; d="scan'208";a="581916016" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 13 Jan 2011 10:56:13 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Jan 2011 16:55:57 +0100 Message-ID: In-Reply-To: <4D2EF504.20700@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) Thread-Index: AcuzIPQWsMl6GLHySiGezcgTxba5mgAGSg+w References: <4D2EBFD5.4030006@cisco.com> <4D2EF504.20700@cisco.com> From: "Romascanu, Dan (Dan)" To: "Benoit Claise" Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2011 15:56:22 -0000 Actually this may be a good idea. You can make this comment to the IESG as the charter is in public external review. It will draw more attention to the PMOL guidelines which is not a bad thing either.=20 Thanks and Regards, Dan =20 > -----Original Message----- > From: Benoit Claise [mailto:bclaise@cisco.com]=20 > Sent: Thursday, January 13, 2011 2:50 PM > To: Romascanu, Dan (Dan) > Cc: ops-dir@ietf.org; IETF DNS Directorate;=20 > aaa-doctors@ietf.org; mib-doctors@ietf.org; YANG Doctors > Subject: Re: [OPS-DIR] FW: WG Review: Metric Blocks for use=20 > with RTCP's Extended Report Framework (xrblock) >=20 > Dan, >=20 > Understood. Btw, interestingly, I was working on the PMOL=20 > framework this morning. The IETF last-call is not that far. > However, I was thinking of a generic sentence that will point=20 > to PMOL without mentioning it. > Something such as: "The definition of performance metrics=20 > should be consistent with the existing common practice in the IETF" >=20 > Regards, Benoit. > > Hard to refer it in the charter as long as the RFC is not published. > > > > Dan > > > > > >> -----Original Message----- > >> From: Benoit Claise [mailto:bclaise@cisco.com] > >> Sent: Thursday, January 13, 2011 11:03 AM > >> To: Romascanu, Dan (Dan) > >> Cc: ops-dir@ietf.org; IETF DNS Directorate; aaa-doctors@ietf.org;=20 > >> mib-doctors@ietf.org; YANG Doctors > >> Subject: Re: [OPS-DIR] FW: WG Review: Metric Blocks for use with=20 > >> RTCP's Extended Report Framework (xrblock) > >> > >> Dan, > >> > >> This one would be a good candidate for the PMOL guidelines. > >> Not sure if PMOL should be mentioned in the charter though... > >> > >> Regards, Benoit. > >>> > >>> -----Original Message----- > >>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] > >> On Behalf > >>> Of IESG Secretary > >>> Sent: Tuesday, January 11, 2011 8:38 PM > >>> To: new-work@ietf.org > >>> Subject: WG Review: Metric Blocks for use with RTCP's > >> Extended Report > >>> Framework (xrblock) > >>> > >>> A new IETF working group has been proposed in the Real-Time=20 > >>> Applications and Infrastructure Area. The IESG has not made any=20 > >>> determination as yet. > >>> The following draft charter was submitted, and is provided for=20 > >>> informational purposes only. Please send your comments to=20 > the IESG=20 > >>> mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. > >>> > >>> Metric Blocks for use with RTCP's Extended Report Framework > >> (xrblock) > >>> ------------------------------------------- > >>> Current Status: Proposed Working Group Last modified: 2010-12-03 > >>> > >>> Chairs: TBD > >>> > >>> Real-Time Applications and Infrastructure Area Directors: > >>> Gonzalo Camarillo > >>> Robert Sparks > >>> > >>> Real-Time Applications and Infrastructure Area Advisor: > >>> Robert Sparks > >>> > >>> Mailing Lists: TBD > >>> > >>> Description of Working Group: > >>> > >>> RFC3611, "RTP Control Protocol Extended Reports (RTCP XR)" > >> established > >>> a framework to allow new information to be conveyed in RTCP,=20 > >>> supplementing the original report blocks defined in RFC > >> 3550, "RTP: A > >>> Transport Protocol for Real-Time Applications". > >>> > >>> The XRBLOCK working group is chartered to work within this > >> framework, > >>> evaluating proposals for report block definitions containing new=20 > >>> metrics. The group will follow the guidelines established > >> in RFC5968, > >>> "Guidelines for Extending the RTP Control Protocol=20 > (RTCP)" and RTP=20 > >>> Monitoring Architecture being developed in the RTPCORE > >> working group. > >>> Goals and Milestones: > >>> > >>> Mar 2011 Submit RTCP XR Report Block for Measurement Identity Mar > >>> 2011 Submit RTCP XR Report Block for Burst/Gap Discard metric > >>> Reporting > >>> Mar 2011 Submit RTCP XR Report Block for Burst/Gap Loss metric > >>> Reporting > >>> Jun 2011 Submit RTCP XR Report Block for Concealed Seconds metric > >>> Reporting > >>> Jun 2011 Submit RTCP XR Report Block for Delay metric=20 > Reporting Jun > >>> 2011 Submit RTCP XR Report Block for Discard metric Reporting Sep > >>> 2011 Submit RTCP XR Report Block for Jitter Buffer Metric=20 > Reporting=20 > >>> Sep 2011 Submit RTCP XR Report Block for Loss Concealment metric > >>> Reporting > >>> Sep 2011 Submit RTCP XR Report Block for Packet Delay > >> Variation Metric > >>> Reporting > >>> Dec 2011 Submit RTCP XR Report Block for Run Length Encodings of > >>> Discarded Packets > >>> Dec 2011 Submit RTCP XR Report Block for QoE Metrics Reporting=20 > >>> _______________________________________________ > >>> OPS-DIR mailing list > >>> OPS-DIR@ietf.org > >>> https://www.ietf.org/mailman/listinfo/ops-dir > >> >=20 >=20 From acmorton@att.com Thu Jan 13 08:19:41 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BE933A69ED; Thu, 13 Jan 2011 08:19:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.796 X-Spam-Level: X-Spam-Status: No, score=-105.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x3v0JKeo84ZO; Thu, 13 Jan 2011 08:19:39 -0800 (PST) Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id D01E83A6B33; Thu, 13 Jan 2011 08:19:38 -0800 (PST) X-VirusChecked: Checked X-Env-Sender: acmorton@att.com X-Msg-Ref: server-14.tower-161.messagelabs.com!1294935706!39170224!1 X-StarScan-Version: 6.2.9; banners=-,-,- X-Originating-IP: [144.160.20.145] Received: (qmail 26268 invoked from network); 13 Jan 2011 16:21:58 -0000 Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-14.tower-161.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Jan 2011 16:21:58 -0000 Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0DGLsKE020271; Thu, 13 Jan 2011 11:21:54 -0500 Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0DGLoRY020197; Thu, 13 Jan 2011 11:21:50 -0500 Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p0DGLSwE002221; Thu, 13 Jan 2011 11:21:28 -0500 Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p0DGLPAC002152; Thu, 13 Jan 2011 11:21:25 -0500 Message-Id: <201101131621.p0DGLPAC002152@alpd052.aldc.att.com> Received: from acmt.att.com (martym.mt.att.com[135.16.251.71](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20110113162124gw1004lk1ve>; Thu, 13 Jan 2011 16:21:24 +0000 X-Originating-IP: [135.16.251.71] X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Thu, 13 Jan 2011 11:21:55 -0500 To: "Romascanu, Dan (Dan)" , "Benoit Claise" From: Al Morton In-Reply-To: References: <4D2EBFD5.4030006@cisco.com> <4D2EF504.20700@cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailman-Approved-At: Thu, 13 Jan 2011 08:21:20 -0800 Cc: aaa-doctors@ietf.org, mib-doctors@ietf.org, ops-dir@ietf.org, IETF DNS Directorate , YANG Doctors Subject: Re: [AAA-DOCTORS] [OPS-DIR] FW: WG Review: Metric Blocks for use with RTCP's Extended Report Framework (xrblock) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2011 16:19:41 -0000 I think some of the RTCP metrics are only defined in a general way, using other standards with more detail as references (when available). I haven't combed the entire crop of RTCP extension drafts, but this was certainly true in some of them, and in RFC 3611, RTCP-XR. I support the comment, in any case, Al At 10:55 AM 1/13/2011, Romascanu, Dan (Dan) wrote: >Actually this may be a good idea. You can make this comment to the IESG >as the charter is in public external review. It will draw more attention >to the PMOL guidelines which is not a bad thing either. > >Thanks and Regards, > >Dan > > > > -----Original Message----- > > From: Benoit Claise [mailto:bclaise@cisco.com] > > Sent: Thursday, January 13, 2011 2:50 PM > > To: Romascanu, Dan (Dan) > > Cc: ops-dir@ietf.org; IETF DNS Directorate; > > aaa-doctors@ietf.org; mib-doctors@ietf.org; YANG Doctors > > Subject: Re: [OPS-DIR] FW: WG Review: Metric Blocks for use > > with RTCP's Extended Report Framework (xrblock) > > > > Dan, > > > > Understood. Btw, interestingly, I was working on the PMOL > > framework this morning. The IETF last-call is not that far. > > However, I was thinking of a generic sentence that will point > > to PMOL without mentioning it. > > Something such as: "The definition of performance metrics > > should be consistent with the existing common practice in the IETF" > > > > Regards, Benoit. > > > Hard to refer it in the charter as long as the RFC is not published. > > > > > > Dan > > > > > > > > >> -----Original Message----- > > >> From: Benoit Claise [mailto:bclaise@cisco.com] > > >> Sent: Thursday, January 13, 2011 11:03 AM > > >> To: Romascanu, Dan (Dan) > > >> Cc: ops-dir@ietf.org; IETF DNS Directorate; aaa-doctors@ietf.org; > > >> mib-doctors@ietf.org; YANG Doctors > > >> Subject: Re: [OPS-DIR] FW: WG Review: Metric Blocks for use with > > >> RTCP's Extended Report Framework (xrblock) > > >> > > >> Dan, > > >> > > >> This one would be a good candidate for the PMOL guidelines. > > >> Not sure if PMOL should be mentioned in the charter though... > > >> > > >> Regards, Benoit. > > >>> > > >>> -----Original Message----- > > >>> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] > > >> On Behalf > > >>> Of IESG Secretary > > >>> Sent: Tuesday, January 11, 2011 8:38 PM > > >>> To: new-work@ietf.org > > >>> Subject: WG Review: Metric Blocks for use with RTCP's > > >> Extended Report > > >>> Framework (xrblock) > > >>> > > >>> A new IETF working group has been proposed in the Real-Time > > >>> Applications and Infrastructure Area. The IESG has not made any > > >>> determination as yet. > > >>> The following draft charter was submitted, and is provided for > > >>> informational purposes only. Please send your comments to > > the IESG > > >>> mailing list (iesg@ietf.org) by Tuesday, January 18, 2011. > > >>> > > >>> Metric Blocks for use with RTCP's Extended Report Framework > > >> (xrblock) > > >>> ------------------------------------------- > > >>> Current Status: Proposed Working Group Last modified: 2010-12-03 > > >>> > > >>> Chairs: TBD > > >>> > > >>> Real-Time Applications and Infrastructure Area Directors: > > >>> Gonzalo Camarillo > > >>> Robert Sparks > > >>> > > >>> Real-Time Applications and Infrastructure Area Advisor: > > >>> Robert Sparks > > >>> > > >>> Mailing Lists: TBD > > >>> > > >>> Description of Working Group: > > >>> > > >>> RFC3611, "RTP Control Protocol Extended Reports (RTCP XR)" > > >> established > > >>> a framework to allow new information to be conveyed in RTCP, > > >>> supplementing the original report blocks defined in RFC > > >> 3550, "RTP: A > > >>> Transport Protocol for Real-Time Applications". > > >>> > > >>> The XRBLOCK working group is chartered to work within this > > >> framework, > > >>> evaluating proposals for report block definitions containing new > > >>> metrics. The group will follow the guidelines established > > >> in RFC5968, > > >>> "Guidelines for Extending the RTP Control Protocol > > (RTCP)" and RTP > > >>> Monitoring Architecture being developed in the RTPCORE > > >> working group. > > >>> Goals and Milestones: > > >>> > > >>> Mar 2011 Submit RTCP XR Report Block for Measurement Identity Mar > > >>> 2011 Submit RTCP XR Report Block for Burst/Gap Discard metric > > >>> Reporting > > >>> Mar 2011 Submit RTCP XR Report Block for Burst/Gap Loss metric > > >>> Reporting > > >>> Jun 2011 Submit RTCP XR Report Block for Concealed Seconds metric > > >>> Reporting > > >>> Jun 2011 Submit RTCP XR Report Block for Delay metric > > Reporting Jun > > >>> 2011 Submit RTCP XR Report Block for Discard metric Reporting Sep > > >>> 2011 Submit RTCP XR Report Block for Jitter Buffer Metric > > Reporting > > >>> Sep 2011 Submit RTCP XR Report Block for Loss Concealment metric > > >>> Reporting > > >>> Sep 2011 Submit RTCP XR Report Block for Packet Delay > > >> Variation Metric > > >>> Reporting > > >>> Dec 2011 Submit RTCP XR Report Block for Run Length Encodings of > > >>> Discarded Packets > > >>> Dec 2011 Submit RTCP XR Report Block for QoE Metrics Reporting > > >>> _______________________________________________ > > >>> OPS-DIR mailing list > > >>> OPS-DIR@ietf.org > > >>> https://www.ietf.org/mailman/listinfo/ops-dir > > >> > > > > >_______________________________________________ >OPS-DIR mailing list >OPS-DIR@ietf.org >https://www.ietf.org/mailman/listinfo/ops-dir From dromasca@avaya.com Fri Jan 14 01:59:01 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C63CA3A69EF; Fri, 14 Jan 2011 01:59:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.532 X-Spam-Level: X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1OAfff5Q38CU; Fri, 14 Jan 2011 01:59:00 -0800 (PST) Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id E96403A6A0D; Fri, 14 Jan 2011 01:58:59 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EADOtL02HCzI1/2dsb2JhbACWD45Hc6chApYngniCVwSOUoJc X-IronPort-AV: E=Sophos;i="4.60,322,1291611600"; d="scan'208";a="54322182" Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 14 Jan 2011 05:01:24 -0500 X-IronPort-AV: E=Sophos;i="4.60,322,1291611600"; d="scan'208";a="582265683" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 14 Jan 2011 05:00:48 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 14 Jan 2011 11:00:36 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for the January 20, 2011 IESG Teleconference. Thread-Index: AcuzdLcSWZoHBRyXQSyYSDR7IV7PMAAXHzJA From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , , "YANG Doctors" Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for the January 20, 2011 IESG Teleconference. X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2011 09:59:01 -0000 Please find below the preliminary agenda of the 1/20 IESG telechat. Please send me your comments, questions and concerns about the documents and WG charters brought up for approval before 1/19 COB.=20 Thanks and Regards, Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary 2. Protocol Actions 2.1 WG Submissions 2.1.1 New Items o draft-ietf-mmusic-image-attributes-10 Negotiation of Generic Image Attributes in SDP (Proposed Standard) Note: Tom Taylor (tom111.taylor@bell.net) is the Document Shepherd. Token: Robert Sparks o draft-ietf-xmpp-3921bis-19 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence (Proposed Standard) Note: Joe Hildebrand (jhildebr@cisco.com) is the document shepherd. Token: Gonzalo Camarillo o draft-ietf-pwe3-oam-msg-map-14 Pseudowire (PW) OAM Message Mapping (Proposed Standard) Note: Andrew Malis, andrew.g.malis@verizon.com is the document shepherd. Token: Stewart Bryant Was deferred by Tim Polk on 2011-01-06 o draft-ietf-ltans-xmlers-10 Extensible Markup Language Evidence Record Syntax (Proposed Standard) Note: Carl Wallace is the document sheperd Token: Tim Polk o draft-ietf-sipcore-keep-11 Indication of support for keep-alive (Proposed Standard) Note: Adam Roach (adam@nostrum.com) is the document shepherd. Token: Robert Sparks o draft-ietf-martini-gin-12 Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP) (Proposed Standard) Note: Bernard Aboba (Bernard_Aboba@hotmail.com) is the document shepherd. Token: Gonzalo Camarillo o draft-ietf-multimob-pmipv6-base-solution-07 Base Deployment for Multicast Listener Support in PMIPv6 Domains (BCP) Note: Behcet Sarikaya (sarikaya@ieee.org) is the document shepherd. Token: Jari Arkko o draft-ietf-roll-routing-metrics-14 Routing Metrics used for Path Calculation in Low Power and Lossy Networks (Proposed Standard) Note: David Culler (culler@eecs.berkeley.edu) is the document shepherd. Token: Adrian Farrel o draft-ietf-6lowpan-hc-13 Compression Format for IPv6 Datagrams in 6LoWPAN Networks (Proposed Standard) Note: The Document Shepherd is 6LoWPAN WG co-chair Carsten Bormann(cabo@tzi.org). Token: Ralph Droms o draft-ietf-isis-layer2-09 Extensions to IS-IS for Layer-2 Systems (Proposed Standard) Note: David Ward (dward@juniper.net) is the document shepherd. Token: Stewart Bryant o draft-ietf-isis-trill-04 TRILL Use of IS-IS (Proposed Standard) Note: David Ward (dward@juniper.net) is the document shepherd. Token: Stewart Bryant o draft-ietf-ccamp-gmpls-g-694-lambda-labels-11 Generalized Labels for Lambda-Switching Capable Label Switching Routers (Proposed Standard) Note: Lou Berger (lberger@labn.net) is the document shepherd. Token: Adrian Farrel o draft-ietf-l3vpn-mvpn-infra-addrs-02 IPv4 and IPv6 Infrastructure Addresses in Multicast-VPN Routes (Proposed Standard) Note: Ben Niven-Jenkins (ben@niven-jenkins.co.uk) is the document shepherd. Token: Stewart Bryant 2.1.2 Returning Items o draft-ietf-tls-rfc4347-bis-04 Datagram Transport Layer Security version 1.2 (Proposed Standard) Note: Joe Salowey (jsalowey@cisco.com) is the document Shepherd. Token: Sean Turner 2.2 Individual Submissions 2.2.1 New Items o draft-saintandre-tls-server-id-check-14 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS) (BCP) Note: There is an open question on whether this document should be a BCP or PS. As the shepherding AD I don't have a strong opinion either way. Token: Alexey Melnikov o draft-schaad-smime-algorithm-attribute-04 Signer Info Algorithm Protection Attribute (Proposed Standard) Note: Jim Schaad (ietf@augustcellars.com) is the Document Shepherd. Token: Sean Turner 2.2.2 Returning Items NONE 3. Document Actions 3.1 WG Submissions 3.1.1 New Items o draft-ietf-sipcore-sec-flows-07 Example call flows using Session Initiation Protocol (SIP) security mechanisms (Informational) Note: Adam Roach (adam@nostrum.com) is the document shepherd. Token: Gonzalo Camarillo o draft-ietf-roll-security-framework-04 A Security Framework for Routing over Low Power and Lossy Networks (Informational) Note: JP Vasseur (jpv@cisco.com) is the document shepherd. Token: Adrian Farrel o draft-ietf-mpls-tp-uni-nni-03 MPLS Transport Profile User-to-Network and Network-to-Network Interfaces (Informational) Note: Loa Andersson (loa@pi.nu) is the Document Shepherd. Token: Adrian Farrel o draft-ietf-mptcp-threat-07 Threat Analysis for TCP Extensions for Multi-path Operation with Multiple Addresses (Informational) Note: Yoshifumi Nishida (nishida@sfc.wide.ad.jp) is the document shepherd. Token: Lars Eggert o draft-ietf-mptcp-architecture-04 Architectural Guidelines for Multipath TCP Development (Informational) Note: Philip Eardley (philip.eardley@bt.com) is the Document Shepherd. Token: Lars Eggert 3.1.2 Returning Items NONE 3.2 Individual Submissions Via AD 3.2.1 New Items o draft-merrick-jms-uri-10 URI Scheme for Java(tm) Message Service 1.0 (Informational) Token: Alexey Melnikov o draft-nsri-tls-aria-01 Addition of the ARIA Cipher Suites to Transport Layer Security (TLS) (Informational) Note: Woo-Hwan Kim (whkim5@ensec.re.kr) is the document shepherd Token: Sean Turner o draft-schaad-smime-hash-experiment-04 Experiment: Hash functions with parameters in CMS and S/MIME (Experimental) Note: Jim Schaad (ietf@augustcellars.com) is the document shepherd. Token: Sean Turner 3.2.2 Returning Items NONE 3.3 IRTF and Independent Submission Stream Documents 3.3.1 New Items o draft-zorn-radius-keywrap-18 Cisco Vendor Specific RADIUS Attributes for the Delivery of Keying Material (Informational) Token: Dan Romascanu Was deferred by Russ Housley on 2011-01-05 3.3.2 Returning Items NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o Light-Weight Implementation Guidance (lwig) Token: Jari 4.1.2 Proposed for Approval o Audio/Video Transport Payloads (payload) Token: Robert o Metric Blocks for use with RTCP's Extended Report Framework (xrblock) Token: Robert o Audio/Video Transport Core Maintenence (avtcore) Token: Robert o Audio/Video Transport Extensions (avtext) Token: Robert 4.2 WG Rechartering 4.2.1 Under Evaluation for IETF Review o Mobility EXTensions for IPv6 (mext) Token: Jari From dromasca@avaya.com Fri Jan 28 03:30:29 2011 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 589A83A67CC; Fri, 28 Jan 2011 03:30:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.571 X-Spam-Level: X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67a58iujSBhl; Fri, 28 Jan 2011 03:30:28 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id DE8643A67B3; Fri, 28 Jan 2011 03:30:18 -0800 (PST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAMM3Qk3GmAcF/2dsb2JhbAClAHOiMwKZJ4VPBJAG X-IronPort-AV: E=Sophos;i="4.60,391,1291611600"; d="scan'208";a="261969735" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 Jan 2011 06:33:24 -0500 X-IronPort-AV: E=Sophos;i="4.60,391,1291611600"; d="scan'208";a="575659080" Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 28 Jan 2011 06:33:23 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 28 Jan 2011 12:33:05 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for February 3, 2011 IESG Teleconference Thread-Index: Acu+drnSBo4jfz5dQ8ufF0ZijBRjjgAaBq9Q From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , , "YANG Doctors" Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for February 3, 2011 IESG Teleconference X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jan 2011 11:30:29 -0000 Please find below the preliminary agenda of the 2/3 IESG telechat. Please send me your comments, questions or concerns about the documents and charters brought up for approval before 2/2 COB.=20 Thanks and Regards, Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary 2. Protocol Actions 2.1 WG Submissions 2.1.1 New Items o draft-ietf-ltans-xmlers-11 Extensible Markup Language Evidence Record Syntax (Proposed Standard) Note: Carl Wallace is the document sheperd Token: Tim Polk Was deferred by Peter Saint-Andre on 2011-01-19 o draft-ietf-pmol-metrics-framework-07 Guidelines for Considering New Performance Metric Development (BCP) Note: Al Morton (acmorton@att.com) is the document shepherd. Token: Dan Romascanu 2.1.2 Returning Items NONE 2.2 Individual Submissions 2.2.1 New Items o draft-turner-additional-new-asn-06 Additional New ASN.1 Modules (Proposed Standard) Token: Tim Polk o draft-turner-cms-symmetrickeypackage-algs-00 Algorithms for Cryptographic Message Syntax (CMS)=20 Protection of Symmetric Key Package Content Types (Proposed Standard) Note: Sean Turner (turners@ieca.com) is the document Shepherd. Token: Tim Polk 2.2.2 Returning Items NONE 3. Document Actions 3.1 WG Submissions 3.1.1 New Items o draft-ietf-speermint-architecture-17 Session PEERing for Multimedia INTerconnect Architecture (Informational) Note: Document Shepherd: Jason Livingood (Jason_Livingood@cable.comcast.com) Token: Gonzalo Camarillo o draft-morton-ippm-rfc4148-obsolete-03 RFC 4148 and the IPPM Metrics Registry are Obsolete (Informational) Note: Document shepherd is Henk Uijterwaal (henk@ripe.net). Token: Lars Eggert 3.1.2 Returning Items o draft-ietf-nsis-tunnel-13 NSIS Operation Over IP Tunnels (Experimental) Note: The document shepherd is Jukka Manner (jukka.manner@tkk.fi). Token: Lars Eggert 3.2 Individual Submissions Via AD 3.2.1 New Items o draft-groves-eccsi-00 Elliptic Curve-based Certificate-less Signatures for Identifier Based Encryption (ECCSI) (Informational) Token: Tim Polk o draft-groves-mikey-sakke-00 MIKEY-SAKKE: Sakai-Kasahara Key Exchange in Multimedia Internet KEYing (MIKEY) (Informational) Token: Tim Polk o draft-groves-sakke-00 Sakai-Kasahara Key Establishment (SAKKE) (Informational) Token: Tim Polk o draft-turner-sha0-sha1-seccon-03 Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms (Informational) Note: Sean Turner (turners@ieca.com) is the document Shepherd. Token: Peter Saint-Andre 3.2.2 Returning Items NONE 3.3 IRTF and Independent Submission Stream Documents 3.3.1 New Items NONE 3.3.2 Returning Items NONE 3.3.3 For Action o draft-irtf-rrg-design-goals-06 Design Goals for Scalable Internet Routing (Informational) Note: Independent submission via IRTF. Joel Halpern (jmh@joelhalpern.com) is the document shepherd. Token: Jari Arkko o draft-irtf-dtnrg-sdnv-08 Using Self-Delimiting Numeric Values in Protocols (Informational) Note: IRTF Submission. Elwyn Davies (elwynd@dial.pipex.com) is the document shepherd. Token: Russ Housley o draft-irtf-dtnrg-bundle-security-17 Bundle Security Protocol Specification (Experimental) Note: IRTF submission. Elwyn Davies (elwynd@dial.pipex.com) is the document shepherd. Token: Russ Housley o draft-irtf-dtnrg-cbhe-08 Compressed Bundle Header Encoding (CBHE) (Experimental) Note: IRTF submission. Elwyn Davies (elwynd@dial.pipex.com) is the document shepherd. Token: Russ Housley o draft-irtf-dtnrg-bundle-metadata-block-09 Delay-Tolerant Networking Metadata Extension Block (Experimental) Note: IRTF submission. Elwyn Davies (elwynd@dial.pipex.com) is the document shepherd. Token: Russ Housley o draft-irtf-dtnrg-bundle-previous-hop-block-12 Delay-Tolerant Networking Previous Hop Insertion Block (Experimental) Note: IRTF submission. Elwyn Davies (elwynd@dial.pipex.com) is the document shepherd. Token: Russ Housley o draft-irtf-dtnrg-iana-bp-registries-01 Delay-Tolerant Networks (DTN) Bundle Protocol IANA Registries (Informational) Note: IRTF submission. Elwyn Davies (elwynd@dial.pipex.com) is the document shepherd. 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 Light-Weight Implementation Guidance (lwig) Token: Jari