From rtg-dir-bounces@ietf.org  Mon Jan  5 04:00:25 2009
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 90FB23A676A;
	Mon,  5 Jan 2009 04:00:25 -0800 (PST)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 35FDB3A67F1
	for <rtg-dir@core3.amsl.com>; Mon,  5 Jan 2009 04:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id UEICTHLfzw7d for <rtg-dir@core3.amsl.com>;
	Mon,  5 Jan 2009 04:00:23 -0800 (PST)
Received: from runaway.fenron.com (unknown
	[IPv6:2001:470:117:128:230:48ff:fe92:8e81])
	by core3.amsl.com (Postfix) with ESMTP id 8C08C3A676A
	for <rtg-dir@ietf.org>; Mon,  5 Jan 2009 04:00:22 -0800 (PST)
Received: from runaway.fenron.com (localhost [127.0.0.1])
	by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id n05C04Wm053380
	for <rtg-dir@ietf.org>; Mon, 5 Jan 2009 04:00:04 -0800 (PST)
	(envelope-from fenner@runaway.fenron.com)
Received: (from fenner@localhost)
	by runaway.fenron.com (8.13.8/8.13.8/Submit) id n05C04ZJ053372
	for rtg-dir@ietf.org; Mon, 5 Jan 2009 04:00:04 -0800 (PST)
	(envelope-from fenner)
Date: Mon, 5 Jan 2009 04:00:04 -0800 (PST)
Message-Id: <200901051200.n05C04ZJ053372@runaway.fenron.com>
From: fenner@fenron.com (Bill Fenner)
To: rtg-dir@ietf.org (Routing Area Directorate)
Subject: IESG agenda for 2009-01-08 telechat.
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

                              IESG Agenda

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

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

1. Administrivia

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

2. Protocol Actions

    Reviews should focus on these questions: "Is this document a
    reasonable basis on which to build the salient part of the Internet
    infrastructure? If not, what changes would make it so?"

      2.1 WG Submissions

           2.1.1 New Item


             Area  Date

             RTG         Simplified Extension of LSP Space for IS-IS
                         (Proposed Standard) - 1 of 5
                         draft-ietf-isis-wg-extlsp-05.txt [Open Web
                         Ballot]
                  Token: Ross Callon
                         Secure/Multipurpose Internet Mail Extensions
             SEC         (S/MIME) Version 3.2 Message Specification
                         (Proposed Standard) - 2 of 5
                         draft-ietf-smime-3851bis-08.txt [Open Web
                         Ballot]
                  Token: Tim Polk
                         Secure/Multipurpose Internet Mail Extensions
             SEC         (S/MIME) Version 3.2 Certificate Handling
                         (Proposed Standard) - 3 of 5
                         draft-ietf-smime-3850bis-08.txt [Open Web
                         Ballot]
                  Token: Tim Polk
                         A Framework for Session Initiation Protocol
             RAI         (SIP) Session Policies (Proposed Standard) - 4
                         of 5
                         draft-ietf-sip-session-policy-framework-05.txt
                         [Open Web Ballot]
                  Token: Cullen Jennings
             RTG         Capabilities Advertisement with BGP-4
                         (Proposed Standard) - 5 of 5
                         draft-ietf-idr-rfc3392bis-03.txt [Open Web
                         Ballot]
                  Token: David Ward

           2.1.2 Returning Item
                 NONE

      2.2 Individual Submissions

            2.2.1 New Item
                  NONE
            2.2.2 Returning Item


               Area  Date

               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


