headers
IESG Secretary | 26 Nov 2008 23:28
Picon
Favicon

IESG Telechat Agenda (HTML) for December 4, 2008

IESG Agenda

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

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       AreaDate
TSV NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11
draft-ietf-nfsv4-minorversion1-26.txt [Open Web Ballot]
Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.
Token: Lars Eggert
TSV pNFS Block/Volume Layout (Proposed Standard) - 2 of 11
draft-ietf-nfsv4-pnfs-block-10.txt [Open Web Ballot]
Token: Lars Eggert
TSV Object-based pNFS Operations (Proposed Standard) - 3 of 11
draft-ietf-nfsv4-pnfs-obj-09.txt [Open Web Ballot]
Token: Lars Eggert
APP Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11
draft-ietf-sieve-notify-mailto-09.txt [Open Web Ballot]
Note: Barry Leiba to be the expert reviewer for the registry this creates.
Token: Lisa Dusseault
INT Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11
draft-ietf-mip4-dsmipv4-08.txt [Open Web Ballot]
Token: Jari Arkko
APP Extended URLFETCH for binary and converted parts (Proposed Standard) - 6 of 11
draft-cridland-urlfetch-binary-03.txt [Open Web Ballot]
Note: Eric Burger is document shepherd.  Note this is a lemonade WG document despite the name.
Token: Chris Newman
APP The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11
draft-ietf-lemonade-imap-notify-07.txt [Open Web Ballot]
Note: Eric Burger is document shepherd
Token: Chris Newman
INT Measures for making DNS more resilient against forged answers (Proposed Standard) - 8 of 11
draft-ietf-dnsext-forgery-resilience-09.txt [Open Web Ballot]
Token: Mark Townsley
INT Multiple Care-of Addresses Registration (Proposed Standard) - 9 of 11
draft-ietf-monami6-multiplecoa-10.txt [Open Web Ballot]
Token: Jari Arkko
TSV NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11
draft-ietf-nfsv4-minorversion1-dot-x-09.txt [Open Web Ballot]
Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.
Token: Lars Eggert
INT Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11
draft-ietf-6man-reserved-iids-01.txt [Open Web Ballot]
Token: Jari Arkko
2.1.2 Returning Item       AreaDate
TSV GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 1
draft-ietf-nsis-ntlp-17.txt [Open Web Ballot]
Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please indicate in the comment field that you have performed this re-evaluation and also include some motivation behind your decision.
Token: Magnus Westerlund

2.2 Individual Submissions

          2.2.1 New Item       AreaDate
GEN IESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1
draft-housley-iesg-rfc3932bis-06.txt [Open Web Ballot]
Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html
Token: Jari Arkko
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
      NONE
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       AreaDate
GEN IANA Allocation Guidelines for the Address Resolution Protocol (ARP) (Informational) - 1 of 1
draft-arkko-arp-iana-rules-01.txt [Open Web Ballot]
Token: Russ Housley
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       AreaDate
APP DNS Blacklists and Whitelists (Informational) - 1 of 1
draft-irtf-asrg-dnsbl-08.txt
Note: Propose to respond "1. The IESG has not found any conflict between this document and IETF work."
Token: Lisa Dusseault
3.3.2 Returning Item
      NONE
3.3.3 For Action       AreaDate
INT PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1
draft-bberry-rfc4938bis-00.txt
Note: Independent submission, being reviewed by pppext
Token: Mark Townsley

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 CEA Media Type Application "cea-2018+xml" (Russ Housley)
6.2 IANA expert for TLS registries (Pasi Eronen)
6.3 Request to the RFC Editor to expedite processing of the CAPWAP Protocol Specification (Dan Romascanu)
6.4 Approval of application/emma+xml media type (Chris Newman)
6.5 Telechat schedule for January (Tim Polk)

7. Working Group News

