Complete EN 300 468 Table 2: six new tables + vendored specs#4
Merged
Conversation
Latest published versions (newer-version probes 404). Grounds the remaining DVB table_id allocations: protection message 0x7B + AIT 0x74 (102 809), MPE-IFEC 0x7A (102 772), downloadable font info 0x7C (303 560). Container 0x75 and MPE-FEC 0x78 were already grounded by the vendored TS 102 323 / EN 301 192.
…aining DVB tables - docs: ts_102_809_apps.md (51 tables), ts_102_772_mpe_ifec.md (12), en_303_560_ttml.md (26) via the geometry extractor - TableId: ProtectionMessage 0x7B, DownloadableFontInfo 0x7C (0x75/0x78/0x7A already present) - tables/mod.rs + compiling stubs for container, mpe, mpe_fec, mpe_ifec, protection_message, downloadable_font_info
…bles - Container (0x75, TS 102 323 §7.3.1.4) - MPE datagram_section (0x3E, EN 301 192 §7.1 — typed IP/MAC view of the DSM-CC private section; SSI=0 checksum trailer preserved verbatim, SSI=1 CRC recomputed) - MPE-FEC (0x78, EN 301 192 §9.9 + §9.10 real_time_parameters 12/1/1/18) - MPE-IFEC (0x7A, TS 102 772 §5.2; its own RealTimeParameters per Table 3) - Protection message (0x7B, TS 102 809 §9): authentication message (ext 0x0000-0x00FF = authentication_group_id, PDF p.66 Table 41) + certificate collection (ext 0x0100, Table 51) + raw fallthrough - DFIS (0x7C, EN 303 560; 0x4C-in-spec is the acknowledged allocation accident per EN 300 468 V1.19.1 Table 2 NOTE 2; the 0x02 dual conditional confirmed intentional against PDF pp.30-31) Every allocated table_id in EN 300 468 V1.19.1 Table 2 is now implemented. House idiom throughout: typed headers + borrowed raw loops, Parse/Serialize symmetry, no CRC verify on parse, serde derives + borrow, full in-module test sets. TableId gains ProtectionMessage/DownloadableFontInfo. 516 dvb-si lib tests pass (62 new), clippy -D warnings clean, MSRV 1.75.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Vendors TS 102 809 v1.3.1 / TS 102 772 v1.1.1 / EN 303 560 v1.1.1 (latest; newer probes 404) + extracted reference MDs, then implements the six remaining allocated table_ids: Container 0x75, MPE datagram 0x3E (typed), MPE-FEC 0x78, MPE-IFEC 0x7A, protection message 0x7B (auth + cert-collection variants), DFIS 0x7C.
Notable spec archaeology: EN 303 560 says table_id 0x4C — EN 300 468 V1.19.1 Table 2 NOTE 2 confirms that was accidentally double-allocated with the INT and corrects it to 0x7C.
Every allocated table_id in EN 300 468 V1.19.1 Table 2 is now implemented. House idiom enforced throughout (typed headers + borrowed raw loops, Parse/Serialize symmetry, no CRC-verify-on-parse, serde + borrow). 516 dvb-si lib tests (62 new), clippy clean, MSRV 1.75.
🤖 Generated with Claude Code