[IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for February 26, 2009

[IESG Secretary <[e-mail]>]

IESG Agenda

IESG Agenda

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

---

1. Administrivia

1.1 Roll Call
1.2 Bash the Agenda
1.3 Approval of the Minutes of the past telechat
1.4 List of Remaining Action Items from Last Telechat

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 RTG Dissemination of flow specification rules (Proposed Standard) - 1 of 2 http://www.ietf.org/internet-drafts/draft-ietf-idr-flow-spec-05.txt" rel="nofollow">draft-ietf-idr-flow-spec-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2997&filename=draft-ietf-idr-flow-spec" rel="nofollow">[Open Web Ballot] Token: David Ward TSV A One-Way Packet Duplication Metric (Proposed Standard) - 2 of 2 http://www.ietf.org/internet-drafts/draft-ietf-ippm-duplicate-07.txt" rel="nofollow">draft-ietf-ippm-duplicate-07.txt Token: Lars Eggert 2.1.2 Returning Item       Area Date RTG ForCES Protocol Specification (Proposed Standard) - 1 of 2 http://www.ietf.org/internet-drafts/draft-ietf-forces-protocol-21.txt" rel="nofollow">draft-ietf-forces-protocol-21.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2069&filename=draft-ietf-forces-protocol" rel="nofollow">[Open Web Ballot] Token: Ross Callon RTG The RPF Vector TLV (Proposed Standard) - 2 of 2 http://www.ietf.org/internet-drafts/draft-ietf-pim-rpf-vector-08.txt" rel="nofollow">draft-ietf-pim-rpf-vector-08.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2930&filename=draft-ietf-pim-rpf-vector" rel="nofollow">[Open Web Ballot] Token: David Ward 2.2 Individual Submissions           2.2.1 New Item       NONE 2.2.2 Returning Item       Area Date GEN IANA Allocation Guidelines for the Address Resolution Protocol (ARP) (Proposed Standard) - 1 of 1 http://www.ietf.org/internet-drafts/draft-arkko-arp-iana-rules-05.txt" rel="nofollow">draft-arkko-arp-iana-rules-05.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2949&filename=draft-arkko-arp-iana-rules" rel="nofollow">[Open Web Ballot] Token: Russ Housley 2.2.3 For Action       Area Date INT Extending ICMP for Interface and Next-hop Identification (Proposed Standard) - 1 of 1 http://www.ietf.org/internet-drafts/draft-atlas-icmp-unnumbered-06.txt" rel="nofollow">draft-atlas-icmp-unnumbered-06.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2662&filename=draft-atlas-icmp-unnumbered" rel="nofollow">[Open Web Ballot] Note: Needs to go back to the WG due to the IPR declaration Token: Jari Arkko

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 APP Downgrading mechanism for Email Address Internationalization (Experimental) - 1 of 3 http://www.ietf.org/internet-drafts/draft-ietf-eai-downgrade-11.txt" rel="nofollow">draft-ietf-eai-downgrade-11.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2915&filename=draft-ietf-eai-downgrade" rel="nofollow">[Open Web Ballot] Note: Harald Alvestrand is document shepherd Token: Chris Newman RTG Requirements for the Conversion Between Permanent Connections and Switched Connections in a Generalized Multiprotocol Label Switching (GMPLS) Network (Informational) - 2 of 3 http://www.ietf.org/internet-drafts/draft-ietf-ccamp-pc-and-sc-reqs-06.txt" rel="nofollow">draft-ietf-ccamp-pc-and-sc-reqs-06.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2941&filename=draft-ietf-ccamp-pc-and-sc-reqs" rel="nofollow">[Open Web Ballot] Token: Ross Callon RTG Description of the RSVP-TE Graceful Restart Procedures (Informational) - 3 of 3 http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gr-description-04.txt" rel="nofollow">draft-ietf-ccamp-gr-description-04.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2942&filename=draft-ietf-ccamp-gr-description" rel="nofollow">[Open Web Ballot] Token: Ross Callon 3.1.2 Returning Item       Area Date INT Requirements for Multicast Support in Virtual Private LAN Services (Informational) - 1 of 1 http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-mcast-reqts-07.txt" rel="nofollow">draft-ietf-l2vpn-vpls-mcast-reqts-07.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=2611&filename=draft-ietf-l2vpn-vpls-mcast-reqts" rel="nofollow">[Open Web Ballot] Note: Bringing back to telechat to get attention on remaining discusses. Token: Mark Townsley 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       Area Date GEN Analysis of Inter-Domain Routing Requirements and History (Historic) - 1 of 2 http://www.ietf.org/internet-drafts/draft-irtf-routing-history-09.txt" rel="nofollow">draft-irtf-routing-history-09.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=3005&filename=draft-irtf-routing-history" rel="nofollow">[Open Web Ballot] Token: Ross Callon GEN A Set of Possible Requirements for a Future Routing Architecture (Historic) - 2 of 2 http://www.ietf.org/internet-drafts/draft-irtf-routing-reqs-10.txt" rel="nofollow">draft-irtf-routing-reqs-10.txt https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&ballot_id=3006&filename=draft-irtf-routing-reqs" rel="nofollow">[Open Web Ballot] Token: Ross Callon

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                     NONE           4.2.2 Proposed for Approval                     NONE

5. IAB News We Can Use

6. Management Issues

6.1 Request for ATOM Link Relation [IANA #209057] (Michelle Cotton)
6.2 late IPR declarations (Jari Arkko)
6.3 Document Submission cutoff for IETF 74 (Tim Polk)
6.4 IESG Statement on Activities that are OBE (Russ Housley)
6.5 Potential Notes in EAP-FAST Documents (Russ Housley)

7. Working Group News