3. Document Actions

      3.1 WG Submissions

          Reviews should focus on these questions: "Is this document a
          reasonable
          contribution to the area of Internet engineering which it
          covers? If
          not, what changes would make it so?"

            3.1.1 New Item


               Area  Date

                           DES and IDEA Cipher Suites for Transport
               SEC         Layer Security (TLS) (Informational) - 1 of
                           2
                           draft-ietf-tls-des-idea-02.txt [Open Web
                           Ballot]
                    Token: Tim Polk
               TSV         Packet Delay Variation Applicability
                           Statement (Informational) - 2 of 2
                           draft-ietf-ippm-delay-var-as-01.txt [Open
                           Web Ballot]
                    Token: Lars Eggert

            3.1.2 Returning Item
                  NONE
            3.1.3 For Action

                 Area  Date

                 RTG         The RPF Vector TLV (Informational) - 1 of
                             1
                             draft-ietf-pim-rpf-vector-06.txt [Open Web
                             Ballot]
                      Token: David Ward


      3.2 Individual Submissions Via AD

          Reviews should focus on these questions: "Is this document a
          reasonable
          contribution to the area of Internet engineering which it
          covers? If
          not, what changes would make it so?"

           3.2.1 New Item


             Area  Date

                         Performance Analysis of Inter-Domain Path
             RTG         Computation Methodologies (Informational) - 1
                         of 3
                         draft-dasgupta-ccamp-path-comp-analysis-02.txt
                         [Open Web Ballot]
                  Token: Ross Callon
             INT         VoIP Configuration Server Address Option
                         (Informational) - 2 of 3
                         draft-raj-dhc-tftp-addr-option-04.txt [Open
                         Web Ballot]
                  Token: Jari Arkko
             INT         Service Selection for Mobile IPv4
                         (Informational) - 3 of 3
                         draft-korhonen-mip4-service-07.txt [Open Web
                         Ballot]
                  Token: Jari Arkko

           3.2.2 Returning Item
                 NONE

      3.3 Independent Submissions Via RFC Editor

          The IESG will use RFC 3932 responses: 1) The IESG has not
          found any conflict between this document and IETF work; 2)
          The
          IESG thinks that this work is related to IETF work done in WG
          <X>, but this does not prevent publishing; 3) The IESG thinks
          that publication is harmful to work in WG <X> and recommends
          not publishing at this time; 4) The IESG thinks that this
          document violates the IETF procedures for <X> and should
          therefore not be published without IETF review and IESG
          approval; 5) The IESG thinks that this document extends an
          IETF protocol in a way that requires IETF review and should
          therefore not be published without IETF review and IESG
          approval.

          The document shepherd must propose one of these responses in
          the Data Tracker note and supply complete text in the IESG
          Note portion of the write-up. The Area Director ballot
          positions
          indicate consensus with the response proposed by the
          document shepherd.

          Other matters may be recorded in comments, and the comments
          will
          be passed on to the RFC Editor as community review of the
          document.

                3.3.1 New Item
                      NONE
                3.3.2 Returning Item
                      NONE

4. Working Group Actions

         4.1 WG Creation

                   4.1.1 Proposed for IETF Review
                                       NONE
                  4.1.2 Proposed for Approval
                           Area  Date
                           APP  Dec 11 Message Organization (morg) - 1
                                       of 1
                                Token: Chris

         4.2 WG Rechartering

                  4.2.1 Under evaluation for IETF Review
                           Area  Date
                           OPS  Dec 17 Network Configuration (netconf)
                                       - 1 of 2
                                Token: Dan
                           TSV  Dec 19 IP Performance Metrics (ippm) -
                                       2 of 2
                                Token: Lars

                   4.2.2 Proposed for Approval
                                       NONE

5. IAB News We Can Use

6. Management Issues

6.1 Nomcom appointment to the IAOC (Ross Callon)

7. Working Group News


From rtg-dir-bounces@ietf.org  Mon Jan 12 04:00:33 2009
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D383F28C10A;
	Mon, 12 Jan 2009 04:00:33 -0800 (PST)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id D931F28C11A
	for <rtg-dir@core3.amsl.com>; Mon, 12 Jan 2009 04:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ljVL+DgPmDLV for <rtg-dir@core3.amsl.com>;
	Mon, 12 Jan 2009 04:00:32 -0800 (PST)
Received: from runaway.fenron.com (unknown
	[IPv6:2001:470:117:128:230:48ff:fe92:8e81])
	by core3.amsl.com (Postfix) with ESMTP id 8BFBB28C10A
	for <rtg-dir@ietf.org>; Mon, 12 Jan 2009 04:00:31 -0800 (PST)
Received: from runaway.fenron.com (localhost [127.0.0.1])
	by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id n0CC05oe083359
	for <rtg-dir@ietf.org>; Mon, 12 Jan 2009 04:00:05 -0800 (PST)
	(envelope-from fenner@runaway.fenron.com)
Received: (from fenner@localhost)
	by runaway.fenron.com (8.13.8/8.13.8/Submit) id n0CC0552083352
	for rtg-dir@ietf.org; Mon, 12 Jan 2009 04:00:05 -0800 (PST)
	(envelope-from fenner)
Date: Mon, 12 Jan 2009 04:00:05 -0800 (PST)
Message-Id: <200901121200.n0CC0552083352@runaway.fenron.com>
From: fenner@fenron.com (Bill Fenner)
To: rtg-dir@ietf.org (Routing Area Directorate)
Subject: IESG agenda for 2009-01-15 telechat.
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

                              IESG Agenda

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

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

1. Administrivia

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

2. Protocol Actions

    Reviews should focus on these questions: "Is this document a
    reasonable basis on which to build the salient part of the Internet
    infrastructure? If not, what changes would make it so?"

      2.1 WG Submissions

           2.1.1 New Item


              Area  Date

                          Encoding of Objective Functions in the Path
              RTG         Computation Element Communication Protocol
                          (PCEP) (Proposed Standard) - 1 of 3
                          draft-ietf-pce-of-06.txt [Open Web Ballot]
                   Token: Ross Callon
                          Diff-Serv Aware Class Type Object for Path
              RTG         Computation Element Communication Protocol
                          (Proposed Standard) - 2 of 3
                          draft-ietf-pce-dste-02.txt [Open Web Ballot]
                   Token: Ross Callon
              APP         A Protocol for Remotely Managing Sieve
                          Scripts (Proposed Standard) - 3 of 3
                          draft-ietf-sieve-managesieve-06.txt [Open Web
                          Ballot]
                   Token: Lisa Dusseault

           2.1.2 Returning Item
                 NONE

      2.2 Individual Submissions

               2.2.1 New Item

                    Area  Date

                    GEN         Vouch By Reference (Proposed Standard)
                                - 1 of 1
                                draft-hoffman-dac-vbr-05.txt [Open Web
                                Ballot]
                         Token: Russ Housley

               2.2.2 Returning Item
                     NONE

3. Document Actions

       3.1 WG Submissions

           Reviews should focus on these questions: "Is this document a
           reasonable
           contribution to the area of Internet engineering which it
           covers? If
           not, what changes would make it so?"

              3.1.1 New Item

                  Area  Date

                  RTG         MANET Extension of OSPF using CDS
                              Flooding (Experimental) - 1 of 3
                              draft-ietf-ospf-manet-mdr-04.txt [Open
                              Web Ballot]
                       Token: David Ward
                  RTG         OSPF MPR Extension for Ad Hoc Networks
                              (Experimental) - 2 of 3
                              draft-ietf-ospf-manet-mpr-03.txt [Open
                              Web Ballot]
                       Token: David Ward
                  RTG         Extensions to OSPF to Support Mobile Ad
                              Hoc Networking (Experimental) - 3 of 3
                              draft-ietf-ospf-manet-or-01.txt [Open Web
                              Ballot]
                       Token: David Ward

              3.1.2 Returning Item
                    NONE

       3.2 Individual Submissions Via AD

           Reviews should focus on these questions: "Is this document a
           reasonable
           contribution to the area of Internet engineering which it
           covers? If
           not, what changes would make it so?"

                 3.2.1 New Item
                       NONE
                 3.2.2 Returning Item
                       NONE

       3.3 Independent Submissions Via RFC Editor

           The IESG will use RFC 3932 responses: 1) The IESG has not
           found any conflict between this document and IETF work; 2)
           The
           IESG thinks that this work is related to IETF work done in
           WG
           <X>, but this does not prevent publishing; 3) The IESG
           thinks
           that publication is harmful to work in WG <X> and recommends
           not publishing at this time; 4) The IESG thinks that this
           document violates the IETF procedures for <X> and should
           therefore not be published without IETF review and IESG
           approval; 5) The IESG thinks that this document extends an
           IETF protocol in a way that requires IETF review and should
           therefore not be published without IETF review and IESG
           approval.

           The document shepherd must propose one of these responses in
           the Data Tracker note and supply complete text in the IESG
           Note portion of the write-up. The Area Director ballot
           positions
           indicate consensus with the response proposed by the
           document shepherd.

           Other matters may be recorded in comments, and the comments
           will
           be passed on to the RFC Editor as community review of the
           document.

                 3.3.1 New Item
                       NONE
                 3.3.2 Returning Item
                       NONE

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 IESG Statement regarding chartered work overcome by events before
IESG consideration (Ron Bonica)
6.2 Draft Statement on BCP Status for Examples (Dan Romascanu)

