[ARIN-consult] Oppose retiring email templates

Owen DeLong owen at delong.com
Fri Sep 25 17:18:41 EDT 2009

On Sep 25, 2009, at 2:12 PM, Mark Kosters wrote:

> Hi
> If we can tussle this apart a bit. There are two classes of templates.
> The first class of templates are those that do not appear to be  
> automated.
> Those are orgs, pocs, and requests for number resources.

> The second class of templates are swips - reassign detailed,  
> reassign simple,
> reallocate, and netmod.  These are heavily automated.
> For the first class, we like to hear from you if we can deprecate  
> the use
> of templates and use the web interface.
There are reasons beyond automation to preserve the email templates.
Having said that, I do have some tools that do somewhat automate the
production of number resource applications and POC updates which
I occasionally do on behalf of my clients.

Therefore, I oppose deprecation even of these templates.

> For the second class, we have had start of a discussion of better ways
> to handle automated and bulk submissions at the San Antonio meeting.  
> The
> discussion leaned towards using a RESTful web interface.  Of course,  
> if we
> were to do this, there would be ample time to agree to this approach  
> and to
> cut over. We are not there yet.
I'm all for adding the ability to use the RESTful web interface or  
some other
API for automation/bulk submissions, but, I do not think that it  
should be
done to the exclusion of the email template submission.


More information about the ARIN-consult mailing list