FW: PRELIMINARY Agenda and Package for April 27, 2006 Telechat

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

Please find below the list of documents for approval on the preliminary
agenda of the 4/27 IESG call. Please provide feedback and raise any
issues, comments, concerns related to these documents until 4/26 COB the
latest. 

Dan


 

 

-----Original Message-----

2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-iptel-tel-np-09.txt
    Number Portability Parameters for the "tel" URI (Proposed Standard)
- 1 of 
    2 
    Note: Proto Shepherd: Jonathan Rosenberg jdrosen@cisco.com 
    Token: Cullen Jennings
  o draft-ietf-ippm-reordering-12.txt
    Packet Reordering Metric for IPPM (Proposed Standard) - 2 of 2 
    Note: PROTO shepherd: Henk Uijterwaal (henk.uijterwaal@ripe.net) 
    Token: Lars Eggert

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
  o draft-rja-ripv2-auth-04.txt
    RIPv2 Cryptographic Authentication (Proposed Standard) - 1 of 1 
    Token: Russ Housley


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-ccamp-loose-path-reopt-02.txt
    Reoptimization of Multiprotocol Label Switching (MPLS) Traffic
Engineering 
    (TE) loosely routed Label Switch Path (LSP) (Informational) - 1 of 3

    Token: Ross Callon
  o draft-ietf-ccamp-inter-domain-framework-04.txt
    A Framework for Inter-Domain MPLS Traffic Engineering
(Informational) - 2 
    of 3 
    Token: Ross Callon
  o draft-ietf-tcpm-tcp-dcr-07.txt
    Improving the Robustness of TCP to Non-Congestion Events
(Experimental) - 3 
    of 3 
    Note: PROTO Shepherd: Ted Faber (faber@isi.edu) 
    Token: Lars Eggert

3.1.2 Returning Item
  o draft-ietf-pce-architecture-05.txt
    A Path Computation Element (PCE) Based Architecture (Informational)
- 1 of 
    1 
    Token: Ross Callon


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-kornijenko-ivis-urn-00.txt
    A URN Namespace for the Latvian National Government Integration
Project 
    (Informational) - 1 of 1 
    Token: Ted Hardie

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
3.3.3 For Action
  o draft-murphy-iser-telnet-04.txt
    iSeries Telnet Enhancements (Informational) - 1 of 1 
    Token: Brian Carpenter