Skip to content

docs: update org profile Namespace section to draft-02 flat naming - #1

Open
kentaro wants to merge 1 commit into
dns-aid:mainfrom
kentaro:fix-profile-readme-draft02-naming
Open

docs: update org profile Namespace section to draft-02 flat naming#1
kentaro wants to merge 1 commit into
dns-aid:mainfrom
kentaro:fix-profile-readme-draft02-naming

Conversation

@kentaro

@kentaro kentaro commented Aug 10, 2026

Copy link
Copy Markdown

What

The org profile README still documents the draft-01 namespace form:

_{agent-name}._{protocol}._agents.{your-domain}

Under draft-mozleywilliams-dnsop-dnsaid-02, the agent's primary owner name is the flat FQDN {agent-name}.{your-domain} — the form requestors try first, valid as an X.509 SAN dNSName. The protocol is no longer encoded as an FQDN label; it is carried in SvcParams (alpn, or the experimental bap key). See docs/rfc/wire-format.abnf in dns-aid-core for the -02 grammar.

This PR updates the Namespace section and step 3 of the four-step workflow accordingly. The _index._agents.{domain} enumeration leaf is kept (still part of the current spec), and the optional walkable _agents alias is mentioned.

Why now

dns-aid-core migrated to draft-02 flat naming in v0.24.0 (dns-aid/dns-aid-core#155, dns-aid/dns-aid-core#167), so the org profile is the last place still showing the -01 form to newcomers.

Scope

Documentation only; no changes outside the Namespace wording and the one workflow example.

The org profile still described the draft-01 namespace form
(_{agent-name}._{protocol}._agents.{your-domain}). Under
draft-mozleywilliams-dnsop-dnsaid-02 the agent's primary owner name
is the flat FQDN {agent-name}.{your-domain}, with the protocol
carried in SvcParams (alpn / bap) rather than in the name.
The _index._agents leaf remains the reserved enumeration record.

Signed-off-by: Kentaro Kuribayashi <kentarok@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant