<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Tobias,</div><div><br></div><div>To answer your question, the IRT object would be created in either of two ways:</div><div> </div><div>i) dbupdate or</div><div>ii) myAfriNIC (currently unimplemented)</div><div><br></div><div>much like we already do now for other objects. That is to say that the user won't have to jump through any additional hoops to get this done. To create an IRT object via the dbupdate the user will simply have to send an e-mail matching the template below to <a href="mailto:auto-dbm@afrinic.net">auto-dbm@afrinic.net</a>:</div><div><div><span class="Apple-style-span" style="font-family: Times; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><pre>
<b><u>irt</u></b>: [mandatory] [single] [primary/look-up key]
address: [mandatory] [multiple] [ ]
phone: [optional] [multiple] [ ]
fax-no: [optional] [multiple] [ ]
e-mail: [mandatory] [multiple] [lookup key]
abuse-mailbox: [optional] [multiple] [inverse key]
signature: [optional] [multiple] [ ]
encryption: [optional] [multiple] [ ]
org: [optional] [multiple] [inverse key]
admin-c: [mandatory] [multiple] [inverse key]
tech-c: [mandatory] [multiple] [inverse key]
auth: [mandatory] [multiple] [inverse key]
remarks: [optional] [multiple] [ ]
irt-nfy: [optional] [multiple] [inverse key]
notify: [optional] [multiple] [inverse key]
mnt-by: [mandatory] [multiple] [inverse key]
changed: [mandatory] [multiple] [ ]
source: [mandatory] [single] [ ]</pre></span><div><br></div><div>[Incidentally, this was pulled directly from our current WHOIS server. I snipped the description of each attribute for brevity sake]</div><div><br></div><div>In order to link the IRT object to the inetnum and inetnum6 objects an mnt-irt attribute will have to be added to the latter two and (perhaps) made mandatory. That; however, is a backend change and shouldn't unduly affect the users' experience at all. </div><div><br></div><div>The steps to do this in myAfriNIC would be relatively painless- at least from a users' (rather than an implementers') point-of-view. The user would simply be presented with a form in which to enter the aforementioned information and, once its been validated, the data would be written to the WHOIS database. The process for creating inetnum and inetnum6 objects would then need to be modified to take into account the IRT object which has to have been created beforehand. Conceptually it might look something like this:</div><div><br></div><div><span class="Apple-style-span" style="font-family: Times; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; "><pre><b><u>inetnum</u></b>: [mandatory] [single] [primary/look-up key]
netname: [mandatory] [single] [lookup key]
descr: [mandatory] [multiple] [ ]
country: [mandatory] [multiple] [ ]
org: [optional] [single] [inverse key]
admin-c: [mandatory] [multiple] [inverse key]
tech-c: [mandatory] [multiple] [inverse key]
status: [mandatory] [single] [ ]
remarks: [optional] [multiple] [ ]
notify: [optional] [multiple] [inverse key]
mnt-by: [mandatory] [multiple] [inverse key]
mnt-lower: [optional] [multiple] [inverse key]
mnt-domains: [optional] [multiple] [inverse key]</pre><pre>mnt-irt:<span class="Apple-tab-span" style="white-space:pre"> </span>[mandatory] [multiple] [inverse key] # <---- this could be an additional field in a form in myAfriNIC tying the IRT and inetnum objects
changed: [mandatory] [multiple] [ ]
source: [mandatory] [single] [ ]<br></pre></span><div><br></div></div><div><br></div><div>Hope I answered the question to your satisfaction. Do please let me know if any of this is unclear of perhaps I've inadvertently left something out.</div><div><br></div><div>cheers,</div><div>-Alex.</div><div><br></div></div></div><br></body></html>