ietf-tools / ietf-tools/draftforge

List Abbreviations: Expansion Not Found Issues (Abbreviations Inside Abbreviations, Expansions in Quotes, Expansion Follows in Parens,etc.)

Open
#74 0 comments 0 reactions 1 assignee View on GitHub

@NGPixel is already working on this.

Since Jun 4, 2026.

Dominant language
JavaScript
Stars
12
Forks
8
PR merge metrics
No merged PRs in 30d

Description

An expansion is not found for these cases:

  1. EAP-TTLS - not expanded

Original:
This requirement also applies to TLS-based EAP methods such as EAP
Tunneled Transport Layer Security (EAP-TTLS)…

Note: Perhaps this issue was related to hyphenation of the abbreviation as well (see Issue #43).

Otherwise, maybe the issue is that abbrev-updates uses the expansion of EAP (an abbreviation inside this abbreviation) “Extensible Authentication Protocol Tunneled Transport Layer Security”? If so, this could be a wider issue as we have lots of abbreviations inside abbreviations. We recommend that authors use the abbreviation instead of the expansion inside another abbreviation. Note that this may actually need to remedied in the abbreviations list itself.

  1. EPI - not expanded

Original:
“EAP Provisioning Identifiers” (EPI).

Notes:
Another use of an abbreviation inside an abbreviation.
Currently, EPI is expanded at abbrev-updates only as “Educational Policy Institute” , so likely a warning since it is a "new" abbreviation (related to Issue #53).
Noting here to ensure we can handle expansions inside of quotes.

  1. EST - not expanded

Original:
It is RECOMMENDED that the provisioning methods provide for a method
which can be used without affecting network access. A specification
could define provisioning endpoints such as Enrollment over Secure
Transport (EST) [RFC7030], or Internet X.509 Public Key
Infrastructure Certificate Management Protocol (CMP) [RFC9810].

Perhaps the issue is the line break? This looks otherwise the same as abbrev-updates.

  1. TEAP (Tunnel Extensible Authentication Protocol)

For instances where authors use the format above (abbreviation then expansion in parens), we get a warning that the abbreviation is "used before the expansion". Sometimes authors use this format throughout and we would not change it. Is it possible for these types of instances to be considered a match to the content in the abbrev list? Otherwise, it is impossible to know from the warning if this format is being used or if TEAP is being used before it is expanded generally.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.