Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for November 15, 2007 Telechat

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Fri, 9 Nov 2007 09:14:29 +0100

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. 

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 
    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 
    Token: Magnus Westerlund
  o draft-ietf-tsvwg-ecn-mpls-02.txt
    Explicit Congestion Marking in MPLS (Proposed Standard) - 4 of 6 
    Note: Lars Eggert ([email-masked]) is document shepherd. 
    Token: Lars Eggert
  o draft-ietf-sigtran-rfc4233update-02.txt
    TEI Query Request Number Change (Proposed Standard) - 5 of 6 
    Token: Jon Peterson
  o draft-ietf-mipshop-handover-key-03.txt
    Distributing a Symmetric FMIPv6 Handover Key using SEND (Proposed
Standard) 
    - 6 of 6 
    Note: Document Shepherd is Vijay Devarapalli 
    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) 
    (Proposed Standard) - 1 of 1 
    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 
    Note: Document Shepherd: Spencer Shepler ([email-masked]) 
    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 
    Token: Jon Peterson
  o draft-ietf-eap-netsel-problem-08.txt
    Network Discovery and Selection Problem (Informational) - 3 of 5 
    Token: Mark Townsley
  o draft-ietf-behave-p2p-state-05.txt
    State of Peer-to-Peer(P2P) Communication Across Network Address 
    Translators(NATs) (Informational) - 4 of 5 
    Token: Magnus Westerlund
  o draft-ietf-smime-cades-06.txt
    CMS Advanced Electronic Signatures (CAdES) (Informational) - 5 of 5 
    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 
    (EPC) and Related Standards (Informational) - 1 of 2 
    Token: Lisa Dusseault
  o draft-lepinski-dh-groups-03.txt
    Additional Diffie-Hellman Groups for use with IETF Standards 
    (Informational) - 2 of 2 
    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) 
    - 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

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
[email-masked]
https://www1.ietf.org/mailman/listinfo/aaa-doctors