[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for March 6, 2008

[IESG Secretary <[e-mail]>]

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the March 6, 2008 IESG Teleconference

This agenda was generated at 15:12:47 EDT, February 28, 2008
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-imapext-i18n-15.txt
    Internet Message Access Protocol Internationalization (Proposed Standard) - 
    1 of 7 
    Token: Lisa Dusseault
  o draft-ietf-sipping-consent-format-06.txt
    A Document Format for Requesting Consent (Proposed Standard) - 2 of 7 
    Token: Jon Peterson
  o draft-ietf-sipping-pending-additions-04.txt
    The Session Initiation Protocol (SIP) Pending Additions Event Package 
    (Proposed Standard) - 3 of 7 
    Token: Jon Peterson
  o draft-ietf-sipping-service-examples-14.txt
    Session Initiation Protocol Service Examples (BCP) - 4 of 7 
    Token: Jon Peterson
  o draft-ietf-ecrit-lost-07.txt
    LoST: A Location-to-Service Translation Protocol (Proposed Standard) - 5 of 
    7 
    Token: Jon Peterson
  o draft-ietf-netconf-notification-12.txt
    NETCONF Event Notifications (Proposed Standard) - 6 of 7 
    Token: Dan Romascanu
  o draft-ietf-tls-rfc4346-bis-09.txt
    The Transport Layer Security (TLS) Protocol Version 1.2 (Proposed Standard) 
    - 7 of 7 
    Token: Tim Polk

2.1.2 Returning Item
  o draft-ietf-msec-ipsec-extensions-08.txt
    Multicast Extensions to the Security Architecture for the Internet Protocol 
    (Proposed Standard) - 1 of 2 
    Note: Lakshminath Dondeti is the proto shepherd. 
    Token: Tim Polk
  o draft-ietf-netlmm-proxymip6-11.txt
    Proxy Mobile IPv6 (Proposed Standard) - 2 of 2 
    Note: Document Shepherd is Jonne Soininen 
    Token: Jari Arkko


2.2 Individual Submissions
2.2.1 New Item
  o draft-harrington-text-mib-doc-template-04.txt
    A Template for Documents Containing a MIB Module (BCP) - 1 of 2 
    Token: Dan Romascanu
  o Two-document ballot:  - 2 of 2
     - draft-moriarty-post-inch-rid-soap-05.txt
       IODEF/RID over SOAP (Proposed Standard) 
     - draft-moriarty-post-inch-rid-05.txt
       Real-time Inter-network Defense (Proposed Standard) 
    Token: Tim Polk

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-msec-mikey-applicability-08.txt
    On the applicability of various MIKEY modes and extensions (Informational) 
    - 1 of 2 
    Note: Document Shepherd is Lakshminath Dondeti, [e-mail] 
    Token: Tim Polk
  o draft-ietf-mediactrl-requirements-04.txt
    Media Server Control Protocol Requirements (Informational) - 2 of 2 
    Token: Jon Peterson

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
  o draft-levin-mmusic-xml-media-control-13.txt
    XML Schema for Media Control (Informational) - 1 of 1 
    Token: Cullen Jennings

3.2.2 Returning Item
NONE
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 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 Timing over IP Connection and Transfer of Clock (tictoc) - 1 of 2
    Token: Mark
  o Internationalized Domain Name (idn) - 2 of 2
    Token: Lisa
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o Multiparty Multimedia Session Control (mmusic) - 1 of 1
    Token: Cullen
4.2.2 Proposed for Approval
    NONE

5. IAB News We can use

6. Management Issue

 6.1 RFC Errata (Russ Housley)

 6.2 Accelerate processing for draft-brenner-dime-peem-01 (Dan Romascanu)

7. Agenda Working Group News


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