<div>
<h1>IESG Agenda</h1>
Good approximation of what will be included in the Agenda of next Telechat (2008-12-04).<br><br><h2>1. Administrivia</h2>
<ul>
1.1 Roll Call<br>
1.2 Bash the Agenda<br>
1.3 Approval of the Minutes of the past telechat<br>
1.4 List of Remaining Action Items from Last Telechat<br>
</ul>
<p></p>
<p>
</p>
<h2>2. Protocol Actions
</h2>
<blockquote>
Reviews should focus on these questions: "Is this document a<br>
reasonable basis on which to build the salient part of the Internet<br>
infrastructure? If not, what changes would make it so?"
</blockquote>

  
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

  <h3>2.1 WG Submissions</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
2.1.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-minorversion1-26.txt">draft-ietf-nfsv4-minorversion1-26.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2135&amp;filename=draft-ietf-nfsv4-minorversion1">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.<br>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>pNFS Block/Volume Layout (Proposed Standard) - 2 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-pnfs-block-10.txt">draft-ietf-nfsv4-pnfs-block-10.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2136&amp;filename=draft-ietf-nfsv4-pnfs-block">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>Object-based pNFS Operations (Proposed Standard) - 3 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-pnfs-obj-09.txt">draft-ietf-nfsv4-pnfs-obj-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2137&amp;filename=draft-ietf-nfsv4-pnfs-obj">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-mailto-09.txt">draft-ietf-sieve-notify-mailto-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2644&amp;filename=draft-ietf-sieve-notify-mailto">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Barry Leiba to be the expert reviewer for the registry this creates.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lisa <at> osafoundation.org">Lisa Dusseault</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-mip4-dsmipv4-08.txt">draft-ietf-mip4-dsmipv4-08.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2733&amp;filename=draft-ietf-mip4-dsmipv4">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>Extended URLFETCH for binary and converted parts (Proposed Standard) - 6 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-cridland-urlfetch-binary-03.txt">draft-cridland-urlfetch-binary-03.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2816&amp;filename=draft-cridland-urlfetch-binary">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Eric Burger is document shepherd.&nbsp; Note this is a lemonade WG document despite the name.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:chris.newman <at> sun.com">Chris Newman</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-lemonade-imap-notify-07.txt">draft-ietf-lemonade-imap-notify-07.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2852&amp;filename=draft-ietf-lemonade-imap-notify">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Eric Burger is document shepherd</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:chris.newman <at> sun.com">Chris Newman</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Measures for making DNS more resilient against forged answers (Proposed Standard) - 8 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-dnsext-forgery-resilience-09.txt">draft-ietf-dnsext-forgery-resilience-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2871&amp;filename=draft-ietf-dnsext-forgery-resilience">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:townsley <at> cisco.com">Mark Townsley</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Multiple Care-of Addresses Registration (Proposed Standard) - 9 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-monami6-multiplecoa-10.txt">draft-ietf-monami6-multiplecoa-10.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2878&amp;filename=draft-ietf-monami6-multiplecoa">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-minorversion1-dot-x-09.txt">draft-ietf-nfsv4-minorversion1-dot-x-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2892&amp;filename=draft-ietf-nfsv4-minorversion1-dot-x">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-6man-reserved-iids-01.txt">draft-ietf-6man-reserved-iids-01.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2954&amp;filename=draft-ietf-6man-reserved-iids">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
</table>2.1.2 Returning Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-17.txt">draft-ietf-nsis-ntlp-17.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=1546&amp;filename=draft-ietf-nsis-ntlp">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please indicate in the comment field that you have performed this re-evaluation and also include some motivation behind your decision. <br>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:magnus.westerlund <at> ericsson.com">Magnus Westerlund</a></td>
</tr>
</table>
</td>
</tr></table>
<h3>2.2 Individual Submissions</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
2.2.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>GEN</td>
<td nowrap></td>
<td>IESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-housley-iesg-rfc3932bis-06.txt">draft-housley-iesg-rfc3932bis-06.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2895&amp;filename=draft-housley-iesg-rfc3932bis">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
</table>2.2.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>
</td>
</tr></table>
<h2>3. Document Actions</h2>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

  <h3>3.1 WG Submissions
