Skip to content

docs: align RFC + IEC 62443 compliance docs with shipped features#565

Merged
DavidCozens merged 1 commit into
mainfrom
docs/at-rest-crypto-and-transport-accuracy
Jun 9, 2026
Merged

docs: align RFC + IEC 62443 compliance docs with shipped features#565
DavidCozens merged 1 commit into
mainfrom
docs/at-rest-crypto-and-transport-accuracy

Conversation

@DavidCozens

Copy link
Copy Markdown
Owner

Summary

Audit of docs/rfc-compliance.md and docs/iec62443.md against the implemented codebase, fixing both over- and under-claims.

IEC 62443 (docs/iec62443.md)

RFC compliance (docs/rfc-compliance.md)

  • Under-claim — TLS transports. RFC 5425 §4.1 omitted SolidSyslogLwipRawTcpStream (E28) from the TLS-capable byte transports; added it.
  • Staleness. RFC 5424 §6.2.3 note referenced the now-private SolidSyslogFormatter_PrintUsAsciiString; updated to the public SolidSyslogHeaderField sink. The ? substitution behaviour itself was verified accurate.

Everything else in both docs reconciled with the code (summary row counts, substitution char, MSGID bound, UTF-8/BOM, keepalive/connect-timeout behaviour, mTLS, etc.).

Docs-only — no code or test changes.

🤖 Generated with Claude Code

The compliance docs drifted from the implementation in three places:

- IEC 62443 under-claimed at-rest crypto: E17 shipped mbedTLS AES-256-GCM
  (S17.04) alongside the OpenSSL variant, but CR 2.12 / CR 3.9 and the
  SL3/SL4 recipes only listed SolidSyslogOpenSslAesGcmPolicy. Now offers
  SolidSyslog{OpenSsl,MbedTls}AesGcmPolicy and reframes the E17 refs as
  shipped rather than in-progress.
- IEC 62443 over-claimed SolidSyslogFormatter as an SL1 wiring component;
  S14.08 made the formatter library-private, so application code never
  touches it. Dropped from the SL1 recipe and CR 2.8.
- RFC 5425 §4.1 omitted SolidSyslogLwipRawTcpStream (E28) from the list of
  TLS-capable byte transports; added it. Also updated the RFC 5424 §6.2.3
  note to reference the public SolidSyslogHeaderField sink rather than the
  now-private formatter entry point.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@DavidCozens, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8f5727ed-1ace-4a8f-95f1-45e054ccfe7f

📥 Commits

Reviewing files that changed from the base of the PR and between 32e358f and 9064112.

📒 Files selected for processing (2)
  • docs/iec62443.md
  • docs/rfc-compliance.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/at-rest-crypto-and-transport-accuracy

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

☀️   Quality Summary

   🚦   build-linux-gcc: 100% successful (✔️ 1521 passed)
   🚦   build-freertos-host-tdd-plustcp: 100% successful (✔️ 1872 passed)
   🚦   build-linux-clang: 100% successful (✔️ 1453 passed)
   🚦   sanitize-linux-gcc: 100% successful (✔️ 1453 passed)
   🚦   integration-linux-openssl: 100% successful (✔️ 16 passed)
   🚦   integration-linux-mbedtls: 100% successful (✔️ 14 passed)
   🚦   integration-windows-openssl: 100% successful (✔️ 16 passed)
   🚦   bdd-linux-syslog-ng: 94% successful (✔️ 49 passed, 🙈 3 skipped)
   🚦   bdd-windows-otel: 88% successful (✔️ 46 passed, 🙈 6 skipped)
   🚦   bdd-freertos-qemu-plustcp: 87% successful (✔️ 45 passed, 🙈 7 skipped)
   🚦   bdd-freertos-qemu-lwip: 87% successful (✔️ 45 passed, 🙈 7 skipped)
   🚦   build-windows-msvc: 100% successful (✔️ 1298 passed)
   🚦   build-linux-tunable-override: 100% successful (✔️ 1453 passed)
   ⚠️   Clang-Tidy: No warnings
   ⚠️   CPPCheck: No warnings


Created by Quality Monitor v1.14.0 (#f3859fd). More details are shown in the GitHub Checks Result.

@DavidCozens DavidCozens merged commit 16ddce4 into main Jun 9, 2026
27 checks passed
@DavidCozens DavidCozens deleted the docs/at-rest-crypto-and-transport-accuracy branch June 9, 2026 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant