[MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for November 29, 2007 Telechat

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Mon, 26 November 2007 13:04 UTC

Return-path: <mib-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 1Iwdd3-0000kK-RG; Mon, 26 Nov 2007 08:04:01 -0500
Received: from mib-doctors by megatron.ietf.org with local (Exim 4.43) id 1Iwdd2-0000jv-KP for mib-doctors-confirm+ok@megatron.ietf.org; Mon, 26 Nov 2007 08:04:00 -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: [MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for November 29, 2007 Telechat
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org

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

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. 

Thanks and Regards,

Dan
 


 

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

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 
    Token: Magnus Westerlund
  o draft-ietf-geopriv-revised-civic-lo-06.txt
    Revised Civic Location Format for PIDF-LO (Proposed Standard) - 2 of 9
 
    Note: Robert is proto shepherd 
    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 
    Token: Magnus Westerlund
  o draft-ietf-rmt-bb-fec-rs-05.txt
    Reed-Solomon Forward Error Correction (FEC) Schemes (Proposed
Standard) - 4 
    of 9 
    Token: Magnus Westerlund
  o draft-ietf-smime-bfibecms-08.txt
    Using the Boneh-Franklin and Boneh-Boyen identity-based encryption 
    algorithms with the Cryptographic Message Syntax (CMS) (Proposed
Standard) 
    - 5 of 9 
    Token: Tim Polk
  o draft-ietf-smime-ibearch-06.txt
    Identity-based Encryption Architecture (Proposed Standard) - 6 of 9 
    Token: Tim Polk
  o draft-ietf-avt-rfc3119bis-05.txt
    A More Loss-Tolerant RTP Payload Format for MP3 Audio (Proposed
Standard) - 
    7 of 9 
    Note: Colin Perkins is the document shepherd. 
    Token: Cullen Jennings
  o draft-ietf-avt-rfc2833biscas-05.txt
    Definition of Events For Channel-Oriented Telephony Signalling
(Proposed 
    Standard) - 8 of 9 
    Note: Proto shepherd is Roni Even 
    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 
    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 
    1 
    Note: Document Shepherd is <pete.mccann@motorola.com> 
    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 
    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) - 
    1 of 1 
    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 
    Note: No document shepherd 
    Token: Jari Arkko
  o draft-irtf-mobopts-l2-abstractions-04.txt
    Unified L2 Abstractions for L3-Driven Fast Handover (Experimental) - 2
of 2 
    Note: This is an IRTF submission 
    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 
    Reordering Measurements (Informational) - 1 of 1 
    Note: Suggest to respond to the RFC Editor with RFC 3932, Section 3,
Option 
    2: "The IESG thinks that this work is related to IETF work done in the
IPPM 
    WG, but this does not prevent publishing." 
    Token: Lars Eggert

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


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