From aaa-doctors-bounces@ietf.org Fri Nov 09 03:16:07 2007
Return-path: <aaa-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IqP26-0002ZH-Ks; Fri, 09 Nov 2007 03:16:06 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IqP1u-0002RZ-96; Fri, 09 Nov 2007 03:15:54 -0500
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IqP1t-0000o7-Fn; Fri, 09 Nov 2007 03:15:54 -0500
X-IronPort-AV: E=Sophos;i="4.21,394,1188792000"; d="scan'208";a="82069901"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5])
	by co300216-co-outbound.avaya.com with ESMTP; 09 Nov 2007 03:15:52 -0500
X-IronPort-AV: E=Sophos;i="4.21,394,1188792000"; d="scan'208";a="129298951"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	09 Nov 2007 03:15:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 9 Nov 2007 09:14:29 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A045E45A6@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for November 15, 2007 Telechat 
Thread-Index: AcgidQE3nBUgA58iToyGdeXNvUArqAAMp0zw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	<dns-dir@ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21be852dc93f0971708678c18d38c096
Cc: 
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for November 15,
	2007 Telechat 
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/aaa-doctors>,
	<mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.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://www1.ietf.org/mailman/listinfo/aaa-doctors>,
	<mailto:aaa-doctors-request@ietf.org?subject=subscribe>
Errors-To: aaa-doctors-bounces@ietf.org

Please find below the preliminary agenda of the 11/15 IESG telechat. =
Please let me know if there are any concerns or questions related to the =
documents that are being brought for IESG approval until 11/14 COB the =
latest.=20

Dan


2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-xcon-framework-09.txt
    A Framework for Centralized Conferencing (Proposed Standard) - 1 of =
6

    Note: Adam Roach is proto shepherd=20
    Token: Cullen Jennings
  o draft-ietf-simple-prescaps-ext-08.txt
    Session Initiation Protocol (SIP) User Agent Capability Extension to =

    Presence Information Data Format (PIDF) (Proposed Standard) - 2 of 6 =

    Token: Jon Peterson
  o draft-ietf-behave-nat-icmp-06.txt
    NAT Behavioral Requirements for ICMP protocol (BCP) - 3 of 6=20
    Token: Magnus Westerlund
  o draft-ietf-tsvwg-ecn-mpls-02.txt
    Explicit Congestion Marking in MPLS (Proposed Standard) - 4 of 6=20
    Note: Lars Eggert (lars.eggert@nokia.com) is document shepherd.=20
    Token: Lars Eggert
  o draft-ietf-sigtran-rfc4233update-02.txt
    TEI Query Request Number Change (Proposed Standard) - 5 of 6=20
    Token: Jon Peterson
  o draft-ietf-mipshop-handover-key-03.txt
    Distributing a Symmetric FMIPv6 Handover Key using SEND (Proposed
Standard)=20
    - 6 of 6=20
    Note: Document Shepherd is Vijay Devarapalli=20
    Token: Jari Arkko

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-garcia-simple-presence-dictionary-06.txt
    The Presence-Specific Static Dictionary for Signaling Compression
(Sigcomp)=20
    (Proposed Standard) - 1 of 1=20
    Token: Jon Peterson

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-nfsv4-nfs-rdma-problem-statement-07.txt
    NFS RDMA Problem Statement (Informational) - 1 of 5=20
    Note: Document Shepherd: Spencer Shepler (spencer.shepler@sun.com)=20
    Token: Lars Eggert
  o draft-ietf-sipping-ipv6-torture-tests-04.txt
    Session Initiation Protocol (SIP) Torture Test Messages for Internet =

    Protocol Version 6 (IPv6) (Informational) - 2 of 5=20
    Token: Jon Peterson
  o draft-ietf-eap-netsel-problem-08.txt
    Network Discovery and Selection Problem (Informational) - 3 of 5=20
    Token: Mark Townsley
  o draft-ietf-behave-p2p-state-05.txt
    State of Peer-to-Peer(P2P) Communication Across Network Address=20
    Translators(NATs) (Informational) - 4 of 5=20
    Token: Magnus Westerlund
  o draft-ietf-smime-cades-06.txt
    CMS Advanced Electronic Signatures (CAdES) (Informational) - 5 of 5=20
    Token: Tim Polk

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
  o draft-mealling-epc-urn-02.txt
    A Uniform Resource Name Namespace For The EPCglobal Electronic =