</h3>
<blockquote>
Reviews should focus on these questions: "Is this document a reasonable<br>
contribution to the area of Internet engineering which it covers? If<br>
not, what changes would make it so?"<br>
</blockquote>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
3.1.1 New Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>3.1.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>
<h3>3.2 Individual Submissions Via AD
</h3>
<blockquote>
Reviews should focus on these questions: "Is this document a reasonable<br>
contribution to the area of Internet engineering which it covers? If<br>
not, what changes would make it so?"<br>
</blockquote>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
3.2.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>GEN</td>
<td nowrap></td>
<td>IANA Allocation Guidelines for the Address Resolution Protocol (ARP) (Informational) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-arkko-arp-iana-rules-01.txt">draft-arkko-arp-iana-rules-01.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2949&amp;filename=draft-arkko-arp-iana-rules">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:housley <at> vigilsec.com">Russ Housley</a></td>
</tr>
</table>3.2.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>
<h3>3.3 Independent Submissions Via RFC Editor
</h3>
<blockquote>
The IESG will use RFC 3932 responses: 1) The IESG has not<br>
found any conflict between this document and IETF work; 2) The<br>
IESG thinks that this work is related to IETF work done in WG<br>
&lt;X&gt;, but this does not prevent publishing; 3) The IESG thinks<br>
that publication is harmful to work in WG &lt;X&gt; and recommends<br>
not publishing at this time; 4) The IESG thinks that this<br>
document violates the IETF procedures for &lt;X&gt; and should<br>
therefore not be published without IETF review and IESG<br>
approval; 5) The IESG thinks that this document extends an<br>
IETF protocol in a way that requires IETF review and should<br>
therefore not be published without IETF review and IESG approval.<br><br>
The document shepherd must propose one of these responses in<br>
the Data Tracker note and supply complete text in the IESG<br>
Note portion of the write-up. The Area Director ballot positions<br>
indicate consensus with the response proposed by the<br>
document shepherd.<br><br>
Other matters may be recorded in comments, and the comments will<br>
be passed on to the RFC Editor as community review of the document.
</blockquote>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
3.3.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>DNS Blacklists and Whitelists (Informational) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-irtf-asrg-dnsbl-08.txt">draft-irtf-asrg-dnsbl-08.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Propose to respond "1. The IESG has not found any conflict between this document and IETF work."</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lisa <at> osafoundation.org">Lisa Dusseault</a></td>
</tr>
</table>3.3.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>3.3.3 For Action
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-bberry-rfc4938bis-00.txt">draft-bberry-rfc4938bis-00.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Independent submission, being reviewed by pppext</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:townsley <at> cisco.com">Mark Townsley</a></td>
</tr>
</table>
</td>
</tr></table>
<h2>4. Working Group Actions</h2>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

<h3>4.1 WG Creation</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.1.1 Proposed for IETF Review<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.1.2 Proposed for Approval<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
</td>
</tr></table>
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

<h3>4.2 WG Rechartering</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.2.1 Under evaluation for IETF Review<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.2.2 Proposed for Approval<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
</td>
</tr></table>
<p></p>
<p>
</p>
<h2>5. IAB News We Can Use</h2>
<p></p>
<p>
</p>
<h2> 6. Management Issues</h2>
6.1 CEA Media Type Application "cea-2018+xml" (Russ Housley)<br>6.2 IANA expert for TLS registries (Pasi Eronen)<br>6.3 Request to the RFC Editor to expedite processing of the CAPWAP Protocol Specification (Dan Romascanu)<br>6.4 Approval of application/emma+xml media type (Chris Newman)<br>6.5 Telechat schedule for January (Tim Polk)<br><p></p>
<p>
</p>
<h2>7. Working Group News</h2>
<p>
</p>
</div>
Permalink | Reply | 0 comments |
headers
IESG Secretary | 26 Nov 2008 23:28
Picon
Favicon

IESG Telechat Agenda (Plain Text) for December 4, 2008


          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the December 4, 2008 IESG Teleconference

