<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="trans.xsl"?>
<?xml-model href="trans.rng" schematypens="http://relaxng.org/ns/structure/1.0" ?>
<registry xmlns="http://www.iana.org/assignments" id="trans">
<category>Public Notary Transparency</category>
  <title>Public Notary Transparency</title>
  <created>2021-08-04</created>
  <updated>2021-12-14</updated>
  
  <registry id="trans-hash-algorithms">
    <title>Hash Algorithms</title>
    <xref type="rfc" data="rfc9162"/>
    <expert>Unassigned</expert>
    <range>
      <value>0x00-0xDF</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>0xE0-0xEF</value>
      <registration_rule>Experimental Use</registration_rule>
    </range>
    <range>
      <value>0xF0-0xFF</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <record date="2021-08-04">
      <value>0x00</value>
      <algorithm>SHA-256</algorithm>
      <oid>2.16.840.1.101.3.4.2.1</oid>
      <xref type="rfc" data="rfc6234"/>
    </record>
    <record>
      <value>0x01-0xDF</value>
      <algorithm>Unassigned</algorithm>
      <oid/>
    </record>
    <record date="2021-08-04">
      <value>0xE0-0xEF</value>
      <algorithm>Reserved for Experimental Use</algorithm>
      <oid/>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <value>0xF0-0xFF</value>
      <algorithm>Reserved for Private Use</algorithm>
      <oid/>
      <xref type="rfc" data="rfc9162"/>
    </record>
  </registry>
  
  <registry id="trans-signature-algorithms">
    <title>Signature Algorithms</title>
    <xref type="rfc" data="rfc9162"/>
    <expert>Unassigned</expert>
    <note>This is a subset of the "TLS SignatureScheme" registry, limited to
those algorithms that are appropriate for CT.  A major advantage
of this is leveraging the expertise of the TLS Working Group and
its designated expert(s).
    </note>
    <note>The value 0x0403 appears twice.  While this may be confusing, it
is okay because the verification process is the same for both
algorithms, and the choice of which to use when generating a
signature is purely internal to the log server.
    </note>
    <range>
      <value>0x0000-0x0807</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>0x0808-0xFDFF</value>
      <registration_rule>Expert Review</registration_rule>
    </range>
    <range>
      <value>0xFE00-0xFEFF</value>
      <registration_rule>Experimental Use</registration_rule>
    </range>
    <range>
      <value>0xFF00-0xFFFF</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <record>
      <signature>0x0000-0x0402</signature>
      <algorithm>Unassigned</algorithm>
    </record>
    <record date="2021-08-04">
      <signature>ecdsa_secp256r1_sha256 (0x0403)</signature>
      <algorithm>ECDSA (NIST P-256) with SHA-256</algorithm>
      <xref type="uri" data="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf">FIPS186-4</xref>
    </record>
    <record date="2021-08-04">
      <signature>ecdsa_secp256r1_sha256 (0x0403)</signature>
      <algorithm>Deterministic ECDSA (NIST P-256) with HMAC-SHA256</algorithm>
      <xref type="rfc" data="rfc6979"/>
    </record>
    <record date="2021-08-04">
      <signature>0x0404-0x0806</signature>
      <algorithm>Unassigned</algorithm>
    </record>
    <record date="2021-08-04">
      <signature>ed25519 (0x0807)</signature>
      <algorithm>Ed25519 (PureEdDSA with the edwards25519 curve)</algorithm>
      <xref type="rfc" data="rfc8032"/>
    </record>
    <record>
      <signature>0x0808-0xFDFF</signature>
      <algorithm>Unassigned</algorithm>
    </record>
    <record date="2021-08-04">
      <signature>0xFE00-0xFEFF</signature>
      <algorithm>Reserved for Experimental Use</algorithm>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <signature>0xFF00-0xFFFF</signature>
      <algorithm>Reserved for Private Use</algorithm>
      <xref type="rfc" data="rfc9162"/>
    </record>
  </registry>
  
  <registry id="trans-versionedtranstype">
    <title>VersionedTransTypes</title>
    <xref type="rfc" data="rfc9162"/>
    <expert>Unassigned</expert>
    <note>The range 0x0000-0x00FF is reserved so that v1 SCTs are
