IESG Secretary | 14 Dec 01:11 2007
Picon

IESG Telechat Agenda (HTML) for December 20, 2007

IESG Agenda

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

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
SEC Three-Document ballot: [Open Web Ballot] - 1 of 10
Certificate Management Messages over CMS (Proposed Standard) - 1 of 10
draft-ietf-pkix-2797-bis-06.txt
Note: PROTO Shepherd: Stefan Santesson <stefans <at> microsoft.com>
Certificate Managmement Messages over CMS (CMC): Complience Requirements (Proposed Standard)
draft-ietf-pkix-cmc-compl-05.txt
Note: PROTO Shepherd: Stefan Santesson <stefans <at> microsoft.com>
Certificate Management over CMS (CMC): Transport Protocols (Proposed Standard)
draft-ietf-pkix-cmc-trans-07.txt
Note: PROTO Shepherd: Stefan Santesson <stefans <at> microsoft.com>
Token: Tim Polk
INT Hash Based Addresses (HBA) (Proposed Standard) - 2 of 10
draft-ietf-shim6-hba-04.txt [Open Web Ballot]
Note: Please also read draft-ietf-shim6-applicability
Mark Townsley to handle any IPR questions in AD review/IETF LC/IESG, if any
Document Shepherd is Geoff Huston <gih <at> apnic.net>
Token: Jari Arkko
INT Failure Detection and Locator Pair Exploration Protocol for IPv6 Multihoming (Proposed Standard) - 3 of 10
draft-ietf-shim6-failure-detection-09.txt
Note: Please also read draft-ietf-shim6-applicability
Mark is handling this for Jari as he is an author
Token: Mark Townsley
INT Shim6: Level 3 Multihoming Shim Protocol for IPv6 (Proposed Standard) - 4 of 10
draft-ietf-shim6-proto-09.txt [Open Web Ballot]
Note: Please also read draft-ietf-shim6-applicability
Document Shepherd is Geoff Huston <gih <at> apnic.net>
Token: Jari Arkko
INT Domain Name System (DNS) IANA Considerations (BCP) - 5 of 10
draft-ietf-dnsext-2929bis-06.txt [Open Web Ballot]
Token: Mark Townsley
SEC Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (Proposed Standard) - 6 of 10
draft-ietf-pkix-rfc3280bis-09.txt
Note: new version expected to be submitted Friday to address last call comments
Token: Sam Hartman
APP SIEVE Email Filtering: Extension for Notifications (Proposed Standard) - 7 of 10
draft-ietf-sieve-notify-11.txt [Open Web Ballot]
Token: Lisa Dusseault
APP Sieve Notification Mechanism: xmpp (Proposed Standard) - 8 of 10
draft-ietf-sieve-notify-xmpp-07.txt
Token: Lisa Dusseault
SEC Multicast Extensions to the Security Architecture for the Internet Protocol (Proposed Standard) - 9 of 10
draft-ietf-msec-ipsec-extensions-07.txt [Open Web Ballot]
Note: Lakshminath Dondeti is the proto shepherd.
Token: Tim Polk
RAI A Framework for Consent-based Communications in the Session Initiation Protocol (SIP) (Proposed Standard) - 10 of 10
draft-ietf-sip-consent-framework-03.txt [Open Web Ballot]
Note: Keith Drage is the document shepherd
Token: Cullen Jennings
2.1.2 Returning Item
      NONE

2.2 Individual Submissions

          2.2.1 New Item       AreaDate
