<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hello All,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The list has been rather silent so I thought I would share the next iteration of my proposed differential access (aka tiered) model. Unfortunately ICANN has required Registration Authorities in the Temporary Specification to provide access to Legitimate Interest users but has provided little to no thought leadership on how to move forward with that demand.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As noted previously, my model defers to the hard work that others on this list have done on establishing the credentials for accreditation bodies. I instead have focus on market dynamics, governance and Registrant administrative remedies. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In addition to this policy/governance framework document, I have also drafted an Registrant Data Access Agreement which I will be posting shortly. This is designed to be a standard agreement by with Legitimate Interest Users can enter into with Registration Authorities to access their non-public Registrant data. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The only other missing piece which I have started work on this week, is the proposed ADR rules by which Data Subjects will be able to initiate a claim against a Legitimate Interest User which they believe has exceeded the scope of their legitimate use.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>With these three components, there will exist an entire eco-system for a new differentiated (tiered) access model. In the spirit of the GDPR this is a Privacy by Design model that is centered on placing the rights of the Data Subject at the apex of that hierarchy, as opposed to the current model where the Data Subject’s fundamental human rights are all too often collateral damage to other commercial interests. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As always I welcome any feedback.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Michael <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>