Hi Marco, Thank you for your prompt reply and approval. We have marked your approval here: https://queue.rfc-editor.org/final-review/rfc10023.
We have made your requested updates and posted the updated files below. We have now received all necessary approvals and will move this document forward in the publication process at this time. — FILES (please refresh): — The updated files have been posted here: https://www.rfc-editor.org/authors/rfc10023.txt https://www.rfc-editor.org/authors/rfc10023.pdf https://www.rfc-editor.org/authors/rfc10023.html https://www.rfc-editor.org/authors/rfc10023.xml Diff files showing all changes: https://www.rfc-editor.org/authors/rfc10023-diff.html https://www.rfc-editor.org/authors/rfc10023-rfcdiff.html (side by side) Diff files showing changes made during Final Review: https://www.rfc-editor.org/authors/rfc10023-auth48diff.html https://www.rfc-editor.org/authors/rfc10023-auth48rfcdiff.html (side by side) Thank you for your time and attention during Final Review. All the best, Kaelin Foody RFC Production Center > On Jul 22, 2026, at 5:35 AM, Marco Davids > <[email protected]> wrote: > > RFC-editor, > > Thank you for your review. > > Below, please find my response inline. > > -------- Original Message -------- > *Subject: *Final Review: RFC-to-be 10023 (draft-davids-forsalereg) in XML > *From: *[email protected] > *To: *[email protected] > *Cc: *[email protected], [email protected], > [email protected] > *Date: *Tue, 21 Jul 2026 23:30:45 -0000 > >> 1) <!-- [rfced] Please insert any keywords (beyond those that appear in >> the title) for use on https://www.rfc-editor.org/search. --> > > I propose the following additional keywords: > > domain name system > domain sale > domain brokerage > domain aftermarket > TXT record > attrleaf > >> 2) <!-- [rfced] We note that the following five instances introduce each >> appendix, but they are incomplete sentences. How may we make each of >> these complete sentences? >> A.1. Example 1: Code Format >> A proprietary format, defined and used by agreement between parties - >> for example, a domain name registry and its registrars - without a >> clearly specified meaning for third parties. > > Proposed new text: > > The following example illustrates a proprietary format defined and used by > agreement between parties (for example, a domain name registry and its > registrars), without a clearly specified meaning for third parties. > >> A.2. Example 2: Free Text Format >> Free format text, with some additional unstructured information, >> aimed at being human-readable: > > Proposed new text: > > The following example shows a free text format with additional unstructured > information intended to be human-readable: > >> A.3. Example 3: URI Format >> The holder of "example.com" wishes to signal that the domain is for >> sale and adds this record to the "example.com" zone: > > Proposed new text: > > The following example shows the TXT record that the holder of "example.com" > adds to the zone to signal that the domain is for sale: > >> A.4. Example 4: Asking Price Format >> Consists of an uppercase currency code (e.g., USD, EUR), followed by >> a numeric amount. > > Proposed new text: > > The following examples illustrate the asking price format, which consists of > an uppercase currency code (e.g., USD or EUR) followed by a numeric amount. > >> A.5. Example 5: Combinations >> An example of multiple valid TXT records from which a processor can >> choose: > > Proposed new text: > > The following example shows multiple valid TXT records from which a processor > can choose: > >> 3) <!-- [rfced] Please review each artwork element in the xml file. >> Specifically, >> should any artwork element be tagged as sourcecode or another element? > > No changes required. > >> 4) <!-- [rfced] Please review whether any of the notes in this document >> should be in the <aside> element. It is defined as "a container for >> content that is semantically less important or tangential to the >> content that surrounds it" >> (https://authors.ietf.org/en/rfcxml-vocabulary#aside). > > No changes required. > >> 5) <!-- [rfced] FYI - We have added expansions for abbreviations upon first >> use >> per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review each >> expansion in the document carefully to ensure correctness. >> Top-Level Domain (TLD) >> cross-site scripting (XSS) > > Thank you - looking good. > >> 6) <!-- [rfced] FYI: We updated the authoring organization for this >> reference to match the information provided at the URL: >> Original: >> [ISO4217] SIX Group, "ISO 4217 Currency Codes", >> <https://www.iso.org/iso-4217-currency-codes.html>. >> Current: >> [ISO4217] ISO, "ISO 4217 Currency Codes", >> <https://www.iso.org/iso-4217-currency-codes.html>. > > Thank you. Approved. > >> 7) <!-- [rfced] Please review the "Inclusive Language" portion of the online >> Style Guide <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> >> and let us know if any changes are needed. Updates of this nature typically >> result in more precise language, which is helpful for readers. >> Note that our script did not flag any words in particular, but this should >> still be reviewed as a best practice. > > Reviewed and looking good to me. > >> Approving for publication >> -------------------------- >> To approve your RFC for publication, please reply to this email stating >> that you approve this RFC for publication. Please use 'REPLY ALL', >> as all the parties CCed on this message need to see your approval. > > With the proposed changes incorporated, I approve this RFC for publication. > > With kind regards, > > -- > Marco Davids > Research Engineer > > SIDN | Meander 501 | 6825 MD | Postbus 5022 | 6802 EA | ARNHEM > T +31 (0)26 352 55 00 | www.sidnlabs.nl | X/Twitter: @marcodavids > https://ipv6.camp/@marcodavids | Matrix: @marco:sidnlabs.nl > Nostr: 11ed01ff277d94705c2931867b8d900d8bacce6f27aaf7440ce98bb50e02fb34 > > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
