The following errata report has been submitted for RFC9803, "Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8718 -------------------------------------- Type: Technical Reported by: Yixin Sun <[email protected]> Section: 8 Original Text ------------- <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> Corrected Text -------------- <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. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC9803 (draft-ietf-regext-epp-ttl-18) -------------------------------------- Title : Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values Publication Date : June 2025 Author(s) : G. Brown Category : PROPOSED STANDARD Source : Registration Protocols Extensions Stream : IETF Verifying Party : IESG _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
