RFC 9891 on Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation Extension

rfc-editor@rfc-editor.org Thu, 20 November 2025 21:58 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id C67778D88F7D; Thu, 20 Nov 2025 13:58:03 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 99F9BC000CC0; Thu, 20 Nov 2025 13:58:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9891 on Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation Extension
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20251120215803.99F9BC000CC0@rfcpa.rfc-editor.org>
Date: Thu, 20 Nov 2025 13:58:03 -0800
Message-ID-Hash: YLVUREHUQKD2EZFWSM4PREGOR3DIZWY3
X-Message-ID-Hash: YLVUREHUQKD2EZFWSM4PREGOR3DIZWY3
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, acme@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2zZ8-aGDvML5ml-qbPfOZiVWxSU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9891

        Title:      Automated Certificate Management Environment (ACME) 
                    Delay-Tolerant Networking (DTN) Node ID Validation 
                    Extension 
        Author:     B. Sipos
        Status:     Experimental
        Stream:     IETF
        Date:       November 2025
        Mailbox:    brian.sipos+ietf@gmail.com
        Pages:      26
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-acme-dtnnodeid-18.txt

        URL:        https://www.rfc-editor.org/info/rfc9891

        DOI:        10.17487/RFC9891

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

This document is a product of the Automated Certificate Management Environment Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team