Hi, I've been wondering how we could avoid the chicken/egg problem for BRSKI and ACP deployment. Here is a suggestion.
This is not for today (I will be fast asleep for the meeting anyway), but comments would be welcome. Regards Brian Carpenter -------- Forwarded Message -------- Subject: I-D Action: draft-carpenter-anima-otp-casa-00.txt Date: Mon, 20 Jul 2026 17:22:21 -0700 From: [email protected] Reply-To: [email protected] To: [email protected] Internet-Draft draft-carpenter-anima-otp-casa-00.txt is now available. Title: One-time Pad for Authorizing Device Identity Author: Brian E. Carpenter Name: draft-carpenter-anima-otp-casa-00.txt Pages: 6 Dates: 2026-07-20 Abstract: This document describes how devices joining an autonomic control plane as defined in RFC 8994 may use the bootstrapping mechanism defined in RFC 8995 even if they cannot use a manufacturer-installed X.509 certificate. Instead, such devices may generate a self-signed certificate embedding a unique token selected from a one-time pad. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-carpenter-anima-otp-casa/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-carpenter-anima-otp-casa-00.html Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
