<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Leo,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
On timings... my justification here is that the dates of meetings aren't set, so there's a twofold problem, really. I would like the record to be kept for at least the two meetings
<b>following</b> the event at which the CoC was breached (and yes, I'm assuming that most of our breaches will happen at meetings). Furthermore, if one autumn meeting happens in October and the next in November, that means the information may, in some circumstances,
only be held for one meeting.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
On the major and minor, I'm not saying we should determine them, rather I'm saying that classification in general might not be a great idea.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Brian</div>
<div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div></div>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top:0px; margin-bottom:0px">Brian Nisbet (he/him)</p>
<p style="margin-top:0px; margin-bottom:0px">Service Operations Manager</p>
<p style="margin-top:0px; margin-bottom:0px">HEAnet CLG, Ireland's National Education and Research Network</p>
<p style="margin-top:0px; margin-bottom:0px">1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland</p>
<p style="margin-top:0px; margin-bottom:0px">+35316609040 brian.nisbet@heanet.ie www.heanet.ie</p>
<p style="margin-top:0px; margin-bottom:0px">Registered in Ireland, No. 275301. CRA No. 20036270 </p>
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Leo Vegoda <leo@vegoda.org><br>
<b>Sent:</b> Friday 1 April 2022 15:26<br>
<b>To:</b> Brian Nisbet <brian.nisbet@heanet.ie><br>
<b>Cc:</b> coc-tf@ripe.net <coc-tf@ripe.net>; chair-team@ripe.net <chair-team@ripe.net><br>
<b>Subject:</b> Re: [coc-tf] CoC Process and Next Steps</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">CAUTION[External]: This email originated from outside of the organisation. Do not click on links or open the attachments unless you recognise the sender and know the content is safe.<br>
<br>
<br>
Hi Brian,<br>
<br>
On Fri, Apr 1, 2022 at 1:37 AM Brian Nisbet <brian.nisbet@heanet.ie> wrote:<br>
><br>
> Leo,<br>
><br>
> Great stuff, thank you!<br>
><br>
> The data protection piece is fair, albeit I'd love to expand that to 18 and 36 months to guarantee it covering 3 meetings to more easily spot patterns, but Athina is the expert here.<br>
<br>
We didn't spend a long time discussing the specific periods. I suppose<br>
there are two questions:<br>
<br>
- What advantage do we get from retaining records for 50% longer?<br>
- How difficult would it be to change the record retention policy, if<br>
the Code of Conduct Team wanted to do so?<br>
<br>
> Under 4 we still say: "In all cases, the RIPE Chair Team and the RIPE NCC will be informed of a decision by the CoC Team before it is implemented." Is it intended to change that language to reflect only major (you said significant, but if we're using minor/major
language elsewhere, I'm assuming significant = major) breaches will be informed prior to implementation?<br>
<br>
You are right. That needs to be adjusted before we publish the draft.<br>
<br>
> My biggest concern is that we now have to create broad classifications of what a minor or major breach is, which I'll admit I'd been hoping we could avoid.<br>
<br>
Can we not leave that to the Code of Conduct Team, when they are<br>
selected? We have given non-exhaustive examples in the lists. If we<br>
try to define major and minor we'll still need the Code of Conduct<br>
Team to apply their good sense when something different happens.<br>
Perhaps it is simplest for them to take account of each individual<br>
situation and set a category accordingly?<br>
<br>
Thanks,<br>
<br>
Leo<br>
</div>
</span></font></div>
</body>
</html>