You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: move SVCB key numbers to RFC 9460 Private Use range (v0.9.0) (#38)
All custom SvcParamKeys migrated from the Expert Review range
(65001-65010) to the Private Use range (65280-65534) per RFC 9460
Section 14.3:
cap=key65400, cap-sha256=key65401, bap=key65402,
policy=key65403, realm=key65404, sig=key65405
The old numbers (65001-65010) required IANA registration. The new
numbers (65400-65405) are in the Private Use range and free to use.
Verified end-to-end against live Route53 and NIOS backends.
BREAKING CHANGE: Existing DNS records using old key numbers will
need re-publishing.
Signed-off-by: Igor Racic <iracic82@gmail.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,11 @@ All notable changes to DNS-AID will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [0.9.0] - 2026-02-24
9
+
10
+
### Changed
11
+
-**SVCB key numbers moved to RFC 9460 Private Use range** — All custom SvcParamKeys migrated from the Expert Review range (65001–65010) to the Private Use range (65280–65534) per RFC 9460 Section 14.3. New mapping: cap=key65400, cap-sha256=key65401, bap=key65402, policy=key65403, realm=key65404, sig=key65405. **Breaking:** existing DNS records using the old key numbers will need re-publishing.
12
+
8
13
## [0.8.0] - 2026-02-21
9
14
10
15
### Added
@@ -15,7 +20,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
15
20
16
21
### Changed
17
22
-**BANDAID → DNS-AID rename** — All references to "BANDAID" and `bandaid_` updated to "DNS-AID" and `dnsaid_` across source, tests, docs, and metadata files. IETF draft reference updated from `draft-mozleywilliams-dnsop-bandaid-02` to `draft-mozleywilliams-dnsop-dnsaid-01`
18
-
-**`bap` SvcParamKey number** — Changed from `key65003` to `key65010` to match IETF draft Section 4.4.3 example. **Breaking:** existing DNS records with `key65003` for bap will need re-publishing
23
+
-**`bap` SvcParamKey number** — Changed from `key65003` to `key65010` to match IETF draft Section 4.4.3 example. **Breaking:** existing DNS records with `key65003` for bap will need re-publishing (further updated to `key65402` in v0.9.0)
19
24
20
25
## [0.7.3] - 2026-02-19
21
26
@@ -150,15 +155,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
150
155
-**Experimental Models Documentation** — Marked `agent_metadata` and `capability_model` modules as experimental with status docstrings
151
156
152
157
### Fixed
153
-
-**Route53 SVCB custom params** — Route53 rejects private-use SvcParamKeys (`key65001`–`key65006`). The Route53 backend now demotes custom DNS-AID params to TXT records with `dnsaid_` prefix, keeping the publish working without data loss
158
+
-**Route53 SVCB custom params** — Route53 rejects private-use SvcParamKeys (`key65400`–`key65405`). The Route53 backend now demotes custom DNS-AID params to TXT records with `dnsaid_` prefix, keeping the publish working without data loss
154
159
-**Cloudflare SVCB custom params** — Same demotion applied to the Cloudflare backend
155
160
-**CLI `--backend` help text** — Now lists all five backends (route53, cloudflare, infoblox, ddns, mock) instead of just "route53, mock"
156
161
-**SECURITY.md contact** — Updated from placeholder LF mailing list to interim maintainer email
157
162
-**Bandit config** — Migrated from `.bandit` INI to `pyproject.toml``[tool.bandit]` for newer bandit compatibility
158
163
-**CLI ANSI escape codes** — Stripped Rich/Typer ANSI codes in test assertions for Python 3.13 compatibility
159
164
160
165
### Notes
161
-
- BIND/DDNS backends natively support custom SVCB params (`key65001`–`key65006`) — no demotion needed
166
+
- BIND/DDNS backends natively support custom SVCB params (`key65400`–`key65405`) — no demotion needed
162
167
- DNSSEC enforcement defaults to `False` (backwards compatible)
163
168
- DANE cert matching defaults to `False` (advisory TLSA existence check remains the default)
These key numbers are in the private-use range pending IANA registration through the IETF draft process. The numeric form (`key65001`) is the default wire format; the string form (`cap`) can be enabled via the `DNS_AID_SVCB_STRING_KEYS` environment variable for human-readable debugging.
These key numbers are in the Private Use range pending IANA registration through the IETF draft process. The numeric form (`key65400`) is the default wire format; the string form (`cap`) can be enabled via the `DNS_AID_SVCB_STRING_KEYS` environment variable for human-readable debugging.
|`NIOS_VERIFY_SSL`| No |`false`| Verify TLS certificate |
510
510
511
-
**DNS-AID Compliance**: NIOSWAPI supports ServiceMode SVCB records (priority >0) with full SVC parameters including custom DNS-AID keys (`key65001`–`key65006`). Fully compliant with the DNS-AID draft.
511
+
**DNS-AID Compliance**: NIOSWAPI supports ServiceMode SVCB records (priority >0) with full SVC parameters including custom DNS-AID keys (`key65400`–`key65405`). Fully compliant with the DNS-AID draft.
Copy file name to clipboardExpand all lines: docs/getting-started.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -380,7 +380,7 @@ dns-aid delete \
380
380
381
381
### NIOS DNS-AID Compliance
382
382
383
-
NIOS WAPI supports ServiceMode SVCB records (priority > 0) with full SVC parameters, including custom DNS-AID keys natively via `key65001`–`key65006`. This makes it fully compliant with the DNS-AID draft.
383
+
NIOS WAPI supports ServiceMode SVCB records (priority > 0) with full SVC parameters, including custom DNS-AID keys natively via `key65400`–`key65405`. This makes it fully compliant with the DNS-AID draft.
0 commit comments