[AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for August 13, 2009 Telechat

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Fri, 07 August 2009 09:37 UTC

Return-Path: <dromasca@avaya.com>
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 91F3D28C0EC; Fri, 7 Aug 2009 02:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level:
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[AWL=0.188, 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 tgFa0gGi46ZT; Fri, 7 Aug 2009 02:37:22 -0700 (PDT)
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 60C8E28C147; Fri, 7 Aug 2009 02:37:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.43,341,1246852800"; d="scan'208";a="179319332"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Aug 2009 05:37:25 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 07 Aug 2009 05:37:24 -0400
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, 07 Aug 2009 11:37:13 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0401909C1C@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: PRELIMINARY Agenda and Package for August 13, 2009 Telechat
thread-index: AcoW5p+XfxQA88oGQnq1/FMZJbkC9AAW4gaA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: dns-dir@ietf.org, ops-ads@tools.ietf.org, aaa-doctors@ietf.org, mib-doctors@ietf.org
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for August 13, 2009 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/mail-archive/web/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>
X-List-Received-Date: Fri, 07 Aug 2009 09:37:23 -0000

 Please find below the preliminary agenda of the 8/13 IESG telechat.
Please send your comments, questions, and concerns before 8/12 COB. 

Thanks and Regards,

Dan



2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-rmt-bb-lct-revised-10.txt
    Layered Coding Transport (LCT) Building Block (Proposed Standard) -
1
of 12 
    Token: Magnus Westerlund
  o draft-ietf-sieve-mime-loop-09.txt
    Sieve Email Filtering: MIME part Tests, Iteration, Extraction,
Replacement 
    and Enclosure (Proposed Standard) - 2 of 12 
    Note: Alexey Melnikov <alexey.melnikov@isode.com> is the
document 
    shepherd for this document. 
    Token: Lisa Dusseault
  o draft-ietf-mpls-ldp-end-of-lib-03.txt
    LDP End-of-LIB (Proposed Standard) - 3 of 12 
    Note: Proto write-up has been revised. Make sure to use new version.

    Token: Adrian Farrel
  o draft-ietf-netconf-partial-lock-09.txt
    Partial Lock RPC for NETCONF (Proposed Standard) - 4 of 12 
    Token: Dan Romascanu
  o draft-ietf-nea-pa-tnc-04.txt
    PA-TNC: A Posture Attribute Protocol (PA) Compatible with TNC
(Proposed 
    Standard) - 5 of 12 
    Token: Tim Polk
  o draft-ietf-nea-pb-tnc-04.txt
    PB-TNC: A Posture Broker Protocol (PB) Compatible with TNC (Proposed

    Standard) - 6 of 12 
    Token: Tim Polk
  o draft-ietf-dime-diameter-qos-11.txt
    Diameter Quality of Service Application (Proposed Standard) - 7 of
12

    Note: Victor Fajardo [vfajardo@tari.toshiba.com] is the document
shepherd 
    for this document. 
    Token: Dan Romascanu
  o draft-ietf-opsawg-syslog-snmp-04.txt
    Mapping Simple Network Management Protocol (SNMP) Notifications to
SYSLOG 
    Messages (Proposed Standard) - 8 of 12 
    Note: Scott Bradner (sob@harvard.edu) is the document shepherd. 
    Token: Dan Romascanu
  o draft-ietf-opsawg-syslog-msg-mib-05.txt
    Definitions of Managed Objects for Mapping SYSLOG Messages to Simple

    Network Management Protocol (SNMP) Notifications (Proposed Standard)
-
9 of 
    12 
    Note: Scott Bradner (sob@harvard.edu) is the document shepherd. 
    Token: Dan Romascanu
  o draft-ietf-l3vpn-as4octet-ext-community-03.txt
    Four-octet AS Specific BGP Extended Community (Proposed Standard) -
10
of 
    12 
    Token: Ross Callon
  o draft-ietf-mpls-tp-requirements-09.txt
    MPLS-TP Requirements (Proposed Standard) - 11 of 12 
    Note: Loa Andersson (loa@pi.nu) is the document shepherd. 
    Token: Adrian Farrel
  o draft-ietf-l3vpn-v6-ext-communities-02.txt
    IPv6 Address Specific BGP Extended Communities Attribute (Proposed 
    Standard) - 12 of 12 
    Token: Ross Callon

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-iana-rfc3330bis-07.txt
    Special Use IPv4 Addresses (BCP) - 1 of 2 
    Token: Russ Housley
  o draft-freed-sieve-in-xml-05.txt
    Sieve Email Filtering: Sieves and display directives in XML
(Proposed

    Standard) - 2 of 2 
    Note: Cyrus Daboo <cyrus@daboo.name> is the document shepherd.
This 
    is a Sieve WG document, despite the name.. 
    Token: Lisa Dusseault

2.2.2 Returning Item
  o draft-housley-iesg-rfc3932bis-07.txt
    IESG Procedures for Handling of Independent and IRTF Stream
Submissions 
    (BCP) - 1 of 2 
    Note: There is no document shepherd 
    Token: Jari Arkko
  o draft-dusseault-impl-reports-04.txt
    Guidance on Interoperation and Implementation Reports for
Advancement
to 
    Draft Standard (BCP) - 2 of 2 
    Token: Tim Polk


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-nat-behavior-discovery-07.txt
    NAT Behavior Discovery Using STUN (Experimental) - 1 of 3 
    Token: Magnus Westerlund
  o draft-ietf-ipfix-export-per-sctp-stream-03.txt
    IPFIX Export per SCTP Stream (Informational) - 2 of 3 
    Token: Dan Romascanu
  o draft-ietf-pwe3-mpls-transport-04.txt
    Application of Ethernet Pseudowires to MPLS Transport Networks 
    (Informational) - 3 of 3 
    Note: Matthew Bocci (matthew.bocci@alcatel-lucent.com) is the
document
 
    shepherd 
    Token: Ralph Droms

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-iana-special-ipv4-registry-01.txt
    IANA IPv4 Special Purpose Address Registry (Informational) - 1 of 1 
    Token: Russ Housley

3.2.2 Returning Item
  o draft-housley-tls-authz-extns-07.txt
    Transport Layer Security (TLS) Authorization Extensions
(Experimental)
- 1 
    of 1 
    Token: Tim Polk

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
    NONE
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Mobility for IPv4 (mip4) - 1 of 1
    Token: Jari Arkko