[RTG-DIR] PLEASE READ: New routing directorate processes

Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com> Thu, 02 March 2017 21:28 UTC

Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 568E312964D; Thu, 2 Mar 2017 13:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metaswitch.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gv2agJIiJiPl; Thu, 2 Mar 2017 13:28:35 -0800 (PST)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0129.outbound.protection.outlook.com [104.47.38.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60B49120724; Thu, 2 Mar 2017 13:28:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=/F+ERLjhSsIFkpg5dU/6RU5L6Pdqq8XXu/+l6BsN3/U=; b=eguQL6nmYB+wth8HUUGsTwqkjUviPH0NIq1cemCsLWhP8bwYPbUvCmmVlNNMrOqDrXTgruPl2rlS0IpCv2rM6hYXDNEHx9OLkqrIe4Oj1UdrgCi39iZWt8M30MUWau7xsOqttoDwpCCuS6VwC67kqzgCTp0vro4k08EcbiCsryk=
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) by BY2PR0201MB1911.namprd02.prod.outlook.com (10.163.75.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.12; Thu, 2 Mar 2017 21:28:33 +0000
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) by BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) with mapi id 15.01.0933.020; Thu, 2 Mar 2017 21:28:32 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: "rtg-ads@ietf.org" <rtg-ads@ietf.org>, "rtg-chairs@ietf.org" <rtg-chairs@ietf.org>, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
Thread-Topic: PLEASE READ: New routing directorate processes
Thread-Index: AdKTlTjJE13w9z04Q0mvwdRkw4lUfw==
Date: Thu, 02 Mar 2017 21:28:32 +0000
Message-ID: <BY2PR0201MB1910C3E2073A819B00DA7A7E84280@BY2PR0201MB1910.namprd02.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [86.132.75.121]
x-ms-office365-filtering-correlation-id: 057dc5d2-7d39-4f6e-2b21-08d461b313f5
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BY2PR0201MB1911;
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1911; 7:+dd+nbXhbXznmJzAW5pkTq8UXloN1MHQCnr4Je/VJ4RBHtneCyt6BnXEwHJPeHF46OO+oS/DK5ssVLz+p1PP9xu9IiblSBsiWOH8jgWJDigdJo/lKCwowglm6IAMxQTWcwNeyPabvsBfzO/U2J6Gv3OaZ7YNEJNXk8ztjWHTTDidGwkPTL/bnq/Tdr8WZ3sEsk/qxbgLvhC/gZqo08GM4JNUyU3PoPRx08mEUo7oKUb0ZNZaboQW5J7Xldjx6RJf6zvNpa9cIW+dorUfCLbgWEr4r+S1KQGn5cZNQJ2W8op9ArWj2aUez4clTwDubPjPcHJSB/JmD5f2CJB/OedjQA==
x-microsoft-antispam-prvs: <BY2PR0201MB19112A6F58362A8C1B4A911A84280@BY2PR0201MB1911.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(50582790962513)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123562025)(20161123558025)(20161123564025)(20161123560025)(20161123555025)(6072148); SRVR:BY2PR0201MB1911; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1911;
x-forefront-prvs: 023495660C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(39450400003)(25584004)(33656002)(2201001)(53936002)(55016002)(25786008)(38730400002)(81166006)(6506006)(189998001)(7696004)(7736002)(77096006)(122556002)(575854001)(86362001)(54356999)(50986999)(3846002)(6436002)(790700001)(6116002)(102836003)(2900100001)(9686003)(5660300001)(6306002)(54896002)(3660700001)(74316002)(606005)(236005)(3280700002)(2906002)(99286003)(2501003)(4326008)(8936002)(66066001)(10126004)(8676002)(92566002)(7906003); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1911; H:BY2PR0201MB1910.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR0201MB1910C3E2073A819B00DA7A7E84280BY2PR0201MB1910_"
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Mar 2017 21:28:32.5457 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1911
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-dir/chrRnZomjlK9Hf7CZe7lcDJTh8Y>
Cc: Min Ye <amy.yemin@huawei.com>
Subject: [RTG-DIR] PLEASE READ: New routing directorate processes
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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>
X-List-Received-Date: Thu, 02 Mar 2017 21:28:38 -0000

Dear RTG ADs, RTG chairs and Directorate Members

As many of you will have already noticed, we have recently started to use a new system for managing review assignments in the Routing Area Directorate.  This system, which was implemented by Robert Sparks and Tero Kivinen, integrates your review assignments directly with the IETF datatracker.  It is now being used by many (perhaps all) of the IETF's directorates.

The new system

a)      makes it easier and faster to request reviews of documents

b)      simplifies the communications between the directorate coordinators and directorate members

c)      links a draft's datatracker page with the directorate's review(s).

This email sets out the implications for you as ADs, chairs and directorate members.  If you have any questions or comments, please let me know.


If you are an AD
You can request the directorate to review a draft (either at IETF last call or any other time) directly from the draft's page in the datatracker.  If the directorate has already reviewed the draft then you will see links to the previous reviews on that page.  Click on the link to "request a review".  You will need to select the type of the review (typically "IETF last call" or "Early review") and set a deadline.  Submit the request, and then the co-ordinators will do the rest.


If you are a WG chair
WG chairs are also free to request a directorate review of any of their WG's drafts, at any time.  Please follow the same procedure as the ADs, above.  You should set the review type to "Early review" if the draft is still in the working group (i.e. not already with the IESG).


If you are a member of the directorate
Please see the following web page, where you can manage all of your directorate assignments and preferences.  (You need to be logged into your datatracker account.)
https://datatracker.ietf.org/accounts/review/

This page shows your current assignments as well as your previously completed assignments.  You can set preferences for how often you want to receive assignments, configure periods that you will be unavailable, set up automatic reminders for assignments that you have accepted, etc.  You can also use this page to register an interest in reviewing a particular draft for the directorate (although, of course, do feel free to review any draft you like at any time!)

The directorate coordinators will (normally) hand out assignments using a round robin algorithm, although the tool will help us to take your individual reviewing preferences into account.  When you are given an assignment, you will receive an email from myself (jonathan.hardwick@metaswitch.com<mailto:jonathan.hardwick@metaswitch.com>) or Amy (amy.yemin@huawei.com<mailto:amy.yemin@huawei.com>).  The email will contain a link to the datatracker for your convenience - please click on it and tell us if you will accept the assignment, or not.  We will try to remind you about your assignment if we don't see a response, but it is better if we don't have to chase.  Please adjust your email filters to permit these emails.

When you have completed your assignment, please go to your review page in the datatracker (the above link) and close down the assignment.  You can either enter a link to an email that you've already sent to the RTG-DIR list, or you can paste your review directly into the datatracker.  Whatever works best for you.


Best regards
Jon & Amy