[ARIN-consult] Consultation on ARIN Online Change Notifications

[Roman Tatarnikov]

I think both Email and API should be good. API gives ability to integrate all
the notifications with some kind of CRM/ERP/Monitoring System, while emails
will ensure that people who don't have such systems (or need for ARIN
Notifications in them) can still remain in the loop.

There actually has been one item I wanted to advise for email notifications
for a while - it's to use X-Headers. This will allow for better filtration and
prioritization. For example, I have the following rules:

	:0
	* FROM ?? arin-tech-discuss(-bounces)?@arin\.net
	* SUBJECT ?? ^\[arin-tech-discuss\] Completion of ([A-Za-z]+ )?Operation Testing ([Aa]nd|\&) Evaluation( Monthly Maintenance)?
	| rm -f `grep -rlE '^Subject: \[arin-tech-discuss\] (Monthly )?Operational Testing (and|\&) Evaluation( Monthly Maintenance)?' ~/Maildir/.Inbox/new`

The idea is that once OT&E is completed, the email announcing its start would
be deleted. Pretty simple, except that Subject line varies a lot and this
filter doesn't always work.

Plus, the line of code is longer than 80 symbols, so it makes me want to pull
my hair out. I know, my own fault, so lets move on.

If there were X-Headers for various notification types then we wouldn't rely
on verbiage of Subject and could filter everything better in GMail/`procmail`.
For example:

	:0
	* SUBJECT ?? your posts got .+ impressions last week
	* ^X-LinkedIn-Class: EMAIL-DEFAULT$
	* ^X-LinkedIn-Template: email_weekly_analytics_recap$
	/dev/null

I know that tons of people say that they "never check email" and that's it's
"so 90s", but a huge amount of people who are active in network operations and
internet governance use email a lot. I suspect the audience that would
interact with ARIN notifications is full of people who would prefer email.

On Mon, Aug 26, 2024 at 11:23:43AM -0400, Peter Potvin via ARIN-consult wrote:
> I would like to see email notifications implemented as a bare minimum, with
> the option for API-based notifications at a later date.
> 
> Kind regards,
> Peter Potvin
> 
> 
> On Mon, Aug 26, 2024 at 11:19 AM ARIN <info at arin.net> wrote:
> 
> > ARIN is seeking feedback from the community on a potential improvement (
> > https://www.arin.net/participate/community/acsp/consultations/2024/2024-4/),
> > suggested by a community member, that ARIN create a modern mechanism that
> > allows resource holders to be notified of any changes to resources or
> > accounts they manage.
> >
> > The stated benefit of this potential improvement is that it would allow
> > greater control over valuable resources and increase the accuracy of ARIN’s
> > database.
> >
> > We have identified two options to create these notifications:
> >
> > Email - The least “modern” option, but this would be consistent with other
> > ARIN notifications, and mirrors what is available through the other
> > Regional Internet Registries (RIRs). This would take approximately three
> > months to develop once work is scheduled.
> >
> > REST endpoint – ARIN can define a REST endpoint, and customers would have
> > to develop/deploy and then provide us the URL to send notifications to.
> > This would take approximately six months to develop once work is
> > scheduled.
> >
> > These options vary in complexity to develop, and the level of effort
> > required for customer adoption. We are interested in community feedback on
> > the value of a change notification feature and thoughts on the possible
> > delivery methods described or others you may suggest.
> >
> > Please provide comments to arin-consult at arin.net. You can subscribe to
> > this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult
> >
> > This consultation will remain open until 5:00 PM ET on 9 September. ARIN
> > seeks clear direction through community input, so your feedback is
> > important.
> >
> > Thank you for your continued support to improve ARIN's services.
> >
> >
> > Regards,
> >
> > John Curran
> > President and CEO
> > American Registry for Internet Numbers (ARIN)

-- 
Roman V Tatarnikov | https://linkedin.com/in/rtatarnikov
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20240826/867ae675/attachment.sig>