<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On May 23, 2012, at 12:30 AM, Martin Hannigan wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">.3.4
Notice of Refusal<br>
<br>
ARIN will provide a written and detailed notice that includes the<br>
specific reasons why when refusing any number resource or ASN transfer. This<br>
notice will be provided to all parties to a transfer.<br>
</span></blockquote>
</div>
<br>
<div>Martin - </div>
<div> </div>
<div> It is generally the recipient who has difficulty qualifying during a transfer, </div>
<div> and while the specific reason is often "Recipient can't demonstrate need </div>
<div> in accordance with policy", the proposed language suggests that more </div>
<div> detailed information should be returned to both the current resource holder </div>
<div> and intended recipient. If that is the case, then it is important to note that</div>
<div> this information may contain technical & business planning information of </div>
<div> the intended recipient which is only known to ARIN via NDA and therefore </div>
<div> not readily releasable. </div>
<div><br>
</div>
<div> Of course, this may not be as frequent an issue given the legacy aspects</div>
<div> of the proposed policy change, but as written, the notice would appear </div>
<div> to apply to transfers of any resources and may run afoul of NDA terms</div>
<div> unless this disclosure is very clearly specified in the proposed policy, </div>
<div> and specifically authorized in advance by intended recipients when </div>
<div> applying to transfer resources. Supplying this information to only the </div>
<div> recipient would not cause this problem (and we presently do provide</div>
<div> that information in the request ticket) but that may not meet your goals</div>
<div> for the proposed policy change.</div>
<div><br>
</div>
<div>FYI,</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
</body>
</html>