<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=""><div class="">I’d argue that SWIP has historically been the primary mechanism by which recipients of allocations document their utilization of received space; is this still the case? Or are other means of documenting utilization now acceptable for allocations? (Asking as someone who hasn’t done a SWIP in 7+ years)...</div><div class=""><br class=""></div><div class="">-C</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 17, 2017, at 10:08 AM, David Huberman <<a href="mailto:daveid@panix.com" class="">daveid@panix.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">In addition to these options/questions, I feel like we glossed over the question posed by Marty Hannigan: what is the value of REQUIRING SWIP anymore? As a community member (not as an AC member) I have trouble supporting any of these as I'm not sure I support SWIP being anything other than voluntary. Whois reassignments are not the proper place for the information LE wants, in my opinion, and has almost no value to NOCs. And ARIN doesn't need it anymore for qualification purposes for a scarce resource. So what's he point of all this? Genuine question; no tone implied.<br class=""><br class="">Sent from my iPhone</div><div class=""><br class="">On Jul 17, 2017, at 12:13 PM, Jason Schiller <<a href="mailto:jschiller@google.com" class="">jschiller@google.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">I am replying to bring the conversation to one of the suggestions <div class="">on the table.<div class=""><br class=""></div><div class="">Owen DeLong's suggesting of SWIP all IPv6 business users, and </div><div class="">not Residential users,</div><div class=""><br class=""></div><div class="">Or Kevin Blumberg (and David Farmer) suggestion of SWIP'ing all </div><div class="">prefixes that might show up as a more specific in the global routing </div><div class="">table.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">These are roughly the same result, and have a question of which</div><div class="">has a more easily understandable policy. </div><div class=""><br class=""></div><div class="">The question is who here supports one or both of these </div><div class="">proposals?</div><div class=""><br class=""></div><div class="">Who oppose one (if so which one) or both of these proposals?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">I would like to suggest one friendly amendment... </div><div class="">- ISPs are required to SWIP IP space that is a reallocation. </div><div class="">- ISPs are required to SWIP IP space that is a reassignment</div><div class=""> whenever that down stream customer requests such. That </div><div class=""> SWIP must be a reassign detail, reassign simple, or a </div><div class=""> residential privacy (if applicable) per the customer request.</div><div class=""><br class=""></div><div class="">___Jason</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Jul 17, 2017 at 10:42 AM, John Curran <span dir="ltr" class=""><<a href="mailto:jcurran@arin.net" target="_blank" class="">jcurran@arin.net</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 17 Jul 2017, at 9:47 AM, <a href="mailto:hostmaster@uneedus.com" class="">hostmaster@uneedus.com</a> wrote:<br class="">
> ,,,<br class="">
<span class="">> This is the problem. ARIN is not a carrier. While disclosure to ARIN to obtain number resources for the connection is OK, Public disclosure by or at the direction of ARIN policy of elements like domain name, name, address and telephone number is not. Since name, address, telephone number and domain name have already been identified have been defined in the order as elements of CPNI that are protected, world disclosure by ARIN or because of ARIN rules would not be a protected disclosure.<br class="">
><br class="">
> The ISP might also be in trouble for providing the information to ARIN, if they know that ARIN intends to publish this information in a public directory, rather than disclosing it to ARIN solely to maintain number resources. As suggested by the OP, might have to call them customer 1-n. However that would violate the NRPM as written. Since the City, State and Zip Code are part of the address, even the "protected" residential records CPNI are being disclosed in violation of the CPNI Order.<br class="">
><br class="">
> There is a big difference between disclosure to ARIN for taking care of numbering policy, and disclosure to the entire world. Third party disclosure is the main thing that the CPNI rules are intended to address. That is only permitted when it is needed for the provision of service.<br class="">
<br class="">
</span>Compliance with registry policy is indeed necessary to receive number resources;<br class="">
it is up to you to determine whether IP number resources are necessary for provision<br class="">
of your Internet services.<br class="">
<br class="">
If you choose not to make use of Internet Numbers Registry System resources for<br class="">
provision of Internet services (or not assign them to your customers), then that is<br class="">
your choice. Some ISPs may feel that it is necessary to seek consent of customers<br class="">
who wish to have public IP number resources assigned in the size that would result in<br class="">
their publication in the public registry, whereas others may not based on their reading<br class="">
of applicable regulations regarding handling of CPNI information. Such choices are<br class="">
an operational and business matter left to each ISP to decide based on their individual<br class="">
understanding and circumstances.<br class="">
<br class="">
Thanks!<br class="">
<span class="im HOEnZb">/John<br class="">
<br class="">
John Curran<br class="">
President and CEO<br class="">
</span><div class="HOEnZb"><div class="h5">ARIN<br class="">
<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
PPML<br class="">
You are receiving this message because you are subscribed to<br class="">
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank" class="">http://lists.arin.net/mailman/<wbr class="">listinfo/arin-ppml</a><br class="">
Please contact <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.<br class="">
</div></div></blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><font color="#555555" face="'courier new', monospace" class=""><div class=""><span style="font-family: arial;" class=""><font color="#555555" face="'courier new', monospace" class="">_______________________________________________________<br class=""></font><div class=""><font face="'courier new', monospace" class="">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank" class="">jschiller@google.com</a>|571-266-0006</font></div><div class=""><font face="'courier new', monospace" class=""><br class=""></font></div></span></div></font></div>
</div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">PPML</span><br class=""><span class="">You are receiving this message because you are subscribed to</span><br class=""><span class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).</span><br class=""><span class="">Unsubscribe or manage your mailing list subscription at:</span><br class=""><span class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br class=""><span class="">Please contact <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.</span></div></blockquote></div>_______________________________________________<br class="">PPML<br class="">You are receiving this message because you are subscribed to<br class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="http://lists.arin.net/mailman/listinfo/arin-ppml" class="">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">Please contact info@arin.net if you experience any issues.</div></blockquote></div><br class=""></body></html>