On Aug 30, 2025, at 2:07 PM, Guy Harris <[email protected]> wrote: > > https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-opsawg-pcaplinktype-11.txt > > which I presume is at least partially auto-generated and thus based on the > current draft, has some nits it reports. > > I'll look at those.
So we have: draft-ietf-opsawg-pcaplinktype-11.txt: -(1756): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding Yes, it's non-ASCII characters in UTF-8 encoding, i.e. "Tüxen, M." I seem to remember *some* discussion of the use of non-ASCII characters for names with diacritical marks that concluded with "it's probably OK", perhaps because we found RFCs that used them, but I don't remember the details. If it's an issue, we could go with "Tuexen, M.". Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. Both are from ü from "Tüxen, M.", as per the above. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 130: '... 11-49 and 52-97 MUST not be assigned....' "{::boilerplate bcp14}" appears to be missing from draft-ietf-opsawg-pcaplinktype.md, although it's in draft-ietf-opsawg-pcap.md and draft-ietf-opsawg-pcapng.md. It was in earlier Git revisions; I put it back. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1067 has weird spacing: '...ription fd.io...' No weirder than any of the other "Description" lines, all of which have two spaces after "Description". "fd.io" is the name of an organization; that may have confused idnits. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: * Values from 0 to 65000 are allocated following a First-Come First-Served policy (Section 4.4 of [RFC8126]). Values in the ranges 0-10, 50-51, and 98-301 are already assigned; values in the ranges 11-49 and 52-97 MUST not be assigned. Fixed to be "MUST NOT". Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-04) exists of draft-ietf-opsawg-pcapng-03 That's probably just the result of the -11 draft having been generated before draft-ietf-opsawg-pcapng-04 was published - the draft number is automatically generated by the process of building the documents from the Markdown source. _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
