<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
All, <br>
<br>
Trying to keep the core issues simple here, for my simple mind,
differential access and URL owner discretion over some access levels
are both obvious features and need to be built into any software,
but the devil is in the details of who has access to what here.<br>
<br>
If implementation has to run ahead of ICANN policy here, in support
of the "perfect not being the enemy of the good[enough]" I would
suggest an initial strategy that maximizes URL owner control over
access, and minimizes built in access to the legitimate account
management needs of registrar's and registries. Let further access
be determined by court order on a case by case basis.<br>
<br>
Beyond that, let further access follow policy decisions in which all
the stakeholders are engaged in the policy development dialogue and
policy development process. That may include national security
concerns and local law enforcement concerns being admitted to the
dialogue much the way GAC participates in policy discussions. <br>
<br>
Without thinking through whether this is a good idea or a bad idea:
<i>What are the merits of simply saying that national security and
law enforcement concerns should flow through GAC with those
agencies engaging in dialogue with their own respective GAC
representatives and the national agencies those GAC
representatives come from? </i><br>
<br>
Sam L.<br>
<br>
<div class="moz-cite-prefix"><font color="#000099">On 01/02/2016
9:14 AM, Carlton Samuels wrote:<br>
</font></div>
<blockquote
cite="mid:CAOZQb9TQSmov0B-mhAvRef5=DMQ0YnPrVjvebXTu61XYf+SZFw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><font color="#000099">I have a
more nuanced view of the ALAC's position. There is nothing
that says a conscientious data controller within the DNS
ecosystem - which to my understanding is a wider net than
gTLDs - cannot implement from Day One the software feature
set that makes differentiated access to RD possible.
Because it is likely that by doing so, early adopters in the
broader ecosystem could, by virtue of this endorsement, be
encouraged to make use of it.</font></div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><font color="#000099"><br>
</font></div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><font color="#000099">Sure, the
official ICANN use policy is lagging and that is not
unusual. But the consensus for differentiated access is
arguably well-formed. The perfect must not be allowed to
become the enemy of the good. Such a position merely signals
endorsement of the best practice and eschew its retardation.</font></div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><font color="#000099"><br>
</font></div>
<div class="gmail_default" style="font-family:comic sans
ms,sans-serif;font-size:small"><font color="#000099">-Carlton</font>
</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="gmail_signature"><br>
==============================<br>
Carlton A Samuels<br>
Mobile: 876-818-1799<br>
<i><font color="#33CC00">Strategy, Planning, Governance,
Assessment & Turnaround</font></i><br>
=============================</div>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
------------------------------------------------
"It is a disgrace to be rich and honoured
in an unjust state" -Confucius
------------------------------------------------
Dr Sam Lanfranco (Prof Emeritus & Senior Scholar)
Econ, York U., Toronto, Ontario, CANADA - M3J 1P3
email: <a class="moz-txt-link-abbreviated" href="mailto:Lanfran@Yorku.ca">Lanfran@Yorku.ca</a> Skype: slanfranco
blog: <a class="moz-txt-link-freetext" href="http://samlanfranco.blogspot.com">http://samlanfranco.blogspot.com</a>
Phone: +1 613-476-0429 cell: +1 416-816-2852</pre>
</body>
</html>