RFC 9891: Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation Extension
In plain English — editorial summary, not part of the RFC
This document specifies an extension to the Automated Certificate Management Environment (ACME) protocol that allows an ACME server to validate the Delay-Tolerant Networking (DTN) Node ID for an ACME client. A DTN Node ID is an identifier used in the Bundle Protocol (BP) to name a "singleton endpoint": an endpoint that is registered on a single BP Node. The DTN Node ID is encoded both as a certificate Subject Alternative Name (SAN) identity of type otherName with an Other Name form of BundleEID and as an ACME Identifier type "bundleEID".
Document record
- Document ID
- RFC9891
- Published
- November 2025
- Authors
- B. Sipos
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- sec
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9447Automated Certificate Management Environment (ACME) Challenges Using an Authority TokenCurrent
September 2023
- RFC 8823Extensions to Automatic Certificate Management Environment for End-User S/MIME CertificatesCurrent
April 2021
- RFC 8737Automated Certificate Management Environment (ACME) TLS Application-Layer Protocol Negotiation (ALPN) Challenge ExtensionCurrent
February 2020
- RFC 9758Updates to the 'ipn' URI SchemeCurrent
May 2025
- RFC 9713Bundle Protocol Version 7 Administrative Record Types RegistryCurrent
January 2025
- RFC 9675Delay-Tolerant Networking Management Architecture (DTNMA)Current
November 2024
- RFC 9538Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management EnvironmentCurrent
February 2024
- RFC 9883An Attribute for Statement of Possession of a Private KeyCurrent
October 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?