New WG acronyms need more validation

[ietf-svn-bot]

owner:olau@iola.dk resolution_fixed type_defect | by rjsparks@nostrum.com

---

Currently, I can create a charter for a working group with an acronym consisting of a single hyphen.

That leads to a charter filename of
charter-ietf---00-00

Similarly, I can specify an acronym of 1, 1-, or -1,

Having a group with a purely numeric (even if more than one digit) acronym might be problematic. Do we want to allow that? Is there any real reason to disallow it?

Finally, we currently allow creating a working group with a single letter acronym. Is there any reason to disallow that?

---

Issue migrated from trac:1080 at 2022-03-04 02:53:32 +0000

[ietf-svn-bot]

@olau@iola.dk commented

---

Right that's a bug. Currently, we allow "[-a-z0-9]+". Do we even need to support hyphens in new groups, or is that actually only needed for existing groups? If we need them, I'll add a rule to prevent a hyphen as first or last letter.

One letter acronyms and numeric acronyms: I guess those could be confusing, and they're probably harder to google.

Technically there isn't a problem, though, at least within the Datatracker AFAIK. Not sure about the various support tools, but they're most likely using [a-z0-9]+. So it's a policy decision.

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

We should not permit hyphens in new groups.

Let's also require an alpha first character, and at least 2 characters. I'd like to require more, but apart from the requirement of no hyphens in new groups, the rest is already a bit arbitrary, so maybe not push that to requiring 3 characters.

[ietf-svn-bot]

@olau@iola.dk changed status from new to closed

[ietf-svn-bot]

@olau@iola.dk changed resolution from `` to fixed

[ietf-svn-bot]

@olau@iola.dk commented

---

Fixed in 214b1e0:

Be more strict when chartering a new group, only accept [a-z][a-z0-9]+
as acronym (specifically not hyphens), closes #1080.