[MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for March 12, 2009 Telechat
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 06 March 2009 07:23 UTC
Return-Path: <dromasca@avaya.com>
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 20C0F3A68A4; Thu, 5 Mar 2009 23:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 FxohhMJsu3YP; Thu, 5 Mar 2009 23:23:10 -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 E2C723A67E4; Thu, 5 Mar 2009 23:23:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.38,313,1233550800"; d="scan'208";a="163743746"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 06 Mar 2009 02:23:39 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 06 Mar 2009 02:23:38 -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, 06 Mar 2009 08:23:29 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A040149440B@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PRELIMINARY Agenda and Package for March 12, 2009 Telechat
Thread-Index: Acmd8mGTQWWyMd/1QJmsvKzvIy+zuwAOajcg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: aaa-doctors@ietf.org, "MIB Doctors (E-mail)" <mib-doctors@ietf.org>, ops-dir@ietf.org, IETF DNS Directorate <dns-dir@ietf.org>
Subject: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for March 12, 2009 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/mail-archive/web/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>
X-List-Received-Date: Fri, 06 Mar 2009 07:23:11 -0000
Please find below the preliminary agenda of the 3/12 IESG telechat. Please send me you comments and concerns before 3/11 COB. 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-behave-turn-13.txt Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) (Proposed Standard) - 1 of 9 Token: Magnus Westerlund o draft-ietf-avt-rtp-uemclip-04.txt RTP payload format for mU-law EMbedded Codec for Low-delay IP communication (UEMCLIP) speech codec (Proposed Standard) - 2 of 9 Note: The document shepherd is Roni Even. Token: Cullen Jennings o draft-ietf-btns-connection-latching-08.txt IPsec Channels: Connection Latching (Proposed Standard) - 3 of 9 Token: Tim Polk o draft-ietf-softwire-security-requirements-06.txt Softwire Security Analysis and Requirements (Proposed Standard) - 4 of 9 Token: Mark Townsley o draft-ietf-netconf-tls-07.txt NETCONF Over Transport Layer Security (TLS) (Proposed Standard) - 5 of 9 Note: Mehmet Ersue is the PROTO-shepherd Token: Dan Romascanu o draft-ietf-ntp-ntpv4-proto-11.txt Network Time Protocol Version 4 Protocol And Algorithms Specification (Proposed Standard) - 6 of 9 Token: Mark Townsley o draft-ietf-ntp-ntpv4-mib-05.txt Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4) (Proposed Standard) - 7 of 9 Token: Mark Townsley o draft-ietf-lemonade-profile-bis-12.txt The Lemonade Profile (Proposed Standard) - 8 of 9 Note: Glenn Parsons is the Document Shepherd Token: Chris Newman o draft-ietf-netlmm-pmipv6-heartbeat-05.txt Heartbeat Mechanism for Proxy Mobile IPv6 (Proposed Standard) - 9 of 9 Token: Jari Arkko 2.1.2 Returning Item o draft-ietf-usefor-usepro-14.txt Netnews Architecture and Protocols (Proposed Standard) - 1 of 1 Token: Lisa Dusseault 2.2 Individual Submissions 2.2.1 New Item o draft-farrel-rtg-common-bnf-08.txt Reduced Backus-Naur Form (RBNF) A Syntax Used in Various Protocol Specifications (Proposed Standard) - 1 of 2 Token: Ross Callon o draft-gulbrandsen-imap-response-codes-07.txt IMAP Response Codes (Proposed Standard) - 2 of 2 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 NONE 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-jones-dime-3gpp-eps-command-codes-01.txt Diameter Command Code Registration for Third Generation Partnership Project (3GPP) Evolved Packet System (EPS) (Informational) - 1 of 1 Note: IETF LC ends on 3/5. A new revised I-D will be available immediatly after the Last Call. Token: Dan Romascanu 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 o Locator/ID Separation Protocol (lisp) - 1 of 3 Token: Jari Arkko o Session Initiation Protocol Core (sipcore) - 2 of 3 Token: Cullen Jennings o Dispatch (dispatch) - 3 of 3 Token: Cullen Jennings 4.1.2 Proposed for Approval NONE 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval o Network File System Version 4 (nfsv4) - 1 of 3 Token: Lars Eggert o Ad-Hoc Network Autoconfiguration (autoconf) - 2 of 3 Token: Jari Arkko o Routing Over Low power and Lossy networks (roll) - 3 of 3 Token: David Ward
- [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package … Romascanu, Dan (Dan)