<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div dir="ltr">On May 2, 2019, at 8:29 AM, Fernando Frediani <<a href="mailto:fhfrediani@gmail.com">fhfrediani@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">On 02/05/2019 12:16, Scott Leibrand
wrote:<br>
</div>
<blockquote type="cite" cite="mid:84CD7519-05FD-45C5-8651-A4DD7F9B925B@gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
<div>ARIN’s only authority is to over their registry of who “has”
which addresses, so the only thing I can imagine they could do
would be to threaten to revoke unrelated registrations from a
transit provider who willfully or negligently accepted the BGP
announcement of space from an entity it wasn’t registered to.
But if tier 1 transit providers aren’t willing to filter, let
alone depeer, each other over hijacking today, it seems unlikely
they’d be willing to stop accepting formerly legitimate prefixes
from a peer or customer network just because ARIN is trying to
take that space away to punish the network for accepting an
unrelated hijacked announcement. <br>
</div>
</blockquote>
<br>
It doesn't really seem to be this the discussion about Transit
providers accepting or not certain announcements. Even if a Transit
Provider accepts announcements from people who are not responsible
for an allocation nor has authorization to do that they should only
be warned to take correction measures. I don't think the main aim of
the propose is do anything with Transit providers.<br>
Even in a hypothesis a Transit provider has no filters a hijack will
not occur if a hijacker doesn't initiate it.<br></div></blockquote><div><br></div><div>If the hijacker is someone with no relationship with ARIN, we can’t punish them by kicking them out of a club they’re not a member of. If you’re ok with ARIN doing nothing about hijacks by entities who don’t have ARIN resources, fine: that’s the status quo. But if you do want ARIN to do something on those cases (which I believe are the vast majority of hijacks) the only action I can see that ARIN could take at that point is against whichever of their transit providers is accepting the hijacked routes. </div><div><br></div><div>-Scott</div><br><blockquote type="cite"><div dir="ltr">
<blockquote type="cite" cite="mid:84CD7519-05FD-45C5-8651-A4DD7F9B925B@gmail.com">
<div><div>
<div dir="ltr"><br>
On May 2, 2019, at 7:18 AM, Adam Thompson <<a href="mailto:athompson@merlin.mb.ca" moz-do-not-send="true">athompson@merlin.mb.ca</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15
(filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:491264963;
mso-list-type:hybrid;
mso-list-template-ids:-1954626090 269025295 269025305 269025307 269025295 269025305 269025307 269025295 269025305 269025307;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Instead of focusing on whether the
current proposal is or isn’t in scope, I suggest we
re-cast the discussion as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">So
far, we have unanimous community agreement that BGP
hijacking is bad.<o:p></o:p></li>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">So
far, we have broad agreement that “something ought
to be done” about BGP hijacking, although detailed
opinions vary significantly.<o:p></o:p></li>
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1">So
what (else)
<b><u>can</u></b> ARIN do about it? (Caveat: the
answer “<i>nothing</i>” is unacceptable to a
significant proportion of PPML participants.)<o:p></o:p></li>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My suggested direction to the AC
and/or the board would therefore be: <b><i><u>Find</u></i></b>
something ARIN can do to help combat the problem (more
effectively). If this requires expanding the scope of
ARIN’s operations or policies, bring that back to the
membership (possibly via PPML?) with the accompanying
financial & legal analysis, as usual.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Now the question becomes: what is
the most appropriate mechanism, within ARIN’s existing
policies, to bring a request like that to the AC
and/or Board? It seems clear to me that the petition
already underway here is not meeting, and will not
meet, the needs of the community very well.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Adam<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;color:#44546A;mso-fareast-language:EN-CA" lang="EN-US">Adam Thompson</span></b><span style="font-size:9.0pt;color:#44546A;mso-fareast-language:EN-CA" lang="EN-US"><br>
Consultant, Infrastructure Services<br>
<b><image001.png></b><br>
100 - 135 Innovation Drive<br>
Winnipeg, MB, R3T 6A8<br>
(204) 977-6824 or 1-800-430-6404 (MB only)<br>
<a href="mailto:athompson@merlin.mb.ca" moz-do-not-send="true"><span style="color:#44546A">athompson@merlin.mb.ca</span></a><br>
<a href="http://www.merlin.mb.ca/" moz-do-not-send="true"><span style="color:#44546A">www.merlin.mb.ca</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>ARIN-PPML</span><br>
<span>You are receiving this message because you are
subscribed to</span><br>
<span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" moz-do-not-send="true">ARIN-PPML@arin.net</a>).</span><br>
<span>Unsubscribe or manage your mailing list subscription
at:</span><br>
<span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" moz-do-not-send="true">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br>
<span>Please contact <a href="mailto:info@arin.net" moz-do-not-send="true">info@arin.net</a> if you
experience any issues.</span><br>
</div>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.
</pre>
</blockquote>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>ARIN-PPML</span><br><span>You are receiving this message because you are subscribed to</span><br><span>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</span><br><span>Unsubscribe or manage your mailing list subscription at:</span><br><span><a href="https://lists.arin.net/mailman/listinfo/arin-ppml">https://lists.arin.net/mailman/listinfo/arin-ppml</a></span><br><span>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</span><br></div></blockquote></body></html>