[MIB-DOCTORS] FW: PREMINARY Agenda and Package for June 4, 2009 Telechat

["Romascanu, Dan (Dan)" <dromasca at avaya.com>]

Please find below the preliminary agenda of the 6/4 IESG telechat.
Please send me your questions, comments and concerns about the relevant
documents and WG charter brought to approval before Wednesday 6/3 COB. 

Thanks and Regards,

Dan

---------------------------------------



2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-dkim-ssp-10.txt
    DomainKeys Identified Mail (DKIM) Author Domain Signing Practices
(ADSP) 
    (Proposed Standard) - 1 of 7 
    Note: Document shepherd is Stephen Farrell
(stephen.farrell at cs.tcd.ie)
 
    Token: Pasi Eronen
  o draft-ietf-sip-outbound-18.txt
    Managing Client Initiated Connections in the Session Initiation
Protocol 
    (SIP) (Proposed Standard) - 2 of 7 
    Token: Robert Sparks
  o draft-ietf-mmusic-sdp-capability-negotiation-10.txt
    SDP Capability Negotiation (Proposed Standard) - 3 of 7 
    Note: Proto Shepherd: Jean-Francois Mule (jf.mule at cablelabs.com) 
    Token: Cullen Jennings
  o draft-ietf-netlmm-pmip6-ipv4-support-12.txt
    IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 4 of 7 
    Token: Jari Arkko
  o draft-ietf-ippm-more-twamp-02.txt
    More Features for the Two-Way Active Measurement Protocol - TWAMP
(Proposed 
    Standard) - 5 of 7 
    Token: Lars Eggert
  o draft-ietf-dkim-rfc4871-errata-05.txt
    RFC 4871 DomainKeys Identified Mail (DKIM) Signatures -- Update
(Proposed 
    Standard) - 6 of 7 
    Token: Pasi Eronen
  o draft-ietf-dnsext-dnsproxy-05.txt
    DNS Proxy Implementation Guidelines (BCP) - 7 of 7 
    Token: Ralph Droms

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-crocker-email-arch-13.txt
    Internet Mail Architecture (Proposed Standard) - 1 of 1 
    Note: Tony Hansen is document shepherd. 
    Token: Alexey Melnikov

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-avt-seed-srtp-11.txt
    The SEED Cipher Algorithm and Its Use with the Secure Real-time
Transport 
    Protocol (SRTP (Informational) - 1 of 2 
    Token: Cullen Jennings
  o draft-ietf-geopriv-sip-lo-retransmission-02.txt
    Implications of 'retransmission-allowed' for SIP Location Conveyance

    (Informational) - 2 of 2 
    Token: Cullen Jennings

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-ietf-sip-ua-privacy-08.txt
    UA-Driven Privacy Mechanism for SIP (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
  o draft-ford-behave-top-06.txt
    Unintended Consequence of two NAT deployments with Overlapping
Address
 
    Space (Informational) - 1 of 1 
    Token: Magnus Westerlund

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
    NONE
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
  o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 1
    Token: Magnus Westerlund
4.2.2 Proposed for Approval
    NONE