[MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for November 6, 2008 Telechat
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 31 October 2008 05:28 UTC
Return-Path: <mib-doctors-bounces@ietf.org>
X-Original-To: mib-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-mib-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA8413A6BC7; Thu, 30 Oct 2008 22:28:51 -0700 (PDT)
X-Original-To: mib-doctors@core3.amsl.com
Delivered-To: mib-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00B033A6BB8; Thu, 30 Oct 2008 22:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.687
X-Spam-Level:
X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[AWL=-0.088, 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 s7vYMeKkiBai; Thu, 30 Oct 2008 22:28:48 -0700 (PDT)
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 BE3373A6A82; Thu, 30 Oct 2008 22:28:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.33,520,1220241600"; d="scan'208";a="126826954"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 31 Oct 2008 01:28:44 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 31 Oct 2008 01:28:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Oct 2008 06:28:40 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040109AF12@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PRELIMINARY Agenda and Package for November 6, 2008 Telechat
Thread-Index: Ack639An4xl609dSTZymshi/N1BJjwAOSFUg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, aaa-doctors@ietf.org, IETF DNS Directorate <dns-dir@ietf.org>, ops-dir@ietf.org
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for November 6, 2008 Telechat
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mib-doctors-bounces@ietf.org
Errors-To: mib-doctors-bounces@ietf.org
Please find below the preliminary agenda of the IESG 11/6 telechat. Please send your comments and concerns related to the documents submitted for approval until 11/5 COB the latest. Thanks and Regards, Dan 2. Protocol Actions Reviews should focus on these questions: "Is this document a reasonable basis on which to build the salient part of the Internet infrastructure? If not, what changes would make it so?" 2.1 WG Submissions 2.1.1 New Item o draft-ietf-emu-eap-gpsk-16.txt EAP Generalized Pre-Shared Key (EAP-GPSK) Method (Proposed Standard) - 1 of 7 Note: document shepherd: Joe Salowey <jsalowey@cisco.com> Token: Pasi Eronen o draft-ietf-sip-sips-08.txt The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) (Proposed Standard) - 2 of 7 Note: The proto Shepherd for this document is Dean Willis. Token: Cullen Jennings o draft-ietf-psamp-info-11.txt Information Model for Packet Sampling Exports (Proposed Standard) - 3 of 7 Note: Juergen Quittek is the PROTO shepherd Token: Dan Romascanu o draft-ietf-avt-dtls-srtp-06.txt Datagram Transport Layer Security (DTLS) Extension to Establish Keys for Secure Real-time Transport Protocol (SRTP) (Proposed Standard) - 4 of 7 Note: The document shepherd is Roni Even. Token: Cullen Jennings o draft-ietf-behave-dccp-04.txt Network Address Translation (NAT) Behavioral Requirements for the Datagram Congestion Control Protocol (BCP) - 5 of 7 Token: Magnus Westerlund o draft-ietf-sip-dtls-srtp-framework-05.txt Framework for Establishing an SRTP Security Context using DTLS (Proposed Standard) - 6 of 7 Note: Last Call ends Oct 31. Dean Willis will act as the proto shepherd. Token: Cullen Jennings o draft-ietf-vrrp-unified-spec-02.txt Virtual Router Redundancy Protocol Version 3 for IPv4 and IPv6 (Proposed Standard) - 7 of 7 Token: David Ward 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item o draft-ietf-behave-stun-test-vectors-03.txt Test vectors for STUN (Informational) - 1 of 2 Token: Magnus Westerlund o draft-ietf-idr-as-documentation-reservation-00.txt AS Number Reservation for Documentation Use (Informational) - 2 of 2 Token: David Ward 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item o draft-narten-successful-bof-03.txt Considerations for Having a Successful BOF (Informational) - 1 of 2 Token: Russ Housley o draft-rescorla-tls-suiteb-09.txt Suite B Profile for Transport Layer Security (TLS) (Informational) - 2 of 2 Token: Tim Polk 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG <X>, but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG <X> and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for <X> and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item NONE 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval o Application-Layer Traffic Optimization (alto) - 1 of 2 Token: Lisa Dusseault o Low Extra Delay Background Transport (ledbat) - 2 of 2 Token: Lars Eggert 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2 Token: Magnus Westerlund o Mobility for IP: Performance, Signaling and Handoff Optimization (mipshop) - 2 of 2 Token: Jari Arkko _______________________________________________ MIB-DOCTORS mailing list MIB-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/mib-doctors
- [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package … Romascanu, Dan (Dan)