7. Working Group News


From rtg-dir-bounces@ietf.org  Wed Jan 14 11:39:26 2009
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 4713E3A686A;
	Wed, 14 Jan 2009 11:39:26 -0800 (PST)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 462A23A6A5B
	for <rtg-dir@core3.amsl.com>; Wed, 14 Jan 2009 11:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level: 
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.167, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id RfIO-OnRvHQs; Wed, 14 Jan 2009 11:39:24 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7ob114.obsmtp.com [64.18.2.214])
	by core3.amsl.com (Postfix) with ESMTP id 6B6E73A686A;
	Wed, 14 Jan 2009 11:39:24 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob114.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSW4/WVab6ANmqtLKm6J/mB39L1QYZcrM@postini.com;
	Wed, 14 Jan 2009 11:39:10 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Wed, 14 Jan 2009 11:35:44 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Jan
	2009 11:35:44 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959);	 Wed, 14 Jan 2009 11:35:43 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9767F.48D0429D"
Subject: FW: Routing AD Office Hours in Minneapolis
Date: Wed, 14 Jan 2009 14:35:40 -0500
Message-ID: <3525C9833C09ED418C6FD6CD9514668C057ADA43@emailwf1.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Routing AD Office Hours in Minneapolis
Thread-Index: Ack/tZ7jVOsKSDs8QRmP4a5+UWGrpQ2x7mUg
From: Ross Callon <rcallon@juniper.net>
To: <rtg-chairs@ietf.org>,
	<rtg-dir@ietf.org>
X-OriginalArrivalTime: 14 Jan 2009 19:35:43.0891 (UTC)
	FILETIME=[4A758630:01C9767F]
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

------_=_NextPart_001_01C9767F.48D0429D
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dave and I will once again have drop-in routing AD office hours from 2pm
to 5pm the Sunday immediately before the upcoming IETF in San Francisco.
I have reserved the IESG breakout room (I reserved it until 5:30 just in
case we run slightly late).=20

=20

I don't know yet which room will be assigned as the IESG breakout room.
The IETF secretariat will know once we are in San Francisco, and I will
send out email when I know -- but this email will probably be sent right
at the last minute (or at least some time Sunday at the IETF). Dave and
I have another meeting which runs to 2pm, and thus if we are a few
minutes late don't panic.=20

=20

Let us know if you intend to drop by, or just drop by.

=20

Thanks, Ross (and Dave) =20


------_=_NextPart_001_01C9767F.48D0429D
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Dave and I will once again have =
drop-in
routing AD office hours from 2pm to 5pm the Sunday immediately before =
the
upcoming IETF in San Francisco. I have reserved the IESG breakout room =
(I
reserved it until 5:30 just in case we run slightly late). =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I don't know yet which room will be
assigned as the IESG breakout room. The IETF secretariat will know once =
we are
in San Francisco, and I will send out email when I know -- but this =
email will
probably be sent right at the last minute (or at least some time Sunday =
at the
IETF). Dave and I have another meeting which runs to 2pm, and thus if we =
are a
few minutes late don't panic. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Let us know if you intend to drop =
by, or
just drop by.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, Ross (and Dave)&nbsp; =
</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

</body>

</html>

------_=_NextPart_001_01C9767F.48D0429D--


From rtg-dir-bounces@ietf.org  Wed Jan 14 11:40:12 2009
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5A9FC3A6A72;
	Wed, 14 Jan 2009 11:40:12 -0800 (PST)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6C3163A6A81
	for <rtg-dir@core3.amsl.com>; Wed, 14 Jan 2009 11:40:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.434
X-Spam-Level: 
X-Spam-Status: No, score=-6.434 tagged_above=-999 required=5 tests=[AWL=0.164, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 4NekhQPq66Yc; Wed, 14 Jan 2009 11:40:10 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155])
	by core3.amsl.com (Postfix) with ESMTP id 782943A6A72;
	Wed, 14 Jan 2009 11:40:10 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by
	exprod7ob101.postini.com ([64.18.6.12]) with SMTP
	ID DSNKSW4/i73jDLQrjf4vENoXtBNLh3yjvlVO@postini.com;
	Wed, 14 Jan 2009 11:39:56 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net
	(172.24.192.35) with Microsoft SMTP Server id 8.1.336.0;
	Wed, 14 Jan 2009 11:36:47 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by
	p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Jan
	2009 11:36:47 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959);	 Wed, 14 Jan 2009 11:36:47 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9767F.6F174389"
Subject: RE: Routing AD Office Hours in San Francisco
Date: Wed, 14 Jan 2009 14:36:44 -0500
Message-ID: <3525C9833C09ED418C6FD6CD9514668C057ADA47@emailwf1.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Routing AD Office Hours in San Francisco
Thread-Index: Ack/tZ7jVOsKSDs8QRmP4a5+UWGrpQ2x7mUgAAB+SrA=
From: Ross Callon <rcallon@juniper.net>
To: <rtg-chairs@ietf.org>,
	<rtg-dir@ietf.org>
X-OriginalArrivalTime: 14 Jan 2009 19:36:47.0001 (UTC)
	FILETIME=[70135890:01C9767F]
Cc: Ross Callon <rcallon@juniper.net>, David Ward <dward@cisco.com>
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>,
	<mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

------_=_NextPart_001_01C9767F.6F174389
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

OOps, I forgot to update the subject line.=20

=20

Ross=20

=20

________________________________

From: Ross Callon=20
Sent: 14 January 2009 14:36
To: 'rtg-chairs@ietf.org'; 'rtg-dir@ietf.org'
Cc: 'David Ward'; Ross Callon
Subject: FW: Routing AD Office Hours in Minneapolis

=20

Dave and I will once again have drop-in routing AD office hours from 2pm
to 5pm the Sunday immediately before the upcoming IETF in San Francisco.
I have reserved the IESG breakout room (I reserved it until 5:30 just in
case we run slightly late).=20

=20

I don't know yet which room will be assigned as the IESG breakout room.
The IETF secretariat will know once we are in San Francisco, and I will
send out email when I know -- but this email will probably be sent right
at the last minute (or at least some time Sunday at the IETF). Dave and
I have another meeting which runs to 2pm, and thus if we are a few
minutes late don't panic.=20

=20

Let us know if you intend to drop by, or just drop by.

=20

Thanks, Ross (and Dave) =20


------_=_NextPart_001_01C9767F.6F174389
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>OOps, I forgot to update the =
subject line.
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Ross <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Ross =
Callon <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 14 January 2009 =
14:36<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
'rtg-chairs@ietf.org';
'rtg-dir@ietf.org'<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> 'David Ward'; Ross =
Callon<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> FW: Routing AD =
Office
Hours in Minneapolis</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Dave and I will once again have =
drop-in
routing AD office hours from 2pm to 5pm the Sunday immediately before =
the
upcoming IETF in San Francisco. I have reserved the IESG breakout room =
(I
reserved it until 5:30 just in case we run slightly late). =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I don't know yet which room will be
assigned as the IESG breakout room. The IETF secretariat will know once =
we are
in San Francisco, and I will send out email when I know -- but this =
email will
probably be sent right at the last minute (or at least some time Sunday =
at the
IETF). Dave and I have another meeting which runs to 2pm, and thus if we =
are a
few minutes late don't panic. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Let us know if you intend to drop =
by, or
just drop by.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks, Ross (and Dave)&nbsp; =
</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

</body>

</html>

------_=_NextPart_001_01C9767F.6F174389--



From rtg-dir-bounces@ietf.org  Thu Jan 22 10:54:33 2009
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3401828C266; Thu, 22 Jan 2009 10:54:33 -0800 (PST)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD43A28C25F; Thu, 22 Jan 2009 10:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.236
X-Spam-Level: 
X-Spam-Status: No, score=-5.236 tagged_above=-999 required=5 tests=[AWL=-0.947, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_URGBIZ=0.725, URG_BIZ=1.585]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3aXjTtIGN1jn; Thu, 22 Jan 2009 10:54:31 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by core3.amsl.com (Postfix) with ESMTP id E5F9028C140; Thu, 22 Jan 2009 10:54:30 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKSXjA0qCMs6o3ozQWTKRBwL9xK0WVf9WJ@postini.com; Thu, 22 Jan 2009 10:54:14 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Thu, 22 Jan 2009 10:51:24 -0800
Received: from p-emsmtp03.jnpr.net ([66.129.254.54]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 10:51:24 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959);	 Thu, 22 Jan 2009 10:51:24 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: Nominating Committee call for Internet and Routing AD Nominees 
Date: Thu, 22 Jan 2009 13:51:22 -0500
Message-ID: <3525C9833C09ED418C6FD6CD9514668C058586D6@emailwf1.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nominating Committee call for Internet and Routing AD Nominees 
Thread-Index: Acl8GEeFyda7AKyeQP60BX7JnlSRsgAqf75w
From: Ross Callon <rcallon@juniper.net>
To: <rtg-chairs@ietf.org>, <rtg-dir@ietf.org>, <routing-discussion@ietf.org>
X-OriginalArrivalTime: 22 Jan 2009 18:51:24.0316 (UTC) FILETIME=[6C8895C0:01C97CC2]
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org FYI.=20