distinguishable from v2 SCTs and other TransItem structures.
    </note>
    <range>
      <value>0x0100-0xDFFF</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>0xE000-0xEFFF</value>
      <registration_rule>Experimental Use</registration_rule>
    </range>
    <range>
      <value>0xF000-0xFFFF</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0000-0x00FF</value>
      <version>Reserved</version>
      <xref type="rfc" data="rfc6962"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0100</value>
      <version>x509_entry_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0101</value>
      <version>precert_entry_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0102</value>
      <version>x509_sct_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0103</value>
      <version>precert_sct_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0104</value>
      <version>signed_tree_head_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0105</value>
      <version>consistency_proof_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04" updated="2021-09-01">
      <value>0x0106</value>
      <version>inclusion_proof_v2</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record>
      <value>0x0107-0xDFFF</value>
      <version>Unassigned</version>
    </record>
    <record date="2021-08-04">
      <value>0xE000-0xEFFF</value>
      <version>Reserved for Experimental Use</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <value>0xF000-0xFFFF</value>
      <version>Reserved for Private Use</version>
      <xref type="rfc" data="rfc9162"/>
    </record>
  </registry>

  <registry id="trans-log-artifact-extensions">
    <title>Log Artifact Extensions</title>
    <xref type="rfc" data="rfc9162"/>
    <expert>Unassigned</expert>
    <range>
      <value>0x0000-0xDFFF</value>
      <registration_rule>Specification Required</registration_rule>
    </range>
    <range>
      <value>0xE000-0xEFFF</value>
      <registration_rule>Experimental Use</registration_rule>
    </range>
    <range>
      <value>0xF000-0xFFFF</value>
      <registration_rule>Private Use</registration_rule>
    </range>
    <record>
      <value>0x0000-0xDFFF</value>
      <status>Unassigned</status>
      <use>n/a</use>
    </record>
    <record date="2021-08-04">
      <value>0xE000-0xEFFF</value>
      <status>Reserved for Experimental Use</status>
      <use>n/a</use>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <value>0xF000-0xFFFF</value>
      <status>Reserved for Private Use</status>
      <use>n/a</use>
      <xref type="rfc" data="rfc9162"/>
    </record>
  </registry>

  <registry id="trans-log-ids">
    <title>Log IDs</title>
    <xref type="rfc" data="rfc9162"/>
    <registration_rule>First Come First Served</registration_rule>
    <note>All OIDs in the range from 1.3.101.8192 to 1.3.101.16383 have been
set aside for Log IDs.  This is a limited resource of 8,192 OIDs,
each of which has an encoded length of 4 octets.
    </note>
    <note>The 1.3.101.80 arc has also been set aside for Log IDs.  This is an
unlimited resource, but only the 128 OIDs from 1.3.101.80.0 to
1.3.101.80.127 have an encoded length of only 4 octets.
    </note>

    <record date="2021-08-04">
      <id>1.3.101.8192-1.3.101.16383</id>
      <url>Unassigned</url>
      <operator>Unassigned</operator>
    </record>
    <record date="2021-08-04">
      <id>1.3.101.80.0-1.3.101.80.*</id>
      <url>Unassigned</url>
      <operator>Unassigned</operator>
    </record>
  </registry>
  
  <registry id="trans-error-types">
    <title>Error Types</title>
    <xref type="rfc" data="rfc9162"/>
    <expert>Unassigned</expert>
    <registration_rule>Specification Required</registration_rule>
    <record date="2021-08-04">
      <identifier>malformed</identifier>
      <meaning>The request could not be parsed.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>badSubmission</identifier>
      <meaning>submission is neither a valid certificate nor a valid precertificate.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>badType</identifier>
      <meaning>type is neither 1 nor 2.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>badChain</identifier>
      <meaning>The first element of chain is not the certifier of the submission, or the second 
        element does not certify the first, etc.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>badCertificate</identifier>
      <meaning>One or more certificates in the chain are not valid (e.g., not properly encoded).</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>unknownAnchor</identifier>
      <meaning>The last element of chain (or, if chain is an empty array, the submission)
        is not, and nor is it certified by, an accepted trust anchor.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>shutdown</identifier>
      <meaning>The log is no longer accepting submissions.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>firstUnknown</identifier>
      <meaning>first is before the latest known STH but is not from an existing STH.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>secondUnknown</identifier>
      <meaning>second is before the latest known STH but is not from an existing STH.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>secondBeforeFirst</identifier>
      <meaning>second is smaller than first.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>hashUnknown</identifier>
      <meaning>hash is not the hash of a known leaf (may be caused by skew or by a known certificate not yet merged).</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>treeSizeUnknown</identifier>
      <meaning>hash is before the latest known STH but is not from an existing STH.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>startUnknown</identifier>
      <meaning>start is greater than the number of entries in the Merkle Tree.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
    <record date="2021-08-04">
      <identifier>endBeforeStart</identifier>
      <meaning>start cannot be greater than end.</meaning>
      <xref type="rfc" data="rfc9162"/>
    </record>
  </registry>

  <people/>
</registry>
