[IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for July 2, 2009

IESG Secretary <iesg-secretary-reply@ietf.org> Thu, 25 June 2009 22:41 UTC

Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: iesg-agenda-dist@ietf.org
Delivered-To: iesg-agenda-dist@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id B578428C0E7; Thu, 25 Jun 2009 15:41:00 -0700 (PDT)
From: IESG Secretary <iesg-secretary-reply@ietf.org>
To: iesg-agenda-dist@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090625224100.B578428C0E7@core3.amsl.com>
Date: Thu, 25 Jun 2009 15:41:00 -0700
Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for July 2, 2009
X-BeenThere: iesg-agenda-dist@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Distribution of IESG agendas <iesg-agenda-dist.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iesg-agenda-dist>
List-Post: <mailto:iesg-agenda-dist@ietf.org>
List-Help: <mailto:iesg-agenda-dist-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iesg-agenda-dist>, <mailto:iesg-agenda-dist-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2009 22:41:00 -0000

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the July 2, 2009 IESG Teleconference

This agenda was generated at 15:41:0 EDT, June 25, 2009
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-avt-rtcpssm-18.txt
    RTCP Extensions for Single-Source Multicast Sessions with Unicast Feedback 
    (Proposed Standard) - 1 of 12 
    Token: Cullen Jennings
  o draft-ietf-tcpm-rfc2581bis-05.txt
    TCP Congestion Control (Draft Standard) - 2 of 12 
    Note: Document Shepherd: Wesley Eddy (wesley.m.eddy@nasa.gov). Interop 
    Report: http://www.ietf.org/mail-archive/web/tcpm/current/msg03133.html 
    Token: Lars Eggert
  o draft-ietf-adslmib-vdsl2-07.txt
    Definitions of Managed Objects for Very High Speed Digital Subscriber Line 
    2 (VDSL2) (Proposed Standard) - 3 of 12 
    Token: Dan Romascanu
  o draft-ietf-mipshop-mos-dns-discovery-06.txt
    Locating IEEE 802.21 Mobility Servers using DNS (Proposed Standard) - 4 of 
    12 
    Note: Document shepherd is Vijay Devarapalli &lt;vijay@wichorus.com&gt; 
    Token: Jari Arkko
  o draft-ietf-avt-rtp-mps-02.txt
    RTP Payload Format for Elementary Streams with MPEG Surround multi- channel 
    audio (Proposed Standard) - 5 of 12 
    Token: Cullen Jennings
  o draft-ietf-dime-qos-attributes-12.txt
    Quality of Service Attributes for Diameter (Proposed Standard) - 6 of 12 
    Token: Dan Romascanu
  o draft-ietf-geopriv-civic-address-recommendations-02.txt
    Considerations for Civic Addresses in PIDF-LO - Guidelines and IANA 
    Registry Definition (BCP) - 7 of 12 
    Token: Cullen Jennings
  o draft-ietf-sip-body-handling-06.txt
    Message Body Handling in the Session Initiation Protocol (SIP) (Proposed 
    Standard) - 8 of 12 
    Note: Theo Zourzouvillys is the document shepherd 
    Token: Robert Sparks
  o draft-ietf-ospf-dynamic-hostname-04.txt
    Dynamic Hostname Exchange Mechanism for OSPF (Proposed Standard) - 9 of 12 
    Token: Ross Callon
  o draft-ietf-l2tpext-circuit-status-extensions-04.txt
    L2TPv3 Extended Circuit Status Values (Proposed Standard) - 10 of 12 
    Note: &nbsp; Ignacio Goyret &lt;igoyret@alcatel-lucent.com&gt; is the WG 
    shepherd. &nbsp; for this document.. 
    Token: Ralph Droms
  o draft-ietf-sipcore-subnot-etags-02.txt
    An Extension to Session Initiation Protocol (SIP) Events for Conditional 
    Event Notification (Proposed Standard) - 11 of 12 
    Note: Dean Willis (dean.willis@softarmor.com) is document shepherd. 
    Token: Robert Sparks
  o draft-ietf-pwe3-vccv-bfd-05.txt
    Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit 
    Connectivity Verification (VCCV) (Proposed Standard) - 12 of 12 
    Token: Ralph Droms

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-dusseault-impl-reports-03.txt
    Guidance on Interoperation and Implementation Reports (BCP) - 1 of 2 
    Token: Tim Polk
  o draft-dawkins-nomcom-dont-wait-03.txt
    Nominating Committee Process: Earlier Announcement of Open Positions and 
    Solicitation of Volunteers (BCP) - 2 of 2 
    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-geopriv-l7-lcp-ps-09.txt
    GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and 
    Requirements (Informational) - 1 of 9 
    Token: Cullen Jennings
  o draft-ietf-pwe3-ms-pw-arch-06.txt
    An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge 
    (Informational) - 2 of 9 
    Note: &nbsp; David Sinicrope (david.sinicrope@ericsson.com) is the. &nbsp; 
    Document Shepherd for this document. 
    Token: Ralph Droms
  o draft-ietf-pce-inter-layer-frwk-10.txt
    Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering 
    (Informational) - 3 of 9 
    Token: Ross Callon
  o draft-ietf-opsec-blackhole-urpf-04.txt
    Remote Triggered Black Hole filtering with uRPF (Informational) - 4 of 9 
    Token: Ron Bonica
  o draft-ietf-dccp-ccid4-04.txt
    Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: 
    TCP-Friendly Rate Control for Small Packets (TFRC-SP) (Experimental) - 5 of 
    9 
    Note: Document Shepherd: Pasi Sarolahti (pasi.sarolahti@iki.fi) [was Gorry 
    Fairhurst, but he's not a DCCP chair anymore] 
    Token: Lars Eggert
  o draft-ietf-smime-new-asn1-05.txt
    New ASN.1 Modules for CMS and S/MIME (Informational) - 6 of 9 
    Note: Sean Turner (turners@ieca.com) is the document shepherd. 
    Token: Tim Polk
  o draft-ietf-ancp-security-threats-07.txt
    Security Threats and Security Requirements for the Access Node Control 
    Protocol (ANCP) (Informational) - 7 of 9 
    Note: Matthew Bocci (matthew.bocci@alcatel-lucent.com) is the document 
    shepherd. 
    Token: Ralph Droms
  o draft-ietf-dccp-quickstart-05.txt
    Quick-Start for Datagram Congestion Control Protocol (DCCP) (Experimental) 
    - 8 of 9 
    Note: Document shepherd is Pasi Sarolahti &lt;pasi.sarolahti@iki.fi&gt; 
    Token: Lars Eggert
  o draft-ietf-pkix-tac-04.txt
    Traceable Anonymous Certificate (Experimental) - 9 of 9 
    Token: Tim Polk

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-livingood-woundy-p4p-experiences-10.txt
    Comcast's ISP Experiences In a P4P Technical Trial (Informational) - 1 of 1 
    Token: Lisa Dusseault

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
  o draft-irtf-mobopts-location-privacy-solutions-15.txt
    Mobile IPv6 Location Privacy Solutions (Experimental) - 1 of 1 
    Note: The document shepherd is Basavaraj Patil 
    &lt;Basavaraj.Patil@nokia.com&gt; 
    Token: Jari Arkko


4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
  o STORage Maintenance (storm) - 1 of 1
    Token: Lars
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 3
    Token: Magnus
  o IP Flow Information Export (ipfix) - 2 of 3
    Token: Dan
  o DNS Extensions (dnsext) - 3 of 3
    Token: Ralph
4.2.2 Proposed for Approval
  o Site Multihoming by IPv6 Intermediation (shim6) - 1 of 3
    Token: Jari
  o Diameter Maintenance and Extensions (dime) - 2 of 3
    Token: Dan
  o Integrated Security Model for SNMP (isms) - 3 of 3
    Token: Pasi

5. IAB News We can use

6. Management Issue

7. Working Group News