[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: Documents on Agenda for July 6, 2006 IESG Telechat

 



Please see below for the documents on the agenda for the July 6th
telechat. I there are any comments or concerns, please send the to me
before July 5th, COB.

Thanks,

Dan

---

----- Forwarded message from IESG Secretary <iesg-secretary@ietf.org>
-----

INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the
July 6, 2006 IESG Teleconference

This agenda was generated at 17:18:52 EDT, June 29, 2006 Web version of
this agenda can be found at:
http://www.ietf.org/IESG/agenda.html
 

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-ipfix-protocol-22.txt
    IPFIX Protocol Specification (Proposed Standard) - 1 of 3 
    Token: Dan Romascanu
  o Two-document ballot:  - 2 of 3
     - draft-ietf-radext-rfc2619bis-04.txt
       RADIUS Authentication Server MIB for IPv6 (Proposed Standard) 
     - draft-ietf-radext-rfc2618bis-04.txt
       RADIUS Authentication Client MIB for IPV6 (Proposed Standard) 
       Note: Version 04 was submitted on Monday 6/26, prior to the I-D 
       submission deadline. Please use this version for review, as soon
as it 
       shows up in the I-D repository. 
    Token: Dan Romascanu
  o draft-ietf-sieve-rfc3598bis-05.txt
    Sieve Email Filtering -- Subaddress Extension (Proposed Standard) -
3 of 3 
    Token: Lisa Dusseault

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
  o draft-ietf-ipsec-ike-auth-ecdsa-05.txt
    IKE and IKEv2 Authentication Using ECDSA (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-ipfix-architecture-11.txt
    Architecture for IP Flow Information Export (Informational) - 1 of 4

    Token: Dan Romascanu
  o Two-document ballot:  - 2 of 4
     - draft-ietf-radext-dynauth-client-mib-06.txt
       Dynamic Authorization Client MIB (Informational) 
     - draft-ietf-radext-dynauth-server-mib-06.txt
       Dynamic Authorization Server MIB (Informational) 
    Token: Dan Romascanu
  o Two-document ballot:  - 3 of 4
     - draft-ietf-radext-rfc2621bis-04.txt
       RADIUS Accounting Server MIB for IPv6 (Informational) 
     - draft-ietf-radext-rfc2620bis-04.txt
       RADIUS Accounting Client MIB for IPv6 (Informational) 
       Note: Version 04 documents were submitted on 6/26, prior to the
I-D 
       submission deadline. Please use this version for reviews when
they 
       become available in the I-D repository 
    Token: Dan Romascanu
  o draft-ietf-avt-rfc2190-to-historic-06.txt
    RTP Payload Format for H.263 using RFC2190 to Historic status
(Historic) - 
    4 of 4 
    Note: PROTO shepherd: Colin Perkins csp@csperkins.org 
    Token: Cullen Jennings

3.1.2 Returning Item
  o draft-ietf-dnsext-mdns-46.txt
    Linklocal Multicast Name Resolution (LLMNR) (Informational) - 1 of 1

    Token: Mark Townsley


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-klensin-norm-ref-01.txt
    A Process Experiment in Normative Reference Handling (Experimental)
- 1 of 
    4 
    Note: RFC 3933 process experiment 
    Token: Brian Carpenter
  o draft-mankin-pub-req-09.txt
    Requirements for IETF Technical Publication Service (Informational)
- 2 of 
    4 
    Token: Brian Carpenter
  o draft-alvestrand-ipod-02.txt
    IETF Operational Notes (Experimental) - 3 of 4 
    Note: RFC 3933 process experiment 
    Token: Brian Carpenter
  o draft-nystrom-ct-kip-01.txt
    Cryptographic Token Key Initialization Protocol Version 1.0
(Informational) 
    - 4 of 4 
    Token: Russ Housley

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-vandyke-mscml-09.txt
    Media Server Control Markup Language (MSCML) and Protocol
(Informational) - 
    1 of 2 
    Token: Brian Carpenter
  o draft-vanderveen-eap-sake-02.txt
    Extensible Authentication Protocol Method for Shared-secret
Authentication 
    and Key Establishment (EAP-SAKE) (Informational) - 2 of 2 
    Token: Jari Arkko