This agenda was generated at 14:28:36 EDT, November 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-nfsv4-minorversion1-26.txt
    NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11 
    Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.. 
    Token: Lars Eggert
  o draft-ietf-nfsv4-pnfs-block-10.txt
    pNFS Block/Volume Layout (Proposed Standard) - 2 of 11 
    Token: Lars Eggert
  o draft-ietf-nfsv4-pnfs-obj-09.txt
    Object-based pNFS Operations (Proposed Standard) - 3 of 11 
    Token: Lars Eggert
  o draft-ietf-sieve-notify-mailto-09.txt
    Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11 
    Note: Barry Leiba to be the expert reviewer for the registry this creates. 
    Token: Lisa Dusseault
  o draft-ietf-mip4-dsmipv4-08.txt
    Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11 
    Token: Jari Arkko
  o draft-cridland-urlfetch-binary-03.txt
    Extended URLFETCH for binary and converted parts (Proposed Standard) - 6 of 
    11 
    Note: Eric Burger is document shepherd.&nbsp; Note this is a lemonade WG 
    document despite the name. 
    Token: Chris Newman
  o draft-ietf-lemonade-imap-notify-07.txt
    The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11 
    Note: Eric Burger is document shepherd 
    Token: Chris Newman
  o draft-ietf-dnsext-forgery-resilience-09.txt
    Measures for making DNS more resilient against forged answers (Proposed 
    Standard) - 8 of 11 
    Token: Mark Townsley
  o draft-ietf-monami6-multiplecoa-10.txt
    Multiple Care-of Addresses Registration (Proposed Standard) - 9 of 11 
    Token: Jari Arkko
  o draft-ietf-nfsv4-minorversion1-dot-x-09.txt
    NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11 
    Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd. 
    Token: Lars Eggert
  o draft-ietf-6man-reserved-iids-01.txt
    Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11 
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-nsis-ntlp-17.txt
    GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 1 
    Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please 
    indicate in the comment field that you have performed this re-evaluation 
    and also include some motivation behind your decision. . 
    Token: Magnus Westerlund

2.2 Individual Submissions
2.2.1 New Item
  o draft-housley-iesg-rfc3932bis-06.txt
    IESG Procedures for Handling of Independent and IRTF Stream Submissions 
    (BCP) - 1 of 1 
    Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html 
    Token: Jari Arkko

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
NONE
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-arkko-arp-iana-rules-01.txt
    IANA Allocation Guidelines for the Address Resolution Protocol (ARP) 
    (Informational) - 1 of 1 
    Token: Russ Housley

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-irtf-asrg-dnsbl-08.txt
    DNS Blacklists and Whitelists (Informational) - 1 of 1 
    Note: Propose to respond "1. The IESG has not found any conflict between 
    this document and IETF work." 
    Token: Lisa Dusseault

3.3.2 Returning Item
NONE
3.3.3 For Action
  o draft-bberry-rfc4938bis-00.txt
    PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics 
    (Informational) - 1 of 1 
    Note: Independent submission, being reviewed by pppext 
    Token: Mark Townsley

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 Issue

 6.1 CEA Media Type Application "cea-2018+xml" (Russ Housley)

 6.2 IANA expert for TLS registries (Pasi Eronen)

 6.3 Request to the RFC Editor to expedite processing of the CAPWAP Protocol Specification (Dan Romascanu)

 6.4 Approval of application/emma+xml media type (Chris Newman)

 6.5 Telechat schedule for January (Tim Polk)

7. Agenda Working Group News
Permalink | Reply | 0 comments |
headers
IESG Secretary | 1 Dec 2008 15:17
Picon
Favicon

IESG Telechat Agenda (HTML) for December 4, 2008

