[stir] I-D Action: draft-ietf-stir-certificate-transparency-04.txt

internet-drafts@ietf.org Mon, 17 August 2026 13:47 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178697442803.423538.4073302864843868927@dt-datatracker-7c6ddbc678-86d5j>
Date: Mon, 17 Aug 2026 06:47:08 -0700
Message-ID-Hash: 2XBPHUJC6CKRS5WKD6VJXUPYDSU5E7PV
CC: stir@ietf.org
Reply-To: stir@ietf.org
Subject: [stir] I-D Action: draft-ietf-stir-certificate-transparency-04.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/rrWx1OW7N0GCB7RNVxGlC8tGub0>

Internet-Draft draft-ietf-stir-certificate-transparency-04.txt is now
available. It is a work item of the Secure Telephone Identity Revisited (STIR)
WG of the IETF.

   Title:   STI Certificate Transparency
   Authors: Chris Wendt
            Rob Śliwa
            Alec Fenichel
            Vinit Anil Gaikwad
   Name:    draft-ietf-stir-certificate-transparency-04.txt
   Pages:   16
   Dates:   2026-08-17

Abstract:

   This document describes a framework for the use of the Certificate
   Transparency (CT) protocol for publicly logging the existence of
   Secure Telephone Identity (STI) certificates as they are issued or
   observed.  This allows any interested party that is part of the STI
   ecosystem to audit STI certification authority (CA) activity and
   audit both the issuance of suspect certificates and the certificate
   logs themselves.  The intent is to establish a level of trust within
   the STI ecosystem that relies on the verification of telephone
   numbers.  This involves requiring STI certificates to be listed in an
   established log and refusing to honor those that are not.  This
   effectively establishes the precedent that STI CAs must add all
   issued certificates to the logs and thus establishes unique
   association of STI certificates to an authorized provider or assignee
   of a telephone number resource.  In the STI ecosystem, the primary
   role of CT is to provide verifiable trust by detecting the
   unauthorized issuance of duplicate telephone number level delegate
   certificates or provider level certificates.  This provides a robust
   auditable mechanism for the detection of unauthorized creation of
   certificate credentials for illegitimate spoofing of telephone
   numbers or service provider codes (SPC).

   The framework borrows the log structure and API model from RFC6962 to
   enable public auditing and verifiability of certificate issuance.
   While the foundational mechanisms for log operation, Merkle Tree
   construction, and Signed Certificate Timestamps (SCTs) are aligned
   with RFC6962, this document contextualizes their application in the
   STIR ecosystem, focusing on verifiable control over telephone number
   or service provider code resources.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-stir-certificate-transparency/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-stir-certificate-transparency-04

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-stir-certificate-transparency-04

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

[stir] I-D Action: draft-ietf-stir-certificate-tr… internet-drafts