User Tools

Site Tools


provenance:design:dns

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
provenance:design:dns [2026/09/17 02:38] – Spoki's ZMap tuple suppressed too: ZMap/XMap 111->110, scanner-generic 155->154, residue 975->974; both folds still agree. Authored by Claude karel.kubicek.claudeprovenance:design:dns [2026/09/17 09:37] (current) – Record RFC prose follow-up and source checks; Authored by Claude karel.kubicek.claude
Line 552: Line 552:
  
 **One quote is normalised and says so on the page.** Ager et al. (IMC 2010) is rendered "2 , 000" and "10, 000" with a stray space and "dif- fer" hyphenated across a line break — in ''paper.cols.txt'' **and** in a ''pypdf'' re-extraction of ''paper.pdf'', so it is the source's own typesetting, not a column-repair artefact. The page carries a footnote saying so. **One quote is normalised and says so on the page.** Ager et al. (IMC 2010) is rendered "2 , 000" and "10, 000" with a stray space and "dif- fer" hyphenated across a line break — in ''paper.cols.txt'' **and** in a ''pypdf'' re-extraction of ''paper.pdf'', so it is the source's own typesetting, not a column-repair artefact. The page carries a footnote saying so.
 +
 +===== RFC prose follow-up (2026-09-17) =====
 +
 +The external-currency pass in [[#Review log]] intentionally left RFC 9460, RFC 9567, RFC 9520 and RFC 9606 out of the page: four bare RFC numbers would be a reading list, not measurement guidance. This follow-up adds one measurement-facing paragraph for each. It adds no corpus figure and no bibliography entry. The four paragraphs were checked against the [[https://www.rfc-editor.org/rfc-index/|RFC Editor index]] and the individual RFC records on 2026-09-17.
 +
 +<code>
 +Command run:
 +bash scripts/external_checks_dns.sh | awk '/^== RFCs the page names/{show=1} /^== GitHub repositories/{show=0} show {print}'
 +
 +Relevant checker output on 2026-09-17:
 +RFC9460   November 2023  PROPOSED STANDARD  obs_by=-          upd_by=-            Service Binding and Parameter Specification via the DNS
 +RFC9520   December 2023  PROPOSED STANDARD  obs_by=-          upd_by=-            Negative Caching of DNS Resolution Failures
 +RFC9567   April 2024     PROPOSED STANDARD  obs_by=-          upd_by=-            DNS Error Reporting
 +RFC9606   June 2024      PROPOSED STANDARD  obs_by=-          upd_by=-            DNS Resolver Information
 +
 +Source records read:
 +https://www.rfc-editor.org/info/rfc9460/
 +https://www.rfc-editor.org/info/rfc9567/
 +https://www.rfc-editor.org/info/rfc9520/
 +https://www.rfc-editor.org/info/rfc9606/
 +</code>
 +
 +The required delegated model 'sonnet' external-currency pass was attempted for this prose change, but the available delegation service rejected model ''sonnet'' (only GPT models were exposed). No alternate model was substituted. I manually re-read the four fetched RFC Editor records and found no correction to the four paragraphs; this environment limitation is recorded rather than mislabeled as a Sonnet result.
  
 ===== External checks ===== ===== External checks =====
provenance/design/dns.1789612680.txt.gz · Last modified: by karel.kubicek.claude