Hi Rich, Ack - thanks for your quick reply.
Please note that we have updated table 1 and IANA has updated the registry to reflect the following: 0xF000-0xFFFF Reserved for Private or Experimental Use Please review and let us know if you approve the RFC for publication. The files are available here: https://www.rfc-editor.org/authors/rfc9748.xml https://www.rfc-editor.org/authors/rfc9748.txt https://www.rfc-editor.org/authors/rfc9748.pdf https://www.rfc-editor.org/authors/rfc9748.html Diffs highlighting the this recent update only: https://www.rfc-editor.org/authors/rfc9748-lastdiff.html https://www.rfc-editor.org/authors/rfc9748-lastrfcdiff.html (side by side) AUTH48 diffs: https://www.rfc-editor.org/authors/rfc9748-auth48diff.html https://www.rfc-editor.org/authors/rfc9748-auth48rfcdiff.html (side by side) Comprehensive diffs: https://www.rfc-editor.org/authors/rfc9748-diff.html https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html (side by side) Thank you, RFC Editor/sg > On Feb 28, 2025, at 10:11 AM, Salz, Rich <rs...@akamai.com> wrote: > > I can confirm that separate ranges ARE NOT needed. > > From: Sandy Ginoza <sgin...@staff.rfc-editor.org> > Date: Friday, February 28, 2025 at 1:09 PM > To: Rich Salz <rs...@akamai.com> > Cc: RFC Editor <rfc-edi...@rfc-editor.org>, "ntp-...@ietf.org" > <ntp-...@ietf.org>, "ntp-cha...@ietf.org" <ntp-cha...@ietf.org>, > "dsibold.i...@gmail.com" <dsibold.i...@gmail.com>, Erik Kline > <ek.i...@gmail.com>, "auth48archive@rfc-editor.org" > <auth48archive@rfc-editor.org>, "i...@iana.org" <i...@iana.org> > Subject: Re: AUTH48: RFC-to-be 9748 <draft-ietf-ntp-update-registries-16> for > your review > > Hi Rich, We asked IANA for their input on how this should be handled. Because > Sections 4. 1 and 4. 2 of RFC 8126 differentiate between Private and > Experimental Use, they would like confirmation that separate ranges for > Private and Experimental > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside your organization. > ZjQcmQRYFpfptBannerEnd > Hi Rich, > > We asked IANA for their input on how this should be handled. Because > Sections 4.1 and 4.2 of RFC 8126 differentiate between Private and > Experimental Use, they would like confirmation that separate ranges for > Private and Experimental Use are not needed. > > Thanks! > RFC Editor/sg > > > > > > >> On Feb 22, 2025, at 1:45 PM, Salz, Rich <rs...@akamai.com> wrote: >> >> >>> B) Section 3 >> >> Your changes are fine. >> >> >>> B.2) The bullets refer to "Private or Experimental Use”. We assume this >>> refers to "experimentation and development” mentioned in the notes for the >>> ref ID codes and kiss codes registries. However, the extension field types >>> registry doesn’t mention “Private Use” - should it? >> >> https://www.youtube.com/watch?v=r51XmKajDX4 :) >> >> Change either one as long as they are consistent. >> >> On 2/21/25, 5:01 PM, "Sandy Ginoza" <sgin...@staff.rfc-editor.org >> <mailto:sgin...@staff.rfc-editor.org>> wrote: >> >> >> !-------------------------------------------------------------------| >> This Message Is From an External Sender >> This message came from outside your organization. >> |-------------------------------------------------------------------! >> >> >> Hi Rich, >> >> >> Thank you for your quick reply! We have update the document per your replies >> below, and we have a few followup questions below. >> >> >> The current files are available here: >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.xml__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0P9UtXXsA$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.xml__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0P9UtXXsA$> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.txt__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0MLJ6vLmw$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.txt__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0MLJ6vLmw$> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.pdf__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0O_r6497A$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.pdf__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0O_r6497A$> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0M43DgWWg$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0M43DgWWg$> >> >> >> >> AUTH48 diffs: >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-auth48diff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0P08lO6pw$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-auth48diff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0P08lO6pw$> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-auth48rfcdiff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0MNFBIZ5g$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-auth48rfcdiff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0MNFBIZ5g$> >> (side by side) >> >> >> Comprehensive diffs: >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-diff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0P2J7qlyg$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-diff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0P2J7qlyg$> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0OqVCjHEg$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0OqVCjHEg$> >> (side by side) >> >> >> >> >> A) We updated the text as follows. Please let us know if any updates are >> desired. >> >> >> >>> **RSALZ: Sure, use a real value like you suggested. I thought it would be >>> more clear to but if it's confusing, please make your change. >> >> >> >> >> Original: >> * Many of the entries in the Extension Field Types registry have >> swapped some of the nibbles; 0x1234 is listed as 0x1432 for >> example. >> >> >> Current: >> * Many of the entries in the "NTP Extension Field Types" registry >> have swapped some of the nibbles; for example, 0x0302 was listed >> for Cookie Message Request instead of 0x0203. >> >> >> >> >> B) Section 3 >> >> >> B.1) The first and second bullet are related. We would like to update the >> text to refer to the specific registry names. In addition, we propose a >> slight update to the format of section 3. >> Please see the proposed updates in this test file and let us know if they >> are acceptable. >> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-test2.html >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-test2.html>*section-3__;Iw!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0NmFzyW2A$ >> >> >> >> >> >> B.2) The bullets refer to "Private or Experimental Use”. We assume this >> refers to "experimentation and development” mentioned in the notes for the >> ref ID codes and kiss codes registries. However, the extension field types >> registry doesn’t mention “Private Use” - should it? >> >> >> https://urldefense.com/v3/__https://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml >> >> <https://urldefense.com/v3/__https://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml>*ntp-parameters-3__;Iw!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0OohrWl7A$ >> >> 0xF000-0xFFFF Reserved for Experimental Use >> >> >> Diffs comparing the current RFC text with the proposed text are available >> here: >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-test2-diff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0PL5zADVg$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-test2-diff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0PL5zADVg$> >> >> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-test2-rfcdiff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0PZZKy_mQ$ >> >> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-test2-rfcdiff.html__;!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0PZZKy_mQ$> >> (side by side) >> >> >> >> >> Please review and let us know if we may make any of the changes noted above. >> >> >> Thank you! >> RFC Editor/sg >> >> >> >> >> >> >> >> >> >>> On Feb 21, 2025, at 10:28 AM, Salz, Rich <rsalz=40akamai....@dmarc.ietf.org >>> <mailto:40akamai....@dmarc.ietf.org>> wrote: >>> >>> **RSALZ: Comments from me indicated like this. >>> >>> **RSALZ: Summary: all your suggested changes are fine. >>> >>> 1) <!-- [rfced] May we update this text for clarity? Note that it appears >>> in the Abstract and the Introduction. >>> >>> >>> Original: >>> Some registries have wrong values, some registries do not follow >>> current common practice, and some are just right. For the sake of >>> completeness, this document reviews all NTP and NTS registries, and >>> makes updates where necessary. >>> >>> >>> Perhaps: >>> Some registries are correct, but some include incorrect assignments >>> and some don’t follow common practice. For the sake of completeness, >>> this document reviews all NTP and NTS registries, and corrects the >>> registries where necessary. >>> --> >>> >>> **RSALZ: Yes, this is fine. >>> >>> >>> >>> 2) <!-- [rfced] To better align with the text in section 2 and for clarity, >>> may we update the text as follows? >>> >>> >>> Original: >>> The bulk of this document can be divided into two parts: >>> >>> >>> * First, each registry, its defining document, and a summary of its >>> syntax is defined. >>> >>> >>> * Second, the revised format and entries for each registry that is >>> being modified is specified. >>> >>> >>> >>> >>> Perhaps: >>> The bulk of this document can be divided into two parts: >>> >>> >>> * a summary of the relevant registries, including syntax requirements, >>> registration procedures, and the defining documents. >>> >>> >>> * a revised format and entries for each registry >>> being modified. >>> --> >>> >>> **RSALZ: Yes, this is fine. >>> >>> >>> >>> 3) <!-- [rfced] As we believe "these" refers to the code points (not the >>> registries), may we update the text as described below? Also, are the >>> codes 4 ASCII characters or are they allowed to be up to 4 ASCII >>> characters? >>> >>> >>> Original: >>> Both of these are allowed to >>> be four ASCII characters; padded on the right with all-bits-zero if >>> necessary. >>> >>> >>> Perhaps: >>> Reference identifiers and kiss codes can be up to four ASCII characters, >>> padded on the right with all-bits-zero if necessary. >>> --> >>> >>> **RSALZ: You are right, up to four. So a KISS CODE of BYE would be 42 59 45 >>> 0x00 >>> >>> >>> >>> >>> 4) <!-- [rfced] Because the registries were created (i.e., it's no longer a >>> request), we updated the text as follows. Please let us know if >>> corrections are needed. >>> >>> >>> Original: >>> The formal request to define the registries >>> is in [RFC5905], Section 16. >>> >>> >>> Perhaps: >>> The registries were created per >>> Section 16 of [RFC5905]. >>> --> >>> >>> **RSALZ: This is fine. >>> >>> 5) <!-- [rfced] Is this a real example of something that was registered >>> incorrectly? >>> https://urldefense.com/v3/__https://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml<https://urldefense.com/v3/__https://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml>*ntp-parameters-3__;Iw!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0OohrWl7A$ >>> >>> >>> __;Iw!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBoc1YOIi$ >>> > or >>> <https://urldefense.com/v3/__http://web.archive.org/web/20230927142951/https:/ >>> >>> <https://urldefense.com/v3/__http://web.archive.org/web/20230927142951/https:/> >>> >>> <https://urldefense.com/v3/__http://web.archive.org/web/20230927142951/https:/> >>> >>> <https://urldefense.com/v3/__http://web.archive.org/web/20230927142951/https:/>>*https://urldefense.com/v3/__http://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml >>> >>> <https://urldefense.com/v3/__http://www.iana.org/assignments/ntp-parameters/ntp-parameters.xhtml>*ntp-parameters-3__;LyM!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBoWoq2hA$__;Kg!!GjvTz_vk!TYJzc65Eh4bQpv8UN07sbIeVR-MC4-MtSM8A39G0aVjFvpWY8CGxH9akn4twc6ydeO2kQ6ElxK5PV0Nr9I9bOA$ >>> >. Would >>> it be helpful to use a real example (e.g., 0x0203 vs 0x0302 (Cookie Message >>> Request))? >>> >>> >>> Original: >>> * Many of the entries in the Extension Field Types registry have >>> swapped some of the nibbles; 0x1234 is listed as 0x1432 for >>> example. >>> --> >>> >>> **RSALZ: Sure, use a real value like you suggested. I thought it would be >>> more clear to but if it's confusing, please make your change. (And I >>> apologize for the URL mangling my employer's email does) >>> >>> >>> >>> 6) <!-- [rfced] Section 3: Because this document seems to only update the >>> NTP registries, may we update the text as follows? >>> >>> >>> Original: >>> The following general guidelines apply to all registries updated here: >>> >>> >>> Perhaps: >>> The following general guidelines apply to the NTP registries: >>> --> >>> >>> ** RSALZ: Yes >>> >>> >>> 7) <!-- [rfced] Section 3: This text seems misplaced. Perhaps this is >>> intended to appear in Section 4? >>> >>> >>> Original: >>> Each entry described in the sub-sections below is intended to >>> completely replace the existing entry with the same name. >>> --> >>> >>> **RSALZ: Yes, this should be moved to be the only text in Section 4 >>> >>> 8) <!-- [rfced] Note that we have added "and this document has been added >>> as a reference" to the text in the IANA Considerations section. Please let >>> us know if any corrections are needed. >>> >>> >>> For example: >>> Original: >>> The registration procedure is changed to Specification Required. >>> >>> >>> Current: >>> The registration procedure has been changed to Specification Required >>> and this document has been added as a reference. >>> --> >>> >>> **RSALZ: Yes >>> >>> >>> 9) <!-- [rfced] We have updated the text as follows to note that this >>> document has been added as a reference to the NTP Extension Field Types >>> registry. Please let us know if any updates are needed. >>> >>> >>> Original: >>> The registration procedure is changed to Specification Required. >>> >>> >>> The reference [RFC5906] should be added, if possible. >>> >>> >>> Current: >>> The registration procedure has been changed to Specification Required >>> and [RFC5906] and this document have been added as references. >>> --> >>> >>> **RSALZ: Yes >>> >>> >>> 10) <!-- [rfced] To what does "the appropriate table" refer? Is it the >>> Reference column in table 1, or the tables as they appear in the IANA >>> registry? >>> >>> >>> Original: >>> This document adds no new security considerations, as they are >>> defined in the document that defines the extension. See the >>> References column of the appropriate table. >>> --> >>> >>> **RSALZ: change "table" to "IANA registry" >>> >>> >>> >>> 11) <!-- [rfced] Please review the "Inclusive Language" portion of the >>> online Style Guide >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/styleguide/part2/ >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/styleguide/part2/> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/styleguide/part2/> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/styleguide/part2/>>*inclusive_language__;Iw!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBil908-y$ >>> > >>> 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. >>> --> >>> >>> >>> **RSALZ: Done, all good. >>> >>> >>> Thank you. >>> >>> >>> RFC Editor >>> >>> >>> On Feb 20, 2025, at 4:57 PM, rfc-edi...@rfc-editor.org >>> <mailto:rfc-edi...@rfc-editor.org> >>> <mailto:rfc-edi...@rfc-editor.org<mailto:rfc-edi...@rfc-editor.org>> wrote: >>> >>> >>> *****IMPORTANT***** >>> >>> >>> Updated 2025/02/20 >>> >>> >>> 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/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBh1YdBIa$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBh1YdBIa$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBh1YdBIa$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBh1YdBIa$>> >>> ). >>> >>> >>> 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__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBpWpNMtS$ >>> >>> <https://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBpWpNMtS$> >>> >>> <https://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBpWpNMtS$ >>> >>> <https://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBpWpNMtS$>> >>> ). >>> >>> >>> * 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__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBlZ5aoXM$ >>> >>> <https://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBlZ5aoXM$> >>> >>> <https://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBlZ5aoXM$ >>> >>> <https://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBlZ5aoXM$>> >>> >. >>> >>> >>> * 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 <mailto:rfc-edi...@rfc-editor.org> >>> <mailto:rfc-edi...@rfc-editor.org <mailto: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 <mailto:auth48archive@rfc-editor.org> >>> <mailto:auth48archive@rfc-editor.org >>> <mailto: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__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBr0VWIY4$ >>> >>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBr0VWIY4$> >>> >>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBr0VWIY4$ >>> >>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBr0VWIY4$>> >>> >>> >>> >>> * The archive itself: >>> https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBuvLY-n0$ >>> >>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBuvLY-n0$> >>> >>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBuvLY-n0$ >>> >>> <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBuvLY-n0$>> >>> >>> >>> >>> * 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 <mailto:auth48archive@rfc-editor.org> >>> <mailto:auth48archive@rfc-editor.org <mailto: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/rfc9748.xml__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBgdbKoMa$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.xml__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBgdbKoMa$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.xml__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBgdbKoMa$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.xml__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBgdbKoMa$>> >>> >>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBoiQrBRh$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBoiQrBRh$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBoiQrBRh$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBoiQrBRh$>> >>> >>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.pdf__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnYlkRLC$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.pdf__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnYlkRLC$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.pdf__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnYlkRLC$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.pdf__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnYlkRLC$>> >>> >>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.txt__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmi5jUtG$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.txt__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmi5jUtG$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.txt__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmi5jUtG$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748.txt__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmi5jUtG$>> >>> >>> >>> >>> Diff file of the text: >>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-diff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmzs57d6$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-diff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmzs57d6$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-diff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmzs57d6$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-diff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBmzs57d6$>> >>> >>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBn1y1nWN$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBn1y1nWN$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBn1y1nWN$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-rfcdiff.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBn1y1nWN$>> >>> (side by side) >>> >>> >>> Diff of the XML: >>> https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-xmldiff1.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBj3rwPoZ$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-xmldiff1.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBj3rwPoZ$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-xmldiff1.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBj3rwPoZ$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9748-xmldiff1.html__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBj3rwPoZ$>> >>> >>> >>> >>> >>> >>> Tracking progress >>> ----------------- >>> >>> >>> The details of the AUTH48 status of your document are here: >>> https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9748__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnsii2HV$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9748__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnsii2HV$> >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9748__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnsii2HV$ >>> >>> <https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9748__;!!GjvTz_vk!Ws0Wu4NcHIWNWxUSfybWn5_5t2DW39aRXnZ_kp1z4RyVyxwLmV6rF6OtfowtizKBk5I95RN7rTiZBnsii2HV$>> >>> >>> >>> >>> Please let us know if you have any questions. >>> >>> >>> Thank you for your cooperation, >>> >>> >>> RFC Editor >>> >>> >>> -------------------------------------- >>> RFC9748 (draft-ietf-ntp-update-registries-16) >>> >>> >>> Title : Updating the NTP Registries >>> Author(s) : R. Salz >>> WG Chair(s) : Dieter Sibold, Karen O'Donoghue >>> >>> >>> Area Director(s) : Erik Kline, Éric Vyncke >>> -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
