rttp 1.3.1__tar.gz → 1.3.2__tar.gz

{rttp-1.3.1 → rttp-1.3.2}/CHANGELOG.md

@@ -6,6 +6,32 @@ All notable changes to the `rttp` package. Format follows
 
 ---
 
+## [1.3.2] -- 2026-11-09
+
+**Vector re-anchoring release -- no code change.** The published conformance
+vectors are re-anchored to `draft-li-rttp-iqa-addressing-02` (TXT sha256
+`02491c5a...`, 40 pp., 2026-11-01): every `applies_to`, `spec_ref`, `reason`
+and `expected` field now cites the I-D sections directly (`§§4, 7.1` set-level;
+per-row `§4.1` / `§4.2` / `§4.5.2` / `§7.1.1` / `§4.3`; the seal envelope stays
+under `AICENT-002 (RTTP-SEAL-ENVELOPE-v1.2.6 sec. 7)`, beyond -02). Vector
+bytes are unchanged -- only anchor metadata and citation text moved; every
+replay is byte-identical.
+
+* **New vector-set digest:** `sha256 8640e390...` (13,874 bytes, was
+  `4b743e63...` at 13,460 bytes). Shipped byte-identically in all three
+  packages; manifest regenerated.
+* **Documented annotations:** the `-lead` rejection vector carries a CONFLICT
+  note against the -02 ABNF (the I-D ABNF literally allows a leading hyphen;
+  the implementation is stricter and -03 will tighten it); the JS metadata
+  test now asserts the re-anchored `applies_to`.
+* **Docs:** specification status updated to revision -02 with the TXT digest;
+  conformance records now point at https://iqa.org/conformance/ and
+  https://iqa.org/challenge/ .
+* Self-test counts unchanged: **80 passed with 3 skipped** (83 with
+  `[ed25519]`); node --test all pass; the independent JS replay stays at 35.
+
+---
+
 ## [1.3.1] -- 2026-10-05
 
 **Synchronization release -- no code change.** The codec, the pulse frame, the

{rttp-1.3.1 → rttp-1.3.2}/PKG-INFO

@@ -1,11 +1,11 @@
 Metadata-Version: 2.4
 Name: rttp
-Version: 1.3.1
+Version: 1.3.2
 Summary: RTTP reference implementation: PulseHeader128 framing, rttp:// addressing, and self-certifying Ed25519 seals (AICENT-002 sec. 4.1 / sec. 10 / sec. 11).
 Author: RTTP.COM Organization
 License-Expression: Apache-2.0
 Project-URL: Homepage, https://rttp.com/
-Project-URL: Specification, https://rttp.com/AICENT-002/
+Project-URL: Specification, https://rttp.com/URI/
 Keywords: rttp,protocol,ai-agents,intent-addressing,uri-scheme,ed25519,conformance
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
@@ -31,7 +31,7 @@ Dynamic: license-file
 128-byte `PulseHeader128` frame, `rttp://` intent addressing, and self-certifying
 Ed25519 seals.**
 