-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of NomCom Chair
Sent: 21 January 2009 17:34
To: IETF Announcement list
Subject: Nominating Committee call for Internet and Routing AD Nominees=20

The nominating committee asks for your urgent assistance.
Please nominate additional individuals you think would be good folks to
consider for the Internet and Routing AD slots we are responsible for
filling. =20
Nominations should be sent to nomcom08@ietf.org.
Nominations will be accepted through Friday, February 6, although the
sooner they are submitted the better, as nominees will not have very
long
to provide questionnaires to the committee.
Self nomination is permitted.

Thank you for your assistance,
Joel M. Halpern
IETF 2008 / 2009 nominating committee chair

PS: There is no need to resubmit nominations you are sure were submitted
earlier.  There is no harm in submitting one if you are not sure.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From rtg-dir-bounces@ietf.org  Mon Jan 26 04:00:43 2009
Return-Path: <rtg-dir-bounces@ietf.org>
X-Original-To: rtg-dir-archive@megatron.ietf.org
Delivered-To: ietfarch-rtg-dir-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE7D43A6A67; Mon, 26 Jan 2009 04:00:43 -0800 (PST)
X-Original-To: rtg-dir@core3.amsl.com
Delivered-To: rtg-dir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6BD3A6A67 for <rtg-dir@core3.amsl.com>; Mon, 26 Jan 2009 04:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGa1iLRHMrlk for <rtg-dir@core3.amsl.com>; Mon, 26 Jan 2009 04:00:41 -0800 (PST)
Received: from runaway.fenron.com (unknown [IPv6:2001:470:117:128:230:48ff:fe92:8e81]) by core3.amsl.com (Postfix) with ESMTP id C60013A67FB for <rtg-dir@ietf.org>; Mon, 26 Jan 2009 04:00:40 -0800 (PST)
Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id n0QC0BhC073854 for <rtg-dir@ietf.org>; Mon, 26 Jan 2009 04:00:11 -0800 (PST) (envelope-from fenner@runaway.fenron.com)
Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id n0QC0BPb073853 for rtg-dir@ietf.org; Mon, 26 Jan 2009 04:00:11 -0800 (PST) (envelope-from fenner)
Date: Mon, 26 Jan 2009 04:00:11 -0800 (PST)
Message-Id: <200901261200.n0QC0BPb073853@runaway.fenron.com>
From: fenner@fenron.com (Bill Fenner)
To: rtg-dir@ietf.org (Routing Area Directorate)
Subject: IESG agenda for 2009-01-29 telechat.
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/rtg-dir>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
Sender: rtg-dir-bounces@ietf.org
Errors-To: rtg-dir-bounces@ietf.org

                              IESG Agenda

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

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

1. Administrivia

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

