From fenner@fenron.com Mon May 4 03:58:51 2009 Return-Path: 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 3EC3A3A6DD3 for ; Mon, 4 May 2009 03:58:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.541 X-Spam-Level: X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, 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 RG2I+oZkJSnS for ; Mon, 4 May 2009 03:58:41 -0700 (PDT) Received: from runaway.fenron.com (unknown [IPv6:2001:470:117:128:230:48ff:fe92:8e81]) by core3.amsl.com (Postfix) with ESMTP id 776AA3A6FCD for ; Mon, 4 May 2009 03:58:40 -0700 (PDT) Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id n44B027J088080 for ; Mon, 4 May 2009 04:00:02 -0700 (PDT) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id n44B02wP088079 for rtg-dir@ietf.org; Mon, 4 May 2009 04:00:02 -0700 (PDT) (envelope-from fenner) Date: Mon, 4 May 2009 04:00:02 -0700 (PDT) Message-Id: <200905041100.n44B02wP088079@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) Subject: IESG agenda for 2009-05-07 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 10:58:51 -0000 IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2009-05-07). ----------------------------------------------------------------------- 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 TSV Apr 29 RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) draft-ietf-tsvwg-rsvp-proxy-proto-08 [txt] [Open Web Ballot] Note: Please read the informational document draft-ietf-tsvwg-rsvp-proxy-approaches before this one! IPR: * Cisco's Statement about IPR claimed in draft-ietf-tsvwg-rsvp-proxy-proto Token: Magnus Westerlund Point-to-Multipoint Multiprotocol Label Switching (MPLS) RTG May 02 Traffic Engineering (TE) Management Information Base (MIB) module (Proposed Standard) draft-ietf-mpls-p2mp-te-mib-09 [txt] [Open Web Ballot] Token: Ross Callon OPS May 02 RADIUS Design Guidelines (BCP) draft-ietf-radext-design-07 [txt] [Open Web Ballot] Token: Dan Romascanu Was deferred by Cullen Jennings on 2009-04-22 Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) INT May 03 Options for IEEE 802.21 Mobility Services (MoS) Discovery (Proposed Standard) draft-ietf-mipshop-mos-dhcp-options-13 [txt] [Open Web Ballot] Token: Jari Arkko SEC May 02 Transport Subsystem for the Simple Network Management Protocol (SNMP) (Proposed Standard) draft-ietf-isms-tmsm-17 [txt] [Open Web Ballot] Token: Pasi Eronen SEC May 02 Transport Security Model for SNMP (Proposed Standard) draft-ietf-isms-transport-security-model-13 [txt] [Open Web Ballot] Token: Pasi Eronen SEC May 03 Secure Shell Transport Model for SNMP (Proposed Standard) draft-ietf-isms-secshell-16 [txt] [Open Web Ballot] Token: Pasi Eronen Remote Authentication Dial-In User Service (RADIUS) Usage SEC May 03 for Simple Network Management Protocol (SNMP) Transport Models (Proposed Standard) draft-ietf-isms-radius-usage-06 [txt] [Open Web Ballot] Token: Pasi Eronen TSV May 04 The DCCP Service Code (Proposed Standard) draft-ietf-dccp-serv-codes-09 [txt] [Open Web Ballot] Token: Lars Eggert INT May 03 Mobile IPv6 Fast Handovers (Proposed Standard) draft-ietf-mipshop-rfc5268bis-01 [txt] [Open Web Ballot] Note: http://www.arkko.com/ietf/mipshop/ draft-ietf-mipshop-rfc5268bis-01-from-rfc5268.diff.html Token: Jari Arkko 2.1.2 Returning Item Area Date GEN May 02 Cryptographic Message Syntax (CMS) (Draft) rfc3852 [txt] [Open Web Ballot] Token: Tim Polk 2.2 Individual Submissions 2.2.1 New Item Area Date APP May 04 Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP) (Proposed Standard) draft-thomson-beep-async-02 [txt] [Open Web Ballot] Note: Chris Newman is the document shepherd. Token: Alexey Melnikov APP May 02 Internet Message Access Protocol (IMAP) - URL Access Identifier Extension (Proposed Standard) draft-ncook-urlauth-accessid-02 [txt] [Open Web Ballot] Note: Eric Burger is the document shepherd. This document is a Normative dependency for a Lemonade WG document, updating another Lemonade document. Token: Alexey Melnikov 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item Area Date APP May 02 Lemonade Notifications Architecture (Informational) draft-ietf-lemonade-notifications-10 [txt] [Open Web Ballot] Note: Eric Burger is the document shepherd. Token: Alexey Melnikov SEC May 02 The Camellia Cipher in OpenPGP (Informational) draft-ietf-openpgp-camellia-04 [txt] [Open Web Ballot] Note: Derek Atkins has agreed to shepherd Token: Tim Polk RTG Apr 29 Industrial Routing Requirements in Low Power and Lossy Networks (Informational) draft-ietf-roll-indus-routing-reqs-05 [txt] [Open Web Ballot] Note: This I-D was updated after IETF last call to synchronise with IESG review comments made for draft-ietf-roll-urban-routing-reqs. It also pickes up GenArt review coments. Token: Adrian Farrel TSV May 03 RSVP Proxy Approaches (Informational) draft-ietf-tsvwg-rsvp-proxy-approaches-06 [txt] [Open Web Ballot] Note: Read this before the Protocol document IPR: * Cisco's Statement about IPR claimed in draft-ietf-tsvwg-rsvp-proxy-approaches-02.txt Token: Magnus Westerlund 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item Area Date RAI Apr 29 Report from the IETF workshop on P2P Infrastructure, May 28, 2008 (Informational) draft-p2pi-cooper-workshop-report-01 [txt] [Open Web Ballot] Token: Cullen Jennings 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item Area Date SEC May 01 Password-Authenticated Diffie-Hellman Exchange (PAK) (Informational) draft-brusilovsky-pak-10 [txt] [Open Web Ballot] IPR: * Alcatel-Lucent's Statement about IPR related to draft-brusilovsky-pak-10 Token: Tim Polk INT Apr 30 Transmission of IPv4 Packets over ISATAP Interfaces (Informational) draft-templin-isatapv4-02 [txt] [Open Web Ballot] Token: Jari Arkko 3.3.2 Returning Item Area Date RAI May 03 Media Server Markup Language (MSML) (Informational) draft-saleem-msml-08 [txt] [Open Web Ballot] IPR: * Convedia's statement about IPR claimed in draft-saleem-msml Token: Robert Sparks 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review Area Date APP Apr 29 Yet Another Mail (yam) Token: Alexey TSV Apr 25 STORage Maintenance (storm) Token: Lars APP Apr 28 Extensible Messaging and Presence Protocol (xmpp) Token: Cullen 4.1.2 Proposed for Approval Area Date APP Apr 06 Open Authentication Protocol (oauth) Token: Lisa 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review Area Date RAI Apr 30 Audio/Video Transport (avt) Token: Cullen 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 7. Working Group News From fenner@fenron.com Mon May 18 03:58:32 2009 Return-Path: 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 E9FC828C250 for ; Mon, 18 May 2009 03:58:32 -0700 (PDT) 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 67XEmnND-45A for ; Mon, 18 May 2009 03:58:31 -0700 (PDT) Received: from runaway.fenron.com (unknown [IPv6:2001:470:117:128:230:48ff:fe92:8e81]) by core3.amsl.com (Postfix) with ESMTP id 8BABB3A7028 for ; Mon, 18 May 2009 03:58:31 -0700 (PDT) Received: from runaway.fenron.com (localhost [127.0.0.1]) by runaway.fenron.com (8.13.8/8.13.8) with ESMTP id n4IB027q031334 for ; Mon, 18 May 2009 04:00:02 -0700 (PDT) (envelope-from fenner@runaway.fenron.com) Received: (from fenner@localhost) by runaway.fenron.com (8.13.8/8.13.8/Submit) id n4IB02s9031333 for rtg-dir@ietf.org; Mon, 18 May 2009 04:00:02 -0700 (PDT) (envelope-from fenner) Date: Mon, 18 May 2009 04:00:02 -0700 (PDT) Message-Id: <200905181100.n4IB02s9031333@runaway.fenron.com> From: fenner@fenron.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) Subject: IESG agenda for 2009-05-21 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 10:58:33 -0000 IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2009-05-21). ----------------------------------------------------------------------- 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 TSV May 17 RSVP Extensions for Path-Triggered RSVP Receiver Proxy (Proposed Standard) draft-ietf-tsvwg-rsvp-proxy-proto-09 [txt] [Open Web Ballot] Note: Please read the informational document draft-ietf-tsvwg-rsvp-proxy-approaches before this one! IPR: * Cisco's Statement about IPR claimed in draft-ietf-tsvwg-rsvp-proxy-proto Token: Magnus Westerlund Was deferred by Cullen Jennings on 2009-05-05 INT May 14 IPv4 Support for Proxy Mobile IPv6 (Proposed Standard) draft-ietf-netlmm-pmip6-ipv4-support-12 [txt] [Open Web Ballot] Token: Jari Arkko TSV May 18 DCCP Simultaneous-Open Technique to Facilitate NAT/ Middlebox Traversal (Proposed Standard) draft-ietf-dccp-simul-open-08 [txt] [Open Web Ballot] Token: Lars Eggert RTG May 17 MPLS Generic Associated Channel (Proposed Standard) draft-ietf-mpls-tp-gach-gal-05 [txt] [Open Web Ballot] Note: This I-D was last called in MPLS and PWE3 It has been approved by the ITU-T IANA comments have been answered satisfactorily Loa Andersson (loa@pi.nu) is the document shepherd Token: Adrian Farrel 2.1.2 Returning Item Area Date SEC May 14 An Internet Attribute Certificate Profile for Authorization (Proposed Standard) draft-ietf-pkix-3281update-05 [txt] [Open Web Ballot] Token: Tim Polk 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item Area Date RAI May 13 H.248/MEGACO Registration Procedures (BCP) draft-groves-megaco-pkgereg-03 [txt] [Open Web Ballot] Note: IESG - when reviewing this, please consider the topic of if it is alright to register a "public" package when the specification is not publicly available. This came up as an IETF LC comment. Token: Cullen Jennings 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item Area Date TSV May 15 Adding Explicit Congestion Notification (ECN) Capability to TCP's SYN/ACK Packets (Experimental) draft-ietf-tcpm-ecnsyn-09 [txt] [Open Web Ballot] Token: Lars Eggert SEC May 16 DomainKeys Identified Mail (DKIM) Service Overview (Informational) draft-ietf-dkim-overview-11 [txt] [Open Web Ballot] Token: Pasi Eronen TSV May 17 RSVP Proxy Approaches (Informational) draft-ietf-tsvwg-rsvp-proxy-approaches-07 [txt] [Open Web Ballot] Note: Read this before the Protocol document IPR: * Cisco's Statement about IPR claimed in draft-ietf-tsvwg-rsvp-proxy-approaches-02.txt Token: Magnus Westerlund Was deferred by Cullen Jennings on 2009-05-05 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item NONE 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item NONE 3.3.3 For Action Area Date INT May 14 The Subnetwork Encapsulation and Adaptation Layer (SEAL) (Informational) draft-templin-seal-23 [txt] [Open Web Ballot] Note: Brought back to the agenda because of desired status change (now Inf) Token: Jari Arkko GEN May 13 Unintended Consequence of two NAT deployments with Overlapping Address Space (Informational) draft-ford-behave-top-06 [txt] Token: Russ Housley 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval Area Date APP Apr 29 Yet Another Mail (yam) Token: Alexey APP Apr 28 Extensible Messaging and Presence Protocol (xmpp) Token: Cullen 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 Ballot Procedures (Russ Housley) 6.2 Revision 1.9 for ID-Checklist.html (Russ Housley) 6.3 Shepherd names in agendas (Jari Arkko) 7. Working Group News From rcallon@juniper.net Mon May 18 07:32:39 2009 Return-Path: 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 71C233A704E for ; Mon, 18 May 2009 07:32:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.472 X-Spam-Level: X-Spam-Status: No, score=-6.472 tagged_above=-999 required=5 tests=[AWL=0.127, BAYES_00=-2.599, 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 d+VQ9lfZm+C9; Mon, 18 May 2009 07:32:32 -0700 (PDT) Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by core3.amsl.com (Postfix) with ESMTP id 7B3C928C30F; Mon, 18 May 2009 07:31:23 -0700 (PDT) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKShFxmgnkNtCIhTdcEIo9u+kayvYPlb+8@postini.com; Mon, 18 May 2009 07:32:59 PDT 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.340.0; Mon, 18 May 2009 07:28:18 -0700 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 May 2009 07:28:18 -0700 Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 May 2009 07:28:18 -0700 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: Status of the Routing Area Directorate Date: Mon, 18 May 2009 10:28:16 -0400 Message-ID: <3525C9833C09ED418C6FD6CD9514668C06863E97@emailwf1.jnpr.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Status of the Routing Area Directorate Thread-Index: AcnU0PmlKVQubdPJSQiAb4bzpO43qgC82bQw From: Ross Callon To: X-OriginalArrivalTime: 18 May 2009 14:28:18.0512 (UTC) FILETIME=[E3610D00:01C9D7C4] Cc: Ross Callon , Adrian Farrel , rtg-chairs@ietf.org X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 14:32:39 -0000 We (Adrian and Ross) think we are not getting the best out of the routing area directorate. This is probably for many reasons, but at least includes the fact that as ADs we have not properly defined the role of the directorate nor our expectations. We think that we should disband the directorate while we work out what it is we want the directorate to do. Then we will be able to recruit again with a specific charter and clearly defined roles. However, we are intending to keep the current rtg-dir email list open until the week before the Stockholm IETF in order to facilitate discussion of how to make better future use of a new directorate. Your views on what the routing directorate could/should be doing would be very welcome and can be sent to the rtg-dir list prior to Stockholm, sent to us directly, or discussed with us in Stockholm. We will flush the routing directorate mailing just prior to the Stockholm IETF, and resubscribe for the new directorate when (and if) it is formed. In terms of what the directorate *should* be doing, there are several possibilities that come to mind: 1) Review some specific documents when asked by the routing ADs. 2) Review all documents that are relevant to the routing area (including all routing area documents, most or all Internet area documents, and probably a few other documents). 3) Help advise the routing ADs when particular questions arise that require judgement and/or specific knowledge. 4) Get together at IETF meetings (or elsewhere) to discuss routing area issues. (Some problems come to mind with this idea: We are all already too busy during IETF meetings; we are unlikely to have either desire or budget to fly to a meeting at any alternate location; it is not clear that we have any urgent routing area issues to discuss that aren't already being discussed elsewhere). In terms of how to ensure that directorate members actually do something in the role (and not just sit on the list and ignore emails to it), we are not quite sure of the preferred approach. One option for document review is to explicitly assign documents to individuals, and fire people from the list if they don't get the review done (with agreed guidelines on how a member can refuse one particular assignment, and how often this is permitted). Another option is to send emails to the list along the lines of "we need one per document volunteer to review the following list of documents", and then fire people who don't review some minimum number of documents (perhaps, one per month(?)). We would be very interested in getting input on any of: What the routing directorate should do, how to ensure that members contribute, and any other topics related to making better use of the directorate. Thanks for your input on this subject. Also, many thanks for the time and effort you have given over the years. Adrian and Ross From rcallon@juniper.net Mon May 18 07:32:57 2009 Return-Path: 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 5E2BA28C308 for ; Mon, 18 May 2009 07:32:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.728 X-Spam-Level: X-Spam-Status: No, score=-5.728 tagged_above=-999 required=5 tests=[AWL=-0.619, BAYES_05=-1.11, 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 ol2C-MPq0kkf; Mon, 18 May 2009 07:32:51 -0700 (PDT) Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by core3.amsl.com (Postfix) with ESMTP id 67CDD3A703F; Mon, 18 May 2009 07:32:37 -0700 (PDT) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKShFx5fnUlLkir7NBcA7f1koNCk7XziiO@postini.com; Mon, 18 May 2009 07:34:13 PDT 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.340.0; Mon, 18 May 2009 07:30:22 -0700 Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 May 2009 07:30:22 -0700 Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 18 May 2009 07:30:22 -0700 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_01C9D7C5.2C773C1F" Subject: Vacation this week Date: Mon, 18 May 2009 10:30:20 -0400 Message-ID: <3525C9833C09ED418C6FD6CD9514668C06863E98@emailwf1.jnpr.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Vacation this week Thread-Index: AcnXxSwV2uvYj6jKRHupeihsidtOMg== From: Ross Callon To: , X-OriginalArrivalTime: 18 May 2009 14:30:22.0547 (UTC) FILETIME=[2D4F4A30:01C9D7C5] X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 14:32:57 -0000 ------_=_NextPart_001_01C9D7C5.2C773C1F Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable I am on vacation all of this week, and next monday. I will be sporadically checking email.=20 =20 Thanks, Ross =20 ------_=_NextPart_001_01C9D7C5.2C773C1F Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

I am on vacation all of this week, and next monday. I = will be sporadically checking email.

 

Thanks, Ross

 

------_=_NextPart_001_01C9D7C5.2C773C1F--