INT Oct 3 IPv4 Address Conflict Detection (Proposed Standard) - 1 of 1
draft-cheshire-ipv4-acd-05.txt [Open Text Ballot]
Note: -05 includes changes based on int-area review.
Token: Mark Townsley
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       AreaDate
RAI Framework for real-time text over IP using the Session Initiation Protocol (SIP) (Informational) - 1 of 8
draft-ietf-sipping-toip-08.txt [Open Web Ballot]
Token: Jon Peterson
INT IP over 802.16 Problem Statement and Goals (Informational) - 2 of 8
draft-ietf-16ng-ps-goals-03.txt [Open Web Ballot]
Note: Document shepherd is Daniel Park <soohong.park <at> samsung.com>
Token: Jari Arkko
INT Requirements for Multicast Support in Virtual Private LAN Services (Informational) - 3 of 8
draft-ietf-l2vpn-vpls-mcast-reqts-05.txt [Open Web Ballot]
Token: Mark Townsley
INT Mobility Services Transport: Problem Statement (Informational) - 4 of 8
draft-ietf-mipshop-mis-ps-05.txt [Open Web Ballot]
Note: Document Shepherd is Stefano Faccin
Token: Jari Arkko
RTG Framework for MPLS-TE to GMPLS migration (Informational) - 5 of 8
draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-04.txt
Token: Ross Callon
RTG Interworking Requirements to Support operation of MPLS-TE over GMPLS Networks (Informational) - 6 of 8
draft-ietf-ccamp-mpls-gmpls-interwork-reqts-03.txt
Token: Ross Callon
INT VPLS Interoperability with CE Bridges (Informational) - 7 of 8
draft-ietf-l2vpn-vpls-bridge-interop-02.txt [Open Web Ballot]
Token: Mark Townsley
INT L2VPN OAM Requirements and Framework (Informational) - 8 of 8
draft-ietf-l2vpn-oam-req-frmk-09.txt [Open Web Ballot]
Token: Mark Townsley
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 A Uniform Resource Name (URN) namespace for the Open Geospatial Consortium (OGC) (Informational) - 1 of 3
draft-creed-ogc-urn-03.txt [Open Web Ballot]
Token: Lisa Dusseault
INT Service Selection for Mobile IPv6 (Informational) - 2 of 3
draft-korhonen-mip6-service-05.txt [Open Web Ballot]
Note: No document shepherd
Token: Jari Arkko
GEN A URN namespace for the Commission for the Management and Application of Geoscience Information (CGI) (Informational) - 3 of 3
draft-sjdcox-cgi-urn-00.txt [Open Web Ballot]
Token: Lisa Dusseault
3.2.2 Returning Item       AreaDate
APP A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) (Informational) - 1 of 1
draft-goodwin-iso-urn-02.txt [Open Web Ballot]
Token: Lisa Dusseault

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

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

7. Working Group News

<div>
<h1>IESG Agenda</h1>
Good approximation of what will be included in the Agenda of next Telechat (2007-12-20).<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>SEC</td>
<td nowrap></td>
<td>Three-Document ballot: 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=1409&amp;filename=draft-ietf-pkix-2797-bis">[Open Web Ballot]</a>
 - 1 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>Certificate Management Messages over CMS (Proposed Standard) - 1 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-pkix-2797-bis-06.txt">draft-ietf-pkix-2797-bis-06.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: PROTO Shepherd: Stefan Santesson &lt;stefans <at> microsoft.com&gt;</td>
</tr>
<tr>
<td></td>
<td></td>
<td nowrap></td>
<td>Certificate Managmement Messages over CMS (CMC): Complience Requirements (Proposed Standard)</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-pkix-cmc-compl-05.txt">draft-ietf-pkix-cmc-compl-05.txt</a>  </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
          <td>Note: PROTO Shepherd: Stefan Santesson &lt;stefans <at> microsoft.com&gt;</td>
</tr>
<tr>
<td></td>
<td></td>
<td nowrap></td>
<td>Certificate Management over CMS (CMC): Transport Protocols (Proposed Standard)</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-pkix-cmc-trans-07.txt">draft-ietf-pkix-cmc-trans-07.txt</a>  </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
          <td>Note: PROTO Shepherd: Stefan Santesson &lt;stefans <at> microsoft.com&gt;</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:tim.polk <at> nist.gov">Tim Polk</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>Hash Based Addresses (HBA) (Proposed Standard) - 2 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-shim6-hba-04.txt">draft-ietf-shim6-hba-04.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=1915&amp;filename=draft-ietf-shim6-hba">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Please also read draft-ietf-shim6-applicability<br>Mark Townsley to handle any IPR questions in AD review/IETF LC/IESG, if any<br>Document Shepherd is Geoff Huston &lt;gih <at> apnic.net&gt;<br>
