Network Working Group P. Chapman Internet-Draft To.Co Technologies Limited Intended status: Informational 16 November 2026 Expires: 20 May 2027 The "_abiz" Underscored and Globally Scoped DNS Node Name for Agentic Business Records draft-toco-abiz-dns-00 Abstract This document specifies use of the underscored DNS node name "_abiz" with TXT resource records to publish a pointer from a domain to a signed public business record served over HTTPS. It describes discovery and verification of that record and requests registration of the "_abiz" node name and the "abiz.json" well-known URI suffix. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on 20 May 2027. Copyright Notice Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/ license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License. Chapman Expires 20 May 2027 [Page 1] Internet-Draft ABIZ DNS Pointer November 2026 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. The ABIZ DNS Assertion . . . . . . . . . . . . . . . . . . . 3 3.1. Owner Name and RRset . . . . . . . . . . . . . . . . . . 3 3.2. Tag Syntax . . . . . . . . . . . . . . . . . . . . . . . 3 3.3. Tags . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.4. Examples . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Well-Known URI Alternative . . . . . . . . . . . . . . . . . 5 5. Discovery Procedure . . . . . . . . . . . . . . . . . . . . . 5 6. Relationship to the Public Business Record . . . . . . . . . 6 6.1. Retrieval . . . . . . . . . . . . . . . . . . . . . . . . 6 6.2. Verification . . . . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 7 8. Privacy Considerations . . . . . . . . . . . . . . . . . . . 8 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 10. Normative References . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 1. Introduction Businesses publish public facts about themselves on the web, but software that discovers a domain may not have a provider-independent way to locate a structured, signed record of those facts. ABIZ (Agentic Business Record) uses a TXT record at "_abiz" under a domain to point to an HTTPS resource serving a signed JSON business record. This document describes the DNS assertion, the discovery procedure, the checks that link a record to the queried domain, and the registrations. The ABIZ 1.1 record schema and the rules for the record's content are specified in [ABIZSPEC]. An ABIZ assertion does not itself establish legal identity, business registration, or endorsement by an AI provider. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. ABIZ assertion: A versioned tag list carried in a TXT resource record at "_abiz.", or the same values carried in a well- known document (Section 4). Queried domain: The domain name for which discovery is being Chapman Expires 20 May 2027 [Page 2] Internet-Draft ABIZ DNS Pointer November 2026 performed, written "". Record host: The host, optionally followed by a permitted path, identified by the "h" tag. Producer: The party that publishes an ABIZ assertion for a domain it controls. Consumer: Software that discovers and validates an ABIZ record. 3. The ABIZ DNS Assertion 3.1. Owner Name and RRset The producer publishes the assertion in a TXT resource record at "_abiz.". A TXT record is an ABIZ assertion when its first tag is "v=abiz1" (Section 3.2). There MUST be exactly one such record at that owner name. More than one makes the ABIZ assertion invalid; none means that no DNS assertion is present. Other TXT records at the same name (including one whose first tag is "V=ABIZ1" or "v=abiz1x") are not ABIZ assertions and are not counted. The character-strings within a single TXT resource record [RFC1035] are concatenated in order, with nothing added between them, before tag parsing. The TTL SHOULD be 300 seconds. 3.2. Tag Syntax After character-string concatenation, the assertion MUST match "abiz- record" in the following ABNF [RFC5234] [RFC7405]: abiz-record = *WSP abiz-version *( abiz-sep abiz-tag ) [ *WSP ";" ] *WSP abiz-version = %s"v" *WSP "=" *WSP %s"abiz1" abiz-sep = *WSP ";" *WSP abiz-tag = tag-name *WSP "=" *WSP tag-value tag-name = 1*( %x21-3A / %x3C / %x3E-7E / %x80-FF ) tag-value = 1*( %x21-3A / %x3C-7E / %x80-FF ) WSP = SP / HTAB * Space and horizontal tab are the only whitespace, and are permitted only at the start and end of the assertion and around ";" and "=". Other control characters MUST NOT appear. A tag value does not contain whitespace or ";". * A tag is split on its first "=" only; a value may itself contain "=". Chapman Expires 20 May 2027 [Page 3] Internet-Draft ABIZ DNS Pointer November 2026 * At most one trailing ";" is permitted. An empty tag, a tag without "=", and a tag with an empty name or value make the assertion invalid. * Tag names and the value "abiz1" are case-sensitive. "H=" is an unknown tag, not "h=". * A recognised tag ("v", "h", "k", "p") that occurs more than once makes the assertion invalid. Unknown tags MUST be ignored, repeated or not, and MUST NOT be given any meaning. Producers SHOULD publish the compact form with no optional whitespace. Consumers MUST accept the full syntax. 3.3. Tags v (REQUIRED): Protocol family version, with the exact value "abiz1". It is always the first tag. h (REQUIRED): The record host: a DNS host name, without scheme, user information, port, query, or fragment. A path MAY follow the host name, only to identify a business unit or division as permitted by [ABIZSPEC]; it MUST NOT contain "." or ".." segments. The host name MUST be a public name. Consumers MUST reject an "h" that names a special-use, loopback, private-network, or link-local host. The record host MAY be operated by a party other than the producer. p (REQUIRED): The raw 32-byte Ed25519 public key [RFC8032] in the base64 encoding of Section 4 of [RFC4648], with padding: exactly 44 characters, the last of which is "=". The encoding MUST be canonical (encoding the decoded octets again gives the same text). The base64url alphabet, unpadded values, and hexadecimal strings are invalid. k (OPTIONAL): The business registration key, in the form specified by [ABIZSPEC]. It is compared case-insensitively. An assertion that lacks "h" or "p", or in which "h", "p", or a present "k" is malformed, is invalid. 3.4. Examples Registered business (illustrative data): Chapman Expires 20 May 2027 [Page 4] Internet-Draft ABIZ DNS Pointer November 2026 _abiz.harbourbikes.example. 300 IN TXT ( "v=abiz1;k=us-or-123456;" "h=harbour-bike-repair.or.us.to.co;" "p=oQ0t/PFgN9pH0QSNUHrY5FLj5igISyzD1z6AXr5NtZo=") Unregistered business (illustrative data): _abiz.marketstand.example. 300 IN TXT ( "v=abiz1;h=market-stand-repairs-portland.biz.to.co;" "p=zc6S6bKXaZXO7NCI+fjtgMWLdbdEeavjVvydQsoQCJ0=") The examples are fictional; the public keys are demonstration values and MUST NOT be reused in production. 4. Well-Known URI Alternative A producer that cannot publish a TXT record, or prefers not to, MAY publish the same assertion at "https:///.well-known/ abiz.json" [RFC8615], where "" is exactly the queried domain (no "www." added or removed) on the default HTTPS port. A producer MAY publish both; if it does, the two MUST carry identical values. The document is a UTF-8 JSON object [RFC8259] whose members "v", "h", "p", and the optional "k" are JSON strings holding exactly the corresponding tag values. A member that is not a string, or whose value would not be a valid tag value, makes the document invalid. Unknown members MUST be ignored. The document is a pointer, not the business record. { "v": "abiz1", "k": "us-or-123456", "h": "harbour-bike-repair.or.us.to.co", "p": "oQ0t/PFgN9pH0QSNUHrY5FLj5igISyzD1z6AXr5NtZo=" } The producer MUST serve the document with status 200, without a redirect, with the media type "application/json", and at no more than 65,536 octets. A consumer MUST apply the safe-retrieval rules of Section 6.1, MUST NOT follow redirects, and MUST treat any other status, media type, or a larger body as an invalid document. A consumer MUST NOT cache the document for more than 300 seconds. 5. Discovery Procedure The DNS assertion takes precedence over the well-known document. A consumer: Chapman Expires 20 May 2027 [Page 5] Internet-Draft ABIZ DNS Pointer November 2026 1. MUST first query TXT at "_abiz.". 2. If the query fails (for example, SERVFAIL or a timeout), MUST report the result as unavailable. It MUST NOT report that no assertion exists and MUST NOT use the well-known document in its place. 3. If the RRset holds two or more ABIZ assertions, MUST treat the result as invalid and MUST NOT use the well-known document. 4. If it holds exactly one, MUST use that assertion. If the assertion is malformed, the result is invalid and the well-known document MUST NOT be used in its place. A consumer MAY also fetch the well-known document; if that document disagrees with the DNS assertion or is invalid, the consumer MUST use the DNS assertion and SHOULD report a warning. 5. If there is no ABIZ assertion in DNS (a name error, no data, or only other TXT records), SHOULD fetch the well-known document. If it is valid, its members are treated exactly as the tags of a DNS assertion. If it is absent or invalid, there is no ABIZ assertion for the domain. A consumer MUST record which source it used. Only the queried domain is consulted: a consumer MUST NOT substitute a parent domain or another name. 6. Relationship to the Public Business Record 6.1. Retrieval The consumer retrieves the record with a GET request to "https://", sending "Accept: application/json"; it SHOULD also append the query "format=json" as defined in [ABIZSPEC]. When retrieving the record or the well-known document, a consumer MUST: * use HTTPS with certificate and host name validation; * refuse to connect to loopback, private-network, and link-local addresses, checking the addresses the host name resolves to; * not follow unsafe redirects (a consumer MAY refuse all redirects, and MUST refuse them for the well-known document); * limit the response size and the time it waits; * accept only a 200 response whose media type is "application/json", and parse it as data without executing anything. Chapman Expires 20 May 2027 [Page 6] Internet-Draft ABIZ DNS Pointer November 2026 A failure that may be temporary (a timeout, a connection or TLS failure, or a 408, 429, or 5xx status) does not establish that the record is absent or invalid; a consumer SHOULD report it as unavailable. 6.2. Verification Before relying on a retrieved record, a consumer MUST check all of the following. A record that fails any of them MUST NOT be treated as published by the controller of the queried domain. 1. The body is a JSON object in the I-JSON profile [RFC7493]; a repeated member name is an error. It validates against the ABIZ 1.1 schema [ABIZSPEC]. 2. The record's "identity_host" member equals the "h" value exactly, including any path. 3. The record's "domains" member includes the queried domain. 4. If the assertion has "k", the record has a "business_key" member equal to it, compared case-insensitively. 5. The record's "public_key" member equals the "p" value (an exact string comparison, since both are canonical). 6. The record's "signature" member is a 64-octet PureEd25519 signature [RFC8032], in padded base64, that verifies under that key. The signed message is the UTF-8 encoding of the canonical JSON form [RFC8785] of the record with its top-level "signature" member removed. These checks link a record to a domain. They do not check the business's legal registration, and a consumer that has not checked a registry MUST NOT describe the business as legally verified. 7. Security Considerations Publication under a DNS domain does not prove legal ownership or registration of a business. The record signature binds the JSON document to the key in the assertion but does not authenticate the assertion itself. An attacker who can change unsigned DNS answers can substitute both the record host and the public key. Producers SHOULD sign their zones and consumers SHOULD validate DNSSEC where they can. Chapman Expires 20 May 2027 [Page 7] Internet-Draft ABIZ DNS Pointer November 2026 The "identity_host" and "domains" checks of Section 6.2 are what stop a domain from pointing at another business's validly signed record and so appearing to be that business. A consumer that omits them is not protected by the signature. A well-known document shows control of the HTTPS origin at the domain, which is not the same as control of its DNS zone: a hosting provider can publish it. This is why the DNS assertion takes precedence and why a malformed or duplicated DNS assertion is never bypassed in favour of the document. A consumer MAY treat a DNS- sourced assertion as stronger evidence of domain control. The "h" value and the well-known URL are attacker-chosen inputs to a consumer that fetches them. The retrieval rules of Section 6.1 (public addresses only, checked after name resolution; redirect, size, and time limits) are requirements, not advice: without them a consumer can be used to reach internal services. Consumers MUST treat a fetched record as untrusted data and MUST NOT automatically follow instructions, URLs, or tool endpoints contained in it. A DNS or origin failure MUST NOT be reported as the absence of a record; otherwise an attacker who can cause failures can make a published business appear unpublished. The producer MUST protect the signing private key. If the key is lost or compromised, the producer replaces it and publishes a new assertion; consumers accept only a record signed with the key currently published and may reject a correctly re-signed record until cached DNS data expires. 8. Privacy Considerations ABIZ assertions and records are public. A producer publishes only facts it intends to be public. A consumer's DNS query and HTTPS request reveal to the DNS operator and the record host that the domain was looked up. 9. IANA Considerations In accordance with [RFC8552], IANA is requested to add the following entry to the "Underscored and Globally Scoped DNS Node Names" registry: Chapman Expires 20 May 2027 [Page 8] Internet-Draft ABIZ DNS Pointer November 2026 +=========+============+===============+ | RR Type | _NODE NAME | Reference | +=========+============+===============+ | TXT | _abiz | This document | +---------+------------+---------------+ Table 1: Requested Underscored DNS Node Registration In accordance with [RFC8615], IANA is also requested to register the following entry in the "Well-Known URIs" registry: URI Suffix: abiz.json Change Controller: To.Co Technologies Limited Specification Document: Section 4 of this document Status: provisional Related Information: [ABIZSPEC] 10. Normative References [RFC1035] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987, . [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, . [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data Encodings", RFC 4648, October 2006, . [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, January 2008, . [RFC7405] Kyzivat, P., "Case-Sensitive String Support in ABNF", RFC 7405, December 2014, . [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, March 2015, . Chapman Expires 20 May 2027 [Page 9] Internet-Draft ABIZ DNS Pointer November 2026 [RFC8032] Josefsson, S. and I. Liusvaara, "Edwards-Curve Digital Signature Algorithm (EdDSA)", RFC 8032, January 2017, . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, May 2017, . [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data Interchange Format", STD 90, RFC 8259, December 2017, . [RFC8552] Crocker, D., "Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves", BCP 222, RFC 8552, March 2019, . [RFC8615] Nottingham, M., "Well-Known Uniform Resource Identifiers (URIs)", RFC 8615, May 2019, . [RFC8785] Rundgren, A., Jordan, B., and S. Erdtman, "JSON Canonicalization Scheme (JCS)", RFC 8785, June 2020, . [ABIZSPEC] To.Co Technologies Limited, "ABIZ - Agentic Business Record Specification, Version 1.1", November 2026, . Author's Address Peter Chapman To.Co Technologies Limited 66 Paul Street London EC2A 4NA United Kingdom Email: pjc@to.co Chapman Expires 20 May 2027 [Page 10]