Hi Kaelin, This has been completed:
Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live (TTL) Values Standards Track [RFC-ietf-regext-epp-ttl-18] [IESG] Any None Active None Registry: https://www.iana.org/assignments/epp-extensions/ Thank you! Best regards, David Dong IANA Services Sr. Specialist On Wed Jun 04 18:49:38 2025, kfo...@staff.rfc-editor.org wrote: > Hi IANA, > > Please make the following capitalization changes in the "Extensions > for the Extensible Provisioning Protocol (EPP)" registry > <https://www.iana.org/assignments/epp-extensions/epp- > extensions.xhtml>: > > OLD: > > Extensible Provisioning Protocol (EPP) Mapping for DNS Time-To-Live > (TTL) values > > NEW (lowercase “t” and uppercase “V”): > > Extensible Provisioning Protocol (EPP) Mapping for DNS Time-to-Live > (TTL) Values > > Thanks, > RFC Editor/kf > > > On Jun 3, 2025, at 10:33 AM, Gavin Brown <gavin.br...@icann.org> > > wrote: > > > > FYI I got a bounce from Orie's old email address so I'm adding his > > new address on this message so he sees the thread! > > > > > On 3 Jun 2025, at 15:28, Gavin Brown <gavin.br...@icann.org> wrote: > > > > > > Greetings, > > > > > > Please find attached a revised XML file. > > > > > > * all your edits are fine, with the exception of the word "also" in > > > the descriptions of the attributes in 1.2.1, which imply that the > > > attributes have multiple uses when they don't. I have removed that > > > word in each paragraph. > > > > > > * I have added comments responding to RFC Editor questions. Where > > > changes have been suggested or requested, they have been made. > > > > > > * I also realised that putting normative text at the end of > > > sections, immediately below examples, was likely to cause confusion > > > to readers, so I have moved the final sentences in 2.2.1 and 2.2.2 > > > above the examples. > > > > > > You can see the changes I made here: > > > > > > https://github.com/gbxyz/epp-ttl- > > > extension/compare/a845acb2e34768d122f857633fd96e3f96af09a4..HEAD > > > > > > I am happy for this version to be published as an RFC. > > > > > > Many thanks! > > > > > > Gavin. > > > > > > > > >> On 3 Jun 2025, at 05:41, rfc-edi...@rfc-editor.org wrote: > > >> > > >> *****IMPORTANT***** > > >> > > >> Updated 2025/06/02 > > >> > > >> RFC Author(s): > > >> -------------- > > >> > > >> Instructions for Completing AUTH48 > > >> > > >> Your document has now entered AUTH48. Once it has been reviewed > > >> and > > >> approved by you and all coauthors, it will be published as an > > >> RFC. > > >> If an author is no longer available, there are several remedies > > >> available as listed in the FAQ > > >> (https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/faq/__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS1xXUhoAu$ [rfc-editor[.]org]). > > >> > > >> You and you coauthors are responsible for engaging other parties > > >> (e.g., Contributors or Working Group) as necessary before > > >> providing > > >> your approval. > > >> > > >> Planning your review > > >> --------------------- > > >> > > >> Please review the following aspects of your document: > > >> > > >> * RFC Editor questions > > >> > > >> Please review and resolve any questions raised by the RFC Editor > > >> that have been included in the XML file as comments marked as > > >> follows: > > >> > > >> <!-- [rfced] ... --> > > >> > > >> These questions will also be sent in a subsequent email. > > >> > > >> * Changes submitted by coauthors > > >> > > >> Please ensure that you review any changes submitted by your > > >> coauthors. We assume that if you do not speak up that you > > >> agree to changes submitted by your coauthors. > > >> > > >> * Content > > >> > > >> Please review the full content of the document, as this cannot > > >> change once the RFC is published. Please pay particular attention > > >> to: > > >> - IANA considerations updates (if applicable) > > >> - contact information > > >> - references > > >> > > >> * Copyright notices and legends > > >> > > >> Please review the copyright notice and legends as defined in > > >> RFC 5378 and the Trust Legal Provisions > > >> (TLP – > > >> https://urldefense.com/v3/__https://trustee.ietf.org/license- > > >> info__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS167Nt57H$ [trustee[.]ietf[.]org]). > > >> > > >> * Semantic markup > > >> > > >> Please review the markup in the XML file to ensure that elements > > >> of > > >> content are correctly tagged. For example, ensure that > > >> <sourcecode> > > >> and <artwork> are set correctly. See details at > > >> <https://urldefense.com/v3/__https://authors.ietf.org/rfcxml- > > >> vocabulary__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS18EvkUSZ$ [authors[.]ietf[.]org]>. > > >> > > >> * Formatted output > > >> > > >> Please review the PDF, HTML, and TXT files to ensure that the > > >> formatted output, as generated from the markup in the XML file, is > > >> reasonable. Please note that the TXT will have formatting > > >> limitations compared to the PDF and HTML. > > >> > > >> > > >> Submitting changes > > >> ------------------ > > >> > > >> To submit changes, please reply to this email using ‘REPLY ALL’ as > > >> all > > >> the parties CCed on this message need to see your changes. The > > >> parties > > >> include: > > >> > > >> * your coauthors > > >> > > >> * rfc-edi...@rfc-editor.org (the RPC team) > > >> > > >> * other document participants, depending on the stream (e.g., > > >> IETF Stream participants are your working group chairs, the > > >> responsible ADs, and the document shepherd). > > >> > > >> * auth48archive@rfc-editor.org, which is a new archival mailing > > >> list > > >> to preserve AUTH48 conversations; it is not an active > > >> discussion > > >> list: > > >> > > >> * More info: > > >> > > >> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf- > > >> announce/yb6lpIGh- > > >> 4Q9l2USxIAe6P8O4Zc__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS19EuSY-y$ [mailarchive[.]ietf[.]org] > > >> > > >> * The archive itself: > > >> > > >> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS11nkbZf-$ [mailarchive[.]ietf[.]org] > > >> > > >> * Note: If only absolutely necessary, you may temporarily opt out > > >> of the archiving of messages (e.g., to discuss a sensitive > > >> matter). > > >> If needed, please add a note at the top of the message that you > > >> have dropped the address. When the discussion is concluded, > > >> auth48archive@rfc-editor.org will be re-added to the CC list > > >> and > > >> its addition will be noted at the top of the message. > > >> > > >> You may submit your changes in one of two ways: > > >> > > >> An update to the provided XML file > > >> — OR — > > >> An explicit list of changes in this format > > >> > > >> Section # (or indicate Global) > > >> > > >> OLD: > > >> old text > > >> > > >> NEW: > > >> new text > > >> > > >> You do not need to reply with both an updated XML file and an > > >> explicit > > >> list of changes, as either form is sufficient. > > >> > > >> We will ask a stream manager to review and approve any changes > > >> that seem > > >> beyond editorial in nature, e.g., addition of new text, deletion > > >> of text, > > >> and technical changes. Information about stream managers can be > > >> found in > > >> the FAQ. Editorial changes do not require approval from a stream > > >> manager. > > >> > > >> > > >> 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. > > >> > > >> > > >> Files > > >> ----- > > >> > > >> The files are available here: > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803.xml__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS10sKHisN$ [rfc-editor[.]org] > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803.html__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS10jQZ4WO$ [rfc-editor[.]org] > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803.pdf__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS1wytz3bX$ [rfc-editor[.]org] > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803.txt__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS1y_3Ke4Y$ [rfc-editor[.]org] > > >> > > >> Diff file of the text: > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803- > > >> diff.html__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS18pIDBhE$ [rfc-editor[.]org] > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803- > > >> rfcdiff.html__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS1zjArqvN$ [rfc-editor[.]org] (side by side) > > >> > > >> Diff of the XML: > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/authors/rfc9803- > > >> xmldiff1.html__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS16Pm-3xA$ [rfc-editor[.]org] > > >> > > >> > > >> Tracking progress > > >> ----------------- > > >> > > >> The details of the AUTH48 status of your document are here: > > >> https://urldefense.com/v3/__https://www.rfc- > > >> editor.org/auth48/rfc9803__;!!PtGJab4!9MEGQ3QPMBwgCR73KmbtW_g38Xwp_1ZN0LpEjFZDib2GAyUV5G7aDkylrcnHloyigx_rx41anIL- > > >> En-sF9px6WpS103dM4vX$ [rfc-editor[.]org] > > >> > > >> Please let us know if you have any questions. > > >> > > >> Thank you for your cooperation, > > >> > > >> RFC Editor > > >> > > >> -------------------------------------- > > >> RFC9803 (draft-ietf-regext-epp-ttl-18) > > >> > > >> Title : Extensible Provisioning Protocol (EPP) Mapping > > >> for DNS Time-to-Live (TTL) Values > > >> Author(s) : G. Brown > > >> WG Chair(s) : James Galvin, Antoin Verschuren > > >> Area Director(s) : Andy Newton, Orie Steele > > > > > > -- > > > Gavin Brown > > > Principal Engineer, Global Domains & Strategy > > > Internet Corporation for Assigned Names and Numbers (ICANN) > > > > > > https://www.icann.org > > > > > > > -- > > Gavin Brown > > Principal Engineer, Global Domains & Strategy > > Internet Corporation for Assigned Names and Numbers (ICANN) > > > > https://www.icann.org > > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
