Repository navigation
quest: define TS fidelity, recovery, and automated validation #5327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
38e998d
quest: define TS fidelity, recovery, and automated validation
kixelated 2b3a9f2
quest: name redundant TS work by its packet identity scope
kixelated d7e8ea4
quest: clarify TS recovery and validation evidence
kixelated 9808935
Merge origin/main into codex/ts-validation-audit
kixelated File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| # [S] Plan: shared coordinates for redundant TS publishers and exporters | ||
|
|
||
| ## Goal | ||
|
|
||
| Settle what shared information makes redundant TS publishers and exporters | ||
| identify the same content and schedule. Rewrite the implementation quests | ||
| around that contract before promising failover or ST 2022-7 compatibility. | ||
|
|
||
| ## Plan | ||
|
|
||
| The 2026-10-11 audit found two missing prerequisites: | ||
|
|
||
| - Same epoch identity does not establish a source PCR/PTS-to-wall mapping, | ||
| a 33-bit timestamp wrap era, or a common raw-packet position. Importers | ||
| starting at different offsets cannot infer these from the UUID alone. | ||
| `catalog::Timebase::place` applies a supplied mapping; it does not discover | ||
| one. Raw fallback's timeout cuts also depend on acquisition history, even | ||
| though the CLI currently accepts a shared `--epoch` there. | ||
| - Identical TS packets are insufficient for ST 2022-7, which requires the | ||
| matching RTP packets, including headers. Complementary losses on redundant | ||
| paths are a reason to merge them; requiring the two legs to drop the same | ||
| content defeats that benefit. | ||
|
|
||
| Present the maintainer with the actual shared-coordinate choices: an | ||
| explicit common source anchor and era, a common upstream packetizer, or an | ||
| honestly narrowed importer contract. Include what each can prove when the | ||
| standby starts after a timestamp wrap, a clock break, or a fallback group cut. | ||
| Do not derive a media clock from wall arrival and call it deterministic. | ||
|
|
||
| For egress, separate deterministic TS slot/counter identity for common | ||
| content from coordinated RTP packetization, sequence/timestamp/SSRC identity | ||
| and any receiver merge. Decide the intended scope and API before implementing | ||
| `--sync`. NTP-synchronized hosts alone do not supply the missing source map. | ||
|
|
||
| Produce focused implementation quests and explicit refusals for unsupported | ||
| shared-epoch modes. Their automated tests start peers at different source | ||
| offsets, cross wraps, vary delivery skew, and introduce complementary loss; | ||
| compare common content in its shared coordinate rather than whole files | ||
| whose delivered content differs. Actual ST 2022-7 claims require RTP-level | ||
| tests against the [standard](https://pub.smpte.org/latest/st2022-7/st2022-7-2019.pdf). | ||
|
|
||
| ## Related | ||
|
|
||
| - [Same-epoch importers](/quest/m1/hop-aligned-import.md) - currently assumes an input-derived wall anchor is available | ||
| - [Deterministic TS legs](/quest/m2/ts-hitless.md) - TS identity and RTP recovery need separate acceptance evidence | ||
| - [TS passthrough export](/quest/m1/ts-passthrough-export.md) - unchanged packets do not establish identical groups from independent starts |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.