Subject: [dtn] Fw: New Version Notification for draft-sipos-acme-dtnnodeid-00.txt

From: Brian Sipos <[email-masked]>
Date: Fri, 5 Jun 2020 20:37:30 +0000

All,
On the AD advice to give more thought to the security aspects of "how does a TCPCL PKIX certificate come to be?" I have drafted a relatively simple spec which uses existing PKI infrastructure to verify ownership of a DTN Node ID and authorize it to be used in a PKIX certificate.

Any feedback on this mechanism from those with lots of hands-on DTN experience are greatly appreciated! Especially related to routing and BPSEC nuances.
Thanks,
Brian S.
________________________________________
From: [email-masked] <[email-masked]>
Sent: Friday, June 5, 2020 14:08
To: Brian Sipos; Brian Sipos
Subject: New Version Notification for draft-sipos-acme-dtnnodeid-00.txt

A new version of I-D, draft-sipos-acme-dtnnodeid-00.txt
has been successfully submitted by Brian Sipos and posted to the
IETF repository.

Name:           draft-sipos-acme-dtnnodeid
Revision:       00
Title:          Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation Extension
Document date:  2020-06-04
Group:          Individual Submission
Pages:          14
URL:            https://www.ietf.org/internet-drafts/draft-sipos-acme-dtnnodeid-00.txt
Status:         https://datatracker.ietf.org/doc/draft-sipos-acme-dtnnodeid/
Htmlized:       https://tools.ietf.org/html/draft-sipos-acme-dtnnodeid-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-sipos-acme-dtnnodeid

Abstract:
   This document specifies an extension to the Automated Certificate
   Management Environment (ACME) protocol which allows validating the
   Delay-Tolerant Networking (DTN) Node ID for an ACME client.  The use
   of a Uniform Resource Identifier (URI) as ACME identifier is also
   specified.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat