ietf-llm
Maintain a local, queryable corpus of an IETF effort's public record — a Working Group, an IRTF Research Group, a mailing list, or a set of drafts. It pulls together charter, drafts, RFCs, meeting agendas, minutes, slides, transcripts, attendance, mailing list archives, and GitHub issues and pull requests for use with LLM-based tools.
What it's for
A working group's history is spread across mailing list archives, Datatracker, GitHub, and meeting materials — too much to hold in your head, and too scattered to search well by hand. With the record gathered into one queryable corpus, an LLM can help you:
- Get up to date with the state of discussions — what's open, what was recently decided, where a debate currently stands.
- Summarise the arguments already made about an issue — every distinct position on a topic, who holds it, and how the chairs ruled.
- Formulate a new proposal — surface the objections raised against similar ideas before, so you can anticipate them.
- Fact-check assertions about what's happened so far — grounded in the actual list traffic and chair statements, not someone's recollection.
Tip: for an IRTF Research Group, pass its shortname (e.g.
cfrg,hrpc,pearg) wherever the docs use<name>— it works the same as a WG.
Modes of operation
There are three supported workflows:
- Use it as an MCP server — register it with Claude, Codex, Cursor, Gemini, Zed,
etc. and ask questions across any corpus you've gathered. Two ways to run it:
- Local MCP — one server subprocess per client, on your own machine. <-- Best starting point
- As a shared HTTP MCP server — one process serving many concurrent clients (hosted).
- Use it from the CLI — run
semantic search over the cache directly with
ietf-llm-search, no LLM client required.
See the workflow documentation linked above for installation and use instructions, or the full documentation listing.
All three read a corpus you first gather with ietf-llm <corpus>. The RFC series is the
exception: the RFC tools cover every published RFC and belong to no corpus, so they work
without gathering anything — see gathering.
Heads up — gathering reaches the network by default. To make a first gather fast,
ietf-llmpulls a prebuilt snapshot of covered corpora from the public seed store atseed-store.mnot.net(andlist_corporalooks its catalog up there), then freshens only the delta — skipping most of the embedding and download cost. The same store holds the RFC full text thatietf-llm --initinstalls. To turn this off:ietf-llm <corpus> --no-seed(it persists across gathers; re-enable with--seed), or setIETF_LLM_SEED_ENABLED=off(orIETF_LLM_SEED_URL=off) in your environment. With seeding off, gathers run fully cold and offline. It is best-effort either way — an unreachable or unlisted corpus just gathers from scratch.
1 maintainer
Release files for ietf-llm 0.18.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| ietf_llm-0.18.6.tar.gz | 1.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ietf_llm-0.18.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.7 MB
Release files / ietf_llm-0.18.6.tar.gz
| Download URL | ietf_llm-0.18.6.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4adde33857e7756e04a550b3468b305b8e0322d665e7279b4bd3d8e658e38ac
|
|
BLAKE2b-256 checksum How to use checksums |
54485261c73c1fd6a3b8125c368764ceed67f8ad275f03774c00a76ece4c0543
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency logRelease files / ietf_llm-0.18.6-py3-none-any.whl
| Download URL | ietf_llm-0.18.6-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f09bfcff217206b0208f1ba977e046ed7bcc878b74463df187d4f2c6a932b0ed
|
|
BLAKE2b-256 checksum How to use checksums |
e1b29b75332d7c805eab80089d74863d7d2f0ce19994fd1c0b5c1dd4be9cb375
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 30, 2026.
Transparency log
