IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2009-05-21).

1. Administrivia

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

Area	Date
TSV		RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) - 1 of 3
		draft-ietf-tsvwg-rsvp-proxy-proto-09.txt [Open Web Ballot]
		Note: Please read the informational document draft-ietf-tsvwg-rsvp-proxy-approaches before this one!
	Token:	Magnus Westerlund
INT		IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 2 of 3
		draft-ietf-netlmm-pmip6-ipv4-support-12.txt [Open Web Ballot]
	Token:	Jari Arkko
TSV		DCCP Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal (Proposed Standard) - 3 of 3
		draft-ietf-dccp-simul-open-08.txt [Open Web Ballot]
	Token:	Lars Eggert

2.1.2 Returning Item

Area	Date
SEC		An Internet Attribute Certificate Profile for Authorization (Proposed Standard) - 1 of 1
		draft-ietf-pkix-3281update-05.txt [Open Web Ballot]
	Token:	Tim Polk

2.2 Individual Submissions

2.2.1 New Item
NONE
2.2.2 Returning Item

Area	Date
RAI		H.248/MEGACO Registration Procedures (BCP) - 1 of 1
		draft-groves-megaco-pkgereg-03.txt [Open Web Ballot]
		Note: IESG - when reviewing this, please consider the topic of if it is alright to register a "public" package when the specification is not publicly available. This came up as an IETF LC comment.
	Token:	Cullen Jennings

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

Area	Date
TSV		Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) - 1 of 3
		draft-ietf-tcpm-ecnsyn-09.txt [Open Web Ballot]
	Token:	Lars Eggert
SEC		DomainKeys Identified Mail (DKIM) Service Overview (Informational) - 2 of 3
		draft-ietf-dkim-overview-11.txt [Open Web Ballot]
	Token:	Pasi Eronen
TSV		RSVP Proxy Approaches (Informational) - 3 of 3
		draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt [Open Web Ballot]
		Note: Read this before the Protocol document
	Token:	Magnus Westerlund

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
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

3.3.3 For Action

Area	Date
INT		The Subnetwork Encapsulation and Adaptation Layer (SEAL) (Informational) - 1 of 2
		draft-templin-seal-23.txt [Open Web Ballot]
		Note: Brought back to the agenda because of desired status change (now Inf)
	Token:	Jari Arkko
GEN		Unintended Consequence of two NAT deployments with Overlapping Address Space (Informational) - 2 of 2
		draft-ford-behave-top-06.txt
	Token:	Russ Housley

4. Working Group Actions

4.1 WG Creation

4.1.1 Proposed for IETF Review
NONE

4.1.2 Proposed for Approval

Area	Date
APP	Apr 29	Yet Another Mail (yam) - 1 of 1
	Token:	Alexey

4.2 WG Rechartering

4.2.1 Under evaluation for IETF Review
NONE

4.2.2 Proposed for Approval
NONE

5. IAB News We Can Use

6. Management Issues

6.1 Revision 1.9 for ID-Checklist.html (Russ Housley)
6.2 Shepherd names in agendas (Jari Arkko)
6.3 Ballot Procedures (Russ Housley)

7. Working Group News

From wwwrun@core3.amsl.com Thu May 14 16:13:37 2009 Return-Path: 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 4D76828C108; Thu, 14 May 2009 16:13:37 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090514231337.4D76828C108@core3.amsl.com> Date: Thu, 14 May 2009 16:13:37 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for May 21, 2009 X-BeenThere: iesg-agenda-dist@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2009 23:13:37 -0000 INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the May 21, 2009 IESG Teleconference This agenda was generated at 16:13:37 EDT, May 14, 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-tsvwg-rsvp-proxy-proto-09.txt RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) - 1 of 3 Note: Please read the informational document draft-ietf-tsvwg-rsvp-proxy-approaches before this one! Token: Magnus Westerlund o draft-ietf-netlmm-pmip6-ipv4-support-12.txt IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) - 2 of 3 Token: Jari Arkko o draft-ietf-dccp-simul-open-08.txt DCCP Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal (Proposed Standard) - 3 of 3 Token: Lars Eggert 2.1.2 Returning Item o draft-ietf-pkix-3281update-05.txt An Internet Attribute Certificate Profile for Authorization (Proposed Standard) - 1 of 1 Token: Tim Polk 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item o draft-groves-megaco-pkgereg-03.txt H.248/MEGACO Registration Procedures (BCP) - 1 of 1 Note: IESG - when reviewing this, please consider the topic of if it is alright to register a "public" package when the specification is not publicly available. This came up as an IETF LC comment. Token: Cullen Jennings 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-tcpm-ecnsyn-09.txt Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) - 1 of 3 Token: Lars Eggert o draft-ietf-dkim-overview-11.txt DomainKeys Identified Mail (DKIM) Service Overview (Informational) - 2 of 3 Token: Pasi Eronen o draft-ietf-tsvwg-rsvp-proxy-approaches-07.txt RSVP Proxy Approaches (Informational) - 3 of 3 Note: Read this before the Protocol document Token: Magnus Westerlund 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 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 3.3.3 For Action o draft-templin-seal-23.txt The Subnetwork Encapsulation and Adaptation Layer (SEAL) (Informational) - 1 of 2 Note: Brought back to the agenda because of desired status change (now Inf) Token: Jari Arkko o draft-ford-behave-top-06.txt Unintended Consequence of two NAT deployments with Overlapping Address Space (Informational) - 2 of 2 Token: Russ Housley 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval o Yet Another Mail (yam) - 1 of 1 Token: Alexey 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 6.1 Revision 1.9 for ID-Checklist.html (Russ Housley) 6.2 Shepherd names in agendas (Jari Arkko) 6.3 Ballot Procedures (Russ Housley) 7. Agenda Working Group News From wwwrun@core3.amsl.com Thu May 28 15:22:57 2009 Return-Path: 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 808E63A6DB3; Thu, 28 May 2009 15:22:57 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/html; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090528222257.808E63A6DB3@core3.amsl.com> Date: Thu, 28 May 2009 15:22:57 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for June 4, 2009 X-BeenThere: iesg-agenda-dist@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:22:57 -0000 IESG Agenda

IESG Agenda

Good approximation of what will be included in the Agenda of next Telechat (2009-06-04).

1. Administrivia

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

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

2.1.2 Returning Item
NONE

2.2 Individual Submissions

2.2.1 New Item

Area	Date
APP		Internet Mail Architecture (Proposed Standard) - 1 of 1
		draft-crocker-email-arch-13.txt [Open Web Ballot]
		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

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

Area	Date
RAI		UA-Driven Privacy Mechanism for SIP (Informational) - 1 of 1
		draft-ietf-sip-ua-privacy-08.txt [Open Web Ballot]
	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

Area	Date
GEN		Unintended Consequence of two NAT deployments with Overlapping Address Space (Informational) - 1 of 1
		draft-ford-behave-top-06.txt [Open Web Ballot]
	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

Area	Date
TSV	May 27	Behavior Engineering for Hindrance Avoidance (behave) - 1 of 1
	Token:	Magnus

4.2.2 Proposed for Approval
NONE

5. IAB News We Can Use

6. Management Issues

6.1 RFC 4543 IANA allocations for IKEv1 (Pasi Eronen)
6.2 IESG Requirements to NomCom (Russ Housley)
6.3 Review of application/mp21 Media Type (Alexey Melnikov)
6.4 Review of application/3gpp-ims+xml Media Type (Alexey Melnikov)

7. Working Group News

From wwwrun@core3.amsl.com Thu May 28 15:22:57 2009 Return-Path: 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 876833A6E0D; Thu, 28 May 2009 15:22:57 -0700 (PDT) From: IESG Secretary To: iesg-agenda-dist@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20090528222257.876833A6E0D@core3.amsl.com> Date: Thu, 28 May 2009 15:22:57 -0700 (PDT) Subject: [IESG-AGENDA-DIST] IESG Telechat Agenda (Plain Text) for June 4, 2009 X-BeenThere: iesg-agenda-dist@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Distribution of IESG agendas List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 22:22:57 -0000 INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the June 4, 2009 IESG Teleconference This agenda was generated at 15:22:57 EDT, May 28, 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-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@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@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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 4.2.2 Proposed for Approval NONE 5. IAB News We can use 6. Management Issue 6.1 RFC 4543 IANA allocations for IKEv1 (Pasi Eronen) 6.2 IESG Requirements to NomCom (Russ Housley) 6.3 Review of application/mp21 Media Type (Alexey Melnikov) 6.4 Review of application/3gpp-ims+xml Media Type (Alexey Melnikov) 7. Agenda Working Group News