Engineering diagrams · 34 workflows

One transport, shown step by step.

The editable Mermaid sources are preserved with their captions and status notes. Current v0.2 explanations are identified separately from future proposals.

Review status. The source pack passed Mermaid grammar checks. This site now renders its diagrams locally as SVG. Layout and styling remain open for review; rendering is not technical adoption or hardware evidence.

The Type 1 and Type 2 timing options and the clock-hub role are proposals for future work. They do not add wire values or alter the published O2AT v0.2 paper.

Read the full source catalogue · Browse editable files

Group 01

Transport, discovery and session state

The optical link, capability negotiation, packet handling, admission and session lifecycle.

  1. 01System overview: audio forward, control backv0.2 explanation
    Workflow diagram 1: System overview: audio forward, control back

    The mandatory baseline uses full-duplex 1G optical Ethernet. The receiver controls conversion timing and returns cumulative credits so the source sends within available storage.

    The fibre isolates the audio-link path. Separate coaxial clock, power-earth, USB or analogue connections may provide conductive paths between chassis. The diagram is an architectural view, not a claim that an existing DAC accepts O2AT.

    Status: Current v0.2 explanatory workflow. Source sections: 4.1, 5.1, 5.3, 6.1, 6.4.

    Download editable Mermaid source

  2. 02Common optical Ethernet link startupv0.2 explanation
    Workflow diagram 2: Common optical Ethernet link startup

    The mandatory baseline establishes a qualified 1000BASE-SX, full-duplex 1G Ethernet link before o2at discovery. Link-up alone does not permit playback.

    This is the common packet/control workflow, not a newly standardised clock architecture. The diagram shows the common SX optical profile; explicitly qualified LX links and paired forced-operation tests are separate permitted cases. A 10 MHz input is not required for Ethernet link-up. A 10G-only host cannot be assumed to support a 1G SFP. The two directions are Ethernet directions, not an implied raw optical clock channel.

    Status: Current v0.2 explanatory workflow. Source sections: 4.1, 5.1, 5.3, 5.6.

    Download editable Mermaid source

  3. 03Common peer discovery and session negotiationv0.2 explanation
    Workflow diagram 3: Common peer discovery and session negotiation

    HELLO reports capabilities, OPEN fixes the admitted context, and START grants permission to send audio. The receiver begins playback only after the agreed prefill condition.

    OPEN can prepare or acquire a clock; it does not certify that START can yet succeed. START requires a valid conversion clock and, in common-reference mode, an established frequency relationship. The selected clock arrangement must correspond to an admitted v0.2 clock_mode; proposed raw-clock return links require their own extension definition. Reference-tier successful HELLO, OPEN, START and PING responses include clock_status. Short streams can start below normal prefill only when their complete final range is buffered and FINAL_AUDIO agrees with END. An empty stream uses END with total_groups zero and no audio packet. Discovery broadcasts are bounded; established sessions use unicast.

    Status: Current v0.2 explanatory workflow. Source sections: 4.1, 5.5, 5.6.

    Download editable Mermaid source

  4. 04Common format and forward-link capacity admissionv0.2 explanation
    Workflow diagram 4: Common format and forward-link capacity admission

    Compare the complete forward wire demand with 1.000 Gb/s MAC service. The 1.25 GBd optical line rate already includes the 1000BASE-X 8b/10b overhead.

    W includes MAC addresses and EtherType, the optional four-byte VLAN tag, the 12-byte o2at header, minimum MAC padding, FCS, preamble/SFD and inter-frame gap. Do not apply 8b/10b overhead a second time. For the paper's 125 us assembly target, choose G no larger than min(floor(1440/(4*C)), max(1, floor(r*125e-6))). Negotiate a fixed smaller G when required. The paper uses an 85% planning ceiling for advanced direct links, including other forward traffic; it is not a universal guaranteed-latency claim. Reverse full-duplex control does not consume forward serial capacity. Buffer and clock feasibility remain separate admission requirements. Optional 10G fabric capability must be explicitly supported and admitted, not presumed.

    Status: Current v0.2 explanatory workflow. Source sections: 4.1, 5.3, 5.5, 5.6, 5.8, 6.5.

    Download editable Mermaid source

  5. 05Common PCM and native DSD packetisationv0.2 explanation
    Workflow diagram 5: Common PCM and native DSD packetisation

    One PCM group contains one 32-bit container per channel. One DSD group contains 32 chronological one-bit samples per channel. Both use negotiated channel ordering and a fixed 12-byte o2at header.

    PCM16 and PCM24 use zero-filled low padding bits inside the two's-complement PCM32 container. DSD32 is a bit container, not a signed sample or DoP word. Big-endian and MSB-first describe payload packing; they do not change IEEE Ethernet physical bit transmission or line coding. The earliest DSD bit is container bit 31. AUDIO always contains negotiated G groups. FINAL_AUDIO contains 1 to G, including a full G, and must agree with END. Empty streams have no audio packet. MAC minimum padding is outside the declared audio group count.

    Status: Current v0.2 explanatory workflow. Source sections: 4.2, 5.3, 5.4, 5.6, 5.7, 5.8.

    Download editable Mermaid source

  6. 06Common audio receive validation and fault containmentv0.2 explanation
    Workflow diagram 6: Common audio receive validation and fault containment

    Complete-frame integrity and session checks precede FIFO commit. Unrelated traffic is discarded; a confirmed missing packet or invalid data threatening an active stream triggers that stream's protective mute and retirement.

    This diagram covers AUDIO and FINAL_AUDIO. CONTROL additionally validates the source nonce and transaction semantics. The canonical audio binding is talker MAC, listener MAC, VLAN context and session ID. A corrupt Ethernet frame cannot reliably identify an o2at session, so a bad FCS alone does not immediately abort an arbitrary active stream; a subsequently confirmed gap can do so at its playout deadline. Reordering is bounded, the active window is below 32,768 packets, and frame residence must satisfy the sequence-unwrapping limit. The readiness decision is monitored over time; it faults only when the actual deadline is missed, not merely because a packet has not arrived yet. Output mute must use a safe converter-specific method, especially for DSD.

    Status: Current v0.2 explanatory workflow. Source sections: 5.3, 5.4, 5.5, 5.6, 6.5, 7.1.

    Download editable Mermaid source

  7. 07Common admitted-session lifecyclev0.2 explanation
    Workflow diagram 7: Common admitted-session lifecycle

    The named receiver phases separate admission, START acknowledgement, prefill, playback and draining. Every restart creates a new session rather than resetting counters inside the old one.

    This is an explanatory phase diagram, not a complete normative event-transition table. The source prose does not fully tabulate state transitions for END arriving before prefill. END acceptance and final-range validation remain independent bookkeeping and must not bypass the prefill or complete-short-stream rule. A short stream starts only when its complete final range is buffered and FINAL_AUDIO plus END agree. An empty stream closes with END total_groups zero and no audio packet. OPEN and ARMED expire after two seconds without valid peer activity; running sessions abort after one second without valid peer traffic, while an audio deadline can act sooner. Loss of clock validity after START requires immediate safe mute and abort. Holdover retains a session only within declared clock and FIFO margins. STATUS does not authorise automatic resumption or a clock-mode change.

    Status: Current v0.2 explanatory workflow. Source sections: 5.5, 5.6, 6.5, 7.1.

    Download editable Mermaid source

  8. 08Common ordered finish and subsequent format changev0.2 explanation
    Workflow diagram 8: Common ordered finish and subsequent format change

    END accepts the exclusive final group count. The receiver preserves prior in-flight audio, verifies the final range and retires it before a different format can play under a new session.

    The compact exchange shows successful completion of a non-empty stream. Short streams may satisfy prefill through complete-final-range agreement; empty streams use END total_groups zero without FINAL_AUDIO. A missing FINAL_AUDIO still follows the loss policy. After a validated FINAL_AUDIO has played, waiting under mute for END is not an underrun. END and ABORT reply caches survive retirement for at least the retry duration plus admitted frame residence. OPEN may report BUSY while the old session drains; a subsequent new attempt uses a new transaction ID, while a retransmission of the identical request keeps its original ID. ABORT is the separate mute, flush and retire path when discarding the old stream is intended. The new session begins audio sequence numbering at zero only after its own successful START acknowledgement.

    Status: Current v0.2 explanatory workflow. Source sections: 5.5, 5.6, 6.5, 7.1.

    Download editable Mermaid source

  9. 17Direct and switched topologiesv0.2 explanation
    Workflow diagram 17: Direct and switched topologies

    The consumer baseline uses a direct 1G optical connection. An optional fabric can bridge admitted traffic from 1G ports or 10G aggregation within one Layer-2 domain. Receiver credits reach the appropriate source; PAUSE applies only to an adjacent MAC. Packet-switch qualification does not establish transparent timing-reference transfer.

    The two source paths illustrate alternatives or admitted sessions, not unrestricted simultaneous streams to one receiver. A bridge is not an IP router. Fibre isolation applies to the signal link; clock coax and other cables may provide parallel conductive paths. Switch configuration and mixed-speed burst limits require qualification. Ordinary switch retiming breaks an assumed PHY-derived DAC frequency reference unless a separately qualified clock-aware mechanism exists. A proposed dedicated return-clock path may bypass the data switch. Integrated or split timing-transfer extensions are not yet specified by v0.2.

    Status: Current v0.2 explanatory workflow. Source sections: 4.1, 4.2, 5.1, 5.3, 5.6, 6.4, 7.2.

    Download editable Mermaid source

  10. 18Switched-path admissionv0.2 explanation
    Workflow diagram 18: Switched-path admission

    Admission evaluates the actual forwarding policy, every egress budget, queue exposure to bursts, and the control round trip. Receiver credits remain end-to-end, while intermediate queues also need bounded traffic. Qualify the required clock relationship independently of packet admission.

    PCP 6 is an optional scheduling request, not a reservation or a latency guarantee. The direct-link 85% ceiling does not supply a universal switched-path ceiling. This diagram organises engineering checks rather than defining a new admission message exchange. An ordinary packet switch does not preserve an assumed DAC-originated PHY frequency reference. A clock-aware path or dedicated clock route needs its own specification and validation; proposed clock-transfer extensions are outside the present v0.2 definition.

    Status: Current v0.2 explanatory workflow. Source sections: 5.3, 5.6, 5.8, 6.5, 7.2.

    Download editable Mermaid source

  11. 19Validated frame commit and clock-domain crossingv0.2 explanation
    Workflow diagram 19: Validated frame commit and clock-domain crossing

    The illustrated implementation stages each complete frame, checks FCS and protocol validity, then commits coherent audio groups to a dual-clock FIFO. A qualified conversion-clock subsystem controls group retirement and the converter interface. Pointer transfer, reset release and CDC timing still require review.

    Complete-frame staging is one permitted implementation; an atomic rollback design is acceptable only if corrupt groups can never become visible to playback. Rejected foreign traffic does not itself mute an unrelated session. Output protection follows confirmed active-stream faults. No FIFO or FPGA PLL eliminates oscillator phase noise or local coupling.

    Status: Current v0.2 explanatory workflow. Source sections: 5.6, 6.1, 6.5, 7.1.

    Download editable Mermaid source

  12. 20Receiver power and RF partitioningv0.2 explanation
    Workflow diagram 20: Receiver power and RF partitioning

    Separate the placement and power-integrity analysis of the optical and digital circuitry from the sensitive clock and analogue paths. Validate the actual module, return-current structure, thermal design and measured coupling. A shared reference-clock coax may electrically reconnect chassis.

    This is a conceptual block partition, not an analogue schematic or a prescription to split ground planes, remove safety earth or require separate power supplies. Arrows labelled power identify functional supply paths, not galvanic barriers. Neither 1G operation nor a non-retimed module guarantees a particular analogue result.

    Status: Current v0.2 explanatory workflow. Source sections: 4.2, 5.1, 5.2, 6.3, 7.1.

    Download editable Mermaid source

  13. 30Stereo coherence without separate optical left and right linksv0.2 explanation
    Workflow diagram 30: Stereo coherence without separate optical left and right links

    Left and right occupy one indexed group in the same framed stream. After validation and buffering, the receiver releases both under a common audio cadence. Separate internal converter lanes do not require separate optical data links.

    Discarding unrelated malformed or foreign traffic must not mute an admitted stream. Only a confirmed active-stream condition invokes its protection policy. Common transport scheduling does not establish identical analogue channel delays or automatically align two independent DAC chassis.

    Status: Current v0.2 explanatory workflow. Source sections: WP 4.2, WP 5.6-5.7, WP 6.1.

    Download editable Mermaid source

