FW: PRELIMINARY Agenda and Package for June 22, 2006 Telechat

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

Please find below the preliminary agenda for the 6/22 IESG telechat. If
you have any comments, concerns or questions concerning the documents
submitted for approval please send them to me until Wednesday 6/21 COB
the latest. 

Dan
 


 

-----Original Message-----
From: IESG Secretary [mailto:iesg-secretary@ietf.org] 
Sent: Thursday, June 15, 2006 10:59 PM
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-idr-restart-12.txt
    Graceful Restart Mechanism for BGP (Proposed Standard) - 1 of 2 
    Token: Bill Fenner
  o draft-ietf-enum-pstn-04.txt
    IANA Registration for an Enumservice Containing PSTN Signaling
Information 
    (Proposed Standard) - 2 of 2 
    Note: PROTO Sherpherd: Patrik Faltstrom (paf@cisco.com) 
    Token: Jon Peterson

2.1.2 Returning Item
NONE
2.1.3 For Action
  o draft-ietf-ospf-mib-update-11.txt
    OSPF Version 2 Management Information Base (Proposed Standard) - 1
of 1 
    Token: Bill Fenner

2.2 Individual Submissions
2.2.1 New Item
  o draft-arberg-pppoe-iana-01.txt
    IANA Considerations for PPP over Ethernet (PPPoE) (BCP) - 1 of 4 
    Note: Should end IETF LC 06/21 
    Token: Mark Townsley
  o draft-ietf-ipsec-ike-auth-ecdsa-05.txt
    IKE and IKEv2 Authentication Using ECDSA (Proposed Standard) - 2 of
4 
    Token: Russ Housley
  o draft-snell-atompub-feed-thread-12.txt
    Atom Threading Extensions (Proposed Standard) - 3 of 4 
    Token: Lisa Dusseault
  o draft-vaudreuil-futuredelivery-03.txt
    SMTP Submission Service Extension for Future Message Release
(Proposed 
    Standard) - 4 of 4 
    Note: Last Call ends on June 22, 2006 
    Token: Ted Hardie

2.2.2 Returning Item
  o draft-dusseault-caldav-12.txt
    Calendaring Extensions to WebDAV (CalDAV) (Proposed Standard) - 1 of
1 
    Token: Ted Hardie


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
NONE
3.2.2 Returning Item
NONE
3.3 Individual 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.
 

              
	Other matters may be recorded in comments to 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

--