Found 1 record.

Status: Held for Document Update (1)

RFC 9803, "Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values", June 2025

Errata ID: 8718
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Yixin Sun
Date Reported: 2026-01-24
Held for Document Update by: Andy Newton
Date Held: 2026-01-26

Section 8 says:

  <element name="create" type="ttl:commandContainer">
    <unique name="uniqueRRTypeForCreate">
      <selector xpath="ttl:ttl"/>
      <field xpath="@for"/>
    </unique>
  </element>

  <element name="update" type="ttl:commandContainer">
    <unique name="uniqueRRTypeForUpdate">
      <selector xpath="ttl:ttl"/>
      <field xpath="@for"/>
    </unique>
  </element>

  <element name="infData" type="ttl:responseContainer">
    <unique name="uniqueRRTypeForInfo">
      <selector xpath="ttl:ttl"/>
      <field xpath="@for"/>
    </unique>
  </element>

It should say:

  <element name="create" type="ttl:commandContainer">
    <unique name="uniqueRRTypeForCreate">
      <selector xpath="ttl:ttl"/>
      <field xpath="@custom"/>
      <field xpath="@for"/>
    </unique>
  </element>

  <element name="update" type="ttl:commandContainer">
    <unique name="uniqueRRTypeForUpdate">
      <selector xpath="ttl:ttl"/>
      <field xpath="@custom"/>
      <field xpath="@for"/>
    </unique>
  </element>

  <element name="infData" type="ttl:responseContainer">
    <unique name="uniqueRRTypeForInfo">
      <selector xpath="ttl:ttl"/>
      <field xpath="@custom"/>
      <field xpath="@for"/>
    </unique>
  </element>

Notes:

There may exist multiple custom record types, e.g.,
<ttl:ttl for="custom" custom="NEWRRTYPE1">3600</ttl:ttl>
<ttl:ttl for="custom" custom="NEWRRTYPE2">3600</ttl:ttl>
Both "for" and "custom" attributes are needed to uniquely identify the record type. Therefore, the <unique> elements in the XML syntax should be updated as such.

Report New Errata