2. Protocol Actions

    Reviews should focus on these questions: "Is this document a
    reasonable basis on which to build the salient part of the Internet
    infrastructure? If not, what changes would make it so?"

     2.1 WG Submissions

        2.1.1 New Item


          Area  Date

                      GEOPRIV PIDF-LO Usage Clarification,
          RAI         Considerations and Recommendations (Proposed
                      Standard) - 1 of 13
                      draft-ietf-geopriv-pdif-lo-profile-14.txt [Open
                      Web Ballot]
                      Note: Robert Sparks is proto shepherd.
               Token: Cullen Jennings
          INT         NEMO Management Information Base (Proposed
                      Standard) - 2 of 13
                      draft-ietf-mext-nemo-mib-04.txt [Open Web Ballot]
               Token: Jari Arkko
                      Remote Authentication Dial-In User Service
          OPS         (RADIUS) Authorization for Network Access Server
                      (NAS) Management (Proposed Standard) - 3 of 13
                      draft-ietf-radext-management-authorization-06.txt
                      [Open Web Ballot]
               Token: Dan Romascanu
          SEC         Update for RSAES-OAEP Algorithm Parameters
                      (Proposed Standard) - 4 of 13
                      draft-ietf-pkix-rfc4055-update-01.txt [Open Web
                      Ballot]
               Token: Pasi Eronen
          INT         Softwire Mesh Framework (Proposed Standard) - 5
                      of 13
                      draft-ietf-softwire-mesh-framework-05.txt [Open
                      Web Ballot]
               Token: Mark Townsley
                      BGP Encapsulation SAFI and BGP Tunnel
          INT         Encapsulation Attribute (Proposed Standard) - 6
                      of 13
                      draft-ietf-softwire-encaps-safi-04.txt [Open Web
                      Ballot]
               Token: Mark Townsley
          INT         BGP IPSec Tunnel Encapsulation Attribute
                      (Proposed Standard) - 7 of 13
                      draft-ietf-softwire-encaps-ipsec-01.txt [Open Web
                      Ballot]
               Token: Mark Townsley
          INT         BGP Traffic Engineering Attribute (Proposed
                      Standard) - 8 of 13
                      draft-ietf-softwire-bgp-te-attribute-04.txt [Open
                      Web Ballot]
               Token: Mark Townsley
          INT         Advertising an IPv4 NLRI with an IPv6 Next Hop
                      (Proposed Standard) - 9 of 13
                      draft-ietf-softwire-v4nlri-v6nh-01.txt [Open Web
                      Ballot]
               Token: Mark Townsley
                      Pre-Shared Key Cipher Suites for Transport Layer
          SEC         Security (TLS) with SHA-256/384 and AES Galois
                      Counter Mode (Proposed Standard) - 10 of 13
                      draft-ietf-tls-psk-new-mac-aes-gcm-05.txt [Open
                      Web Ballot]
                      Note: Document Shepherd is jsalowey@cisco.com
               Token: Pasi Eronen
          RAI         Post-Repair Loss RLE Report Block Type for RTCP
                      XR (Proposed Standard) - 11 of 13
                      draft-ietf-avt-post-repair-rtcp-xr-04.txt [Open
                      Web Ballot]
               Token: Cullen Jennings
                      A Session Description Protocol (SDP) Offer/Answer
          RAI         Mechanism to Enable File Transfer (Proposed
                      Standard) - 12 of 13
                      draft-ietf-mmusic-file-transfer-mech-10.txt [Open
                      Web Ballot]
               Token: Cullen Jennings
          RTG         Dissemination of flow specification rules
                      (Proposed Standard) - 13 of 13
                      draft-ietf-idr-flow-spec-04.txt [Open Web Ballot]
               Token: David Ward

        2.1.2 Returning Item

            Area  Date

            INT         IEEE 802.21 Mobility Services Framework Design
                        (MSFD) (Proposed Standard) - 1 of 1
                        draft-ietf-mipshop-mstp-solution-11.txt [Open
                        Web Ballot]
                 Token: Jari Arkko


     2.2 Individual Submissions

          2.2.1 New Item


             Area  Date

             SEC         Common Architecture Label IPv6 Security Option
                         (CALIPSO) (Proposed Standard) - 1 of 4
                         draft-stjohns-sipso-06.txt [Open Web Ballot]
                  Token: Tim Polk
             GEN         Vouch By Reference (Proposed Standard) - 2 of
                         4
                         draft-hoffman-dac-vbr-05.txt [Open Web Ballot]
                  Token: Russ Housley
                         Internet Assigned Numbers Authority (IANA)
             RAI         Registration of Instant Messaging and Presence
                         DNS SRV RRs for the Session Initiation
                         Protocol (SIP) (Proposed Standard) - 3 of 4
                         draft-loreto-simple-im-srv-label-03.txt [Open
                         Web Ballot]
                  Token: Jon Peterson
                         The Sieve mail filtering language - extensions
             APP         for checking mailbox status and accessing
                         mailbox metadata (Proposed Standard) - 4 of 4
                         draft-melnikov-sieve-imapext-metadata-08.txt
                         [Open Web Ballot]
                  Token: Lisa Dusseault

          2.2.2 Returning Item
                NONE