Product
Code=20
    (EPC) and Related Standards (Informational) - 1 of 2=20
    Token: Lisa Dusseault
  o draft-lepinski-dh-groups-03.txt
    Additional Diffie-Hellman Groups for use with IETF Standards=20
    (Informational) - 2 of 2=20
    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 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
  o draft-irtf-tmrg-metrics-11.txt
    Metrics for the Evaluation of Congestion Control Mechanisms
(Informational)=20
    - 1 of 1=20
    Note: To be published according to draft-irtf-rfcs-01.txt Based on =
the
=20
    Working Group Summary, I believe that the. second variant suggested =
in
=20
    Appendix A of draft-irtf-rfcs-0. is appropriate for this document:
"This=20
    document in not an IETF Internet Standard.=A0 It represents. the=20
    individual opinion(s) of one or more members of the TMRG. Research
Group of=20
    the Internet Research Task Force. It may be. considered for
standardization=20
    by the IETF or adoption as a. IRTF Research Group consensus document
in the=20
    future."=20
    Token: Lars Eggert


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 IP Flow Information Export (ipfix) - 1 of 2
    Token: Dan Romascanu
  o Network Configuration (netconf) - 2 of 2
    Token: Dan Romascanu


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



From aaa-doctors-bounces@ietf.org Mon Nov 26 08:04:03 2007
Return-path: <aaa-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iwdd4-0000lA-Ve; Mon, 26 Nov 2007 08:04:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iwdcw-0000jP-GG; Mon, 26 Nov 2007 08:03:54 -0500
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iwdcq-0005Ct-Qr; Mon, 26 Nov 2007 08:03:54 -0500
X-IronPort-AV: E=Sophos;i="4.21,467,1188792000"; d="scan'208";a="81341171"
Received: from 5.7.8.135.in-addr.arpa (HELO co300216-co-erhwest.avaya.com)
	([198.152.7.5])
	by nj300815-nj-outbound.avaya.com with ESMTP; 26 Nov 2007 08:03:46 -0500
X-IronPort-AV: E=Sophos;i="4.21,467,1188792000"; d="scan'208";a="134045781"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-erhwest-out.avaya.com with ESMTP;
	26 Nov 2007 08:03:47 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 26 Nov 2007 14:03:34 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A04683528@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PRELIMINARY Agenda and Package for November 29, 2007 Telechat 
Thread-Index: AcgtiK/HlQFahEqWQmazuRv1Cy7UAgCowbWQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	<dns-dir@ops.ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Cc: 
Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for November 29,
	2007 Telechat 
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/aaa-doctors>,
	<mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.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://www1.ietf.org/mailman/listinfo/aaa-doctors>,
	<mailto:aaa-doctors-request@ietf.org?subject=subscribe>
Errors-To: aaa-doctors-bounces@ietf.org

Sorry for the delay, but I was out of the network for the weekend.=20

Please find below the preliminary agenda of the 11/29 IESG telechat. =
Please let me know about any issues and comments until 11/28 COB the =
latest.=20

Thanks and Regards,

Dan
=20


=20

-----Original Message-----
From: IESG Secretary [mailto:iesg-secretary@ietf.org]=20

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-rfc3489bis-13.txt
    Session Traversal Utilities for (NAT) (STUN) (Proposed Standard) - 1
of 9=20
    Token: Magnus Westerlund
  o draft-ietf-geopriv-revised-civic-lo-06.txt
    Revised Civic Location Format for PIDF-LO (Proposed Standard) - 2 of =