IESG Agenda

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

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       AreaDate
TSV NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11
draft-ietf-nfsv4-minorversion1-26.txt [Open Web Ballot]
Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.
Token: Lars Eggert
TSV pNFS Block/Volume Layout (Proposed Standard) - 2 of 11
draft-ietf-nfsv4-pnfs-block-10.txt [Open Web Ballot]
Token: Lars Eggert
TSV Object-based pNFS Operations (Proposed Standard) - 3 of 11
draft-ietf-nfsv4-pnfs-obj-09.txt [Open Web Ballot]
Token: Lars Eggert
APP Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11
draft-ietf-sieve-notify-mailto-09.txt [Open Web Ballot]
Note: Barry Leiba to be the expert reviewer for the registry this creates.
Token: Lisa Dusseault
INT Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11
draft-ietf-mip4-dsmipv4-08.txt [Open Web Ballot]
Token: Jari Arkko
APP Extended URLFETCH for binary and converted parts (Proposed Standard) - 6 of 11
draft-cridland-urlfetch-binary-03.txt [Open Web Ballot]
Note: Eric Burger is document shepherd.  Note this is a lemonade WG document despite the name.
Token: Chris Newman
APP The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11
draft-ietf-lemonade-imap-notify-07.txt [Open Web Ballot]
Note: Eric Burger is document shepherd
Token: Chris Newman
INT Measures for making DNS more resilient against forged answers (Proposed Standard) - 8 of 11
draft-ietf-dnsext-forgery-resilience-09.txt [Open Web Ballot]
Token: Mark Townsley
INT Multiple Care-of Addresses Registration (Proposed Standard) - 9 of 11
draft-ietf-monami6-multiplecoa-10.txt [Open Web Ballot]
Token: Jari Arkko
TSV NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11
draft-ietf-nfsv4-minorversion1-dot-x-09.txt [Open Web Ballot]
Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.
Token: Lars Eggert
INT Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11
draft-ietf-6man-reserved-iids-01.txt [Open Web Ballot]
Token: Jari Arkko
2.1.2 Returning Item       AreaDate
TSV GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 1
draft-ietf-nsis-ntlp-17.txt [Open Web Ballot]
Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please indicate in the comment field that you have performed this re-evaluation and also include some motivation behind your decision.
Token: Magnus Westerlund

2.2 Individual Submissions

          2.2.1 New Item       AreaDate
GEN IESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1
draft-housley-iesg-rfc3932bis-06.txt [Open Web Ballot]
Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html
Token: Jari Arkko
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
      NONE
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       AreaDate
INT Requirements for Replacing AppleTalk (Informational) - 1 of 2
draft-cheshire-dnsext-nbp-07.txt
Token: Mark Townsley
GEN IANA Allocation Guidelines for the Address Resolution Protocol (ARP) (Informational) - 2 of 2
draft-arkko-arp-iana-rules-03.txt [Open Web Ballot]
Token: Russ Housley
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       AreaDate
APP DNS Blacklists and Whitelists (Informational) - 1 of 1
draft-irtf-asrg-dnsbl-08.txt
Note: Propose to respond "1. The IESG has not found any conflict between this document and IETF work."
Token: Lisa Dusseault
3.3.2 Returning Item
      NONE
3.3.3 For Action       AreaDate
INT PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1
draft-bberry-rfc4938bis-00.txt
Token: Mark Townsley

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 CEA Media Type Application "cea-2018+xml" (Russ Housley)
6.2 IANA expert for TLS registries (Pasi Eronen)
6.3 Request to the RFC Editor to expedite processing of the CAPWAP Protocol Specification (Dan Romascanu)
6.4 Approval of application/emma+xml media type (Chris Newman)
6.5 Telechat schedule for January (Tim Polk)

7. Working Group News

<div>
<h1>IESG Agenda</h1>
Good approximation of what will be included in the Agenda of next Telechat (2008-12-04).<br><br><h2>1. Administrivia</h2>
<ul>
1.1 Roll Call<br>
1.2 Bash the Agenda<br>
1.3 Approval of the Minutes of the past telechat<br>
1.4 List of Remaining Action Items from Last Telechat<br>
</ul>
<p></p>
<p>
</p>
<h2>2. Protocol Actions
</h2>
<blockquote>
Reviews should focus on these questions: "Is this document a<br>
reasonable basis on which to build the salient part of the Internet<br>
infrastructure? If not, what changes would make it so?"
</blockquote>

  
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

  <h3>2.1 WG Submissions</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
