<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Oops, in my list of cases where the existing wording does not
make it optional (in my previous reply), I left out "the prefix is
being separately routed".</p>
<div class="moz-cite-prefix">On 9/29/2017 2:25 PM, David Farmer
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAN-Dau0WdX8LMTERfBp7PMj6Ew9Uh_0-BsfQtv08GZ2QaL3A6Q@mail.gmail.com">
<div dir="ltr">I will note the standard will not universally be
"should", if the reason the endusers wants the prefix registered
is they were given permission to route it, or its shorter than
/47, then the standard will be "shall", because of the clauses
in 6.5.5.1. <br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Sep 29, 2017 at 8:58 AM,
Jason Schiller <span dir="ltr"><<a
href="mailto:jschiller@google.com" target="_blank"
moz-do-not-send="true">jschiller@google.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">David, Kevin, Alison
<div><br>
</div>
<div>I am actually comfortable with an implementation
that is short of revocation, </div>
<div>but I am still not comfortable with "should". </div>
<div><br>
</div>
<div>Should makes it optional. Officially not being out
of compliance with</div>
<div>ARIN policy makes it optional. </div>
<div><br>
</div>
<div>I suggest that an ISP refusing to register a
downstream customer</div>
<div>is out of compliance with ARIN policy, and not just
choosing to ignore </div>
<div>an optional recommendation.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Further, a "shall" standard would not allow the ISP or
ARIN Staff any discretion, with a "shall" standard the
mere fact that the enduser made the request means the ISP
MUST make the registration, except for the reasons
explicitly provided in policy. If the ISP has a valid
reason, not explicitly covered in policy, to not make the
registration, a "should" standard allows ARIN Staff to
consider that on equal footing with the reasons the
enduser wants the registration.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>If it is only "should" then an ISP can still hold
the moral high ground</div>
<div>while refusing to support SWIP on the grounds that
they will not</div>
<div>implement tooling and commit resources when it is
only optional.</div>
<div><br>
</div>
<div>It is a question of if you can hold someone
accountable for not</div>
<div>complying or if they are free to ignore something
that is optional.</div>
</div>
</blockquote>
<div><br>
</div>
<div>"Should" is not completely optional, it recognizes
there could be valid reasons for an exception. Where as,
"shall" is required, unless an exception is explicitly
provided. "May" is completely optional. </div>
<div> </div>
<div>Therefore, with a "should" standard, if the situation
escalated to the point of ARIN making an official inquiry,
the ISP will need to articulate a valid reason why they
have not made the requested registration, that is at least
as compelling as the reason for the request by the
enduser. Not doing so would be tantamount to being out of
compliance with ARIN policy.</div>
<div><br>
</div>
</div>
<div>Thanks.</div>
<div><br>
</div>
-- <br>
<div
class="m_7123652226738876934gmail-m_8171138088900687058m_-7612373416746043169gmail_signature">==============================<wbr>=================<br>
David Farmer <a
href="mailto:Email%3Afarmer@umn.edu" target="_blank"
moz-do-not-send="true">Email:farmer@umn.edu</a><br>
Networking & Telecommunication Services<br>
Office of Information Technology<br>
University of Minnesota <br>
2218 University Ave SE Phone: <a
href="tel:%28612%29%20626-0815" value="+16126260815"
target="_blank" moz-do-not-send="true">612-626-0815</a><br>
Minneapolis, MN 55414-3029 Cell: <a
href="tel:%28612%29%20812-9952" value="+16128129952"
target="_blank" moz-do-not-send="true">612-812-9952</a><br>
==============================<wbr>================= </div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
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="http://lists.arin.net/mailman/listinfo/arin-ppml">http://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>
<br>
<pre class="moz-signature" cols="72">--
John Santos
Evans Griffiths & Hart, Inc.
781-861-0670 ext 539
</pre>
</body>
</html>