[AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for September 25, 2008 Telechat
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 19 September 2008 14:28 UTC
Return-Path: <aaa-doctors-bounces@ietf.org>
X-Original-To: aaa-doctors-archive@optimus.ietf.org
Delivered-To: ietfarch-aaa-doctors-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7694B28C137; Fri, 19 Sep 2008 07:28:42 -0700 (PDT)
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 5CBF03A68A9; Fri, 19 Sep 2008 07:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.422
X-Spam-Level:
X-Spam-Status: No, score=-2.422 tagged_above=-999 required=5 tests=[AWL=0.177, 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 3dWc8ln1qZh4; Fri, 19 Sep 2008 07:28:36 -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 A9F7A3A69BD; Fri, 19 Sep 2008 07:28:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.32,429,1217822400"; d="scan'208";a="122288750"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 19 Sep 2008 10:28:48 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.10]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 19 Sep 2008 10:28:47 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 19 Sep 2008 16:28:36 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04FA24F3@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PRELIMINARY Agenda and Package for September 25, 2008 Telechat
Thread-Index: AckZ4G9r71fP/5rKSFaYntjbkGPlaAAgz3KA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: ops-dir@ietf.org, IETF DNS Directorate <dns-dir@ietf.org>, aaa-doctors@ietf.org, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for September 25, 2008 Telechat
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: aaa-doctors-bounces@ietf.org
Errors-To: aaa-doctors-bounces@ietf.org
Please find below the preliminary agenda of the 9/25 IESG telechat. Please review all relevant documents and send me your questions, comments and concerns until 9/24 COB the latest. Thanks and Regards, 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-forces-model-15.txt ForCES Forwarding Element Model (Proposed Standard) - 1 of 7 Token: Ross Callon o draft-ietf-capwap-protocol-specification-12.txt CAPWAP Protocol Specification (Proposed Standard) - 2 of 7 Token: Dan Romascanu o draft-ietf-capwap-dhc-ac-option-01.txt CAPWAP Access Controller DHCP Option (Proposed Standard) - 3 of 7 Token: Dan Romascanu o draft-ietf-ccamp-isis-interas-te-extension-04.txt ISIS Extensions in Support of Inter-AS Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (Proposed Standard) - 4 of 7 Token: Ross Callon o draft-ietf-nfsv4-rpcsec-gss-v2-05.txt RPCSEC_GSS Version 2 (Proposed Standard) - 5 of 7 Note: Document Shepherd: Spencer Shepler (spencer.shepler@gmail.com). Token: Lars Eggert o draft-ietf-mipshop-mstp-solution-06.txt Mobility Services Framework Design (MSFD) (Proposed Standard) - 6 of 7 Token: Jari Arkko o draft-ietf-capwap-protocol-binding-ieee80211-08.txt CAPWAP Protocol Binding for IEEE 802.11 (Proposed Standard) - 7 of 7 Token: Dan Romascanu 2.1.2 Returning Item o draft-ietf-manet-packetbb-15.txt Generalized MANET Packet/Message Format (Proposed Standard) - 1 of 2 Token: Ross Callon o draft-ietf-manet-timetlv-07.txt Representing multi-value time in MANETs (Proposed Standard) - 2 of 2 Token: Ross Callon 2.2 Individual Submissions 2.2.1 New Item o draft-sanchez-webdav-current-principal-01.txt WebDAV Current Principal Extension (Proposed Standard) - 1 of 1 Token: Lisa Dusseault 2.2.2 Returning Item o draft-wilde-sms-uri-16.txt URI Scheme for GSM Short Message Service (Proposed Standard) - 1 of 1 Token: Lisa Dusseault 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-capwap-threat-analysis-04.txt CAPWAP Threat Analysis for IEEE 802.11 Deployments (Informational) - 1 of 1 Token: Dan Romascanu 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item NONE 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG <X>, but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG <X> and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for <X> and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. _______________________________________________ AAA-DOCTORS mailing list AAA-DOCTORS@ietf.org https://www.ietf.org/mailman/listinfo/aaa-doctors
- [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package … Romascanu, Dan (Dan)