3. Document Actions

     3.1 WG Submissions

         Reviews should focus on these questions: "Is this document a
         reasonable
         contribution to the area of Internet engineering which it
         covers? If
         not, what changes would make it so?"

           3.1.1 New Item


              Area  Date

              RAI         SPEERMINT Terminology (Informational) - 1 of
                          4
                          draft-ietf-speermint-terminology-17.txt [Open
                          Web Ballot]
                   Token: Jon Peterson
                          Transparent Interconnection of Lots of Links
              INT         (TRILL): Problem and Applicability Statement
                          (Informational) - 2 of 4
                          draft-ietf-trill-prob-05.txt [Open Web
                          Ballot]
                   Token: Mark Townsley
              RTG         The RPF Vector TLV (Informational) - 3 of 4
                          draft-ietf-pim-rpf-vector-08.txt [Open Web
                          Ballot]
                   Token: David Ward
              SEC         ECDHE_PSK Ciphersuites for Transport Layer
                          Security (TLS) (Informational) - 4 of 4
                          draft-ietf-tls-ecdhe-psk-05.txt [Open Web
                          Ballot]
                   Token: Pasi Eronen

           3.1.2 Returning Item
                 NONE

     3.2 Individual Submissions Via AD

         Reviews should focus on these questions: "Is this document a
         reasonable
         contribution to the area of Internet engineering which it
         covers? If
         not, what changes would make it so?"

          3.2.1 New Item


             Area  Date

                         Private Session Initiation Protocol (SIP)
             RAI         Proxy-to-Proxy Extensions for Supporting the
                         PacketCable Distributed Call Signaling
                         Architecture (Informational) - 1 of 1
                         draft-andreasen-sipping-rfc3603bis-07.txt
                         [Open Web Ballot]
                         Note: Mary Barnes is proto shepherd
                  Token: Cullen Jennings

          3.2.2 Returning Item
                NONE

     3.3 Independent Submissions Via RFC Editor

         The IESG will use RFC 3932 responses: 1) The IESG has not
         found any conflict between this document and IETF work; 2) The
         IESG thinks that this work is related to IETF work done in WG
         <X>, but this does not prevent publishing; 3) The IESG thinks
         that publication is harmful to work in WG <X> and recommends
         not publishing at this time; 4) The IESG thinks that this
         document violates the IETF procedures for <X> and should
         therefore not be published without IETF review and IESG
         approval; 5) The IESG thinks that this document extends an
         IETF protocol in a way that requires IETF review and should
         therefore not be published without IETF review and IESG
         approval.

         The document shepherd must propose one of these responses in
         the Data Tracker note and supply complete text in the IESG
         Note portion of the write-up. The Area Director ballot
         positions
         indicate consensus with the response proposed by the
         document shepherd.

         Other matters may be recorded in comments, and the comments
         will
         be passed on to the RFC Editor as community review of the
         document.

               3.3.1 New Item
                     NONE
               3.3.2 Returning Item
                     NONE
     3.3.3 For Action

         Area  Date

         GEN         Analysis of Inter-Domain Routing Requirements and
                     History (Historic) - 1 of 2
                     draft-irtf-routing-history-09.txt
              Token: Russ Housley
         GEN         A Set of Possible Requirements for a Future
                     Routing Architecture (Historic) - 2 of 2
                     draft-irtf-routing-reqs-10.txt
              Token: Russ Housley


4. Working Group Actions

          4.1 WG Creation

                    4.1.1 Proposed for IETF Review
                                        NONE
                    4.1.2 Proposed for Approval
                                        NONE
         4.2 WG Rechartering

                   4.2.1 Under evaluation for IETF Review
                                       NONE
                  4.2.2 Proposed for Approval
                           Area  Date
                           OPS  Dec 17 Network Configuration (netconf)
                                       - 1 of 2
                                Token: Dan
                           TSV  Dec 19 IP Performance Metrics (ippm) -
                                       2 of 2
                                Token: Lars


5. IAB News We Can Use

6. Management Issues

6.1 IESG Statement regarding chartered work overcome by events before
IESG consideration (Ron Bonica)

7. Working Group News
