<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="">Dynamic assignments are not required to be registered… STATIC assignments are required to be registered, so that argument doesn’t work.<div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 20, 2017, at 13:54 , Chris James <<a href="mailto:chris@datacate.com" class="">chris@datacate.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra">@Paul - The API key is to email it.</div><div class="gmail_extra"><br class=""></div><div class="gmail_extra">@Owen - Very difficult when you have dynamic ranges, and vps/container platforms spanning tens of thousands of instances across these dynamic ranges.</div><div class="gmail_extra"><br class="">
<br class=""><div class="gmail_quote">On Thu, Jul 20, 2017 at 1:51 PM, Paul McNary <span dir="ltr" class=""><<a href="mailto:pmcnary@cameron.net" target="_blank" class="">pmcnary@cameron.net</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Owen<br class="">
<br class="">
The reassignment policy page says IPv6 has to be done vi API.<br class="">
Is that something else that is incorrect on the web site?<br class="">
<br class="">
Paul<br class="">
<br class="">
<br class="">
On 7/20/2017 3:16 PM, Owen DeLong wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How can it be overly difficult to fill out an email template with your customers’<br class="">
Name, Address, Phone Number?<br class="">
<br class="">
Really?<br class="">
<br class="">
Owen<br class="">
<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Jul 19, 2017, at 23:48 , Pallieter Koopmans <<a href="mailto:Pallieter@pallieter.org" target="_blank" class="">Pallieter@pallieter.org</a>> wrote:<br class="">
<br class="">
Hello,<br class="">
<br class="">
ARIN could quantify and require rules for when to SWIP, but in the<br class="">
end, there are going to be exceptions needed if the rules are to be<br class="">
strictly followed. Many will not separately SWIP a separately routed<br class="">
sub-block if it is too difficult or pointless to gather and share that<br class="">
data back upstream to ARIN.<br class="">
<br class="">
Thus a more fuzzy rule to require a best-effort and to add a<br class="">
rule-based reason (preferably both a carrot and a stick) for block<br class="">
owners to do their best to provide (only) useful data. In order to do<br class="">
that, one needs to look back at why that data is needed. For a block<br class="">
owner to assign the SWIP on a sub-block, he basically delegates tech<br class="">
and abuse contact requests down to those that are probably more likely<br class="">
to be able to actually act on the tech/abuse requests (and thus reduce<br class="">
request-handling workload higher up and overall). But for that to<br class="">
work, those tech/abuse contact requests need to be actually handled,<br class="">
otherwise, it is better to leave them with the block owner.<br class="">
<br class="">
In the end, the contact details should be as close to the "person"<br class="">
that is actually capable to both handle (think: volume/languages/etc)<br class="">
and act (think: authority) on the tech/abuse requests.<br class="">
<br class="">
eBrain<br class="">
Innovative Internet Ideas<br class="">
<br class="">
Pallieter Koopmans<br class="">
Managing Director<br class="">
<br class="">
<a href="tel:%2B31-6-3400-3800" value="+31634003800" target="_blank" class="">+31-6-3400-3800</a> (mon-sat 9-22 CET)<br class="">
Skype: PallieterKoopmans<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" target="_blank" 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" target="_blank" class="">info@arin.net</a> if you experience any issues.<br class="">
</blockquote>
______________________________<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" target="_blank" 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" target="_blank" class="">info@arin.net</a> if you experience any issues.<br class="">
</blockquote>
<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" target="_blank" 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" target="_blank" class="">info@arin.net</a> if you experience any issues.</blockquote></div><br class=""></div></div>
<br class="">
<font size="1" style="background-color:white" class=""><span style="font-family:Arial,sans-serif" class=""><span style="font:9px/11px Helvetica,Arial,sans-serif;color:rgb(153,153,153);text-transform:none;text-indent:0px;letter-spacing:normal;word-spacing:0px;float:none;display:inline!important;white-space:normal;background-color:rgb(255,255,255)" class="">This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. This company is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.</span></span></font>_______________________________________________<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=""></div></body></html>