Group 02

Clock and flow control

Receiver timing, credits, packet deadlines, reference loss and source-rate cases.

  1. 09Receiver ownership of conversion timingv0.2 explanation
    Workflow diagram 9: Receiver ownership of conversion timing

    The optical receive path recovers transport symbols and validates complete frames. An independently engineered audio clock subsystem sets FIFO read timing and conversion cadence. Cumulative credits regulate delivery over the return fibre.

    This is clock ownership, not a claim of zero jitter. Local supply coupling, clock-domain crossings and buffer faults still need validation. A 10 MHz input is mandatory on o2at-reference receivers, optional on o2at-basic, and does not discipline Ethernet or USB signalling clocks. The control arrow represents actual group retirement, not direct sampling of an unsafe cross-domain counter.

    Status: Current v0.2 explanatory workflow. Source sections: §6.1, §6.2, §6.3, §7.1.

    Download editable Mermaid source

  2. 10Clock preparation and the START acceptance gatev0.2 explanation
    Workflow diagram 10: Clock preparation and the START acceptance gate

    OPEN may acquire the selected clock, while PING can expose acquisition progress. START succeeds only with valid conversion timing and, in common-reference mode, an established frequency relationship. Audio follows the acknowledgement and respects the initial cumulative grant.

    clock_mode declares receiver-paced or established common-reference operation; it does not itself define an internal/external clock-source selection command. The diagram assumes that source selection has been configured through an implementation-defined mechanism. Shared frequency does not establish a shared sample epoch or zero jitter. The short-stream exception to ordinary prefill is omitted: complete final audio plus matching END can permit earlier playout.

    Status: Current v0.2 explanatory workflow. Source sections: §5.5, §5.6, §6.2, §6.3.

    Download editable Mermaid source

  3. 11Finite holdover and local protection after reference lossv0.2 explanation
    Workflow diagram 11: Finite holdover and local protection after reference loss

    A reference failure can enter holdover only while conversion timing remains valid and the declared time and FIFO limits remain satisfied. Otherwise the receiver mutes and aborts locally. STATUS is best effort and never delays protection; recovery after abort uses a new session.

    The source requires controlled clock transitions but does not specify a complete same-session relock state machine after a reference returns. This diagram deliberately covers bounded holdover and fault restart, without inventing automatic relock or a live clock-mode switch. Exact validity thresholds and holdover drift limits require a documented, measured clock implementation.

    Status: Current v0.2 explanatory workflow. Source sections: §5.5, §5.6, §6.3, §6.5, §6.6.

    Download editable Mermaid source

  4. 12Three source rate-control casesv0.2 explanation
    Workflow diagram 12: Three source rate-control cases

    Receiver credits regulate link delivery in every admitted mode. They can pace an elastic producer, but an independent fixed-rate live source needs a real clock relationship or explicitly selected conversion. A finite FIFO cannot absorb sustained rate mismatch indefinitely.

    The conversion branch identifies a possible system remedy, not a rate-conversion algorithm or profile implemented by v0.2. Shared-reference operation still needs bounded burst and FIFO accounting, and shared frequency does not define the sample epoch. IEEE 802.3x PAUSE is supplementary adjacent-link control, not an end-to-end producer-rate servo.

    Status: Current v0.2 explanatory workflow. Source sections: §5.6, §6.4, §6.5.

    Download editable Mermaid source

  5. 13Cumulative receiver credits and actual consumptionv0.2 explanation
    Workflow diagram 13: Cumulative receiver credits and actual consumption

    The source may send only when sent_end_group + packet_groups <= grant_end_group. The receiver honours already granted space, including groups in flight, and updates consumed_groups from actual audio-side retirement. Grants cannot be retracted; repeated and older notifications do not create extra credit.

    The diagram abstracts control/session validation and the clock gate, which must already have passed. It does not prescribe a new numerical grant formula. Credit accounting must include validated storage, current occupancy and outstanding data; the latest cumulative grant is repeated within the negotiated interval. Clock-domain transfer of retirement counters needs a coherent implementation.

    Status: Current v0.2 explanatory workflow. Source sections: §5.5, §5.6, §6.5.

    Download editable Mermaid source

  6. 14A packet gap retains its original playout deadlinev0.2 explanation
    Workflow diagram 14: A packet gap retains its original playout deadline

    A later packet can wait in a qualified bounded reorder buffer while an earlier range is missing. If that range misses its original playout deadline, the basic profile safely mutes and aborts. Duplicate and late audio is discarded without replaying samples or closing the timing gap.

    Reordering support is optional and must fit the admitted window. The successful branch represents delayed delivery, not mandatory audio retransmission. Concealment would need a future explicitly negotiated policy. Safe DSD protection means converter mute or a validated idle/transition sequence, not blindly substituting all-zero bits.

    Status: Current v0.2 explanatory workflow. Source sections: §5.6, §6.5, §7.1.

    Download editable Mermaid source

