-
Notifications
You must be signed in to change notification settings - Fork 0
Current Status and Errata
Last wiki status review: 2026-07-19
| Item | Current value |
|---|---|
| Public release tag | v2.2.6-public-eval |
| Python package version | 2.2.6 |
| Evaluation suite | ORPRG-Eval v3.2 |
| Canonicalization profile | CP-JSON-2 |
| Authorization-reference profile | orprg.authorization-ref.public-eval.v2 |
| Carrier profile | PermitReceipt.authorization-ref.carrier.public-eval.v1 |
| Internet-Draft | draft-lee-orprg-permit-receipts-00 |
| Separate frozen input |
ietf126-payment-composition-v0.1 — HOLD; not a result |
| Draft status | Active individual Internet-Draft; no IETF consensus |
| Draft expiration | 2026-12-06 |
See Versioning and Compatibility for why these identifiers are separate.
The release is a public evaluation artifact, not production software.
- Release page
- Status: FROZEN PRE-EXECUTION INPUT — NOT A RESULT
- Public posture: HOLD
This separate input does not modify, replace, or supersede v2.2.6-public-eval. It supplies only the ORPRG PermitReceipt inputs for a scoped synthetic IETF 126 composition exercise. It does not contain an external payment or a completed composition result, and no successful composition or interoperability claim should be inferred.
Affected: immutable documentation packaged with v2.2.6-public-eval
Public tracker: issue #1
A fresh Windows 11 / CPython 3.12 virtual environment successfully verified the release sidecar and artifact, but the documented portable command:
python -m pip install --no-build-isolation -e . --no-depsfailed because setuptools==83.0.0 and wheel==0.47.0 were declared as build requirements but were not installed in the fresh environment. Disabling build isolation prevents pip from provisioning them.
python -m pip install -r requirements.txt
python -m pip install -e . --no-depsUse --no-build-isolation only after installing the pinned build requirements or when using the documented hash-locked CPython 3.13/Linux environment that includes them.
The reviewer reported successful packet results after installing the pinned build tools. This is a reproducibility/documentation erratum, not a field-model, production-readiness, certification, or IETF-endorsement claim.
Use these live pages rather than copying transient status into the wiki:
A release should be treated as current only when its tag, release tuple, version taxonomy, release notes, and green QA run agree.
Update this page whenever any of the following changes:
- canonical release tag or asset tuple;
- test or coverage evidence;
- supported reviewer environments;
- known reproducibility or security errata;
- Internet-Draft revision or status;
- IPR link or licensing boundary; or
- public feedback or private vulnerability reporting route.