[rpd] Require newly created AS-SETs to have hierarchical names AFPUB-2026-ASN-001-DRAFT01.

[James Bensley]

Hi Frank,

Thank you for taking the time to read the draft and suggest edits.

Regarding this point from you:

"4. References. In other regions, all IPv4 addresses have been exhausted and it seems that the equivalent to the soft-landing is not any more an issue, because most of the existing members only can access IPv4 addresses via transfers."
this seems to be irrelevant for this proposal. Also the next section is
also called "5. References". is it there by mistake?

This wasn't me; I guess a copy and paste error from the AFRINIC team; this is text from another draft proposal. I will ask them to correct it.

I believe I have incorporated the feedback from all over points from you except this one;

4.  The necessity of "3. Other set types such as route sets are excluded." was questioned. It's not absolutely necessary. But I believe it can
help. Maybe it can start with "For the avoidance of doubt: "  ??

I'm not sure what benefit the text "For the avoidance of doubt" is adding here. Can you explain what is unclear about the existing text which this helps with (that would help me to understand what's wrong with the existing wording)?
"The proposal is not currently extended to any other set types such as route sets, to keep the scope of this change to a more manageable level."

I've put the latest version on GitHub (this avoids the AFRINIC staff potentially having to process many version changes with potentially very minor changes), feel free to comment there or respond here via email and I'll update the gist: https://gist.github.com/jwbensley/d76bfd3e87a5cb85fb28585381623bc4

Thank you for your input and support.

With kind regards,
James Bensley (he/him)
________________________________
From: Frank Habicht <geier at geier.ne.tz>
Sent: 22 May 2026 09:05
To: rpd at afrinic.net <rpd at afrinic.net>
Subject: Re: [rpd] Require newly created AS-SETs to have hierarchical names AFPUB-2026-ASN-001-DRAFT01.

⚠️ Caution: This email originated from outside of your organization. Do not click on links or open attachments unless you recognize the sender and know the content is safe.

so I'm a bit confused - sorry.

On 5/22/2026 9:20 AM, Frank Habicht wrote:
> 3. under 'Proposal'
> "The first element of the name must be an ASN"
> I hope we all understand that 'element' will be the things separated by
> colons (":").
> I would humbly like to suggest to add "preceded by AS-" at the end, so
> this becomes
> "The first element of the name must be an ASN preceded by 'AS-'"
> I think this would just be an editorial change...


RFC2622 section 5
https://www.rfc-editor.org/info/rfc2622/#section-5
gives valid examples such as "AS1:AS-CUSTOMERS, AS1:RS-EXPORT:AS2"

but section 5.1 states that AS-SETs have to start with "as-".

So maybe the word "ASN" in the text refers to a string such as "AS37181"
and not just the number by itself.

And even if not, likely what would need to be added in front would be
"AS" and not "AS-" ...

Not sure about item 3. of my comments - quoted above.

Sorry for confusion.

Frank


_______________________________________________
RPD mailing list
RPD at afrinic.net
https://lists.afrinic.net/mailman/listinfo/rpd
[CompanySignature]
Inter..link GmbH | Boxhagener Straße 80, 10245 Berlin, Germany | Managing Directors: Marc Korthaus, Theo Voss | Commercial Register: Amtsgericht Charlottenburg, HRB 138876 | VAT ID: DE281288887 | Email: hello at inter.link<mailto:hello at inter.link> | Web: inter.link<https://inter.link>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260601/65c71ac1/attachment.html>