Hi folks, Firstly, thanks to Yixin Sun, who initially reported this to me privately, for submitting this report.
IIRC it was never the intention to prevent multiple custom RRs. Therefore I believe the report is correct and should be accepted. Since it affects the XML schema, I believe "Held for Document Update" should be the correct status, since a change to the schema should also change the namespace URI. However, I would welcome WG input on this. Thanks, G. > On 24 Jan 2026, at 4:54 pm, RFC Errata System <[email protected]> > wrote: > > 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://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid8718__;!!PtGJab4!8Nh9IMY4NI5TvMXoD5q_TVrUFlf6YR8tSFGyLlXt_kboQoXLwXCg434h2tm0kiQjH_ALLyUg9NxepqmCdJJLivEhAnE29cn3$ > [rfc-editor[.]org] > > -------------------------------------- > 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 -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
