[AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for December 11, 2008 Telechat

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 05 December 2008 06:08 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 873193A6BCD; Thu, 4 Dec 2008 22:08:13 -0800 (PST)
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 00DF83A688D; Thu, 4 Dec 2008 22:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level:
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125, 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 feXuW6MBWsiv; Thu, 4 Dec 2008 22:08:09 -0800 (PST)
Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 90D693A67EA; Thu, 4 Dec 2008 22:08:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,719,1220241600"; d="scan'208";a="153432855"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 05 Dec 2008 01:08:04 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Dec 2008 01:08:04 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 05 Dec 2008 07:08:02 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04011C0C89@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PRELIMINARY Agenda and Package for December 11, 2008 Telechat
Thread-Index: AclWZNMz+vC5C9RGSCKYt3mXp/6SigAOoLqA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, aaa-doctors@ietf.org, ops-dir@ietf.org, DNS Directorate <dns-dir@ietf.org>
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for December 11, 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 o the IESG telechat on 12/11.
The IESG will hold three telechats in three consecutive weeks in
December, to share load and expedite the review process. Please review
and comment on the relevant documents until 12/10 COB the latest. 

Thanks and Regards,

Dan


-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of
IESG Secretary


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-rmt-bb-fec-basic-schemes-revised-06.txt
    Basic Forward Error Correction (FEC) Schemes (Proposed Standard) - 1
of 11 
    Token: Magnus Westerlund
  o draft-ietf-nfsv4-rfc1831bis-10.txt
    RPC: Remote Procedure Call Protocol Specification Version 2 (Draft 
    Standard) - 2 of 11 
    Note: Document Shepherd: Spencer Shepler (spencer.shepler@gmail.com)

    Token: Lars Eggert
  o draft-ietf-avt-smpte-rtp-14.txt
    Associating Time-codes with RTP streams (Proposed Standard) - 3 of
11

    Note: Tom Taylor is the PROTO Shepherd 
    Token: Cullen Jennings
  o draft-melnikov-imapext-filters-07.txt
    IMAP4 extension for named searches (filters) (Proposed Standard) - 4
of 11 
    Note: Dave Cridland is document shepherd. 
    Token: Chris Newman
  o draft-ietf-isis-hmac-sha-07.txt
    IS-IS Generic Cryptographic Authentication (Proposed Standard) - 5
of
11 
    Token: Ross Callon
  o draft-ietf-smime-sha2-09.txt
    Using SHA2 Algorithms with Cryptographic Message Syntax (Proposed
Standard) 
    - 6 of 11 
    Token: Tim Polk
  o draft-ietf-pce-path-key-05.txt
    Preserving Topology Confidentiality in Inter-Domain Path Computation
Using 
    a Key-Based Mechanism (Proposed Standard) - 7 of 11 
    Token: Ross Callon
  o draft-ietf-mext-nemo-v4traversal-06.txt
    Mobile IPv6 Support for Dual Stack Hosts and Routers (Proposed
Standard) - 
    8 of 11 
    Token: Jari Arkko
  o draft-ietf-tcpm-rfc4138bis-04.txt
    Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious 
    Retransmission Timeouts with TCP (Proposed Standard) - 9 of 11 
    Note: Wesley Eddy (wesley.m.eddy@nasa.gov) (TCPM co-chair) is the
shepherd. 
    Token: Lars Eggert
  o draft-ietf-dhc-dhcpv6-bulk-leasequery-05.txt
    DHCPv6 Bulk Leasequery (Proposed Standard) - 10 of 11 
    Token: Jari Arkko
  o draft-ietf-avt-rtp-g719-04.txt
    RTP Payload format for G.719 (Proposed Standard) - 11 of 11 
    Token: Cullen Jennings

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-daboo-imap-annotatemore-16.txt
    IMAP METADATA Extension (Proposed Standard) - 1 of 1 
    Note: Alexey Melnikov is document shepherd. 
    Token: Chris Newman

2.2.2 Returning Item
NONE

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a
reasonable
	contribution to the area of Internet engineering which it
covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-lemonade-architecture-04.txt
    LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile
Email 
    (MEM) using Internet Mail (Informational) - 1 of 3 
    Note: Alexey Melnikov is document shepherd. 
    Token: Chris Newman
  o draft-ietf-mpls-te-scaling-analysis-04.txt
    An Analysis of Scaling Issues in MPLS-TE Core Networks
(Informational)
- 2 
    of 3 
    Token: Ross Callon
  o draft-ietf-pim-rpf-vector-06.txt
    The RPF Vector TLV (Informational) - 3 of 3 
    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-jerichow-msec-mikey-genext-oma-00.txt
    MIKEY General Extension Payload for OMA BCAST 1.0 (Informational) -
1
of 3 
    Token: Tim Polk
  o draft-housley-internet-draft-sig-file-06.txt
    Digital Signatures on Internet-Draft Documents (Informational) - 2
of
3 
    Token: Tim Polk
  o draft-igoe-secsh-aes-gcm-00.txt
    AES Galois Counter Mode for the Secure Shell Transport Layer
Protocol

    (Informational) - 3 of 3 
    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
  o draft-irtf-asrg-dnsbl-08.txt
    DNS Blacklists and Whitelists (Informational) - 1 of 1 
    Note: Propose to respond "1. The IESG has not found any conflict
between 
    this document and IETF work." 
    Token: Lisa Dusseault



_______________________________________________
AAA-DOCTORS mailing list
AAA-DOCTORS@ietf.org
https://www.ietf.org/mailman/listinfo/aaa-doctors