[arin-discuss] Template-based email as a third registry access method

Gary T. Giesen ggiesen at egate.net
Wed Apr 4 11:36:42 EDT 2012


Just to be clear where costs lie... My impression was that the bulk of the ongoing costs involved with accepting email templates involves things like maintaining email infrustracture, filtering spam, dealing with missing/lost requests (all of which requires human intervention). Some development costs aside, would my proposal involve a great deal of additional ongoing costs for the parser to maintain parity between the "step-by-step" form and the "bulk" submission form? Or perhaps just use the bulk parser to pre-populate the fields in the step-by-step form so you can still use the same validation code?


-----Original Message-----
From: John Curran [mailto:jcurran at arin.net] 
Sent: April 4, 2012 11:28 AM
To: Gary T. Giesen
Cc: Owen DeLong; David Farmer; arin-discuss List
Subject: Re: [arin-discuss] Template-based email as a third registry access method

Gary - 

  To be clear, we do already support email templates, including the
  secure transmission of them via PGP (read: <https://www.arin.net/CA/>)

  If we provided the ability to cut/paste them into ARIN Online, that 
  would also be secure, but would not address the issue that Owen raised
  which is that he would like some of the email template types that are
  no longer present (e.g. requesting new resources) to be developed and
  make available.  

  Doing this development and maintenance would require similar effort to
  simply accepting them via email.  Providing an alternative method to 
  submit may indeed be worth considering, but it is an orthogonal issue
  to Owen's request.


John Curran
President and CEO

On Apr 4, 2012, at 11:15 AM, Gary T. Giesen wrote:

> To address some of the security and email parsing concerns, what about the possibility of having a giant text box in ARIN Online where multiple email templates can be pasted in at once (and of course saved for later editing before submission).  This would ensure users are properly authenticated, allow bulk submission of requests, allow easy editing/copy/paste, and no format changes for people who are already used to the email templates (other than the transport method).
> I would imagine that would go a long way towards addressing some of Owen's concerns while not having to deal most of the issues of receiving and parsing email. I would imagine the maintenance headache would be greatly reduced as well.
> -----Original Message-----
> From: arin-discuss-bounces at arin.net [mailto:arin-discuss-bounces at arin.net] On Behalf Of Owen DeLong
> Sent: April 4, 2012 1:17 AM
> To: David Farmer
> Cc: arin-discuss List; John Curran
> Subject: Re: [arin-discuss] Template-based email as a third registry access method
> On Apr 3, 2012, at 5:50 PM, David Farmer wrote:
>> On 4/3/12 19:29 CDT, Kevin Blumberg wrote:
>>> I would also suggest that the ability to save a draft of a submission be supported.
>> As I was reading this thread I was thinking much the same thing.  I was thinking about why people might want Email Templates back vs. a Web Form.  Other than not wanting to change, I thought about how the work flow has changed.  With a email template you had a form you could work on offline and collect all the information you needed and fill it in as you go. Then submit the form, via email when you had it complete.
> You also had:
> 	1.	A single consolidated document you could review as a cohesive unit.
> 	2.	Easy navigation back and forth checking the document for internal consistency
> 	3.	A set of pre-defined well documented fields.
> 	4.	The ability to easily attach files ad-hoc and reference them within justification fields
> 		(ARIN On-Line pretends to have this, but, the file checking rarely accepts my files
> 		in spite of them conforming to the rules specified. These problems have proven
> 		intermittent and nearly impossible to track down so far.)
> 	5.	Full-text email updates and the ability to easily transfer the template in progress
> 		back and forth between myself and my clients for review, update, etc. prior to
> 		submission to ARIN.
> The work flow has changed substantially and is costing my clients on average $500-$750 more per request just in my time alone.
>> With the Web Form, I believe as implemented, you essentially need all the info for a request all at once, then you do the data entry and submit it.  If you could save partially completed web forms and create your own partially complete templates, maybe we can keep the kind of workflow we had with email templates but keep moving forward with the other improvements ARIN Online has brought.
> It's much worse than that. You have to navigate several disconnected pages in sequence with no useful ability to navigate back and forth in the process. It's not entirely clear from the first page what will be requested on the subsequent pages, etc.
>> I have to say I like ARIN Online and the many improvements, but the web form based workflow can be frustrating at times.  So is workflow the real issue here?
> Most definitely, but, in so many ways, it's hard to imagine making the web-based workflow as useful as the email-based one was.
> Owen
> _______________________________________________
> ARIN-Discuss
> You are receiving this message because you are subscribed to the ARIN Discussion Mailing List (ARIN-discuss at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-discuss
> Please contact info at arin.net if you experience any issues.

More information about the ARIN-discuss mailing list