[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for October 18, 2007

[IESG Secretary <[e-mail]>]

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the October 18, 2007 IESG Teleconference

This agenda was generated at 0:56:52 EDT, October 12, 2007
Web version of this agenda can be found at:
http://www.ietf.org/IESG/agenda.html
                                                                                
1. Administrivia
                                                                                
  1.1 Roll Call
  1.2 Bash the Agenda
  1.3 Approval of the Minutes
  1.4 Review of Action Items

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-ipcdn-pktc-signaling-15.txt
    Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters 
    (MTAs) (Proposed Standard) - 1 of 5 
    Note: Jean Francois Mule is the PROTO SHEPHERD of the document 
    Token: Dan Romascanu
  o draft-ietf-avt-profile-savpf-11.txt
    Extended Secure RTP Profile for RTCP-based Feedback (RTP/SAVPF) (Proposed 
    Standard) - 2 of 5 
    Note: PROTO shepherd is Colin 
    Token: Cullen Jennings
  o draft-ietf-crisp-iris-dchk-07.txt
    A Domain Availability Check (dchk) Registry Type for the Internet Registry 
    Information Service (IRIS) (Proposed Standard) - 3 of 5 
    Note: April Marine is Document Shepherd. 
    Token: Chris Newman
  o draft-ietf-lemonade-reconnect-client-06.txt
    IMAP4 Extensions for Quick Mailbox Resynchronization (Proposed Standard) - 
    4 of 5 
    Token: Chris Newman
  o draft-ietf-tsvwg-udplite-mib-02.txt
    MIB for the UDP-Lite protocol (Proposed Standard) - 5 of 5 
    Note: Shepherd by responsible AD: Magnus Westerlund 
    Token: Magnus Westerlund

2.1.2 Returning Item
  o draft-ietf-magma-mgmd-mib-10.txt
    Multicast Group Membership Discovery MIB (Proposed Standard) - 1 of 2 
    Note: Document Shepherd is Brian Haberman 
    Token: Jari Arkko
  o draft-ietf-sip-answermode-06.txt
    Requesting Answering Modes for the Session Initiation Protocol (SIP) 
    (Proposed Standard) - 2 of 2 
    Note: Keith is shepherd. 
    Token: Cullen Jennings


2.2 Individual Submissions
2.2.1 New Item
  o draft-narten-iana-considerations-rfc2434bis-08.txt
    Guidelines for Writing an IANA Considerations Section in RFCs (BCP) - 1 of 
    1 
    Token: Russ Housley

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-ippm-bw-capacity-05.txt
    Defining Network Capacity (Informational) - 1 of 3 
    Note: Document Shepherd: Matt Zekauskas ([e-mail]). 
    Token: Lars Eggert
  o draft-ietf-nfsv4-nfs-rdma-problem-statement-07.txt
    NFS RDMA Problem Statement (Informational) - 2 of 3 
    Note: Document Shepherd: Spencer Shepler ([e-mail]) 
    Token: Lars Eggert
  o draft-ietf-radext-rfc3576bis-10.txt
    Dynamic Authorization Extensions to Remote Authentication Dial In User 
    Service (RADIUS) (Informational) - 3 of 3 
    Token: Dan Romascanu

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-aboba-sg-experiment-03.txt
    Experiment in Study Group Formation within the Internet Engineering Task 
    Force (IETF) (Experimental) - 1 of 1 
    Note: No document shepherd.. Need to bring this back to the telechat 
    Token: Jari Arkko

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
NONE

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
  o HyperText Transport Protocol Bis (httpbis) - 1 of 1
    Token: Lisa
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o Common Control and Measurement Plane (ccamp) - 1 of 2
    Token: Ross
  o Audio/Video Transport (avt) - 2 of 2
    Token: Cullen
4.2.2 Proposed for Approval
  o Dynamic Host Configuration (dhc) - 1 of 2
    Token: Jari
  o Network File System Version 4 (nfsv4) - 2 of 2
    Token: Lars

5. IAB News We can use

6. Management Issue

 6.1 ion-2026-practice.html (Russ Housley)

 6.2 On Appeals of IESG and Area Director Actions and Decisions (Russ Housley)

7. Agenda Working Group News



_______________________________________________
IESG-AGENDA-DIST mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/iesg-agenda-dist