9
=20
    Note: Robert is proto shepherd=20
    Token: Cullen Jennings
  o draft-ietf-rmt-bb-fec-ldpc-07.txt
    Low Density Parity Check (LDPC) Staircase and Triangle Forward Error =

    Correction (FEC) Schemes (Proposed Standard) - 3 of 9=20
    Token: Magnus Westerlund
  o draft-ietf-rmt-bb-fec-rs-05.txt
    Reed-Solomon Forward Error Correction (FEC) Schemes (Proposed
Standard) - 4=20
    of 9=20
    Token: Magnus Westerlund
  o draft-ietf-smime-bfibecms-08.txt
    Using the Boneh-Franklin and Boneh-Boyen identity-based encryption=20
    algorithms with the Cryptographic Message Syntax (CMS) (Proposed
Standard)=20
    - 5 of 9=20
    Token: Tim Polk
  o draft-ietf-smime-ibearch-06.txt
    Identity-based Encryption Architecture (Proposed Standard) - 6 of 9=20
    Token: Tim Polk
  o draft-ietf-avt-rfc3119bis-05.txt
    A More Loss-Tolerant RTP Payload Format for MP3 Audio (Proposed
Standard) -=20
    7 of 9=20
    Note: Colin Perkins is the document shepherd.=20
    Token: Cullen Jennings
  o draft-ietf-avt-rfc2833biscas-05.txt
    Definition of Events For Channel-Oriented Telephony Signalling
(Proposed=20
    Standard) - 8 of 9=20
    Note: Proto shepherd is Roni Even=20
    Token: Cullen Jennings
  o draft-ietf-mip4-vpn-problem-solution-03.txt
    Mobile IPv4 Traversal Across IPsec-based VPN Gateways (BCP) - 9 of 9 =

    Note: Document Shepherd is Henrik Levkowetz=20
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-mip4-mobike-connectivity-03.txt
    Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE (BCP) =
-
1 of=20
    1=20
    Note: Document Shepherd is <pete.mccann@motorola.com>=20
    Token: Jari Arkko


2.2 Individual Submissions
2.2.1 New Item
  o draft-klensin-unicode-escapes-07.txt
    ASCII Escaping of Unicode Characters (BCP) - 1 of 1=20
    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-manet-jitter-03.txt
    Jitter considerations in Mobile Ad Hoc Networks (MANETs)
(Informational) -=20
    1 of 1=20
    Token: Ross Callon

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-korhonen-mip6-service-05.txt
    Service Selection for Mobile IPv6 (Informational) - 1 of 2=20
    Note: No document shepherd=20
    Token: Jari Arkko
  o draft-irtf-mobopts-l2-abstractions-04.txt
    Unified L2 Abstractions for L3-Driven Fast Handover (Experimental) - =
2
of 2=20
    Note: This is an IRTF submission=20
    Token: Jari Arkko

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-jayasumana-reorder-density-08.txt
    Reorder Density and Reorder Buffer-occupancy Density - Metrics for
Packet=20
    Reordering Measurements (Informational) - 1 of 1=20
    Note: Suggest to respond to the RFC Editor with RFC 3932, Section 3,
Option=20
    2: "The IESG thinks that this work is related to IETF work done in =
the
IPPM=20
    WG, but this does not prevent publishing."=20
    Token: Lars Eggert

3.3.2 Returning Item
  o draft-irtf-tmrg-metrics-11.txt
    Metrics for the Evaluation of Congestion Control Mechanisms
(Informational)=20
    - 1 of 1=20
    Note: To be published according to draft-irtf-rfcs-01.txt Based on =
the
=20
    Working Group Summary, I believe that the. second variant suggested =
in
=20
    Appendix A of draft-irtf-rfcs-0. is appropriate for this document:
"This=20
    document in not an IETF Internet Standard.=A0 It represents. the=20
    individual opinion(s) of one or more members of the TMRG. Research
Group of=20
    the Internet Research Task Force. It may be. considered for
standardization=20
    by the IETF or adoption as a. IRTF Research Group consensus document
in the=20
    future."=20
    Token: Lars Eggert

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



