<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello Job<br>
</p>
<br>
<div class="moz-cite-prefix">On 08/06/2018 2:55 PM, Job Snijders
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20180608105534.GJ29935@vurt.meerval.net">
<pre wrap="">On Fri, Jun 08, 2018 at 02:39:29PM +0400, Daniel Shaw wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 08/06/2018, 13:58, Job Snijders typed:
</pre>
<blockquote type="cite">
<pre wrap="">Daniel, what is the status on the request that it becomes easier to
create route-objects for AfriNIC-managed IP space in the AFRINIC IRR
where non-AfriNIC-managed ASNs are specified as Origin?
</pre>
</blockquote>
<pre wrap="">
I'll repeat I personally see no downside, and there is clearly at
least a handful of people that would like this. Further to summarise
in this thread, I'm not aware of any specific objections to changing
in this way.
[snip]
- When an AFRINIC member who has in-region IP resources, but an
out-of-region ASN logs a request by email/ticket system, the repose
from the customer service folks is good, and they respond to the
request in good time.
</pre>
</blockquote>
<pre wrap="">
That is good to hear
</pre>
<blockquote type="cite">
<pre wrap="">- I also do not believe the argument about operational changes at odd
hours and short notice holds. I stand to be corrected, but I believe
that once the out-of-region 'autnum' is added to the IRR manual (once)
along with a 'mnt-by' that the member controls, that thereafter they
can create, add, or change route(6) objects themselves and auth
against their 'mnt-by' person or role, attached to the origin
'autnum'.
</pre>
</blockquote>
<pre wrap="">
Wait - AfriNIC staff should NOT be creating additional "autnum:" objects
in the AFRINIC database. Those objects already exist in other databases,
AfriNIC is not authoritative for non-AfriNIC managed objects. Can you
elaborate? It would truly be a shame if the community expends
significant energy to clean up one database to introduce a new level of
pollution in another database.
Simply don't require the Origin ASN to be a reference to any object,
consider it a 32-bit integer (and forbid the private & bogon asns).</pre>
</blockquote>
AFRINIC does not create the autnum in the AFRINIC database.
Documentation similar to below will be published on the AFRINIC
website shortly. <br>
<b style="font-weight:normal;"
id="docs-internal-guid-a173c3be-df0f-0ab1-3a64-8f1d2cf7823c">
<h2 dir="ltr"
style="line-height:1.38;margin-top:24pt;margin-bottom:6pt;"><span style="font-size:16pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Creating a Route object with OOR ASN: </span></h2>
<ol style="margin-top:0pt;margin-bottom:0pt;">
<li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Requester submits object to be created on the AFRINIC IRR, via one of the whois interfaces(CLI, Web-update)</span></p></li>
<li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">A message shall be displayed to the person with details on the ticket number created that shall need validation from AFRINIC</span></p></li>
<li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">Request is received on the IRR RT queue via automation on whois which triggers creation of the ticket and also sends the correct object to be created, should the request be approved.</span></p></li>
<li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">AFRINIC Hostmasters shall carry out the validation and check whether such a request can be accepted. </span></p></li>
<li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span style="font-size:11pt;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre;white-space:pre-wrap;">In case this request is approved, AFRINIC Hostmasters shall authorise creation of the object by submitting the object communicated in (3)</span></p></li>
</ol>
<p><b>In regard to the checks that are conducted internally - we
determine whether the org holding the prefix in the AFRINIC
registry is also the holder of the ASN in another RIR
registry. </b><br>
</p>
</b>
<blockquote type="cite"
cite="mid:20180608105534.GJ29935@vurt.meerval.net">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">In other words. There is a once off "bootstrap" involving a single
email and maybe a days wait, to be able to use an out of region
autnum.
I am not yet convinced that a handful of members saying that is "too
difficult" is sufficient motivation to bring development work on the
DBs current authentication model forward to absolute top priority in
the organisation.
</pre>
</blockquote>
<pre wrap="">
Ok.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">It is no different with RPKI ROAs. With a RPKI ROA the prefix owner
can input any ASN they want in the Origin ASN field.
</pre>
</blockquote>
<pre wrap="">
Preaching to the choir :) - which is why I am comfortable in saying
we'll probably do this. At some point.
</pre>
</blockquote>
<pre wrap="">
Is the creation of RPKI ROAs a fully automated process which can be
initiated by end users through the AfriNIC portal?
Kind regards,
Job
_______________________________________________
DBWG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:DBWG@afrinic.net">DBWG@afrinic.net</a>
<a class="moz-txt-link-freetext" href="https://lists.afrinic.net/mailman/listinfo/dbwg">https://lists.afrinic.net/mailman/listinfo/dbwg</a>
</pre>
</blockquote>
Regards<br>
Madhvi<br>
<pre class="moz-signature" cols="72">--
Madhvi Gokool
Registration Services </pre>
</body>
</html>