Hi Authors, Ari - Thank you for your reply! We have updated the document as requested and noted your approval on the AUTH48 status page (see https://www.rfc-editor.org/auth48/rfc9880).
Authors - Please note that some questions (6, 8, 11, 14, 17, 19, 20, 21, 22, and 23) still await author response. These questions (as well as RFC EDITOR followup questions/responses) can be viewed in the main AUTH48 thread from mail sent on 27 October. The updated files have been posted here (please refresh): https://www.rfc-editor.org/authors/rfc9880.txt https://www.rfc-editor.org/authors/rfc9880.pdf https://www.rfc-editor.org/authors/rfc9880.html https://www.rfc-editor.org/authors/rfc9880.xml Diff files: https://www.rfc-editor.org/authors/rfc9880-diff.html https://www.rfc-editor.org/authors/rfc9880-rfcdiff.html (side by side) https://www.rfc-editor.org/authors/rfc9880-auth48diff.html https://www.rfc-editor.org/authors/rfc9880-auth48rfcdiff.html (side by side) For the AUTH48 status page, please see: https://www.rfc-editor.org/auth48/rfc9880. Thank you! Madison Church RFC Production Center > On Nov 21, 2025, at 1:55 AM, Ari Keränen <[email protected]> wrote: > > Hi Madison et al, > > I reviewed the latest draft and noticed that in the regular expression of > names (sec 2.3.3), there is now incorrectly twice “_” in the beginning of the > regular expression for names. Here are suggested fixes: > > OLD: > A nonqualified Quality Name is composed of ASCII letters, digits, and > $ signs, starting with a lower case letter or a $ sign (i.e., using a > pattern of "_[a-z$][A-Za-z$0-9]*"). > > NEW: > A nonqualified Quality Name is composed of ASCII letters, digits, and > $ signs, starting with a lower case letter or a $ sign (i.e., using a > pattern of "[a-z$][A-Za-z$0-9]*"). > > OLD: > They are composed of lower case ASCII letters and > digits, starting with a lowercase ASCII letter (i.e., using a pattern > of "_[a-z][a-z0-9]*"). > > NEW: > They are composed of lower case ASCII letters and > digits, starting with a lowercase ASCII letter (i.e., using a pattern > of "[a-z][a-z0-9]*"). > > > Also, Carsten and I discussed yesterday that the abstract could be make more > readable with following editorial change: > > OLD: > The Semantic Definition Format (SDF) is concerned with Things, namely > physical objects that are available for interaction over a network. SDF is a > format for domain experts to use in the creation and maintenance of data and > interaction models that describe Things. > > NEW: > The Semantic Definition Format (SDF) is a format for domain experts to > use in the creation and maintenance of data and interaction models that > describe Things, i.e., physical objects that are available for interaction > over a network. > > > Otherwise, the latest text and all the changes discussed below look good to > me. > > > Thanks, > Ari > > From: Madison Church <[email protected]> > Date: Wednesday, 12. November 2025 at 17.54 > To: Carsten Bormann <[email protected]>, Michael Koster > <[email protected]>, Ari Keränen <[email protected]> > Cc: [email protected] <[email protected]>, RFC Editor <[email protected]>, > [email protected] <[email protected]>, [email protected] > <[email protected]>, Michael Richardson <[email protected]>, Francesca > Palombini <[email protected]>, [email protected] > <[email protected]> > Subject: Re: [auth48] AUTH48: RFC-to-be 9880 <draft-ietf-asdf-sdf-24> for > your review > > Hi Authors, > > This is another friendly weekly reminder that we await answers to the > followup questions/comments in this thread for RFC-to-be 9880 (originally > sent on 27 October). > > Thank you! > > Madison Church > RFC Production Center > > > On Nov 3, 2025, at 9:09 AM, Madison Church <[email protected]> > > wrote: > > > > Hi Authors, > > > > This is a friendly reminder that we await answers to the followup > > questions/comments below for RFC-to-be 9880. > > > > Thank you, and happy IETF week! > > > > Madison Church > > RFC Production Center > > > >> On Oct 27, 2025, at 2:24 PM, Madison Church <[email protected]> > >> wrote: > >> > >> Hi Carsten, > >> > >> Note that we have added IANA to this thread. > >> > >> After further discussion with IANA regarding questions 11 and 14, we have > >> removed the relative links because they are not permanent. We have > >> reverted the text, so the registry titles appear in quotes (i.e., “SenML > >> Units” and “Secondary Units”) as shown in the updated files. Please let us > >> know if there are any additional textual updates needed. > >> > >> Updated files: > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.txt&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745059003%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Sh7Z7ZOA%2F3BW7t%2F4TT2CEKNmZfikujzqdjMvurHDnZ8%3D&reserved=0 > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.pdf&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745109187%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=HxOKrpjgI2qrVAw9S18Mj%2FlrQO1y6pNX7WzA4WYqUwo%3D&reserved=0 > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745152613%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KQgKf4etWb39c3RBpIexoOLok3yPaQ6%2FLNf3mUNxwqo%3D&reserved=0 > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.xml&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745189319%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=9ql7zAS4eOOEw1IHe1zg6PF35AGZXrptdq%2F34gSOtlU%3D&reserved=0 > >> > >> Updated diff files: > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-diff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745219807%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2BnSaTF6yMo6BXEe6EblM3Iy89cPLJaIpTIAPks2osC8%3D&reserved=0 > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-rfcdiff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745246746%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=hnIUIMm%2BcKOCkOnisOZ9djZqWJTxayUDdfN8l9%2FpfsI%3D&reserved=0 > >> (side by side) > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-auth48diff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745268449%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PUNCAIpIGUVVzU0xDb7x0IOPOb4O8O7WTG2Ni7tyNnI%3D&reserved=0 > >> > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-auth48rfcdiff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745291911%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=23FwOC5M3GTAHtxBCGg7a0LXbbGCPGDxH%2BB3ib8sNVk%3D&reserved=0 > >> (side by side) > >> > >> AUTH48 status page: > >> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9880&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745315369%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=dHE8gk61EI3jGiq4ROf2i6NaGWMLHhatR3oH6dIAD84%3D&reserved=0 > >> > >> Thank you, > >> Madison Church > >> RFC Production Center > >> > >>> On Oct 27, 2025, at 6:42 AM, Madison Church > >>> <[email protected]> wrote: > >>> > >>> Hi Carsten, > >>> > >>> Thank you for your reply, and apologies for the delayed response! We have > >>> updated the document accordingly. Please see below for followup > >>> questions/comments. Note that we have left outstanding items in this > >>> thread for convenience (and removed questions that have been resolved). > >>> > >>>> On Oct 10, 2025, at 3:02 PM, Carsten Bormann <[email protected]> wrote: > >>>> > >>>> RFC-editor, > >>>> > >>>> thank you for preparing this RFC-to-be. > >>>> > >>>> We’ll first reply to the more specific ones of your questions below. > >>>> We will respond to more general questions (that require us to scan the > >>>> document) in the next round (marked here with TO CHECK in questions 6, > >>>> 20, 21, 22, 23). > >>>> > >>>> Please note that we are also preparing a -25, with two typo/C&P fixes > >>>> and one more technical omission fixed (PR #187 to #189 in > >>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fietf-wg-asdf%2FSDF%2Fpulls&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745337705%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=UKYwQrwoUpL7U6noHm5TUgrsoNiJuMEniSd7jovGClw%3D&reserved=0). > >>>> We previously prepared a -24 with PR #186 in it (technical omissions), > >>>> which you already picked up. > >>>> You probably need AD approval for all these. > >>> > >>> 1) Thank you for letting us know! We incorporated these edits into the > >>> document and also sent a reminder (on October 23) for the AD(s) to review > >>> these updates. These updates may be best viewed side-by-side in this diff > >>> file: > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-auth48rfcdiff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745359865%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=4FuGVullsI2IWKlNYoe1pSYbq7BTh4talf6T2DEhhOY%3D&reserved=0. > >>> Please review the files carefully and let us know if they appear as > >>> desired. > >>> > >>>> Grüße, Carsten > >>>> > >>>> > >>>> On 2025-10-07, at 07:03, [email protected] wrote: > >>>>> > >>>>> Authors, > >>>>> > >>>>> While reviewing this document during AUTH48, please resolve (as > >>>>> necessary) > >>>>> the following questions, which are also in the source file. > >>>>> 5) <!-- [rfced] Figure 2: The SVG includes additional information that > >>>>> is > >>>>> not present in the text. Is this as expected? For example, we see 0+, > >>>>> 1, > >>>>> and (c) in the SVG but not in the text artwork. In addition, sdfEvent > >>>>> and > >>>>> sdfAction appear in a different order. Please review. > >>>>> --> > >>>> > >>>> We originally had completely given up on providing a plaintext form of > >>>> the illustration. > >>>> The plaintext illustration that now is in there is somewhat rudimentary. > >>>> As you notice, it doesn’t have the occurrence labels (0+, 1), and it > >>>> doesn’t mark the boxes as compositions which looks almost like a © > >>>> symbol in the generated SVG. > >>>> > >>>> We do warn that this is a limited rendition, so we think we are good. > >>> > >>> 2) Thank you for the explanation! We also note that pointing to the HTML > >>> in the text (and removing the ASCII art) is also an option to avoid > >>> mismatching figures; see > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthors.ietf.org%2Fen%2Fdiagrams&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745383345%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=1FJOoyOilW%2Bx%2BROGYWAaxFLWCb3Lhi5bt4YZZ%2Bj%2BsNQ%3D&reserved=0. > >>> Let us know if you prefer to keep the text/figure as is, or if you would > >>> like to update the document. For example, Figure 1 in RFC 9633 > >>> (https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc9633.txt&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745407434%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=zyZ%2BHWjn8DhlsNmbZPHYbOPcA%2BWmQ6UvaHwjQ98HGcg%3D&reserved=0) > >>> shows how this would appear in the text output. > >>> > >>>>> 6) <!-- [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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthors.ietf.org%2Fen%2Frfcxml-vocabulary%23aside&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745433644%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=nla5ZZiycjR%2FmcbzrKFngG5jvOQ6zmpWTLpBgQNyl0w%3D&reserved=0). > >>>>> --> > >>>> > >>>> [TO CHECK] > >>>> > >>>>> 8) <!-- [rfced] May we rephrase the text below as follows to improve > >>>>> readability and specify "it" in the second sentence? > >>>>> > >>>>> Original: > >>>>> The keyword (map key) that defines an information block is "info". > >>>>> Its value is a JSON map in turn, with a set of entries that represent > >>>>> qualities that apply to the included definition. > >>>>> > >>>>> Perhaps: > >>>>> The keyword (map key) that defines an information block as "info". > >>>> > >>>> This should stay “is” — not a sentence otherwise. > >>>> (This is a statement about the keyword, giving its name as “info”.) > >>>> > >>>>> In turn, the keyword's value is a JSON map with a set of entries that > >>>>> represent > >>>>> qualities that apply to the included definition. > >>>>> --> > >>>> > >>>> We could also make use of the word “nested”: > >>>> > >>>>> The keyword's value is nested a JSON map with a set of entries that > >>>>> represent > >>>>> qualities that apply to the included definition. > >>>> > >>>> In any case, we need to change > >>>> OLD: > >>>> included definition > >>>> NEW: > >>>> included definitions > >>>> > >>>> … to mirror the first paragraph of 3.1. > >>> > >>> 3) Thank you for your proposal! We agree with the suggested text and > >>> updated the sentence with a minor correction to the placement of "nested > >>> a". The sentence now reads as: "The keyword’s value is a nested JSON > >>> map…". Please let us know if this is correct. > >>> > >>>>> 11) <!-- [rfced] FYI - In the XML, we have removed the links from "SenML > >>>>> Units" and "Secondary Units" since those links do not point to the > >>>>> correct > >>>>> section (and the correct section pointers follow shortly > >>>>> thereafter). Please let us know any objections. > >>>> > >>>> I’m not happy with not having those fragment identifiers as links. > >>>> I understand that IANA wants to keep the ability to change their format, > >>>> but that has been outstanding for a long time now. > >>>> The worst that can happen is that the fragment identifier part of the > >>>> link does not work and the link points to the file as a whole. > >>>> > >>>>> Original XML: > >>>>> <t>The unit name <bcp14>SHOULD</bcp14> be as > >>>>> > >>>>> per the <xref section="SenML Units" relative="#senml-units" > >>>>> sectionFormat="bare" > >>>>> target="RFC8428"/> registry > >>>>> > >>>>> or the <xref section="Secondary Units" relative="#secondary-units" > >>>>> sectionFormat="bare" > >>>>> target="RFC8798"/> registry in <xref target="IANA.senml"/> > >>>>> > >>>>> as specified by > >>>>> > >>>>> Sections <xref target="RFC8428" section="4.5.1" sectionFormat="bare"/> > >>>>> and <xref > >>>>> target="RFC8428" section="12.1" sectionFormat="bare"/> of <xref > >>>>> target="RFC8428"/> and > >>>>> <xref section="3" sectionFormat="of" target="RFC8798"/>, respectively. > >>>>> </t> > >>>>> --> > >>> > >>> 4) Understood. We have restored the links for the fragment identifiers. > >>> To clarify, these links refer to RFCs 8428 (for SenML Units) and 8798 > >>> (for Secondary Units) rather than the IANA registries themselves > >>> (<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fsenml%2Fsenml.xhtml%23senml-units&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745458031%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=b3OaDa9iynQxBBYnhkcGmVK0dgH%2FbsGfGmR26UFTBkE%3D&reserved=0> > >>> and > >>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fsenml%2Fsenml.xhtml%23secondary-units&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745483050%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=zPttEK%2FUS5%2BVDeOadpurbRtePCJC6IydxYwPTu428%2BA%3D&reserved=0>). > >>> Is this intentional? We ask this because the in-text citations that > >>> follow the fragment identifier links reference the specific sections of > >>> the RFCs that these registries appear in (so both RFCs are essentially > >>> referenced twice in the same sentence). > >>> > >>>>> 12) <!-- [rfced] The IANA registry includes "(note 1)" as part of the > >>>>> description for unix-time, but there is no note included in the > >>>>> registry. > >>>>> Should the notes be included in the registry > >>>> > >>>> Yes, please. > >>> > >>> 5) We will ask IANA to update to include this note. > >>> > >>>>> or perhaps "(note 1)" should > >>>>> be removed from the description? > >>>>> > >>>>> Original (text): > >>>>> | unix-time | A point in | number | POSIX time | Section | > >>>>> | | civil time | | | 3.4.2 of | > >>>>> | | (note 1) | | | RFC 8949 | > >>>>> | | | | | [STD94] | > >>>>> > >>>>> See the IANA registry: > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Fsdf%2Fsdf.xhtml%23sdftype-values&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745506903%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=g%2F1BaqrBuQQbw2S6bugaqApUmu6i0uFp5gJgEwVmaiY%3D&reserved=0 > >>>>> --> > >>> > >>>>> 14) <!-- [rfced] We have updated this text to remove the use of relative > >>>>> references. Please review. > >>>>> > >>>>> Original: > >>>>> Repository: combining the symbol values from the SenML Units > >>>>> registry and the Secondary Units registry in [IANA.senml] as > >>>>> specified by Sections 4.5.1 and 12.1 of [RFC8428] and Section 3 of > >>>>> [RFC8798], respectively (which by the registration policy are > >>>>> guaranteed to be non-overlapping). > >>>>> > >>>>> Current: > >>>>> Repository: Combining the symbol values from the "SenML Units" > >>>>> registry and the "Secondary Units" registry in the "Sensor > >>>>> Measurement Lists (SenML)" registry group [IANA.senml] as > >>>>> specified by Sections 4.5.2 and 12.1 of [RFC8428] and Section 3 of > >>>>> [RFC8798], respectively (which, by the registration policy, are > >>>>> guaranteed to be non-overlapping). > >>>>> --> > >>>>> > >>>> > >>>> (I can’t see the change in the plaintext here…) > >>>> Please see my comment about relative references into IANA registries > >>>> above in question 11. > >>> > >>> 6) Noted. Relative references have also been restored in this sentence. > >>> Please see our response/followup question to question 11. > >>> > >>>>> 17) <!-- [rfced] References > >>>>> > >>>>> a) Please review the following reference. The original URL for this > >>>>> reference - > >>>>> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.openmobilealliance.org%2Fwp%2Fomna%2Flwm2m%2Flwm2mregistry.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745537876%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2Hiltuk3bpYEkw9supSEpcM2LUDqPAVsxX1pq8raTBE%3D&reserved=0 > >>>>> - > >>>>> redirects to the following URL: > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openmobilealliance.org%2Fspecifications&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745564853%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=BLhFnrS3XCV0WMU72c4y3%2FoxTtZ4wx%2FbziwUVu8EmCY%3D&reserved=0 > >>>>> with the title "OMA > >>>>> Specifications". > >>>>> > >>>>> We could not find a page with the original title for this reference "OMA > >>>>> LightweightM2M (LwM2M) Object and Resource Registry". We did find the > >>>>> following page: > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openmobilealliance.org%2Fspecifications%2Fregistries&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745589665%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=GcWhZCySCJIFRxJEBW74uhAk4s979aXUyxFPHO9Rtx8%3D&reserved=0, > >>>>> which contains separate links to the LwM2M Objects and > >>>>> Resources registries. > >>>>> > >>>>> Would you like to update this reference to point to this new URL? > >>>>> > >>>>> Current: > >>>>> [OMA] Open Mobile Alliance, "OMA LightweightM2M (LwM2M) Object > >>>>> and Resource Registry", > >>>>> > >>>>> <https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.openmobilealliance.org%2Fwp%2Fomna%2Flwm2m%2F&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745614918%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=pOTFx13Bb6GZSHJTuJUrUuZeYpeHqiUd6Qvyfqf3fiw%3D&reserved=0 > >>>>> lwm2mregistry.html>. > >>>> > >>>> Right, so the URL and the title would need to be updated. > >>>> The actual HTML page title is awkward, though. > >>>> > >>>> Title: openmobilealliance.org/specifications/registries/objects/ > >>>> > >>>> Maybe we can use the <h1> title instead of the document.title (which I > >>>> don’t find in the page source, by the way): > >>>> > >>>> NEW: > >>>> Title: LwM2M OBJECTS > >>>> Link: > >>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.openmobilealliance.org%2Fspecifications%2Fregistries%2Fobjects&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745640110%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RwkeQkgQCgt4UvmkzSsIvd9pda8PWyWD6J%2BBh6fDvok%3D&reserved=0 > >>>> > >>>> This link is slightly more specific than what we referenced before, but > >>>> fits the site of the citation (which is about objects, not about > >>>> resources) even better. > >>>> > >>>> (With my browser, the page briefly indicates that it is embarrassed > >>>> about itself and then switches back to what we want here; this may need > >>>> some additional debugging.) > >>>> > >>>>> b) The information for this reference appears to be from the 2020 > >>>>> version > >>>>> of ECMA Standard ECMA-262. However, the URL provided points to the 2024 > >>>>> edition. > >>>>> > >>>>> We've updated this reference to use the information from the URL - that > >>>>> is, > >>>>> the 2024 edition. Please let us know if you have any objections. > >>>>> > >>>>> Current: > >>>>> [ECMA-262] Ecma International, "ECMAScript 2024 Language > >>>>> Specification", 15th Edition, ECMA Standard ECMA-262, June > >>>>> 2024, > >>>>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ecma-international.org%2Fwp-&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745662692%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=euj75LIcZuUaXNPbh86qHylmrNffQEtwgi6HZqa3luk%3D&reserved=0 > >>>>> content/uploads/ECMA-262.pdf>. > >>>>> --> > >>>> > >>>> By now, that would be > >>>> title: ECMA-262, 16th edition, June 2025 > >>>> link: > >>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fecma-international.org%2Fwp-content%2Fuploads%2FECMA-262_16th_edition_june_2025.pdf&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745684995%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=pfjWjzj%2B%2B%2F6YKo3UEPmE1ELLDOtTYAdJsnQvLV1nYRs%3D&reserved=0 > >>>> > >>>> Of course, the intention is not to point just to this specific revision. > >>>> I don’t think we have a general guideline how to deal with documents > >>>> that are on a regular update schedule, so simply going to the 2025 > >>>> revision might be the right thing to do. > >>>> > >>>> (This is based on the belief that the new functionality in 16th edition > >>>> relative to 11th edition does not extend the pattern language resulting > >>>> from applying the suggested limitations in Appendix C.2 to the > >>>> referenced edition. Updating these links does need some care…) > >>> > >>> 7) Both references have been updated. Please review the updated files and > >>> let us know if they appear as desired. > >>> > >>>>> 19) <!-- [rfced] Does "earlier drafts" refer to earlier drafts of the > >>>>> I-D > >>>>> that became this RFC or earlier versions of SDF (defined elsewhere)? > >>>>> Perhaps this can be clarified? > >>>>> > >>>>> Current: > >>>>> Appendix E. Some Changes From Earlier Drafts > >>>>> --> > >>>> > >>>> The first (real) paragraph of Appendix E is actually intended to clarify > >>>> this. > >>>> To answer the question: All the published draft specs have been > >>>> Internet-Drafts, see timeline on > >>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-asdf-sdf%2F&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745705751%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=OM3Peuranha3OaMCgGZPmVLYoZk3YVq%2Fgw5LaMMGsVs%3D&reserved=0 > >>>> > >>>> “Earlier drafts” of course is a bit confusing as the RFC-to-be no longer > >>>> is a draft. > >>>> Maybe “from drafts of this specification”? > >>> > >>> 8) We have updated the title of Appendix E as follows. Additionally, > >>> would the following update clarify "previous revisions of SDF"? > >>> > >>> Current (Title of Appendix E): Some Changes from Earlier Draft Versions > >>> of this Specification > >>> > >>> Current (Text in Appendix E): > >>> Previous revisions of SDF have been in use for several years, and both > >>> significant collections of older SDF models and older SDF conversion > >>> tools are available today. > >>> > >>> Perhaps: > >>> SDF, as defined in earlier drafts versions of this specification, have > >>> been in use > >>> for several years; both significant collections of older SDF models and > >>> older SDF > >>> conversion tools are available today. > >>> > >>>>> 20) <!-- [rfced] Please review each artwork element and let us know if > >>>>> any > >>>>> should be marked as sourcecode (or another element) instead. > >>>>> > >>>>> We updated Figure 5 from artwork to sourcecode. Please confirm that > >>>>> this is > >>>>> correct. > >>>> > >>>> When does a snippet (like the one about warning/danger in 2.3.2, which > >>>> is marked as artwork) become sourcecode? > >>>> Figure 5 is not really parsable per se, it needs to be integrated into > >>>> context to *really* be sourcecode. > >>>> Despite this, marking it as JSON sourcecode probably is OK (even if > >>>> kramdown-rfc would complain that it isn’t really JSON, because it is a > >>>> snippet, or actually two of them in one figure). > >>>> > >>>>> In addition, please consider whether the "type" attribute of any > >>>>> sourcecode > >>>>> element should be set and/or has been set correctly. > >>>> > >>>> [TO CHECK] > >>>> > >>>>> The current list of preferred values for "type" is available at > >>>>> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dsourcecode-types&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745728001%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=wE4Aeo7HccNRCNF%2FPWjRlzqG7Afpsa4WV3t7SPs4Kgw%3D&reserved=0>. > >>>>> If the current list does not contain an applicable type, feel free to > >>>>> suggest additions for consideration. Note that it is also acceptable > >>>>> to leave the "type" attribute not set. > >>>> > >>>> We haven’t really discussed so far whether there should be a sourcecode > >>>> type specifically for SDF. > >>>> By default, application/sdf+json is one (usually leaving out > >>>> application/, so just “sdf+json”). > >>>> We do have precedent for using structured syntax suffixes in > >>>> yang-instance-data+json, so nothing appears to speak against use that. > >>>> (There are 25 instances where this needs to be checked.) > >>>> > >>>>> --> > >>>>> 21) <!-- [rfced] We note that these terms appear both with and without > >>>>> <tt> > >>>>> tags. Please review each instance of the terms below and ensure that > >>>>> they > >>>>> appear in the document as desired. If these terms should be formatted > >>>>> consistently or follow a specific pattern, please let us know. > >>>> > >>>> [TO CHECK] > >>>> > >>>> Generally, when the sourcecode construct is meant, we use the typewriter > >>>> font; when the concept is meant (“an array of string values”…), we > >>>> don’t, and we then use the English capitalization (“Boolean”). > >>>> > >>>>> <tt>absolute-URI</tt> > >>>>> <tt>array</tt> > >>>>> <tt>boolean</tt> > >>>>> <tt>curie</tt> > >>>>> <tt>date-time</tt> (also appears in quotes) > >>>>> <tt>defaultNamespace</tt> > >>>>> <tt>description</tt> > >>>>> <tt>enum</tt> > >>>>> <tt>false</tt> > >>>>> <tt>features</tt> (also appears in quotes) > >>>>> <tt>format</tt> > >>>>> <tt>info</tt> > >>>>> <tt>integer</tt> > >>>>> <tt>items</tt> > >>>>> <tt>json-schema.org</tt> > >>>>> <tt>label</tt> > >>>>> <tt>length</tt> > >>>>> <tt>named-sdq</tt> > >>>>> <tt>namespace</tt> > >>>>> <tt>null</tt> > >>>>> <tt>number</tt> > >>>>> <tt>object</tt> (also appears in quotes) > >>>>> <tt>pattern</tt> (also appears in quotes) > >>>>> <tt>properties</tt> (also appears in quotes) > >>>>> <tt>referenceable-name</tt> (also appears in quotes) > >>>>> <tt>required</tt> > >>>>> <tt>sdfAction</tt> > >>>>> <tt>sdfChoice</tt> > >>>>> <tt>sdfData</tt> > >>>>> <tt>sdfEvent</tt> > >>>>> <tt>sdfObject</tt> > >>>>> <tt>sdfOutputData</tt> > >>>>> <tt>sdfProperty</tt> > >>>>> <tt>sdfRef</tt> > >>>>> <tt>sdfRequired</tt> (also appears in quotes) > >>>>> <tt>sdfThing</tt> > >>>>> <tt>sdf</tt> > >>>>> <tt>sdfType</tt> > >>>>> <tt>string</tt> > >>>>> <tt>toggle</tt> (also appears in quotes) > >>>>> <tt>true</tt> > >>>>> <tt>type</tt> > >>>>> <tt>unit(s)</tt> > >>>>> <tt>value</tt> > >>>>> --> > >>>>> > >>>>> > >>>>> 22) <!-- [rfced] Please review the following terms and let us know > >>>>> if/how > >>>>> we should update for consistency. > >>>>> > >>>>> a) Capitalization > >>>> > >>>> Continue here later… [TO CHECK] > >>>> > >>>>> Properties vs. properties > >>>>> quality names vs. Quality Names > >>>>> SDF model vs. SDF Model > >>>>> > >>>>> b) Spacing > >>>>> data qualities vs. dataqualities > >>>>> data quality vs. data quality > >>>> > >>>> ? > >>> > >>> 9) Apologies for the confusion. Here is the correct side-by-side > >>> comparison: > >>> data quality vs. dataquality > >>> > >>>>> c) Other > >>>>> base SDF vs. SDF base > >>>>> --> > >>>>> > >>>>> > >>>>> 23) <!-- [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. > >>>>> --> > >>>> > >>>> We’ll get to this in the diff reading phase. > >>>> [TO CHECK] > >>> > >>> The files have been posted here (please refresh): > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.txt&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745750091%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=39MR79Tl%2BaqhyigaF90RoZj4IvyaWA2%2Ft2Rfn5jMFFk%3D&reserved=0 > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.pdf&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745773348%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RWnZ5F9AXAucj0oel6bLIVxQ6YbG9%2Bvy2Xd0gSgTXew%3D&reserved=0 > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745796629%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ze%2FRicBnuIlAJjQH6KDuLO5tLwq4Nsr9IgC78xg1Tww%3D&reserved=0 > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.xml&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745818988%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ZerMA7OlYGjdRF0AxYPqyanS9K85xOsHTltosUxSf1U%3D&reserved=0 > >>> > >>> Diff files: > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-diff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745841202%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=wD5iRSoXiZvM10nyOgCcuHBnLJsw36YNA9pEdH5Tpmc%3D&reserved=0 > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-rfcdiff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745863541%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3KgF6RGEeXHMrRSXiQwH2IYLs2ZNI%2FYYo%2BaidDL8xxg%3D&reserved=0 > >>> (side by side) > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-auth48diff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745885171%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0ToMjK3%2BQQqMi2UmN7gX5hH5rScPjAYMEv50Qo3osP8%3D&reserved=0 > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-auth48rfcdiff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745908241%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=SWGqv6r9JBVhJ9ABUMBBR5jT9FIxj7OeQJc38Q22ezI%3D&reserved=0 > >>> (side by side) > >>> > >>> For the AUTH48 status page, see: > >>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9880&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745930831%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RCpAnAJiRUrSYY1BCTXSQqnZUJpTHMo49SdkqzCbTvU%3D&reserved=0. > >>> > >>> Thank you! > >>> > >>> Madison Church > >>> RFC Production Center > >>> > >>>>> Thank you. > >>>> > >>>> Thank you! > >>>> > >>>>> Madison Church and Sandy Ginoza > >>>>> RFC Production Center > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> On Oct 6, 2025, at 9:57 PM, [email protected] wrote: > >>>>> > >>>>> *****IMPORTANT***** > >>>>> > >>>>> Updated 2025/10/06 > >>>>> > >>>>> 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Ffaq%2F&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745956473%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=73w6420FVEx3codOsactCLYQYrX3u0jMxDQuEZavhog%3D&reserved=0). > >>>>> > >>>>> 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrustee.ietf.org%2Flicense-info&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745978205%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=xG5R2ETyjA3ulV9RG7MdBkvXi5Lz8uiFkb%2FgNh3hNtY%3D&reserved=0). > >>>>> > >>>>> * 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthors.ietf.org%2Frfcxml-vocabulary&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596745996446%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=BqyPOrVriEZ2Jdlkrsay4%2FG6R%2B0iMV79Dn3xtomaDcI%3D&reserved=0>. > >>>>> > >>>>> * 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 > >>>>> > >>>>> * [email protected] (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). > >>>>> > >>>>> * [email protected], which is a new archival mailing list > >>>>> to preserve AUTH48 conversations; it is not an active discussion > >>>>> list: > >>>>> > >>>>> * More info: > >>>>> > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Fietf-announce%2Fyb6lpIGh-4Q9l2USxIAe6P8O4Zc&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746014554%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FdKNMuc3c%2BNOHOTa%2BsdoeptE9w0NePV%2BZYb98Ph10rI%3D&reserved=0 > >>>>> > >>>>> * The archive itself: > >>>>> > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fbrowse%2Fauth48archive%2F&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746033577%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=XaLO0B3WE7MULqRh0Vo79yhK%2FaRLz%2FHqwnxjOz7sMcQ%3D&reserved=0 > >>>>> > >>>>> * 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, > >>>>> [email protected] 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://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.xml&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746051012%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=caH951fe5ll80w9Ke%2BnyzE4nete9FHajbgYitV429TM%3D&reserved=0 > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746070344%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=96CkdJiKIq29NEA%2Fe6f7L1PB%2F4IFa%2FOuh13vab1DbF8%3D&reserved=0 > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.pdf&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746090864%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=YE%2BtgDZ7CqHiBj21daTAj87cJxPKYu1JnD9yRyA9R8s%3D&reserved=0 > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880.txt&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746111875%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Zr0cKMKurEaMqIEuQcheudgXx36MoiHJl7AVTw5CNrc%3D&reserved=0 > >>>>> > >>>>> Diff file of the text: > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-diff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746129941%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=UjjGExvlcbw0AIs%2FTbO6ZrtlaH3eKPBJrKW5irqvkN0%3D&reserved=0 > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-rfcdiff.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746150686%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=KqSNtvPs3MFrN7asXn%2BnoWDtq9ZNeNr0%2F1E1EgBAlKE%3D&reserved=0 > >>>>> (side by side) > >>>>> > >>>>> Diff of the XML: > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9880-xmldiff1.html&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746172968%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ES3ZQquIoUpQImB5pXJ7fWUNw8HBu%2BDGyciTxoY35Bc%3D&reserved=0 > >>>>> > >>>>> > >>>>> Tracking progress > >>>>> ----------------- > >>>>> > >>>>> The details of the AUTH48 status of your document are here: > >>>>> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9880&data=05%7C02%7Cari.keranen%40ericsson.com%7C6e838e68034445cd375208de2203af4a%7C92e84cebfbfd47abbe52080c6b87953f%7C0%7C0%7C638985596746192299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=U%2FwFLm%2BpYqx1OJuuudnq9EU3uyvjJp%2BQhANwBr0jdUQ%3D&reserved=0 > >>>>> > >>>>> Please let us know if you have any questions. > >>>>> > >>>>> Thank you for your cooperation, > >>>>> > >>>>> RFC Editor > >>>>> > >>>>> -------------------------------------- > >>>>> RFC 9880 (draft-ietf-asdf-sdf-24) > >>>>> > >>>>> Title : Semantic Definition Format (SDF) for Data and > >>>>> Interactions of Things > >>>>> Author(s) : M. Koster, Ed., C. Bormann, Ed., A. Keränen > >>>>> WG Chair(s) : Michael Richardson, Lorenzo Corneo > >>>>> > >>>>> Area Director(s) : Andy Newton, Orie Steele > >>>>> > >>>>> > >>>> > >>> > >> > > > -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
