<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>RPKI, BGPSec and other related stuff if a different thing from
what this proposal suggests. While the first ones are operational
stuff, therefore how each one operates and although advised and
good practice is always completely optional and discretionary to
each network the second is not necessarily an operational thing
and is an obligation to follow (not pretend you are someone else).
Some people may never implement RPKI, BGPSec and other related
stuff in any reasonable time.</p>
<p>Even when these practices are well deployed in most places there
may still be where they will not (or never). And on those cases
there may still be intentional hijacking cases and they must be
addressed and people must be held responsible.<br>
This proposal intends to make is very clear that using someone's
resources publicly and causing damage not only to an individual
but to a whole ecosystem depending on the case, is a violation of
the policy which they all agreed to respect and follow (think
about people not being able to access their online Banking because
someone hijacked their prefixes for example, is not just a damage
to the bank itself).</p>
<p>Those technical practices and this proposal are different things,
complementary and that works towards a common go in benefit to a
whole ecosystem.</p>
<p>Regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 04/05/2019 10:09, Töma Gavrichenkov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALZ3u+a0OLQnQMyCLPUYpAL2U=FRBJ3AtFkJNK4QQT56F4OzwA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">On Sat, May 4, 2019, 4:28 AM
Marilson Mapa <<a href="mailto:marilson.mapa@gmail.com"
moz-do-not-send="true">marilson.mapa@gmail.com</a>>
wrote:</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>I'm curious why do you not want to let
ARIN try to start getting involved to help
resolve the issue of hijacking?</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Let's be honest here. RPKI, BGPSec and BGP
roles could help resolving the issue of hijacking. This
initiative would tame it a bit at best, but must not be seen
as anything close to a silver bullet.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Actually, one of the strongest concerns of mine
with this proposal is that this may slow down the proper
solution (routing security) deployment due to a false sense of
security it provides.</div>
<div dir="auto"><br>
</div>
<div dir="auto">--</div>
<div dir="auto">Töma</div>
<div class="gmail_quote" dir="auto">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
</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>
</body>
</html>