<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Good afternoon,</div>
<div><br>
</div>
<div>My point about whether we need to definite content was based as I said on my experience with PIR. The considerations may be different in the context of p/p obligations and processes than they are for a contracted party when reviewing a complaint about
a domain. </div>
<div><br>
</div>
<div>However, I focused on Steve’s description of malware as a content issue. Our posted anti-abuse policy lists malware as something that could cause us to act against a domain. The basis is that it creates a threat to the security and stability of the Internet.
Malware is not a content issue for purpose of our complaint analyses. </div>
<div><br>
</div>
<div>I may be forgetting a question. Let me know.</div>
<div><br>
</div>
<div>Don</div>
<br>
</body>
</html>