<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div id="x_compose-container" itemscope="" itemtype="https://schema.org/EmailMessage" style="direction:ltr">
<span itemprop="creator" itemscope="" itemtype="https://schema.org/Organization"><span itemprop="name"></span></span>
<div>
<div style="direction:ltr">Hi McTim,</div>
<div><br>
</div>
<div style="direction:ltr">While I agree language needs to be unequivocal I also acknowledge that sometimes you use language in a policy as an indication of intent and then request the community to help wordsmith that to come up with language that is mutually
acceptable to everyone.</div>
<div><br>
</div>
<div style="direction:ltr">That is what we have done here - we are not under the illusion that our wording is perfect or that we have it totally right - and we know that there are many in this community who can help us tighten this and get the language right,
that is what we are asking for here - let us come to mutually acceptable wording and if people feel language is ambiguous let us here suggestions and discuss.</div>
<div><br>
</div>
<div style="direction:ltr">We welcome input and we welcome further co-authors.</div>
<div><br>
</div>
<div style="direction:ltr">Thanks</div>
<div><br>
</div>
<div style="direction:ltr">Andrew </div>
<div><br>
</div>
<div class="x_acompli_signature">Get <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> McTim <dogwallah@gmail.com><br>
<b>Sent:</b> Wednesday, April 12, 2017 7:04:28 AM<br>
<b>To:</b> Keshwarsingh Nadan<br>
<b>Cc:</b> sm+afrinic@elandsys.com; Andrew Alston; Ben Roberts; Fiona Asonga; rpd@afrinic.net<br>
<b>Subject:</b> Re: [rpd] New Policy Proposal - "Anti-Shutdown (AFPUB-2017-GEN-001-DRAFT-01)"</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi,<br>
<br>
On Tue, Apr 11, 2017 at 6:48 PM, Keshwarsingh Nadan <kn@millenium.net.mu> wrote:<br>
> Moonesawmy<br>
><br>
>>In Section 1 of AFPUB-2017-GEN-001-DRAFT-01, it is stated that "these<br>
>>shutdowns have been shown to cause economic damage". Could you<br>
>>please provide some data about the economic damage?<br>
><br>
> I confine myself within bounds better suited to my own capacity, perhaps this could help?<br>
><br>
> <a href="https://www.brookings.edu/wp-content/uploads/2016/10/intenet-shutdowns-v-3.pdf">
https://www.brookings.edu/wp-content/uploads/2016/10/intenet-shutdowns-v-3.pdf</a><br>
><br>
>>What is the meaning of "direct provable relationships" in Section 13.1?<br>
><br>
> It is my belief that you should unsubscribe from this list since you were unable to understand the basic meaning of whatever you quoted above.<br>
<br>
That was fairly rude, SM has a good point, there is lots of room to<br>
fudge on this language.<br>
<br>
When we write policy, we should give the hostmasters unequivocal<br>
policy that is not open to interpretation.<br>
<br>
<br>
-- <br>
Cheers,<br>
<br>
McTim<br>
"A name indicates what we seek. An address indicates where it is. A<br>
route indicates how we get there." Jon Postel<br>
<br>
</div>
</span></font>
</body>
</html>