Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for July 3, 2008

From: IESG Secretary <[email-masked]>
Date: Thu, 26 Jun 2008 19:23:01 -0700 (PDT)

INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the July 3, 2008 IESG Teleconference

This agenda was generated at 19:23:1 EDT, June 26, 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-rmt-bb-norm-revised-05.txt
    Multicast Negative-Acknowledgment (NACK) Building Blocks (Proposed 
    Standard) - 1 of 14 
    Token: Magnus Westerlund
  o draft-ietf-pwe3-enet-mib-13.txt
    Ethernet Pseudowire (PW) Management Information Base (MIB) (Proposed 
    Standard) - 2 of 14 
    Token: Mark Townsley
  o draft-ietf-pwe3-cep-mib-12.txt
    SONET/SDH Circuit Emulation Service Over Packet (CEP) Management 
    Information Base (MIB) Using SMIv2 (Proposed Standard) - 3 of 14 
    Token: Mark Townsley
  o draft-ietf-pwe3-pw-mpls-mib-14.txt
    Pseudowire (PW) over MPLS PSN Management Information Base (MIB) (Proposed 
    Standard) - 4 of 14 
    Token: Mark Townsley
  o draft-ietf-pwe3-tdm-mib-10.txt
    Managed Objects for TDM over Packet Switched Network (PSN) (Proposed 
    Standard) - 5 of 14 
    Token: Mark Townsley
  o draft-ietf-pwe3-pw-atm-mib-05.txt
    Managed Objects for ATM over Packet Switched Network (PSN) (Proposed 
    Standard) - 6 of 14 
    Token: Mark Townsley
  o draft-ietf-imss-fc-fcsp-mib-02.txt
    MIB for Fibre-Channel Security Protocols (FC-SP) (Proposed Standard) - 7 of 
    14 
    Token: Dan Romascanu
  o draft-ietf-isis-rfc3847bis-00.txt
    Restart Signaling for Intermediate System to Intermediate System (IS-IS) 
    (Proposed Standard) - 8 of 14 
    Token: Ross Callon
  o draft-ietf-isis-rfc3373bis-01.txt
    Three-Way Handshake for Intermediate System to Intermediate System (IS-IS) 
    Point-to-Point Adjacencies (Proposed Standard) - 9 of 14 
    Token: Ross Callon
  o draft-ietf-isis-rfc2966bis-03.txt
    Domain-wide Prefix Distribution with Two-Level IS-IS (Proposed Standard) - 
    10 of 14 
    Token: Ross Callon
  o draft-ietf-isis-te-bis-00.txt
    IS-IS extensions for Traffic Engineering (Proposed Standard) - 11 of 14 
    Token: Ross Callon
  o draft-ietf-isis-rfc2763bis-00.txt
    Dynamic Hostname Exchange Mechanism for IS-IS (Proposed Standard) - 12 of 
    14 
    Token: Ross Callon
  o draft-ietf-isis-rfc3567bis-01.txt
    Intermediate System to Intermediate System (IS-IS) Cryptographic 
    Authentication (Proposed Standard) - 13 of 14 
    Token: Ross Callon
  o draft-ietf-isis-rfc4205bis-00.txt
    Intermediate System to Intermediate System (IS-IS) Extensions in Support of 
    Generalized Multi-Protocol Label Switching (GMPLS) (Proposed Standard) - 14 
    of 14 
    Token: Ross Callon

2.1.2 Returning Item
  o draft-ietf-sipping-uri-services-07.txt
    Framework and Security Considerations for Session Initiation Protocol (SIP) 
    Uniform Resource Identifier (URI)-List Services (Proposed Standard) - 1 of 
    1 
    Token: Jon Peterson

2.2 Individual Submissions
2.2.1 New Item
  o draft-eastlake-ethernet-iana-considerations-07.txt
    IANA Considerations and IETF Protocol Usage for IEEE 802 Parameters (BCP) - 
    1 of 1 
    Token: Dan Romascanu

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-enum-softswitch-req-03.txt
    ENUM-based Softswitch Requirement (Informational) - 1 of 3 
    Token: Jon Peterson
  o Two-document ballot:  - 2 of 3
     - draft-ietf-eai-utf8headers-11.txt
       Internationalized Email Headers (Experimental) 
       Note: Harald Alvestrand is document shepherd. 
     - draft-ietf-eai-smtpext-12.txt
       SMTP extension for internationalized email address (Experimental) 
       Note: Harald Alvestrand is document shepherd. 
    Token: Chris Newman
  o draft-ietf-eai-dsn-06.txt
    Internationalized Delivery Status and Disposition Notifications 
    (Experimental) - 3 of 3 
    Token: Lisa Dusseault

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-hautakorpi-sipping-uri-list-handling-refused-03.txt
    The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header 
    (P-Header) (Informational) - 1 of 1 
    Token: Jon Peterson

3.2.2 Returning Item
NONE
3.2.3 For Action
  o draft-sanjib-private-vlan-09.txt
    Cisco Systems' Private VLANs: Scalable Security in a Multi-Client 
    Environment (Informational) - 1 of 1 
    Note: This is an independent submission, going on telechat for RFC3932 
    check. 
    Token: Mark Townsley
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 IP Security Maintenance and Extensions (ipsecme) - 1 of 1
    Token: Pasi
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o Network-based Localized Mobility Management (netlmm) - 1 of 2
    Token: Jari
  o IPv6 over Low power WPAN (6lowpan) - 2 of 2
    Token: Mark
4.2.2 Proposed for Approval
  o Pseudowire Emulation Edge to Edge (pwe3) - 1 of 1
    Token: Mark

5. IAB News We can use

6. Management Issue

 6.1 Executive Session: Discussion of Appeal (Russ Housley/Tim Polk)

7. Agenda Working Group News

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