Group 03

Interfaces, operations and review

Possible bridges, diagnostics, validation, interoperability and contribution processes.

  1. 15Proposed asynchronous USB audio to o2at feedback bridgeProposed workflow
    Workflow diagram 15: Proposed asynchronous USB audio to o2at feedback bridge

    A proposed bridge compares downstream cumulative group consumption with its observed USB microframe count, filters bounded reporting variation and regulates source-buffer occupancy. Feedback changes the host's average sample delivery while the receiver retains conversion-clock authority.

    This is a proposed bridge, not a documented internal schematic of the N30SA, existing LAiV µDDC or Harmony DAC. The µDDC relationship between external reference and USB feedback remains undocumented in the reviewed public specifications. PCM and vendor-specific native DSD require explicit USB-unit mappings, endpoint/driver qualification and loop-stability tests. O2AT capacity does not prove that USB ingress or the DAC egress supports the same extreme formats.

    Status: Proposed bridge derived from v0.2. Source sections: §5.5, §5.6, §6.1, §6.4, §7.3, §7.4.

    Download editable Mermaid source

  2. 16Admission decision for a proposed legacy PCM input bridgeProposed workflow
    Workflow diagram 16: Admission decision for a proposed legacy PCM input bridge

    Legacy live inputs continue at their originating device's rate and cannot consume o2at credits. A proposed bridge must qualify framing and channel order, then establish a real coherent audio-clock relationship or use an explicitly selected conversion path before normal O2AT admission.

    This is a conditional design decision, not an implemented ADAT, S/MUX or source-clock-tracking profile. The PCM scope does not add an opaque compressed-audio transport. A future tracking profile needs its own estimator, servo and jitter-transfer specification; it must not connect the recovered optical serial clock directly to D/A conversion. Buffering and PAUSE alone cannot stabilise an independent unpausable source.

    Status: Proposed bridge derived from v0.2. Source sections: §4.3, §5.6, §6.4, §6.5.

    Download editable Mermaid source

  3. 21Link, session and clock diagnosticsv0.2 explanation
    Workflow diagram 21: Link, session and clock diagnostics

    A physical link, an admitted audio session and valid conversion timing are separate states. Present all three clearly, show only verified format capabilities, and expose counters and the qualified latency configuration when diagnosing a fault.

    Display updates and best-effort STATUS delivery must never delay local safe mute or abort. Declared holdover is valid only within its clock and FIFO bounds. Diagnostic access may be local or optional; a management application is not required for basic direct playback.

    Status: Current v0.2 explanatory workflow. Source sections: 5.1, 5.6, 6.5, 8.

    Download editable Mermaid source

  4. 22Proposed prototype validation workflowProposed workflow
    Workflow diagram 22: Proposed prototype validation workflow

    Editorial workflow recommendation, not a normative protocol message sequence. Establish test vectors and acceptance criteria, implement the path, measure it, inject faults and publish reproducible evidence with its limitations.

    The order is a recommended project workflow, not an additional conformance requirement. It makes no claim that a working O2AT prototype, independent peer review or completed performance measurements exist. Extreme-rate transport tests do not establish that an existing USB source or DAC supports those rates.

    Status: Proposed editorial or release workflow. Source sections: 7.2, 7.3, 9.2, 9.4.

    Download editable Mermaid source

  5. 23Proposed interoperability and release gatesProposed workflow
    Workflow diagram 23: Proposed interoperability and release gates

    Editorial workflow recommendation, not a normative protocol message sequence. The proposed programme requires independent interoperability evidence, qualified baseline optics and resolved output-safety failures. Fabric claims require a documented switched configuration, and public commercial deployment needs a proper protocol identifier. Any proposed clock-transfer extension also needs an explicit timing specification and independent path qualification.

    The two-source and two-receiver criterion follows the measurable validation programme in section 9.2. EtherType 0x88B5 remains experimental. Passing these project gates does not confer external standards approval, legal clearance or manufacturer endorsement, and the governance process remains proposed. The conditional clock-transfer gate is an editorial extension of the release programme, not a requirement already defined in v0.2. Packet interoperability alone does not establish timing-reference continuity through switches, and a dedicated clock path may bypass them.

    Status: Proposed editorial or release workflow. Source sections: 5.3, 9.2, 9.3, 9.4.

    Download editable Mermaid source

  6. 24Proposed contribution and change controlProposed workflow
    Workflow diagram 24: Proposed contribution and change control

    Editorial workflow recommendation, not a normative protocol message sequence. Contributions identify the affected draft and evidence, receive compatibility and licence review, and lead to a recorded decision. Accepted changes update the relevant specification, registry, tests and release history.

    The submission fields and review ordering are website governance recommendations derived from the paper, not adopted policy or evidence that a formal governing organisation exists. Proposed open licences and third-party obligations must remain distinct; no licence is presented as patent clearance or certification.

    Status: Proposed editorial or release workflow. Source sections: 4.2, 9.3, 9.4.

    Download editable Mermaid source