2.1.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-minorversion1-26.txt">draft-ietf-nfsv4-minorversion1-26.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2135&amp;filename=draft-ietf-nfsv4-minorversion1">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.<br>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>pNFS Block/Volume Layout (Proposed Standard) - 2 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-pnfs-block-10.txt">draft-ietf-nfsv4-pnfs-block-10.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2136&amp;filename=draft-ietf-nfsv4-pnfs-block">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>Object-based pNFS Operations (Proposed Standard) - 3 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-pnfs-obj-09.txt">draft-ietf-nfsv4-pnfs-obj-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2137&amp;filename=draft-ietf-nfsv4-pnfs-obj">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-mailto-09.txt">draft-ietf-sieve-notify-mailto-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2644&amp;filename=draft-ietf-sieve-notify-mailto">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Barry Leiba to be the expert reviewer for the registry this creates.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lisa <at> osafoundation.org">Lisa Dusseault</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-mip4-dsmipv4-08.txt">draft-ietf-mip4-dsmipv4-08.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2733&amp;filename=draft-ietf-mip4-dsmipv4">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>Extended URLFETCH for binary and converted parts (Proposed Standard) - 6 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-cridland-urlfetch-binary-03.txt">draft-cridland-urlfetch-binary-03.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2816&amp;filename=draft-cridland-urlfetch-binary">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Eric Burger is document shepherd.&nbsp; Note this is a lemonade WG document despite the name.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:chris.newman <at> sun.com">Chris Newman</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-lemonade-imap-notify-07.txt">draft-ietf-lemonade-imap-notify-07.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2852&amp;filename=draft-ietf-lemonade-imap-notify">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Eric Burger is document shepherd</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:chris.newman <at> sun.com">Chris Newman</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Measures for making DNS more resilient against forged answers (Proposed Standard) - 8 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-dnsext-forgery-resilience-09.txt">draft-ietf-dnsext-forgery-resilience-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2871&amp;filename=draft-ietf-dnsext-forgery-resilience">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:townsley <at> cisco.com">Mark Townsley</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Multiple Care-of Addresses Registration (Proposed Standard) - 9 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-monami6-multiplecoa-10.txt">draft-ietf-monami6-multiplecoa-10.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2878&amp;filename=draft-ietf-monami6-multiplecoa">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-minorversion1-dot-x-09.txt">draft-ietf-nfsv4-minorversion1-dot-x-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2892&amp;filename=draft-ietf-nfsv4-minorversion1-dot-x">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lars.eggert <at> nokia.com">Lars Eggert</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-6man-reserved-iids-01.txt">draft-ietf-6man-reserved-iids-01.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2954&amp;filename=draft-ietf-6man-reserved-iids">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
</table>2.1.2 Returning Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>TSV</td>
<td nowrap></td>
<td>GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-nsis-ntlp-17.txt">draft-ietf-nsis-ntlp-17.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=1546&amp;filename=draft-ietf-nsis-ntlp">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please indicate in the comment field that you have performed this re-evaluation and also include some motivation behind your decision. <br>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:magnus.westerlund <at> ericsson.com">Magnus Westerlund</a></td>
</tr>
</table>
</td>
</tr></table>
<h3>2.2 Individual Submissions</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
2.2.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>GEN</td>
<td nowrap></td>
<td>IESG Procedures for Handling of Independent and IRTF Stream Submissions (BCP) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-housley-iesg-rfc3932bis-06.txt">draft-housley-iesg-rfc3932bis-06.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2895&amp;filename=draft-housley-iesg-rfc3932bis">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jari.arkko <at> piuha.net">Jari Arkko</a></td>
</tr>
</table>2.2.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>
</td>
</tr></table>
<h2>3. Document Actions</h2>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

  <h3>3.1 WG Submissions