-[AICENT-002 sec. 4.1](https://rttp.com/AICENT-002/) - [sec. 10](https://rttp.com/AICENT-002/) - sec. 11 - v1.2.6
+[AICENT-002 sec. 4.1](https://rttp.com/URI/) - [sec. 10](https://rttp.com/URI/) - sec. 11 - v1.2.6
 
 ---
 
@@ -40,14 +40,14 @@ Ed25519 seals.**
 ```console
 $ pip install rttp
 $ python -m rttp.selftest
-rttp 1.3.1 self-test
+rttp 1.3.2 self-test
 python 3.14.2 on win32
 ...
 [PASS] all 80 checks passed (3 skipped)     # default install: the Ed25519 checks are skipped
 
 $ pip install rttp[ed25519]
 $ python -m rttp.selftest
-rttp 1.3.1 self-test
+rttp 1.3.2 self-test
 python 3.14.2 on win32
 ...
 [PASS] all 83 checks passed                 # with the optional Ed25519 backend
@@ -216,7 +216,7 @@ needing to trust the authors.
 
 | Ecosystem | Name | Status |
 |:---|:---|:---|
-| crates.io | `rttp` | **this project's Rust implementation** -- `1.3.1`, the first formal (non-pre-release) publication; the earlier `1.2.8-alpha` remains published and is not yanked |
+| crates.io | `rttp` | **this project's Rust implementation** -- `1.3.2`; the first formal (non-pre-release) publication was `1.3.1`; the earlier `1.2.8-alpha` remains published and is not yanked |
 | PyPI | `rttp` | **this package** -- `pip install rttp` |
 | npm | **`@aicent/rttp`** | the unscoped `rttp` name on npm is held by an unrelated, unmaintained 2017 REST helper, and the `rttp` scope cannot be created at all -- a personal account already holds that name -- so the JavaScript side is published under this project's own organization. The package name itself is still just `rttp` |
 
@@ -227,18 +227,22 @@ needing to trust the authors.
 * **`rttp` URI scheme** -- **registered**: IANA "URI Schemes" registry,
   Provisional, **CRI 27** (2026-09-22), submitted under RFC 7595.
 * **Internet-Draft (IETF)** -- under IETF review as the combined Individual
-  Submission Internet-Draft `draft-li-rttp-iqa-addressing` (revision -00,
-  16 pp., 2026-09-24, informational -- both schemes, one document):
+  Submission Internet-Draft `draft-li-rttp-iqa-addressing` (revision -02,
+  40 pp., 2026-11-01, informational -- both schemes, one document):
   https://datatracker.ietf.org/doc/draft-li-rttp-iqa-addressing/ .
+  TXT sha256 `02491c5a59d1e7471be04e8e0d4933dfc22ce19f9b054ead0aa449d6b4485044`.
   An Internet-Draft is a working document -- it is not an IETF standard and
   carries no IETF endorsement.
+* **Conformance records** -- sealed runs and vector families:
+  https://iqa.org/conformance/ ; the published vector sets are pinned at
+  https://iqa.org/challenge/ .
 * **Frame layout** -- AICENT-002 sec. 4.1, extended by `SPEC/RTTP-FRAME-EXT-v1.2.6.md`.
 * **Seal envelope** -- `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md`, a **draft**: the format
   is implemented and vector-tested, but it is not yet a numbered AICENT-002 section.
 * **Managed profile** -- implementation only; it predates the sovereign profile and
   has no standalone specification.
 * **AE-128** -- the answer-side counterpart of the pulse frame lives in the
-  sibling packages `iqa-org` 1.3.1 / `@aicent/iqa` 1.3.1 (`iqa.envelope`);
+  sibling packages `iqa-org` 1.3.2 / `@aicent/iqa` 1.3.2 (`iqa.envelope`);
   the two carriers do not parse each other and MUST NOT be conflated.
 * **Managed profile** -- implementation only; it predates the sovereign profile and
   has no standalone specification.

{rttp-1.3.1 → rttp-1.3.2}/README.md

@@ -4,7 +4,7 @@
 128-byte `PulseHeader128` frame, `rttp://` intent addressing, and self-certifying
 Ed25519 seals.**
 
-[AICENT-002 sec. 4.1](https://rttp.com/AICENT-002/) - [sec. 10](https://rttp.com/AICENT-002/) - sec. 11 - v1.2.6
+[AICENT-002 sec. 4.1](https://rttp.com/URI/) - [sec. 10](https://rttp.com/URI/) - sec. 11 - v1.2.6
 
 ---
 
@@ -13,14 +13,14 @@ Ed25519 seals.**
 ```console
 $ pip install rttp
 $ python -m rttp.selftest
-rttp 1.3.1 self-test
+rttp 1.3.2 self-test
 python 3.14.2 on win32
 ...
 [PASS] all 80 checks passed (3 skipped)     # default install: the Ed25519 checks are skipped
 
 $ pip install rttp[ed25519]
 $ python -m rttp.selftest
-rttp 1.3.1 self-test
+rttp 1.3.2 self-test
 python 3.14.2 on win32
 ...
 [PASS] all 83 checks passed                 # with the optional Ed25519 backend
@@ -189,7 +189,7 @@ needing to trust the authors.
 
 | Ecosystem | Name | Status |
 |:---|:---|:---|
-| crates.io | `rttp` | **this project's Rust implementation** -- `1.3.1`, the first formal (non-pre-release) publication; the earlier `1.2.8-alpha` remains published and is not yanked |
+| crates.io | `rttp` | **this project's Rust implementation** -- `1.3.2`; the first formal (non-pre-release) publication was `1.3.1`; the earlier `1.2.8-alpha` remains published and is not yanked |
 | PyPI | `rttp` | **this package** -- `pip install rttp` |
 | npm | **`@aicent/rttp`** | the unscoped `rttp` name on npm is held by an unrelated, unmaintained 2017 REST helper, and the `rttp` scope cannot be created at all -- a personal account already holds that name -- so the JavaScript side is published under this project's own organization. The package name itself is still just `rttp` |
 
@@ -200,18 +200,22 @@ needing to trust the authors.
 * **`rttp` URI scheme** -- **registered**: IANA "URI Schemes" registry,
   Provisional, **CRI 27** (2026-09-22), submitted under RFC 7595.
 * **Internet-Draft (IETF)** -- under IETF review as the combined Individual
-  Submission Internet-Draft `draft-li-rttp-iqa-addressing` (revision -00,
-  16 pp., 2026-09-24, informational -- both schemes, one document):
+  Submission Internet-Draft `draft-li-rttp-iqa-addressing` (revision -02,
+  40 pp., 2026-11-01, informational -- both schemes, one document):
   https://datatracker.ietf.org/doc/draft-li-rttp-iqa-addressing/ .
+  TXT sha256 `02491c5a59d1e7471be04e8e0d4933dfc22ce19f9b054ead0aa449d6b4485044`.
   An Internet-Draft is a working document -- it is not an IETF standard and
   carries no IETF endorsement.
+* **Conformance records** -- sealed runs and vector families:
+  https://iqa.org/conformance/ ; the published vector sets are pinned at
+  https://iqa.org/challenge/ .
 * **Frame layout** -- AICENT-002 sec. 4.1, extended by `SPEC/RTTP-FRAME-EXT-v1.2.6.md`.
 * **Seal envelope** -- `SPEC/RTTP-SEAL-ENVELOPE-v1.2.6.md`, a **draft**: the format
   is implemented and vector-tested, but it is not yet a numbered AICENT-002 section.
 * **Managed profile** -- implementation only; it predates the sovereign profile and
   has no standalone specification.
 * **AE-128** -- the answer-side counterpart of the pulse frame lives in the
-  sibling packages `iqa-org` 1.3.1 / `@aicent/iqa` 1.3.1 (`iqa.envelope`);
+  sibling packages `iqa-org` 1.3.2 / `@aicent/iqa` 1.3.2 (`iqa.envelope`);
   the two carriers do not parse each other and MUST NOT be conflated.
 * **Managed profile** -- implementation only; it predates the sovereign profile and
   has no standalone specification.

{rttp-1.3.1 → rttp-1.3.2}/pyproject.toml

@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "rttp"
-version = "1.3.1"
+version = "1.3.2"
 description = "RTTP reference implementation: PulseHeader128 framing, rttp:// addressing, and self-certifying Ed25519 seals (AICENT-002 sec. 4.1 / sec. 10 / sec. 11)."
 readme = "README.md"
 requires-python = ">=3.9"
@@ -40,11 +40,12 @@ ed25519 = ["cryptography>=41"]
 dev = ["build>=1.0", "twine>=4.0"]
 
 [project.urls]
-# Every URL here was checked live on 2026-09-17. Note that `/spec/...` returns
-# 404 on this host -- it is not a valid path; the specification is served at
-# /AICENT-002/. A dead Project-URL in published metadata is a permanent dead link.
+# Every URL here was checked live on 2026-09-17 (Specification re-checked on
+# 2026-11-09). Note that `/spec/...` returns 404 on this host -- it is not a
+# valid path; the specification is served at /URI/. A dead Project-URL in
+# published metadata is a permanent dead link.
 Homepage = "https://rttp.com/"
-Specification = "https://rttp.com/AICENT-002/"
+Specification = "https://rttp.com/URI/"
 
 [project.scripts]
 rttp-selftest = "rttp.selftest:main"

{rttp-1.3.1 → rttp-1.3.2}/src/rttp/__init__.py

@@ -40,7 +40,7 @@ from . import aid, pulse_header, rttp_uri, seal
 from .pulse_header import PulseHeaderError
 from .rttp_uri import RttpUriError
 
-__version__ = "1.3.1"
+__version__ = "1.3.2"
 
 #: The protocol revision this package implements. Mirrors `pulse_header.SPEC_REV`.
 SPEC_REV = pulse_header.SPEC_REV

{rttp-1.3.1 → rttp-1.3.2}/src/rttp/vectors/rttp-conformance-v1.2.6.json

@@ -1,8 +1,8 @@
 {
   "spec": "RTTP-FRAME-EXT-v1.2.6",
   "applies_to": [
-    "RFC-002 sec. 4.1",
-    "RFC-002 sec. 10"
+    "draft-li-rttp-iqa-addressing-02 §§4, 7.1",
+    "AICENT-002 sec. 7 (seal envelope; beyond -02)"
   ],
   "generated_by": "SPEC/tools/conformance.py",
   "note": "Generated file - do not edit by hand. Change the cases in conformance.py instead.",
@@ -78,7 +78,7 @@
       "action_omitted": false,
       "route_shard_hex": "cdc32d19641c84aca3292de6276de056",
       "tolerance": true,
-      "note": "tolerance - the specification defines no such form; accepted because it is the scheme name under which a handler is registered (RFC-002 sec. 10.6)"
+      "note": "tolerance - the specification defines no such form; accepted because it is the scheme name under which a handler is registered (draft-02 §4.5.2)"
     },
     {
       "uri": "rttp://a-b-c.d-e.f-g/audit-v2",
@@ -98,63 +98,63 @@
   "negative_uris": [
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent/VESSEL",
-      "reason": "uppercase action - lowercase only (RFC-002 sec. 10.3)"
+      "reason": "uppercase action - lowercase only (draft-02 §4.2)"
     },
     {
       "uri": "rttp://F3B2A1C4.rttp.aicent/vessel",
-      "reason": "uppercase intent - lowercase only (RFC-002 sec. 10.3)"
+      "reason": "uppercase intent - lowercase only (draft-02 §4.2)"
     },
     {
       "uri": "RTTP://f3b2a1c4.rttp.aicent/vessel",
-      "reason": "uppercase scheme prefix - canonical form is lowercase (RFC-002 sec. 10.3)"
+      "reason": "uppercase scheme prefix - canonical form is lowercase (draft-02 §4.2)"
     },
     {
       "uri": "WEB+RTTP://f3b2a1c4.rttp.aicent/vessel",
-      "reason": "uppercase scheme prefix on the handler form (RFC-002 sec. 10.3)"
+      "reason": "uppercase scheme prefix on the handler form (draft-02 §4.2)"
     },
     {
       "uri": "rttp://subject@rttp.aicent/vessel",
-      "reason": "userinfo is not defined (RFC-002 sec. 10.3)"
+      "reason": "userinfo is not defined (draft-02 §4.2)"
     },
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent/vessel?x=1",
-      "reason": "query is not defined (RFC-002 sec. 10.3)"
+      "reason": "query is not defined (draft-02 §4.2)"
     },
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent/vessel#f",
-      "reason": "fragment is not defined (RFC-002 sec. 10.3)"
+      "reason": "fragment is not defined (draft-02 §4.2)"
     },
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent:443/vessel",
-      "reason": "port is not defined (RFC-002 sec. 10.3)"
+      "reason": "port is not defined (draft-02 §4.2)"
     },
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent/a/b",
-      "reason": "second path segment - path is a single '/<action>'"
+      "reason": "second path segment - path is a single '/<action>' (draft-02 §4.1)"
     },
     {
       "uri": "rttp://a.b",
-      "reason": "authority has two segments, must be <intent>.<pillar>.<root>"
+      "reason": "authority has two segments, must be <intent>.<pillar>.<root> (draft-02 §4.1)"
     },
     {
       "uri": "rttp://a.b.c.d/e",
-      "reason": "authority has four segments, must be <intent>.<pillar>.<root>"
+      "reason": "authority has four segments, must be <intent>.<pillar>.<root> (draft-02 §4.1)"
     },
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent/",
-      "reason": "trailing '/' with empty action - action is 1*(...)"
+      "reason": "trailing '/' with empty action - action is 1*(...) (draft-02 §4.1)"
     },
     {
       "uri": "https://f3b2a1c4.rttp.aicent/vessel",
-      "reason": "not an rttp scheme - there is no fallback (RFC-002 sec. 10.5)"
+      "reason": "not an rttp scheme - there is no fallback (draft-02 §4.2 + §4.5.2)"
     },
     {
       "uri": "rttp://f3b2a1c4.rttp.aicent/vessel ",
-      "reason": "trailing whitespace"
+      "reason": "trailing whitespace (draft-02 §4.1)"
     },
     {
       "uri": "rttp://-lead.rttp.aicent/vessel",
-      "reason": "intent begins with '-'"
+      "reason": "intent begins with '-' - CONFLICT: draft-02 §4.1 ABNF name-intent literally allows a leading '-'; the vector keeps the stricter rejection and -03 will tighten the ABNF (owner decision 2026-11-09)"
     }
   ],
   "frame_vectors": [
@@ -202,63 +202,63 @@
     {
       "label": "ACTION_LEN exceeds the 16-byte maximum (17)",
       "rule": "R4",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 3.2",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d01011176657373656c0000000000000000000000000000000000"
     },
     {
       "label": "ACTION padding is non-zero",
       "rule": "R4",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 3.2",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d01010676657373656c0078000000000000000000000000000000"
     },
     {
       "label": "ACTION contains an embedded NUL",
       "rule": "R4",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 3.2",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d01010676657300656c0000000000000000000000000000000000"
     },
     {
-      "label": "ACTION violates the sec. 10.2 grammar (uppercase)",
+      "label": "ACTION violates the draft-02 §4.1 grammar (uppercase)",
       "rule": "R4",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 3.2",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d01010656455353454c0000000000000000000000000000000000"
     },
     {
       "label": "SPEC_REV is outside the known set (2)",
       "rule": "R5",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 4",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d02010676657373656c0000000000000000000000000000000000"
     },
     {
       "label": "SPEC_REV is outside the known set (255)",
       "rule": "R5",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 4",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789dff010676657373656c0000000000000000000000000000000000"
     },
     {
       "label": "SPEC_REV=0 with a non-zero extension block",
       "rule": "R6",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 4",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d00010676657373656c0000000000000000000000000000000000"
     },
     {
       "label": "RESERVED is non-zero under SPEC_REV=1",
       "rule": "R7",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 4",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d01010676657373656c0000000000000000000001000000000000"
     },
     {
       "label": "unknown FLAGS bit set under SPEC_REV=1",
       "rule": "R7",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 4",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "reject",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d01030676657373656c0000000000000000000000000000000000"
     }
@@ -267,14 +267,14 @@
     {
       "label": "SPEC_REV=1 with ACTION_LEN=0 is valid and equivalent to omission",
       "rule": "R3",
-      "spec_ref": "RTTP-FRAME-EXT-v1.2.6 sec. 4",
+      "spec_ref": "draft-li-rttp-iqa-addressing-02 §7.1.1",
       "expected": "accept",
       "action": "",
       "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d0101000000000000000000000000000000000000000000000000"
     }
   ],
   "envelope_vector": {
-    "spec": "RTTP-SEAL-ENVELOPE-v1.2.6 sec. 7",
+    "spec": "AICENT-002 (RTTP-SEAL-ENVELOPE-v1.2.6 sec. 7)",
     "alg": "ed25519",
     "seed_hex": "e722fed924c7f76b157faab674ea97bb7c3075f55ad7d3c6319418e22b86d611",
     "aid": "3125ee20b2238281f70ca408192f82152647d365219184fa1fe22c08a42c035e",
@@ -294,7 +294,7 @@
     "action": "",
     "action_omitted": true,
     "uri_anchored": false,
-    "expected": "verify() MUST accept; action is treated as omitted (RFC-002 sec. 10.4 default operation)",
+    "expected": "verify() MUST accept; action is treated as omitted (draft-02 §4.3 default operation)",
     "header_hex": "5254545000000000000000000000000000000082000000000000000000000000000000010000000000000000186cc6acd4b00000ff01bf77b78ff6ceafc363226aa5865622185d42ba8b38fe10bfa702bdfe6af536ea16e20e35fbb48d84c3658d80cad2789d0000000000000000000000000000000000000000000000000000"
   }
 }