Group 04

Proposed timing extensions and clock hub

Future Type 1 and Type 2 timing concepts, plus a proposed clock-hub role. These are not adopted v0.2 wire requirements.

  1. 25Type 1: integrated audio and forward frequency referenceProposed extension
    Workflow diagram 25: Type 1: integrated audio and forward frequency reference

    Proposed Type 1: the transport's audio master has a defined relationship to the continuous forward optical line. The DAC disciplines a local audio oscillator from the recovered reference, then reads the FIFO and performs conversion with that local clock. The ordinary return control path remains present.

    One pipe here means one logical duplex connection, not a claim that all traffic travels in one physical fibre. This frequency-transfer mechanism is not defined by v0.2. Directly connecting a raw CDR output to the converter is not proposed. Clock ratios, noise transfer, holdover and capability signalling require specification and qualification. The nominal Ethernet rate remains fixed; a sample-rate change alters the declared synthesis/divider relationship, not the Ethernet link speed.

    Status: Proposed optical clock-transfer extension. Source sections: Proposed extension, WP 6.1-6.3, E01.

    Download editable Mermaid source

  2. 26Type 2: DAC-master timing returned to the transportProposed extension
    Workflow diagram 26: Type 2: DAC-master timing returned to the transport

    Proposed Type 2: the DAC clock governs local FIFO reads and conversion, and sends a reference upstream. The transport follows that reference for audio production and sends both stereo channels together within the receiver's cumulative credit grant.

    This is a logical architecture. The dotted control arrow does not imply a third physical fibre: its carriage must be defined by the chosen implementation, as illustrated in diagrams 27 and 28. Frequency coherence does not establish a shared sample epoch, eliminate all jitter or remove finite-buffer protection. No new wire-profile identifier is allocated here.

    Status: Proposed optical clock-transfer extension. Source sections: Proposed extension, WP 5.6, WP 6.1-6.5.

    Download editable Mermaid source

  3. 27Type 2 candidate A: frequency transfer over the reverse Ethernet lineProposed extension
    Workflow diagram 27: Type 2 candidate A: frequency transfer over the reverse Ethernet line

    Candidate A retains valid 1000BASE-X signalling in both directions. The DAC's reverse transmitter follows a qualified frequency relationship to its audio clock. The transport extracts the continuous line reference before any elasticity that would replace it with a local clock, cleans it and disciplines audio production. Reverse control frames continue normally.

    The reverse fibre is not an unmodulated raw-clock wire: it carries an encoded Ethernet line with control traffic and idle symbols, and clock recovery remains necessary. Preserve Ethernet tolerances, auto-negotiation and link fault behaviour. Use a direct path or separately qualified frequency-aware topology. This diagram does not assert SyncE compliance, a completed clock plan or a measured implementation. Never feed the forward recovered reference back into the DAC master loop. The nominal Ethernet rate remains fixed; a sample-rate change alters the declared synthesis/divider relationship, not the Ethernet link speed.

    Status: Proposed optical clock-transfer extension. Source sections: Proposed extension, WP 5.1, WP 5.6, WP 6.1, E01, E02.

    Download editable Mermaid source

  4. 28Type 2 candidate B: a genuinely separate optical reference linkProposed extension
    Workflow diagram 28: Type 2 candidate B: a genuinely separate optical reference link

    Candidate B keeps the existing duplex data link intact and adds a dedicated DAC-to-transport optical reference path. The reference can bypass the packet switch. The data link continues carrying stereo audio in one direction and receiver control in the other.

    This requires additional optical hardware and fibre unless a separately specified multiplexing scheme is introduced. The clock channel needs its own waveform or encoding, optical and electrical limits, rate range, duty-cycle behaviour, acquisition, loss detection and jitter budget. An ordinary SFP data sheet does not automatically qualify raw 10 MHz, word-clock or I2S transmission.

    Status: Proposed optical clock-transfer extension. Source sections: Proposed extension, WP 5.1, WP 5.6, WP 6.3, E03.

    Download editable Mermaid source

  5. 29Proposed Type 2 acquisition, holdover and fault workflowProposed extension
    Workflow diagram 29: Proposed Type 2 acquisition, holdover and fault workflow

    The proposed extension establishes one DAC master, verifies the transport's recovered reference and frequency ratio, and then uses the existing START, credit and prefill model. A disturbed reference may continue only within declared clock and FIFO limits. Local protection precedes a non-blocking fault-report attempt and session retirement.

    This is a design workflow, not a defined new wire sequence. Endpoint readiness exchange and fault-report details remain to be specified. Each endpoint protects its own resources; a remote endpoint cannot react to an unreported fault before receiving evidence or reaching its own deadline. A reference-tier receiver follows v0.2's best-effort STATUS rule using the active session binding before retirement, without delaying local mute.

    Status: Proposed optical clock-transfer extension. Source sections: Proposed extension workflow, WP 5.6, WP 6.3-6.5.

    Download editable Mermaid source

  6. 31Proposed clock generator and optical reference hubProposed extension
    Workflow diagram 31: Proposed clock generator and optical reference hub

    The proposed hub offers separately engineered 50 Ω and 75 Ω 10 MHz BNC output classes and an SFP-terminated optical reference service. The selected source remains the frequency authority in Type 1, while the DAC remains the downstream audio-clock authority in Type 2. This adds a device role, not a third architecture.

    The optical clock service is not defined by v0.2 and no wire allocation, optical waveform or existing product conformance is implied. A normal SFP module is not automatically suitable for an arbitrary raw 10 MHz signal. Each BNC class requires its own matched driver, specified load and amplitude convention; an adapter does not change impedance. BNC shields can create conductive paths even when the audio connection is optical. No manufacturer participation or endorsement is asserted.

    Status: Proposed clock-hub device role and service. Source sections: Whitepaper §6.2, Whitepaper §6.3, Proposed clock-hub device role and optical reference extension.

    Download editable Mermaid source

  7. 32Recommended Type 2 hierarchy with a clock hubProposed extension
    Workflow diagram 32: Recommended Type 2 hierarchy with a clock hub

    The hub disciplines the DAC's local audio clock. The DAC then originates the timing reference followed by the transport, which sends stereo audio within receiver grants. The DAC requires a suitable hub-reference input and a distinct transport-facing interface. Forward audio, returned timing and returned control are separate logical services.

    The timing and control arrows do not allocate an additional channel within current v0.2. Their physical carriage must be defined by a qualified future profile, such as the reverse Ethernet frequency-transfer candidate or a separate optical timing path. One ordinary SFP port cannot independently terminate both a hub link and a transport link. The diagram is a functional view and does not prescribe a specific transceiver or PLL. The Type 1 counterpart would instead discipline the source authority; it must not create a competing DAC-to-source clock loop. Shared frequency does not establish phase or sample-epoch alignment.

    Status: Proposed clock-hub device role and service. Source sections: Whitepaper §5.5, Whitepaper §5.6, Whitepaper §6.1, Whitepaper §6.2, Whitepaper §6.4, Proposed Type 2 clock-transfer and clock-hub extensions.

    Download editable Mermaid source

  8. 33Acceptance of an actual reference-discipline designProposed extension
    Workflow diagram 33: Acceptance of an actual reference-discipline design

    Optical transport can remove a conductive reference path, but effective discipline depends on the real clock path, programmed ratios, loop design and operating conditions. Qualification separately measures relative drift, FIFO behaviour, phase noise and absolute accuracy. Absolute accuracy requires an independent reference.

    A shared source can suppress relative frequency error in a properly implemented hierarchy without eliminating source frequency error, residual loop noise or startup phase ambiguity. Measurements of two clocks derived from the same reference do not establish that reference's absolute accuracy. Phase-noise integration limits, timing-error definitions and acceptance bounds must be declared. This is a proposed validation workflow, not evidence that a particular hub or O2AT prototype has passed it.

    Status: Proposed clock-hub device role and service. Source sections: Whitepaper §6.1, Whitepaper §6.2, Whitepaper §6.3, Whitepaper §6.5, Whitepaper §6.6, Proposed clock-hub and optical reference qualification.

    Download editable Mermaid source

  9. 34Reference loss and explicit recovery in a proposed hub hierarchyProposed extension
    Workflow diagram 34: Reference loss and explicit recovery in a proposed hub hierarchy

    Each affected endpoint monitors its required local audio clock and buffer limits. Holdover can retain operation only within declared valid timing and finite FIFO margins. Invalidity or expiry triggers local mute or source stop and abort, followed by a non-blocking fault-report attempt, retirement, explicit reacquisition and a new session.

    The STATUS attempt never waits for delivery and cannot delay local protection. Remote endpoints retain their own clock, liveness and playout-deadline protection even if the notification is lost. Hub-originated reporting and follower-readiness signalling are not new v0.2 wire allocations; a future profile must define their carriage. Clock-state changes within valid holdover still require the applicable status reporting. A returned reference does not by itself authorise resumption, and no automatic switch to an unrelated master is implied. The short-stream prefill exception remains applicable.

    Status: Proposed clock-hub device role and service. Source sections: Whitepaper §5.5, Whitepaper §5.6, Whitepaper §6.3, Whitepaper §6.5, Whitepaper §6.6, Proposed clock-hub and Type 1/Type 2 recovery extension.

    Download editable Mermaid source