</h3>
<blockquote>
Reviews should focus on these questions: "Is this document a reasonable<br>
contribution to the area of Internet engineering which it covers? If<br>
not, what changes would make it so?"<br>
</blockquote>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
3.1.1 New Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>3.1.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>
<h3>3.2 Individual Submissions Via AD
</h3>
<blockquote>
Reviews should focus on these questions: "Is this document a reasonable<br>
contribution to the area of Internet engineering which it covers? If<br>
not, what changes would make it so?"<br>
</blockquote>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
3.2.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Requirements for Replacing AppleTalk (Informational) - 1 of 2</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-cheshire-dnsext-nbp-07.txt">draft-cheshire-dnsext-nbp-07.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:townsley <at> cisco.com">Mark Townsley</a></td>
</tr>
<tr>
<td></td>
<td>GEN</td>
<td nowrap></td>
<td>IANA Allocation Guidelines for the Address Resolution Protocol (ARP) (Informational) - 2 of 2</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-arkko-arp-iana-rules-03.txt">draft-arkko-arp-iana-rules-03.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2949&amp;filename=draft-arkko-arp-iana-rules">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:housley <at> vigilsec.com">Russ Housley</a></td>
</tr>
</table>3.2.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>
<h3>3.3 Independent Submissions Via RFC Editor
</h3>
<blockquote>
The IESG will use RFC 3932 responses: 1) The IESG has not<br>
found any conflict between this document and IETF work; 2) The<br>
IESG thinks that this work is related to IETF work done in WG<br>
&lt;X&gt;, but this does not prevent publishing; 3) The IESG thinks<br>
that publication is harmful to work in WG &lt;X&gt; and recommends<br>
not publishing at this time; 4) The IESG thinks that this<br>
document violates the IETF procedures for &lt;X&gt; and should<br>
therefore not be published without IETF review and IESG<br>
approval; 5) The IESG thinks that this document extends an<br>
IETF protocol in a way that requires IETF review and should<br>
therefore not be published without IETF review and IESG approval.<br><br>
The document shepherd must propose one of these responses in<br>
the Data Tracker note and supply complete text in the IESG<br>
Note portion of the write-up. The Area Director ballot positions<br>
indicate consensus with the response proposed by the<br>
document shepherd.<br><br>
Other matters may be recorded in comments, and the comments will<br>
be passed on to the RFC Editor as community review of the document.
</blockquote>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>
3.3.1 New Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>DNS Blacklists and Whitelists (Informational) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-irtf-asrg-dnsbl-08.txt">draft-irtf-asrg-dnsbl-08.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Propose to respond "1. The IESG has not found any conflict between this document and IETF work."</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lisa <at> osafoundation.org">Lisa Dusseault</a></td>
</tr>
</table>3.3.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</td>
</tr></table>3.3.3 For Action
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics (Informational) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-bberry-rfc4938bis-00.txt">draft-bberry-rfc4938bis-00.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:townsley <at> cisco.com">Mark Townsley</a></td>
</tr>
</table>
</td>
</tr></table>
<h2>4. Working Group Actions</h2>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

<h3>4.1 WG Creation</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.1.1 Proposed for IETF Review<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.1.2 Proposed for Approval<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
</td>
</tr></table>
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

<h3>4.2 WG Rechartering</h3>

<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.2.1 Under evaluation for IETF Review<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
<table border="0" cellspacing="0" cellpadding="0"><tr>
<td>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </td>
<td>

4.2.2 Proposed for Approval<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;  NONE
</td>
</tr></table>
</td>
</tr></table>
<p></p>
<p>
</p>
<h2>5. IAB News We Can Use</h2>
<p></p>
<p>
</p>
<h2> 6. Management Issues</h2>
6.1 CEA Media Type Application "cea-2018+xml" (Russ Housley)<br>6.2 IANA expert for TLS registries (Pasi Eronen)<br>6.3 Request to the RFC Editor to expedite processing of the CAPWAP Protocol Specification (Dan Romascanu)<br>6.4 Approval of application/emma+xml media type (Chris Newman)<br>6.5 Telechat schedule for January (Tim Polk)<br><p></p>
<p>
</p>
<h2>7. Working Group News</h2>
<p>
</p>
</div>
Permalink | Reply | 0 comments |
headers
IESG Secretary | 1 Dec 2008 15:17
Picon
Favicon

