On 10/27/2021 12:26 AM, William Herrin wrote:
On Tue, Oct 26, 2021 at 5:33 PM Andrew Dul <[email protected]> wrote:
I'd might be ok with a URL, but not just "any URL" if the community is
really interested in improving reporting, we likely need a structured
data format and API so that input can be better used by those receiving
the reports.
Hi Andrew,
I'd prefer not to see ARIN leading that effort but I'd point out that
this policy change creates a framework which could lead to such
standardization. If the URL is HTTP, automation could request the URL
with a particular user agent string which, if the server supports it,
would return machine-readable instructions for generating and
transmitting a report instead of the normal human-readable ones.
While ARIN it probably not the best place to formalize this standard
'structured data format' it certainly can be involved in creating and
advocating for its development and standardization. In the same way that
RDAP was developed by RIR staff and then standardized in the IETF.
In this case, if we build it (a URL option)...they will come...in many
many different and likely incompatible ways which is worse that today's
email standard.
I'm disinclined to support this draft to allow a URL as a reporting
mechanism in the absence of the structured data format.
Thanks,
Andrew
_______________________________________________
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
https://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.