Send ARIN-consult mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.arin.net/mailman/listinfo/arin-consult
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-consult digest..."


Today's Topics:

   1. Re: Consultation on Enforcing Hierarchical Naming for AS-SETs
      (Charles Monson)


----------------------------------------------------------------------

Message: 1
Date: Thu, 15 May 2025 09:45:26 -0500
From: Charles Monson <[email protected]>
To: [email protected]
Subject: Re: [ARIN-consult] Consultation on Enforcing Hierarchical
        Naming for AS-SETs
Message-ID:
        <CAAbPay+9eSxmx=uxovtbbxbx7i3ujadvdqzcfsub1vauzko...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

> Questions for the Community:
>
> - Do you have automation that would be impacted by enforcement of this 
> proposed change?

Not currently. However, any impact here would be positive from my
perspective. This is a great idea.

> - Are you negatively impacted by the current AS-SET naming conventions?

Not currently but AS-SET name conflicts have been identified as a
potential issue as we are relying more on automation. Anything that
ensures uniqueness will be a net positive.

> - Should this work be prioritized ahead of other work on ARIN?s development 
> roadmap?

I will just be happy to see it on the roadmap.

I have already been telling customers to create AS-SETs using the
hierarchical naming convention. ARIN enforcing that will make it much
easier.


Charles


------------------------------

Subject: Digest Footer

_______________________________________________
ARIN-consult mailing list
[email protected]
https://lists.arin.net/mailman/listinfo/arin-consult


------------------------------

End of ARIN-consult Digest, Vol 115, Issue 2
********************************************

Reply via email to