<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
My vote is web, and XML RPC.<br>
<br>
On 04/02/2012 04:12 PM, John Brown wrote:
<blockquote
cite="mid:DFB5A45D81B51545ABBBEDD2F167C294355A618A@deathstar3.citylinkfiber.intra"
type="cite">
<pre wrap="">No XML.
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss-bounces@arin.net">arin-discuss-bounces@arin.net</a> [<a class="moz-txt-link-freetext" href="mailto:arin-discuss">mailto:arin-discuss</a>-
<a class="moz-txt-link-abbreviated" href="mailto:bounces@arin.net">bounces@arin.net</a>] On Behalf Of Alec Ginsberg
Sent: Monday, April 02, 2012 1:52 PM
To: Robert Marder
Cc: <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss@arin.net">arin-discuss@arin.net</a>
Subject: Re: [arin-discuss] Bringing back IP resource Request Templates
Once again... All of these reasons are simply illustrating problems that could
be fixed. For example a proper HA infrastructure that is architected properly.
So for all the email template fans. Would you be ok if it was an XML
template?
Sent from my iPhone
On Apr 2, 2012, at 2:49 PM, "Robert Marder" <a class="moz-txt-link-rfc2396E" href="mailto:ram@robertmarder.com"><ram@robertmarder.com></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">This is another very good reason.
Just take a look at ARIN's recent maintenance: email templates were
queued, the web interface and the REST API were both completely down.
It's simply much easier and more reliable to automate email template
submissions than deal with the web interface or web api.
On 02.04.2012 14:41, John Brown wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Templates don't require a web browser.
I've watched hardware vendors move away from CLI to Web based
</pre>
</blockquote>
</blockquote>
<pre wrap="">config.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">It sucks for many reasons. Web looks nicer but doesn't always work
when you need it to.
Email templates allow for a Fire and forget.
Web template (via api, curl, etc) requires that the server be
reachable and able to process in realtime.
eMail template can be generated, sent to the SMTP server and then
handled.
If ARIN's system isn't able to process, that's ok, the email is
QUEUED, either a secondary MX in the "inbox".
Meanwhile the human can go home and know that the job is submitted,
save lost email in transit.
If the request requires a change, you can easily edit the email
template and re-submit. Not so with dynamic / live web interface.
ARIN should provide multiple I/O paths.
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss-bounces@arin.net">arin-discuss-bounces@arin.net</a> [<a class="moz-txt-link-freetext" href="mailto:arin-discuss">mailto:arin-discuss</a>-
<a class="moz-txt-link-abbreviated" href="mailto:bounces@arin.net">bounces@arin.net</a>] On Behalf Of Chris Cappuccio
Sent: Monday, April 02, 2012 1:30 PM
To: Robert Marder
Cc: <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss@arin.net">arin-discuss@arin.net</a>
Subject: Re: [arin-discuss] Bringing back IP resource Request
Templates
On 04/02/12 12:24, Robert Marder wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I agree as well.
Templates are easier to fill out and it's nice to have a
</pre>
</blockquote>
<pre wrap="">convenient
</pre>
<blockquote type="cite">
<pre wrap="">log of all my requests.
</pre>
</blockquote>
<pre wrap="">Most of the cases made here for templates seem like lame excuses.
The web
interface could do all of these things and do them better than your
e-mail client. What do you think the money that you pay to ARIN goes
for?
The real reason would be that folks who do lots of small/frequent
updates have to do them by hand instead of doing them on the web.
But the web interface is supposed to accommodate that as well. We're
talking about dumping text editors and SMTP for HTTP forms which can
be handled automatically as well. But the people who need this
functionality have probably already figured out how to get it with
ARIN.
Chris
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to the
ARIN
Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@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-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</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>
</blockquote>
<pre wrap="">
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@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-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</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>
<pre wrap="">_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@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-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</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>
<pre wrap="">_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@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-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</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>
<div class="moz-signature">-- <br>
<style type="text/css">
<!--
TABLE {
border: solid 1px;
border-color: #000000;
width: 100%;
}
TD
{
font-family: sans-serif;
font-size:12pt;
font-style:normal;
}
P.name { font-weight: bold; font-size: 18px; margin-top: 1px; margin-bottom: 3px; }
P.title { font-size: 14px; margin-top: 1px; margin-bottom: 3px; color: blue; }
P.ph { font-size: 12px; margin-top: 0px; margin-bottom: 2px; }
-->
</style>
<table>
<tbody>
<tr>
<td valign="center">
<p class="name">Jawaid Bazyar</p>
<p class="title">President</p>
<p class="ph">ph 303.815.1814</p>
<p class="ph">fax 303.815.1001</p>
<a href="email:Jawaid.Bazyar@foreThought.net">Jawaid.Bazyar@foreThought.net</a><br>
</td>
<td valign="center">
<a href="http://www.foreThought.net"><img
src="cid:part2.02080905.09080309@foreThought.net"
align="right" border="0"></a>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>