<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear all, <br>
<br>
Our next task force call will be on Monday, 6 February from 2pm-3pm
(UTC+1). We will send the WebEx details a little closer to then. <br>
<br>
The proposed agenda and action items are below. <br>
<br>
Kind regards<br>
<br>
Antony<br>
<br>
<br>
###<br>
<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<b>Proposed Agenda</b><br>
<br>
1) Welcome, finalise agenda, adopt minutes<br>
2) Reviewing Action Items<br>
3) Agreement on Updated Scope<br>
4) Task Force Membership/Mailing List Subscriptions<br>
5) Agreement on Website Content<br>
6) Timeline and Workplan<br>
7) Scheduling Future TF Calls <br>
8) Participation of Task Force Members<br>
<br>
<br>
<b>Action Items</b><br>
<br>
20171801-1: RIPE NCC to capture the wording of the TF’s comments on
scope and produce an updated document to send to the mailing list.
<br>
<br>
20171801-2: RIPE NCC to come up with a draft timeline for the TF. <br>
<br>
20171801-3: Filiz to start a discussion about transparency/web
documentation on the mailing list. <br>
<br>
20171801-4: Filiz to start a discussion regarding openness of TF
calls on the mailing list. <br>
<br>
20171801-5: RIPE NCC to make poll covering Feb, March, April, and
one meeting before RIPE 74. The deadline for TF members to enter
their preferences should be one week. <br>
<br>
20171801-6: Filiz to start a discussion on the mailing list about
how open the TF should be. <br>
<br>
20163011-1: Task force members to each come up with a few topics
they want the Task Force to address and share this on the mailing
list. <br>
<br>
20163011-2: The RIPE NCC to map out areas where accountability
features are already.<br>
<br>
</body>
</html>