I-D Action: draft-mih-sokolov-scitt-payload-binding-03.txt

internet-drafts@ietf.org Sun, 06 September 2026 02:39 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-mih-sokolov-scitt-payload-binding-03.txt
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <178866237384.370426.1757652260397247102@dt-datatracker-9769b79f-xztnc>
Date: Sat, 05 Sep 2026 19:39:33 -0700
Message-ID-Hash: QCCLPLMWTYBR43HWYRMLAN2UBO7TNFZ4
Reply-To: internet-drafts@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/r1PC3DlShNtsMbkonGMjUGmZKiY>

Internet-Draft draft-mih-sokolov-scitt-payload-binding-03.txt is now
available.

   Title:   Canonical Payload Binding: A Signed Statement Construction Profile
   Authors: Steven Mih
            Anton Sokolov
   Name:    draft-mih-sokolov-scitt-payload-binding-03.txt
   Pages:   45
   Dates:   2026-09-05

Abstract:

   Independently written systems that anchor records to a SCITT
   Transparency Service repeatedly need the same construction: a
   canonical form of structured content, a content-addressed identifier
   derived from that form, binding to a SCITT Signed Statement and
   Receipt, and references that cite external artifacts by digest.  This
   document defines that construction as the Canonical Payload Binding
   (CPB).  A payload profile declares its canonicalization algorithm and
   exclusion set and thereby obtains a reproducible derived identifier.
   A CPB Signed Statement carries either the complete statement content
   as specified by RFC 9943 or a digest of content held elsewhere using
   the COSE Hash Envelope of RFC 9995.  CPB also defines an abstract
   typed digest reference information model and one optional protected-
   header encoding, cpb-refs; a payload profile may instead define its
   own reference serialization.  An IANA registry governs CPB
   canonicalization algorithms.  CPB does not define payload content
   formats, establish or require a universal artifact-type registry, or
   require either typed-reference carrier.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-mih-sokolov-scitt-payload-binding/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-mih-sokolov-scitt-payload-binding-03.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-mih-sokolov-scitt-payload-binding-03

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

I-D Action: draft-mih-sokolov-scitt-payload-bindi… internet-drafts