ARIN-consult Message

[ARIN-consult] Oppose retiring email templates

If what I understand is true, only the POC contact and the like are slated to be retired, correct?  We personally have no problems with this, although there are likely members out there that make frequent enough updates to those items that would disagree with this sentiment.

If we are talking about SWIP templates, I wholeheartedly disagree with this proposal.  We, too, have systems that automatically create these templates based on assignment information garnered from our internal provisioning system.  It takes someone two minutes to peruse the accuracy of the 15 or so templates a week and email them to ARIN.  

The introduction of a web form as the only source to update such information will be a detriment to ARIN and a large population of its users, as it's likely that frustration, then apathy, would take over because updating items in bulk through a web form, quite frankly, sucks.  It's just plain time-consuming and will end up making everyone's life more difficult because the SWIPs would simply not be filled out.  I hate to say it, but it's true.  "Web 2.0" is mostly garbage and we don't need a "wizard" or "point and click" interface to do everything. 

I would be in favor of an API, but ARIN must realize that not every member out there has software folk in their employ regularly that are able to just whip up a new interface using the latest alphabet soup du jour.  And while it's probably not considered an API, the idea of being able to upload, say, a CSV file with all the appropriate information could also be something to consider.

SWIP = Serious Business

-evt

> -----Original Message-----
> From: arin-consult-bounces at arin.net [mailto:arin-consult-bounces at arin.net]
> On Behalf Of prescott at wcoil.com
> Sent: Monday, September 28, 2009 10:13 AM
> To: consult at arin.net
> Subject: Re: [ARIN-consult] Oppose retiring email templates
> 
> I also do not want to see email go away.
> It is an easy way of handling template submission.
> 
> The compromise might be to have a restful web interface and have the arin
> email system inject templates into the web interface.
> This would allow the web api, but would also keep the email going for
> those of us who use it.
> 
> -- Kelly Prescott
> 
> On Fri, 25 Sep 2009, Owen DeLong wrote:
> 
> > Date: Fri, 25 Sep 2009 14:18:41 -0700
> > From: Owen DeLong <owen at delong.com>
> > To: Mark Kosters <markk at arin.net>
> > Cc: "consult at arin.net" <consult at arin.net>
> > Subject: Re: [ARIN-consult] Oppose retiring email templates
> >
> >
> > 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.
> >
> > Owen
> >
> > _______________________________________________
> > ARIN-Consult
> > You are receiving this message because you are subscribed to the ARIN
> Consult
> > Mailing
> > List (ARIN-consult at arin.net).
> > Unsubscribe or manage your mailing list subscription at:
> > http://lists.arin.net/mailman/listinfo/arin-consult Please contact the
> ARIN
> > Member Services
> > Help Desk at info at arin.net if you experience any issues.
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN
> Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-consult Please contact the
> ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.