Skip to main content

Supply Chain Integrity, Transparency, and Trust (SCITT) Reference APIs
draft-ietf-scitt-scrapi-10

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, amchamay@microsoft.com, debcooley1@gmail.com, draft-ietf-scitt-scrapi@ietf.org, rfc-editor@rfc-editor.org, scitt-chairs@ietf.org, scitt@ietf.org
Subject: Protocol Action: 'SCITT Reference APIs' to Proposed Standard (draft-ietf-scitt-scrapi-08.txt)

The IESG has approved the following document:
- 'SCITT Reference APIs'
  (draft-ietf-scitt-scrapi-08.txt) as Proposed Standard

This document is the product of the Supply Chain Integrity, Transparency, and
Trust Working Group.

The IESG contact persons are Christopher Inacio and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-scitt-scrapi/


Ballot Text

Technical Summary

   This document describes a REST API that supports the normative
   requirements of the SCITT Architecture.  Optional key discovery and
   query interfaces are provided to support interoperability with X.509
   Certificates, alternative methods commonly used to support public key
   discovery and Artifact Repositories.

Working Group Summary

  There was broad consensus within the working group, no controversy.  

Document Quality

The document contains HTTP requests, some of which include a CBOR EDN body.
They have been reviewed manually.  In addition there has been an early httpdir
review that has been very helpful.

There are no MIBs, MediaTypes, or Yang. 

Existing implementations of this specifications are:
Datatrails [0], Tradeverifyed [1], and Microsoft [2], all are Open Source.

[0] https://www.datatrails.ai
[1] https://tradeverifyd.com
[2] https://www.microsoft.com

Personnel

   The Document Shepherd for this document is Amaury Chamayou. The
   Responsible Area Director is Deb Cooley.

IANA Note

  (Insert IANA Note here or remove section)

RFC Editor Note