The GNS Split Resource Record Set

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 3 September 2026.¶

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.¶

Table of Contents

1. Introduction

In GNS [RFC9498], resource record set sizes are limited by the underlying storage component. For example, in the current instantion in GNUnet on top of R⁵N, Resource record sets must fit into around 64 kilobytes. This includes all records in the set as well as signatures and encryption overhead (e.g. the authentication tag). This prohibits use cases that require some large records or a lot of small records, but also makes post-quantum signature schemes more difficult to integrate.¶

This document defines a new record type that allows record sets to be split across multiple record sets in GNS. The new record type is backwards compatible with the existing GNS, but resolver that do not conform to this specification will be unable to fully retrieve the split record set. In this case, the applicatin must take care and collect all entries of the record set in the zone.¶

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].¶

2. SPLIT

This record consists of a list of resource record types that should exist and belong to this record set.¶

A SPLIT resource record is expected to be found along with other resource records. A SPLIT DATA entry is illustrated in Figure 1.¶

0     8     16    24    32
+-----+-----+-----+-----+
|    RECORD TYPE 0      |
+-----------------------+
|    RECORD TYPE 1      |
+-----------------------+
/           ...         /
/                       /
+-----------------------+
|    RECORD TYPE N-1    |
+-----+-----+-----+-----+

RECORD TYPE X

The 32-bit record type number (as defined in GANA) in network byte order.¶

The record types indicate to the resolve that it SHOULD try to resolve further resource record sets of the specified type(s) if the record type is being asked for as part of the resolution. Otherwise, the record type can be ignored.¶

4. Security Considerations

5. GANA Considerations

GANA is requested to populate this registry as follows:¶

Number: 65555
Name: SPLIT
Contact: gns-registry@gnunet.org
References: [This.I-D]
Description: SPLIT Record Set

Authors' Addresses