IESG Telechat Agenda (Plain Text) for December 4, 2008


          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the December 4, 2008 IESG Teleconference

This agenda was generated at 6:17:8 EDT, December 1, 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-nfsv4-minorversion1-26.txt
    NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11 
    Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd.. 
    Token: Lars Eggert
  o draft-ietf-nfsv4-pnfs-block-10.txt
    pNFS Block/Volume Layout (Proposed Standard) - 2 of 11 
    Token: Lars Eggert
  o draft-ietf-nfsv4-pnfs-obj-09.txt
    Object-based pNFS Operations (Proposed Standard) - 3 of 11 
    Token: Lars Eggert
  o draft-ietf-sieve-notify-mailto-09.txt
    Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11 
    Note: Barry Leiba to be the expert reviewer for the registry this creates. 
    Token: Lisa Dusseault
  o draft-ietf-mip4-dsmipv4-08.txt
    Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11 
    Token: Jari Arkko
  o draft-cridland-urlfetch-binary-03.txt
    Extended URLFETCH for binary and converted parts (Proposed Standard) - 6 of 
    11 
    Note: Eric Burger is document shepherd.&nbsp; Note this is a lemonade WG 
    document despite the name. 
    Token: Chris Newman
  o draft-ietf-lemonade-imap-notify-07.txt
    The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11 
    Note: Eric Burger is document shepherd 
    Token: Chris Newman
  o draft-ietf-dnsext-forgery-resilience-09.txt
    Measures for making DNS more resilient against forged answers (Proposed 
    Standard) - 8 of 11 
    Token: Mark Townsley
  o draft-ietf-monami6-multiplecoa-10.txt
    Multiple Care-of Addresses Registration (Proposed Standard) - 9 of 11 
    Token: Jari Arkko
  o draft-ietf-nfsv4-minorversion1-dot-x-09.txt
    NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11 
    Note: Brian Pawslowski (beepy <at> netapp.com) is the document shepherd. 
    Token: Lars Eggert
  o draft-ietf-6man-reserved-iids-01.txt
    Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11 
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-nsis-ntlp-17.txt
    GIST: General Internet Signalling Transport (Proposed Standard) - 1 of 1 
    Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN please 
    indicate in the comment field that you have performed this re-evaluation 
    and also include some motivation behind your decision. . 
    Token: Magnus Westerlund

2.2 Individual Submissions
2.2.1 New Item
  o draft-housley-iesg-rfc3932bis-06.txt
    IESG Procedures for Handling of Independent and IRTF Stream Submissions 
    (BCP) - 1 of 1 
    Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html 
    Token: Jari Arkko

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
NONE
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-cheshire-dnsext-nbp-07.txt
    Requirements for Replacing AppleTalk (Informational) - 1 of 2 
    Token: Mark Townsley
  o draft-arkko-arp-iana-rules-03.txt
    IANA Allocation Guidelines for the Address Resolution Protocol (ARP) 
    (Informational) - 2 of 2 
    Token: Russ Housley

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-irtf-asrg-dnsbl-08.txt
    DNS Blacklists and Whitelists (Informational) - 1 of 1 
    Note: Propose to respond "1. The IESG has not found any conflict between 
    this document and IETF work." 
    Token: Lisa Dusseault

3.3.2 Returning Item
NONE
3.3.3 For Action
  o draft-bberry-rfc4938bis-00.txt
    PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link Metrics 
    (Informational) - 1 of 1 
    Token: Mark Townsley

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 Issue

 6.1 CEA Media Type Application "cea-2018+xml" (Russ Housley)

 6.2 IANA expert for TLS registries (Pasi Eronen)

 6.3 Request to the RFC Editor to expedite processing of the CAPWAP Protocol Specification (Dan Romascanu)

 6.4 Approval of application/emma+xml media type (Chris Newman)

 6.5 Telechat schedule for January (Tim Polk)

7. Agenda Working Group News
Permalink | Reply | 0 comments |

Gmane