</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>INT</td>
<td nowrap></td>
<td>Failure Detection and Locator Pair Exploration Protocol for IPv6 Multihoming (Proposed Standard) - 3 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-shim6-failure-detection-09.txt">draft-ietf-shim6-failure-detection-09.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Please also read draft-ietf-shim6-applicability<br>Mark is handling this for Jari as he is an author</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>Shim6: Level 3 Multihoming Shim Protocol for IPv6 (Proposed Standard) - 4 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-shim6-proto-09.txt">draft-ietf-shim6-proto-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2286&amp;filename=draft-ietf-shim6-proto">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Please also read draft-ietf-shim6-applicability<br>Document Shepherd is Geoff Huston &lt;gih <at> apnic.net&gt;</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>INT</td>
<td nowrap></td>
<td>Domain Name System (DNS) IANA Considerations (BCP) - 5 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-dnsext-2929bis-06.txt">draft-ietf-dnsext-2929bis-06.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2408&amp;filename=draft-ietf-dnsext-2929bis">[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>SEC</td>
<td nowrap></td>
<td>Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (Proposed Standard) - 6 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-pkix-rfc3280bis-09.txt">draft-ietf-pkix-rfc3280bis-09.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: new version expected to be submitted Friday to address last call comments</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:hartmans-ietf <at> mit.edu">Sam Hartman</a></td>
</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>SIEVE Email Filtering: Extension for Notifications (Proposed Standard) - 7 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-11.txt">draft-ietf-sieve-notify-11.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2643&amp;filename=draft-ietf-sieve-notify">[Open Web Ballot]</a>
</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>APP</td>
<td nowrap></td>
<td>Sieve Notification Mechanism: xmpp (Proposed Standard) - 8 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-sieve-notify-xmpp-07.txt">draft-ietf-sieve-notify-xmpp-07.txt</a> </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>SEC</td>
<td nowrap></td>
<td>Multicast Extensions to the Security Architecture for the Internet Protocol (Proposed Standard) - 9 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-msec-ipsec-extensions-07.txt">draft-ietf-msec-ipsec-extensions-07.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2654&amp;filename=draft-ietf-msec-ipsec-extensions">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Lakshminath Dondeti is the proto shepherd.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:tim.polk <at> nist.gov">Tim Polk</a></td>
</tr>
<tr>
<td></td>
<td>RAI</td>
<td nowrap></td>
<td>A Framework for Consent-based Communications in the Session Initiation Protocol (SIP) (Proposed Standard) - 10 of 10</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-sip-consent-framework-03.txt">draft-ietf-sip-consent-framework-03.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2687&amp;filename=draft-ietf-sip-consent-framework">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Keith Drage is the document shepherd</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:fluffy <at> cisco.com">Cullen Jennings</a></td>
</tr>
</table>2.1.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</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><a href="http://www.ietf.org/IESG/EVALUATIONS/draft-cheshire-ipv4-acd.bal">INT</a></td>
<td nowrap>Oct 3</td>
<td>IPv4 Address Conflict Detection (Proposed Standard) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-cheshire-ipv4-acd-05.txt">draft-cheshire-ipv4-acd-05.txt</a> <a href="http://www.ietf.org/IESG/EVALUATIONS/draft-cheshire-ipv4-acd.bal">[Open Text Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: -05 includes changes based on int-area review.</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:townsley <at> cisco.com">Mark Townsley</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
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>RAI</td>
<td nowrap></td>
<td>Framework for real-time text over IP using the Session Initiation Protocol (SIP) (Informational) - 1 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-sipping-toip-08.txt">draft-ietf-sipping-toip-08.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2302&amp;filename=draft-ietf-sipping-toip">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:jon.peterson <at> neustar.biz">Jon Peterson</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>IP over 802.16 Problem Statement and Goals (Informational) - 2 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-16ng-ps-goals-03.txt">draft-ietf-16ng-ps-goals-03.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2602&amp;filename=draft-ietf-16ng-ps-goals">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Document shepherd is Daniel Park &lt;soohong.park <at> samsung.com&gt;</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>INT</td>
<td nowrap></td>
<td>Requirements for Multicast Support in Virtual Private LAN Services (Informational) - 3 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-mcast-reqts-05.txt">draft-ietf-l2vpn-vpls-mcast-reqts-05.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2611&amp;filename=draft-ietf-l2vpn-vpls-mcast-reqts">[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>Mobility Services Transport: Problem Statement (Informational) - 4 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-mipshop-mis-ps-05.txt">draft-ietf-mipshop-mis-ps-05.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2617&amp;filename=draft-ietf-mipshop-mis-ps">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: Document Shepherd is Stefano Faccin</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>RTG</td>
<td nowrap></td>
<td>Framework for MPLS-TE to GMPLS migration (Informational) - 5 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-04.txt">draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-04.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:rcallon <at> juniper.net">Ross Callon</a></td>
</tr>
<tr>
<td></td>
<td>RTG</td>
<td nowrap></td>
<td>Interworking Requirements to Support operation of MPLS-TE over GMPLS Networks (Informational) - 6 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-ccamp-mpls-gmpls-interwork-reqts-03.txt">draft-ietf-ccamp-mpls-gmpls-interwork-reqts-03.txt</a> </td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:rcallon <at> juniper.net">Ross Callon</a></td>
</tr>
<tr>
<td></td>
<td>INT</td>
<td nowrap></td>
<td>VPLS Interoperability with CE Bridges (Informational) - 7 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-vpls-bridge-interop-02.txt">draft-ietf-l2vpn-vpls-bridge-interop-02.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2633&amp;filename=draft-ietf-l2vpn-vpls-bridge-interop">[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>L2VPN OAM Requirements and Framework (Informational) - 8 of 8</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-ietf-l2vpn-oam-req-frmk-09.txt">draft-ietf-l2vpn-oam-req-frmk-09.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2634&amp;filename=draft-ietf-l2vpn-oam-req-frmk">[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>
</table>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>A Uniform Resource Name (URN) namespace for the Open Geospatial Consortium (OGC) (Informational) - 1 of 3</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-creed-ogc-urn-03.txt">draft-creed-ogc-urn-03.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2594&amp;filename=draft-creed-ogc-urn">[Open Web Ballot]</a>
</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>Service Selection for Mobile IPv6 (Informational) - 2 of 3</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-korhonen-mip6-service-05.txt">draft-korhonen-mip6-service-05.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2626&amp;filename=draft-korhonen-mip6-service">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
      <td>Note: No document shepherd</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>GEN</td>
<td nowrap></td>
<td>A URN namespace for the Commission for the Management and Application of Geoscience Information (CGI) (Informational) - 3 of 3</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-sjdcox-cgi-urn-00.txt">draft-sjdcox-cgi-urn-00.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2639&amp;filename=draft-sjdcox-cgi-urn">[Open Web Ballot]</a>
</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.2.2 Returning Item
<table>
<tr> &nbsp; &nbsp; &nbsp; AreaDate</tr>
<tr>
<td></td>
<td>APP</td>
<td nowrap></td>
<td>A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO) (Informational) - 1 of 1</td>
</tr>
<tr>
<td></td>
<td></td>
<td></td>
<td>
<a href="http://www.ietf.org/internet-drafts/draft-goodwin-iso-urn-02.txt">draft-goodwin-iso-urn-02.txt</a> 
          <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=print_ballot&amp;ballot_id=2277&amp;filename=draft-goodwin-iso-urn">[Open Web Ballot]</a>
</td>
</tr>
<tr>
<td></td>
<td></td>
<td>Token:</td>
      <td><a href="mailto:lisa <at> osafoundation.org">Lisa Dusseault</a></td>
</tr>
</table>
</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
 <br>&nbsp; &nbsp; &nbsp; NONE<br>3.3.2 Returning Item
 <br>&nbsp; &nbsp; &nbsp; NONE<br>
</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>
<p></p>
<p>
</p>
<h2>7. Working Group News</h2>
<p>
</p>
</div>
IESG Secretary | 14 Dec 01:11 2007
Picon

IESG Telechat Agenda (Plain Text) for December 20, 2007


          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the December 20, 2007 IESG Teleconference

This agenda was generated at 19:11:34 EDT, December 13, 2007
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 Three-document ballot:  - 1 of 10
     - draft-ietf-pkix-2797-bis-06.txt
       Certificate Management Messages over CMS (Proposed Standard) 
       Note: PROTO Shepherd: Stefan Santesson &lt;stefans <at> microsoft.com&gt; 
     - draft-ietf-pkix-cmc-compl-05.txt
       Certificate Managmement Messages over CMS (CMC): Complience Requirements 
       (Proposed Standard) 
       Note: PROTO Shepherd: Stefan Santesson &lt;stefans <at> microsoft.com&gt; 
     - draft-ietf-pkix-cmc-trans-07.txt
       Certificate Management over CMS (CMC): Transport Protocols (Proposed 
       Standard) 
       Note: PROTO Shepherd: Stefan Santesson &lt;stefans <at> microsoft.com&gt; 
    Token: Tim Polk
  o draft-ietf-shim6-hba-04.txt
    Hash Based Addresses (HBA) (Proposed Standard) - 2 of 10 
    Note: Please also read draft-ietf-shim6-applicability. Mark Townsley to 
    handle any IPR questions in AD review/IETF LC/IESG, if any. Document 
    Shepherd is Geoff Huston &lt;gih <at> apnic.net&gt;. 
    Token: Jari Arkko
  o draft-ietf-shim6-failure-detection-09.txt
    Failure Detection and Locator Pair Exploration Protocol for IPv6 
    Multihoming (Proposed Standard) - 3 of 10 
    Note: Please also read draft-ietf-shim6-applicability. Mark is handling 
    this for Jari as he is an author 
    Token: Mark Townsley
  o draft-ietf-shim6-proto-09.txt
    Shim6: Level 3 Multihoming Shim Protocol for IPv6 (Proposed Standard) - 4 
    of 10 
    Note: Please also read draft-ietf-shim6-applicability. Document Shepherd is 
    Geoff Huston &lt;gih <at> apnic.net&gt; 
    Token: Jari Arkko
  o draft-ietf-dnsext-2929bis-06.txt
    Domain Name System (DNS) IANA Considerations (BCP) - 5 of 10 
    Token: Mark Townsley
  o draft-ietf-pkix-rfc3280bis-09.txt
    Internet X.509 Public Key Infrastructure Certificate and Certificate 
    Revocation List (CRL) Profile (Proposed Standard) - 6 of 10 
    Note: new version expected to be submitted Friday to address last call 
    comments 
    Token: Sam Hartman
  o draft-ietf-sieve-notify-11.txt
    SIEVE Email Filtering: Extension for Notifications (Proposed Standard) - 7 
    of 10 
    Token: Lisa Dusseault
  o draft-ietf-sieve-notify-xmpp-07.txt
    Sieve Notification Mechanism: xmpp (Proposed Standard) - 8 of 10 
    Token: Lisa Dusseault
  o draft-ietf-msec-ipsec-extensions-07.txt
    Multicast Extensions to the Security Architecture for the Internet Protocol 
    (Proposed Standard) - 9 of 10 
    Note: Lakshminath Dondeti is the proto shepherd. 
    Token: Tim Polk
  o draft-ietf-sip-consent-framework-03.txt
    A Framework for Consent-based Communications in the Session Initiation 
    Protocol (SIP) (Proposed Standard) - 10 of 10 
    Note: Keith Drage is the document shepherd 
    Token: Cullen Jennings

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-cheshire-ipv4-acd-05.txt
    IPv4 Address Conflict Detection (Proposed Standard) - 1 of 1 
    Note: -05 includes changes based on int-area review. 
    Token: Mark Townsley

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-sipping-toip-08.txt
    Framework for real-time text over IP using the Session Initiation Protocol 
    (SIP) (Informational) - 1 of 8 
    Token: Jon Peterson
  o draft-ietf-16ng-ps-goals-03.txt
    IP over 802.16 Problem Statement and Goals (Informational) - 2 of 8 
    Note: Document shepherd is Daniel Park &lt;soohong.park <at> samsung.com&gt; 
    Token: Jari Arkko
  o draft-ietf-l2vpn-vpls-mcast-reqts-05.txt
    Requirements for Multicast Support in Virtual Private LAN Services 
    (Informational) - 3 of 8 
    Token: Mark Townsley
  o draft-ietf-mipshop-mis-ps-05.txt
    Mobility Services Transport: Problem Statement (Informational) - 4 of 8 
    Note: Document Shepherd is Stefano Faccin 
    Token: Jari Arkko
  o draft-ietf-ccamp-mpls-gmpls-interwork-fmwk-04.txt
    Framework for MPLS-TE to GMPLS migration (Informational) - 5 of 8 
    Token: Ross Callon
  o draft-ietf-ccamp-mpls-gmpls-interwork-reqts-03.txt
    Interworking Requirements to Support operation of MPLS-TE over GMPLS 
    Networks (Informational) - 6 of 8 
    Token: Ross Callon
  o draft-ietf-l2vpn-vpls-bridge-interop-02.txt
    VPLS Interoperability with CE Bridges (Informational) - 7 of 8 
    Token: Mark Townsley
  o draft-ietf-l2vpn-oam-req-frmk-09.txt
    L2VPN OAM Requirements and Framework (Informational) - 8 of 8 
    Token: Mark Townsley

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-creed-ogc-urn-03.txt
    A Uniform Resource Name (URN) namespace for the Open Geospatial Consortium 
    (OGC) (Informational) - 1 of 3 
    Token: Lisa Dusseault
  o draft-korhonen-mip6-service-05.txt
    Service Selection for Mobile IPv6 (Informational) - 2 of 3 
    Note: No document shepherd 
    Token: Jari Arkko
  o draft-sjdcox-cgi-urn-00.txt
    A URN namespace for the Commission for the Management and Application of 
    Geoscience Information (CGI) (Informational) - 3 of 3 
    Token: Lisa Dusseault

3.2.2 Returning Item
  o draft-goodwin-iso-urn-02.txt
    A Uniform Resource Name (URN) Namespace for the International Organization 
    for Standardization (ISO) (Informational) - 1 of 1 
    Token: Lisa Dusseault

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

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

7. Agenda Working Group News


Gmane