<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 19 Aug 2017, at 8:13 pm, James Gannon <<a href="mailto:james@cyberinvasion.net" class="">james@cyberinvasion.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">Being honest, I’m not sure of the relevance to ICANN here.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">If we were at a Cloudflare conference I would agree as noted there is no process in that space.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">But in ICANN space, there is policy which is being followed to the letter. </span></div></div></div></blockquote><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>That is exactly why this discussion is relevant to ICANN policy space and NCUC. </div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="">There is no denial of access to infrastructure occurring here. There are private companies refusing service, as is their right, and ICANN policy on domain transfers within the 60 day window being applied. I don’t see where the discussion in the ICANN sphere is needed. No registry has blanket denied access to their registry, no RIR has denied access to IP space, and ICANN has not issued any policy edicts on the topic.</span></div></div></div></blockquote><span class="Apple-tab-span" style="white-space:pre"> </span></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I do not think the domain transfer policy was intended as a mechanism to lock registrants out of being able to have any active registrar, which is how it is being applied in effect here. That an ICANN policy is having an unintended effect (or at least, not widely understood effect that is somewhat controversial) is always worth discussing. </div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>David</div><div><br class=""></div></body></html>