
<!DOCTYPE html>

<html>

  <head>

    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

  </head>

  <body>

    <p>Hi,</p>

    <div class="moz-cite-prefix">On 2026/06/01 11:31, Emmanuel Vitus

      wrote:<br>

    </div>

    <blockquote type="cite"

cite="mid:CAGKde+1xLsYEtrg_iN9PRWKT9yBWXnbjDHETczPJMtZ2BEkhpA@mail.gmail.com">

      <meta http-equiv="content-type" content="text/html; charset=UTF-8">

      <div>

        <div style="font-size:inherit">

          <div style="font-size:inherit">

            <p dir="auto"><span

style="font-size:inherit;font-family:-apple-system,sans-serif">I support

                this proposal.</span><br>

            </p>

            <p dir="auto"><span

style="font-size:inherit;font-family:-apple-system,sans-serif">The

                problem of AS-SET name collisions across IRR databases

                is real and well documented. Requiring hierarchical

                names for newly created AS-SETs is a pragmatic approach

                that improves uniqueness, strengthens authorization and

                aligns AFRINIC with practices already adopted by other

                RIRs.</span><br>

            </p>

            <p dir="auto"><span

style="font-size:inherit;font-family:-apple-system,sans-serif">One point

                of clarification would be helpful. Has AFRINIC

                experienced documented cases where such collisions have

                affected operators within the region?</span></p>

          </div>

        </div>

      </div>

    </blockquote>

    <p>I'm aware of two cases, not going to disclose those details

      though.<br>

      <br>

      Kind regards,<br>

      Jaco</p>

  </body>

</html>