Blockcast

omar@blockcast.net

wit moq MMT MMTP MoQ ATSC 3.0 FEC This document specifies the use of MPEG Media Transport (MMT) as a container format for Media over QUIC (MoQ). MMT carries media over broadcast (ATSC 3.0, ARIB STD-B60), multicast, and unicast (QUIC/WebTransport) networks. This specification defines the mapping of MMT packets to MoQ objects, interaction with Application-Layer FEC, the derivation of MoQ catalogs from MMTP signaling, and compatibility considerations for both ATSC 3.0 and ARIB STD-B60 systems.

Introduction MPEG Media Transport (MMT) is a transport protocol designed for delivery of multimedia content over heterogeneous networks. MMT is supported as a transport in ATSC 3.0 broadcast television (Americas, South Korea), and is the basis for ARIB STD-B60 (Japan). MMT provides native support for:

• Media Processing Units (MPU, branded "mpuf" in the ISO Base Media File Format (ISOBMFF) ) as the media container, with structural similarities to fMP4
• Application-Layer FEC (AL-FEC) supporting multiple schemes including RaptorQ and Reed-Solomon
• Cross-layer signaling for adaptive streaming
• Hybrid delivery combining broadcast and broadband

This document defines how MMT-encapsulated media can be transported over MoQ , enabling:

1. Broadcast-to-Unicast bridging: Content from ATSC 3.0 or ARIB STD-B60 broadcasts can be relayed to MoQ subscribers without transcoding
2. FEC: MMT's AL-FEC integrates with MoQ FEC repair tracks per
3. Multicast promotion: MoQ clients can receive Source-Specific Multicast (SSM) directly when available, per
4. Broadcast signaling: Derive MoQ catalogs from MMTP signaling (Section 12.2)

Relationship to Other MoQ Media Formats This specification complements existing MoQ packaging formats. The MOQT Streaming Format (MSF) carries media packaged with the Low Overhead Media Container (LOC) , and CMSF carries media packaged in the Common Media Application Format (CMAF):

Format	Container	Primary Use Case	FEC Block Profile
MSF (LOC)	WebCodecs chunks	Low-latency unicast	"moq-object-v1"
CMSF	CMAF fMP4	Adaptive streaming	"moq-object-v1"
This spec (MMT)	MMTP + MPU (ISOBMFF)	Broadcast bridge	"iso-ssbg1-v1"

The last column names the block profile under which protects tracks of each packaging. Under "iso-ssbg1-v1" each FEC source packet (FEC Type 1) is one source symbol. Under "moq-object-v1" each loc or cmaf object whose Object Status is Normal occupies whole source symbols. MMT packaging fits these cases:

• Ingesting ATSC 3.0 or ARIB STD-B60 broadcasts
• FEC protection is required for multicast delivery
• Hybrid broadcast/unicast architectures are deployed
• Interoperability with broadcast receivers is needed

CMAF packaging (CMSF) fits these cases:

• Content originates as DASH/HLS
• No multicast delivery is planned
• Interoperability with existing CDN infrastructure is needed

Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. MMTP: MMT Protocol - the packet layer of MMT (ISO 23008-1 Clause 9) MPU: Media Processing Unit - a generic container for independently decodable timed or non-timed data ( Clause 3.1.14) MFU: Media Fragment Unit - a sample or subsample of timed media data, or an item of non-timed media data, within an MPU ( Clause 9.3.1) AL-FEC: Application-Layer Forward Error Correction AU: Access Unit SLT: Service Layer Table - ATSC 3.0 bootstrap signaling MPT: MMT Package Table - signaling table containing MMT asset info PA: Package Access - the signaling message that carries the tables a receiver needs to consume a Package, among them the MPT ( Clause 10.3.2) MPI: Media Presentation Information - signalling table carrying the presentation information document ( Clause 10.3.8)

MMT Overview MMT uses a layered architecture:

MMTP Header Format The fixed fields sum to 96 bits (three 32-bit words). Byte 0 is version(2) | packet_counter_flag(1) | FEC_type(2) | reserved(1) | extension_flag(1) | RAP_flag(1); byte 1 is reserved(2) | type(6), i.e. the packet type occupies the low six bits of the second byte ( Clause 9.2). Senders MUST set all reserved bits in the MMTP packet header to zero. Receivers MUST ignore their values after validating the header; they MUST NOT assign private semantics to reserved bits. Every packet of an MMTP packet flow -- media, repair, and signaling packets alike, on every delivery path -- MUST set the packet counter flag C to 0, so no packet carries the Packet Counter field. Clause 9.2.3 requires all packets of an MMTP flow to share one setting of C; this profile fixes that setting at 0. The MMTP packet header is therefore 12 bytes unless X = 1 adds a header extension. This document profiles MMTP version 0 (V = 00) of ISO/IEC 23008-1:2023 as amended by Amd 1:2025. A packet whose version is not 00 MUST be rejected before its type field is parsed: version 1 uses a different type-field layout and is not defined by this profile. The C = 0 requirement above is also a conformance gate; packets with C = 1 MUST be rejected. An X = 1 header extension is parsed according to its declared length, but this document defines no additional version or packet-counter semantics. Key fields for MoQ mapping:

• Packet ID: Maps to MoQ track within namespace. This document reserves packet_id 0 for the MMTP signaling flow: MMTP packets of packet type 0x02 carrying signaling messages, such as the PA message of a multicast endpoint flow ( Section 5) and the AL-FEC message of Section 8.3. No MoQ track is advertised for the signaling flow, but an mmtp source track MAY carry its AL-FEC message as an object (Section 8). An MMTP packet carrying media (packet type 0x00) or a repair symbol (packet type 0x03) MUST NOT use packet_id 0; a track's packet_id is in the range 1..65535, and on multicast delivery it is the packetId the endpoint advertises for the track ( Section 4.1). On every delivery path, a receiver MUST NOT deliver an MMTP packet on packet_id 0 to a media or repair decoder, including one received as the payload of an object of a media or repair track: a receiver that processes MMTP signaling reads it as a signaling message, and any other receiver discards it ( Section 5 states the same rule for every unlisted packet_id on multicast)
• Timestamp: UTC wallclock send time in the NTP short format of Section 6 (32 bits: 16-bit seconds and 16-bit fraction, relative to the NTP epoch), carried inside the object payload. MoQ Transport defines no per-object timestamp field; receivers needing the send time read it from the preserved MMTP packet header. Because the seconds part is 16 bits, the value wraps every 65 536 seconds (about 18.2 hours): it identifies the send time modulo that period and MUST NOT be interpreted as an absolute wallclock time without an out-of-band era reference. It is used for packet delivery and jitter measurement and is never media time: not a decoding timestamp, presentation timestamp, duration, media-clock epoch, or movie-fragment identifier
• Packet Sequence Number: per-packet_id, incremented by one modulo 2^32 across the flow ( Clause 9.2.3); carried inside the object payload for wrap-aware MMTP-layer loss/ordering detection. It is not the MoQ Object ID. Object IDs number the objects of a group in source order, starting at zero in each group (Section 4.6).
• FEC Type: 0=no AL-FEC, 1=AL-FEC source packet (exactly one 4-byte Source FEC Payload ID trails the packet, Section 8.5), 2=AL-FEC repair packet for FEC payload ID mode 0, 3=AL-FEC repair packet for FEC payload ID mode 1 (not used by this mapping) ( Clause 9.2.3)
• RAP Flag: 1 indicates Random Access Point. On a track that the catalog protects with a keyframe overlay, a packet with RAP_flag 1 also carries the overlay's SS_ID in a header extension of type 0x8B01 ( Section 8.5.1)

A signaling packet (packet type 0x02, on packet_id 0) MUST carry its messages in the signaling message mode of Clause 9.3.4: its MMTP payload begins with the 2-byte payload header of Clause 9.3.4.2: When A = 1, a MSG_length field of 16 bits, or 32 bits when H = 1, precedes each aggregated message; when A = 0 no MSG_length field is present. The signaling message follows ( Clause 10.2), beginning with its message_id. A packet that carries one complete signaling message without aggregation has f_i = 00, A = 0, and frag_count = 0, and its sender sets H = 0 (H has no effect when A = 0), so its payload header is the two bytes 0x00 0x00 and the message_id immediately follows them. A receiver ignores H when A = 0 and parses the header field by field, never by matching those two bytes.

MoQ Object Mapping

Track Structure An MMT stream maps to MoQ tracks as follows:

MMT Component	MoQ Mapping
Package	Namespace
Asset, by Packet ID (video)	Track "video"
Asset, by Packet ID (audio)	Track "audio"
MPU (one MPU per group)	Group; number derived from media time (Section 4.4.1)
MPU data unit (FT=0, FT=1, or FT=2)	Subgroup ID
MMTP packet (fragment) within a data unit	Object; Object IDs count the group's objects from 0 in source order (Section 4.6)
AL-FEC signaling message (OPTIONAL, packet_id 0)	Object in Subgroup 0 immediately before FT=0 (Section 8)
AL-FEC repair	Track "video/repair"

Section 6 maps each object to a new stream. An mmtp track does not follow that rule. It maps each MPU data unit to one subgroup (Section 4.3), and the objects of a subgroup share one stream ( Section 2.2), so each data unit's fragments travel in order on one stream. An mmtp track keeps the Group and Object numbering of Sections 6.1 and 6.2: Group numbers are unique and increase monotonically (Section 4.4.1), and Object IDs start at zero in each group and increase by one (Section 4.6).

Object Payload Each MoQ object carries one complete MMTP packet: The object payload begins at byte zero of the preserved MMTP packet header. It has no MoQ-private envelope, length prefix, harness prefix, or other undocumented bytes before that header. For an FEC Type 1 packet, the Source FEC Payload ID and any profile-defined MMTP header extensions remain in their specified wire locations. No object-layer prefix, suffix, or private replacement for those fields is permitted. When requires the FEC Source Info Object Property (type 0x11), its value remains the four-byte, network-byte-order SS_ID defined by that document; the property is object metadata and is not inserted into this payload. The one exception is the OPTIONAL AL-FEC signaling object of Section 8: its payload is a complete MMTP signaling packet (packet type 0x02) on packet_id 0 with FEC Type 0. Its MMTP payload is the signaling message payload header of Section 3.1 followed by one complete AL-FEC message (f_i = 00, A = 0), rather than an MPU-mode payload header and data-unit fragment, and it carries no Source FEC Payload ID. No other object on an mmtp source track uses packet type 0x02 or packet_id 0. Throughout this document, "MMTP packet" means the header-included wire unit and "MMTP payload" means the bytes that follow the packet header, per . Both MMTP header layers are always preserved: the packet header carries the FEC Type, RAP Flag, and timestamp, and the MPU-mode payload header (the first bytes of the MMTP payload) carries the Fragmentation Indicator and MPU sequence number that receivers and the FEC layer depend on. A publisher that wishes to deliver raw ISOBMFF fragments without MMTP encapsulation publishes the track with CMAF packaging instead. In this profile an MPU can contain one or more ISOBMFF movie fragments: FT=1 carries one movie fragment's metadata and each FT=2 data unit carries one whole sample or one producer-authored subsample of a sample (Section 5.2.1).

Group Boundaries This section defines the object layout of mfu mode (mmtpMode: "mfu", Section 12.1). Group boundaries align with MPU boundaries, and subgroup boundaries align with MPU data-unit boundaries:

• Each group contains all objects of exactly one MPU: a change of MPU sequence number starts a new group, numbered per Section 4.4.1.
• Subgroup 0 of each group carries exactly one complete FT=0 MPU metadata packet. Its data unit contains the authored initialization boxes, including ftyp, mmpu, and moov, and uses FI=0. When the publisher carries the OPTIONAL AL-FEC signaling object of Section 8, that object is in Subgroup 0 of the same group and is the object immediately before the FT=0 object; Subgroup 0 then carries exactly these two objects. No other object precedes FT=0, and a group carries at most one signaling object.
• Subgroups 1..M each carry exactly one subsequent MPU data unit in authored order. An FT=1 movie-fragment-metadata data unit is one complete FI=0 object. An FT=2 timed sample is either one FI=0 object or an FI=1, zero-or-more FI=2, FI=3 object chain. A timed sample whose media exceeds one data unit's capacity is carried as a contiguous run of producer-authored subsample data units (Section 5.2.1), one subgroup per subsample data unit, in ascending offset order. Section 5.2 defines the only permitted fragmentation state machine.
• A timed MPU MUST publish its single FT=0 metadata data unit before any FT=1 or FT=2 data unit; only the OPTIONAL signaling object of Section 8 may precede FT=0. It then MUST publish each FT=1 data unit before every FT=2 sample or subsample that references that movie fragment. If an MPU contains multiple movie fragments, the sequence repeats as FT=1 followed by its FT=2 samples. A receiver MUST validate and process subgroups in ascending Subgroup ID, not network arrival order, and MUST NOT admit an FT=2 sample before its FT=1 metadata: concurrently delivered subgroups MAY arrive in any order and are buffered until their turn. A missing or duplicate FT=0 invalidates the group; a gap, duplicate data-unit identity, or invalid FT=1/FT=2 sequence in that logical order invalidates the affected movie fragment. A receiver MUST NOT infer the missing structure. The signaling object is not a data unit: its presence or absence does not affect this validation, and a signaling object anywhere other than immediately before FT=0 in Subgroup 0, or a second one in a group, invalidates the group.
• The FI=0 or FI=1 object that begins the first FT=2 sample of each timed group -- for a subsample-partitioned sample, the object that begins its offset-0 data unit -- MUST have RAP Flag = 1.

The MPU sequence number remains present in-band (in the MMTP payload header of every MPU fragment) and delimits which packets belong to the same group, but it is not the MoQ Group number. Publishers MUST NOT copy the MPU sequence number into the Group number, and subscribers MUST NOT derive media time or switching decisions from it. (The MPU sequence number is a per-Asset counter. It starts at zero for the first MPU in an Asset and increments by one for every following MPU ( Clause 7.3.3), but it is Asset-local: independently packetized renditions need not assign the same MPU number to the same media instant. Counter-based group numbering therefore cannot satisfy the switching-set alignment requirements of Section 4.4.) For an ISOBMFF source, the publisher MUST preserve initialization in FT=0, MUST copy the authored moof and the original mdat prefix through the byte before the first media sample byte-for-byte into FT=1, and MUST copy the referenced sample bytes byte-for-byte and without transformation into FT=2. A receiver can therefore reconstruct the authored movie fragment without synthesizing box fields, sample timing, or media bytes (Section 5.1). Mapping each data unit to its own subgroup makes a complete metadata unit or sample the unit of in-order delivery, loss, and FEC. A publisher MUST send the objects of an mmtp track in subgroups, not as datagrams: a datagram object belongs to no subgroup ( Section 2.2) and cannot carry this mapping. Subgroups can be delivered concurrently, and a subgroup can still be lost, for example when its stream is reset on a delivery timeout ( Sections 5.2 and 11.3.2); the resulting gap invalidates the affected movie fragment rather than authorizing inferred metadata, timing, or cadence.

Switching Sets When multiple tracks represent alternative renditions of the same media (e.g., an adaptive bitrate (ABR) ladder), they form a switching set: a set of alternate tracks that MUST be time-aligned per Section 4.2 (the same construct that Section 3.2 applies to CMAF tracks). MoQ Group boundaries MUST be media-time-aligned across all tracks of a switching set so that subscribers can switch at group boundaries. Tracks with equal group durations MUST carry the same Group number for the same media interval. Only an intra-only mmtp track can have a shorter group duration than the other tracks, under the exception of Section 4.4.2, which also defines its Group number mapping. A cmaf member keeps equal group durations and the Group number alignment that Section 3.2 requires. The switch is without discontinuity when the MPUs are closed groups of pictures (GOPs). On a join or switch at a Group boundary, leading pictures (Section 4.4.1) that reference the preceding Group are not decodable, and presentation of the new track begins at its RAP. If the old track's next MPU has leading pictures, neither track has decodable pictures for their presentation interval, and the receiver conceals that gap. Switching-set membership is declared in the catalog via the per-track field: defined by Section 5.2.12: an integer identifying a group of tracks that are alternate versions of one another. Two tracks are members of the same switching set if and only if both carry the altGroup field and the values are equal. A track that omits altGroup is a member of no switching set, and the switching-set requirements of this section do not bind it. A repair track (Section 8.2) carries no altGroup. It is not an alternate rendition, and its Groups are FEC blocks ( Section 7.5), not media-time-aligned Groups. A subscriber finds the repair tracks of the rendition it selects through that rendition's fec.repairTrack and the depends fields of Section 5.1.1.

Group Number Formula The Group number of every mmtp-packaged track MUST be computed from media time by the formula in this section. This single definition is what makes group boundaries align across the renditions of a switching set. FEC interleave timing is independent of this grouping; Section 7.1 does not derive FEC block boundaries or a number of Groups per FEC block from this formula: where:

• ticks is the presentation timestamp (PTS) of the MPU's first AU in decode order, expressed in the track's timescale (Hz, Section 4.4.2) as a signed integer. That AU is first in the MPU payload, as ISO/IEC 23008-1 requires, and is the MPU's RAP (Section 4.3). Leading pictures, which follow the RAP in decode order but present before it, do not select ticks, even when they present within the preceding MPU's Group interval.
• groupDurationTicks is the per-track group duration expressed in the same timescale, as a positive integer. The catalog signals it either directly or through an exact millisecond conversion as specified in Section 4.4.2.
• presentationAnchorTicks is the signed timestamp in this track's timescale that corresponds to presentation time zero. It includes the publisher's edit-list, encoder-priming, and composition-time decisions, and MUST be applied before the formula. A track that is intended to be rendered with another audio or video track MUST signal this field; a track that is not part of a synchronized presentation MAY omit it and use zero as its local origin.

The publisher MUST choose presentationAnchorTicks no later than the smallest ticks value of the MPUs it admits for the track. If an MPU's ticks is earlier than the anchor, the publisher MUST reject that MPU. Before the first group is published, the publisher MAY instead revise the catalog anchor and validate the complete initial input again; after publication, the anchor is immutable for that track instance. It MUST NOT clamp the Group number to zero. The floor in the formula is mathematical floor (floor division), not truncation towards zero. With the anchor requirement, every admitted MPU has a non-negative relative_ticks value. The requirement binds ticks only; a leading picture of an admitted MPU can present before the anchor. Timeline origin: ticks is measured on the track's media presentation timeline; presentationAnchorTicks maps that track to the shared presentation timeline. For every set of audio and video tracks intended to be rendered together, the publisher MUST choose one presentation origin and MUST signal an anchor for each track such that has the same rational value for samples representing the same media instant. This is a media-time relation, not an NTP or wall-clock relation, and it is not the Timestamp field of the MMTP packet header (Section 3.1). For ISOBMFF-derived MPU content, the anchor is applied to the composition timeline after edit-list and priming adjustments. All tracks of a switching set MUST use the same presentation origin as well. A publisher that resets the timeline (a timeline discontinuity) MUST reset it identically, at the same media instant, across every affected audio, video, and switching-set track. A discontinuity on an existing track does not reset its Group number sequence. This Group anchor is a MoQ scheduling and switching key only. ISO/IEC 23008-1 presentation timing remains authoritative: the presentation time of an MPU is signaled by the presentation information (or the mpu_timestamp_descriptor when no presentation information is present), with any applicable elst offset, and is not rewritten by this Group number calculation. For each track, when the MPU changes, the computed Group number MUST be strictly greater than the Group number of the preceding admitted MPU. The publisher MUST NOT put two different MPUs in one Group, reuse a Group number, or alter authored timestamps to satisfy this rule. A publisher that restarts or declares a discontinuity MUST retain the last Group number for the existing track instance and resume with a greater number; numeric gaps are allowed. The publisher SHOULD signal the skipped numbers with the PRIOR_GROUP_ID_GAP Object Property ( Section 10.8), as Section 6.1 recommends. If it cannot resume with a greater number while preserving the formula and authored timing, it MUST close that track instance and start a new track with a distinct (namespace, track name) pair before emitting the reset MPU. That new identity is the Group-number scope for the restarted stream; it MUST NOT be presented as a continuation of the old track. Group-number state is transport state; this document defines no new catalog field for it. Because its Group numbers follow media time, an mmtp publisher cannot start a Group early. It MUST NOT set the DYNAMIC_GROUPS Track Property ( Section 10.6) to 1. For two tracks A and B, a receiver can verify that timestamps describe the same presentation instant without floating-point conversion: The group-duration agreement rule in this section applies after the same anchor conversion. Consequently, equal rational values of groupDurationTicks / timescale and correctly paired presentationAnchorTicks values are what align 30-fps video with audio; per-track timescale and groupDurationTicks values alone do not establish synchronization. All arithmetic is in integers: relative_ticks and groupDurationTicks are integers, floor(relative_ticks / groupDurationTicks) is integer division, and implementations MUST NOT compute the group number in floating point or apply any tolerance. An input held in another unit (seconds, milliseconds, a different timescale) MUST be converted to an exact integer tick count before the formula is applied; if that conversion is not exact, the publisher's timescale or group-duration choice is wrong (Section 4.4.2) -- implementations MUST NOT round to compensate. For ISOBMFF content, authored composition timestamps use the media track's mdhd timescale. If that differs from the catalog timescale, the publisher MUST convert the adjusted composition timestamps by the exact ratio timescale / mdhd.timescale before applying this formula. It MUST reject a timestamp that is not an integer in the selected catalog clock; it MUST NOT relabel media ticks as asset-clock ticks. Worked example. A switching set of two video renditions of the same content: rendition A with timescale: 90000, rendition B with timescale: 44100, both with presentationAnchorTicks: 0 and groupDurationMs: 2000 in the catalog (Section 4.4.2). The sample that is 10.5 seconds into the shared presentation timeline has an integer timestamp in both timescales: floor(945000 / 180000) = 5 B: relative_ticks = 463050 -> floor(463050 / 88200) = 5 ]]> Both renditions place the instant in group 5. No intermediate value is shared between the two computations -- only the integer results agree -- which is exactly the property group-boundary switching requires. Negative authored timestamps use the same rule and are not clamped. For one 90 kHz track with groupDurationTicks: 180000, choose the shared presentation anchor presentationAnchorTicks: -180000, which is earlier than the ticks of the first admitted MPU: group 0 MPU 1 ticks = 90000: relative_ticks = 270000 -> group 1 ]]> The negative authored PTS therefore maps to group 0 through the shared earlier anchor. A catalog with the same samples and presentationAnchorTicks: 0 is invalid for this profile; the publisher rejects MPU 0 instead of mapping it to group 0. With reordered samples, the first AU in decode order selects the Group number. This example lists the authored PTS values of the first three AUs of two consecutive MPUs in decode order. MPU 0 is a closed GOP. MPU 1 is an open GOP: its RAP presents at 180000, and its two leading pictures present before it, inside Group 0's interval: ticks is the first entry of each MPU's list. Selecting the minimum presented PTS instead would give ticks 0 and 174000, both in Group 0, which violates the strictly-greater rule above.

Catalog Signaling of Group Duration For a subscriber to apply the formula in Section 4.4.1, the catalog MUST publish the group duration for every mmtp-packaged track. The catalog publishes either the millisecond form or the exact tick form defined here: The timescale is the MSF timescale field ( Section 5.2.21), resolved per the track's packaging value ( Section 5.2.4; this document adds mmtp, Section 12.1):

packaging	Timescale source
mmtp	The timescale field, REQUIRED for mmtp tracks (Section 12.1); absence is a catalog error, and the 90 000 asset_timescale default of Clause 10.3.9.3 does not apply.
cmaf	The timescale field. Section 5.2.21 makes it optional, so this document makes it REQUIRED for any cmaf track to which this section applies (a member of a switching set governed by Section 4.4.1); leaving it unset on such a track is a catalog error.
loc	The timescale field. As for cmaf, this document makes it REQUIRED for any loc track to which this section applies; leaving it unset on such a track is a catalog error. When the publisher also sends the TIMESCALE Property ( Section 2.3.1.2) on such a track, its value MUST equal the field.
(unrecognized packaging)	1 000 000 (microseconds). This row covers track entries whose packaging value is unrecognized; the convention is fixed by this document and does not derive from . A track entry without packaging is malformed ( Section 5.2.4) and fails catalog validation (Section 6.1, step 1).

When groupDurationTicks is absent, conversion is groupDurationTicks = groupDurationMs * timescale / 1000. The catalog publisher MUST choose a groupDurationMs such that the resulting tick count is a positive integer and the conversion is exact (i.e. (groupDurationMs * timescale) % 1000 == 0). If this cannot be satisfied, or if the intended cadence is not an integer number of milliseconds, the catalog MUST publish ticks directly via the exact tick field: If both groupDurationMs and groupDurationTicks are present, groupDurationTicks wins and groupDurationMs is informational; it is not used in the conversion and need not have an exact millisecond conversion. Cases where the override is required include:

• An MPU group duration at a 30-per-second cadence (1/30 s = 33.333... ms): expressing this in integer ms is impossible. If the track timescale is divisible by 30, publishers set groupDurationTicks: timescale / 30 directly (e.g. 3000 at 90 000 Hz, 1500 at 45 000 Hz). A timescale not divisible by 30 cannot represent this cadence as an integer tick count and MUST be changed or rejected for this profile; it MUST NOT be rounded.
• Audio sample-rate timescales not divisible by 1000 Hz, such as 44 100 Hz: a 333 ms field would imply 333 x 44 100 / 1000 = 14 685.3 ticks. A publisher whose authored cadence is the exact integral cadence of 14 685 ticks MUST publish groupDurationTicks: 14685 (about 332.993 ms); it MUST NOT claim that this preserves an exact 333 ms duration. A publisher that requires exactly 333 ms MUST choose a compatible timescale or reject that cadence.

For example, this catalog uses the exact 30-per-second cadence on a 44 100 Hz track. It omits groupDurationMs because 33.333... ms is not an integer millisecond value: Switching-set agreement: every track in the same switching set MUST publish the same effective group duration as a rational number of seconds. Raw groupDurationTicks values need not be equal when track timescales differ. For tracks A and B, subscribers validate exact equality with integer arithmetic: One exception applies, to mmtp tracks only. An mmtp track is intra-only when its framerate field is present and its group duration is one frame period at that rate: Because framerate need not be an integer (29.97), this comparison is made within a relative tolerance of 10^-3 of timescale; a GOP track misses it by a factor of at least two. The tolerance only classifies a track as intra-only. It never enters Group number arithmetic: the remainder test below, the quotient n, and every Group number use exact integers, and Section 4.4.1 forbids any tolerance there. Every other track in the switching set, including every track whose packaging is not mmtp, is a GOP track. Exact equality above is required between all GOP tracks. An intra-only track I MAY instead publish a shorter group duration that divides that of the GOP tracks a whole number of times. For every GOP track G in the switching set: Since an intra-only track has a group boundary at every frame, each GOP group boundary is also one of its group boundaries, and switching remains group-aligned. With quotient n = (G.groupDurationTicks * I.timescale) / (I.groupDurationTicks * G.timescale) and a shared presentation anchor, Group g of G starts at the same instant as Group g * n of I. This mapping is the alternate mechanism that Section 4.2 requires for time-aligned tracks whose Group IDs differ at the same instant. A subscriber can therefore switch from G to I at any G group boundary. It can switch from I to G only at an I group whose number is a multiple of n. Each intra-only track is checked only against the GOP tracks, so switching between two intra-only tracks of one switching set is group-aligned only at GOP track group boundaries. The exception does not apply to a switching set with no GOP track: intra-only tracks with no GOP peer still require exact equality. For example, an mmtp 15 fps intra-only base track with timescale: 90000 and groupDurationTicks: 6000 may share a switching set with a 15 fps GOP track with timescale: 1000000 and groupDurationTicks: 1000000, because 1000000 * 90000 = 15 * (6000 * 1000000). With groupDurationTicks: 1050000 on the GOP track the remainder is non-zero and the catalog is invalid. Two GOP tracks with group durations of 2 s and 1 s are invalid even though one nests in the other. Subscribers SHOULD validate this at catalog load and, on disagreement, SHOULD reject the catalog and signal a catalog-validation error to the application. Subscribers that proceed despite disagreement are non-conformant for switching across the affected tracks; ABR transitions on such tracks will produce group-boundary discontinuities.

Catalog Signaling of Keyframe Interval The group duration above describes the cadence of MMTP media groups (one MPU per group, Section 4.3). It does not describe whether an MPU contains additional keyframes after its required group-start random access point. This document defines an OPTIONAL per-track field for the cadence of all keyframes, which the repair policy of Section 11.4.1 uses to classify FEC blocks: keyframeIntervalMs is the interval between consecutive video keyframes, in integer milliseconds. It is distinct from groupDurationMs: groupDurationMs is the duration of one MPU/group, whereas keyframeIntervalMs describes every keyframe, including any additional keyframes inside an MPU. When the only keyframes are the required group-start RAPs and group duration is constant, the two values are equal; additional RAPs can make the keyframe interval shorter. The field applies to video tracks only; a publisher that cannot determine the cadence simply omits it. Its absence is not a catalog error: subscribers MUST NOT reject a catalog solely because it is missing, and a receiver MUST NOT substitute a locally chosen or observed cadence for it. When present, keyframeIntervalMs MUST be a positive integer; a zero value is a catalog error. The repair policy of Section 11.4.1 relies on a published keyframe interval to exclude keyframes from part of a group, so when the field is present it binds every keyframe of the track: the publisher MUST NOT emit a keyframe other than at a group start or a whole number of intervals after one. A publisher whose encoder can place keyframes off that cadence, for example at scene cuts, omits the field. As with the group duration, the integer-millisecond form cannot express a keyframe cadence whose tick count is non-integer on the track's timescale. A publisher MAY publish an exact override: expressed in the same timescale as groupDurationTicks (Section 4.4.2, selected by the track's packaging). If both keyframeIntervalMs and keyframeIntervalTicks are present, keyframeIntervalTicks wins. Unlike groupDurationTicks, this document places no switching-set agreement requirement on the keyframe interval: it is a per-track hint, and tracks in a switching set MAY carry different keyframe cadences.

Init Segment Signaling Publishers signal MPU metadata inline as the complete FT=0 object in Subgroup 0 of every group (Section 4.3), preceded in that subgroup only by the OPTIONAL AL-FEC signaling object of Section 8. Its data unit contains the authored initialization boxes, including ftyp, mmpu, and moov. In addition, publishers SHOULD carry decoder initialization data in the catalog, using the mechanism of the base catalog that Section 3.1 also uses for CMAF headers. The data is an entry of the root initDataList array ( Section 5.1.7) whose type is "inline" and whose data is the base64 encoding of an ISOBMFF initialization segment (ftyp + moov) sufficient to initialize the decoder for the track (including the codec configuration record, e.g. avcC or hvcC). The track's initRef field ( Section 5.2.13) holds that entry's id. This lets a subscriber initialize its decoder at catalog load, before the first FT=0 MPU metadata object arrives, removing one delivery round trip from the join path (Section 6.1). A receiver ignores an initRef that names no entry, or names an entry whose type is not "inline", and joins without catalog initialization data. Catalog initialization data is a join optimization, not a replacement for in-band metadata: the per-group FT=0 MPU metadata remains authoritative, and a receiver MUST adopt in-band metadata when it differs from the catalog's initialization data. Catalog content is untrusted input; a receiver MUST validate that the decoded data is a well-formed ftyp + moov sequence before passing it to a decoder, and MUST discard it otherwise. Some implementations carry the same bytes in a per-track string field, initData, which does not define. A receiver MAY accept initData on an mmtp track and validates it in the same way. When a track carries both initRef and initData, the receiver uses initRef.

Object Identifier Assignment and Reconstruction The publisher numbers the objects of each group in source order, as Section 6.2 requires. The first object of the group has Object ID 0. It is the AL-FEC signaling object when the group carries one (Section 8), and the FT=0 object otherwise. Each later object, in whichever subgroup, has the Object ID of the object before it plus one. An Object ID therefore identifies one object of its group, as Section 2.1 requires, and the Subgroup ID still identifies the data unit (Section 4.3). The packetizer emits each data unit's packets contiguously (Section 5.2.2), and Subgroup IDs follow source order (Section 5.3.2), so ascending Object ID order within a group is also ascending Subgroup ID order. A FETCH or fill fetch stream, which sends a group's objects in Object ID order ( Section 3.2.1), therefore delivers them in the order that Section 4.3 requires. MoQ Transport carries Object IDs as deltas on the wire ( Sections 11.3.1 and 11.4.1.1), and the objects of every subgroup other than Subgroup 0 have Object IDs greater than zero. A receiver MUST reconstruct each object's absolute Object ID from that encoding. It MUST NOT assume that a subgroup's first Object ID is zero, that successive objects differ by a fixed step, or that an absolute Object ID is carried explicitly. Object IDs identify preserved source objects within a group; they do not replace the MMTP packet sequence, FI countdown, or active-data-unit association required by Sections 5.2 and 5.3.

Media Fragment Unit (MFU) Mode This timed-media profile transports each authored MPU data unit without rewriting it: For conformance, an mmtp track in this document carries timed media only. ISO/IEC 23008-1 Clause 9.3.2.3 defines the Timed Flag as indicating whether the MPU is timed or non-timed, independently of the FT value. Every MPU-mode packet with FT=0, FT=1, or FT=2 in this profile MUST carry T = 1; a packet with T = 0 MUST be rejected. Checking only FT=2 would leave metadata packets unchecked. The ISO non-timed DU identity and four-byte header remain outside this profile; no Item_ID-based mapping is defined here. FT=0 initializes the track, FT=1 supplies the authoritative movie fragment structure and sample table, and FT=2 supplies the exact bytes of each sample. That order is a decoder contract, not a hint.

Authored Movie-Fragment Timing For timed media, receivers MUST derive sample timing and layout only from the authored ISOBMFF metadata carried by FT=0 and FT=1:

1. FT=0 supplies the one media track's mdhd timescale and trex defaults. It MUST contain a usable mvex/trex for that track.
2. FT=1 begins with a byte-for-byte copy of the authored moof and carries a byte-for-byte copy of the original mdat prefix through the byte before the first media sample. This includes the original mdat header and any auxiliary sample information. The mfhd.sequence_number identifies the movie fragment referenced by subsequent timed-MFU DU headers.
3. For the traf whose tfhd.track_ID matches the independent media track's tkhd.track_ID, tfdt supplies the first decode time. Each sample duration and size is resolved using the ISOBMFF precedence rules across trun, tfhd, and trex; composition time is decode time plus the authored trun composition-time offset. Signed offsets MUST remain signed. Sample byte positions are resolved from the authored base-data-offset and trun.data_offset rules, not from a fixed mdat-header guess.
4. Each FT=2 timed DU identifies one sample -- or one producer-authored subsample of it -- by (MPU_sequence_number, movie_fragment_sequence_number, sample_number, offset). A whole-sample data unit carries offset zero; a subsample data unit (Section 5.2.1) carries the authored byte position of its first media byte within the sample. Section 5.3.3 defines sample completion.

A receiver MUST reject a missing or ambiguous media track, timescale, movie-fragment sequence, tfdt, or sample identity. It MUST also reject any sample duration, sample size, byte position, or composition offset that remains unresolved or invalid after applying all authored trun, tfhd, trex, and implicit ISOBMFF rules. An absent per-sample trun composition-time-offset resolves to zero, and an absent trun.data_offset is not by itself an error when the ISOBMFF base-data-offset and run-continuation rules resolve the byte position. The receiver MUST reject overlapping sample byte ranges, undeclared bytes, duplicate samples, duplicate or overlapping subsample data units (Section 5.2.1), and FT=2 media for which the governing FT=0 or FT=1 has not been accepted. It MUST NOT synthesize timing from the MMTP Timestamp, packet or MPU counters, MoQ Object IDs, arrival time, catalog cadence, codec frame-rate guesses, or previously observed samples. The MMTP Timestamp is a send time, not media time (Section 3.1). Any absolute MMT presentation anchor and edit-list offset are applied as specified by PI/MPU presentation signalling and ISOBMFF; a receiver without the required anchor MUST reject that timeline rather than silently omit the authored adjustment.

Fragmentation and Strict Active-DU Reassembly A single MFU can exceed the path MTU, but the ISO MPU-mode payload header does not permit an unbounded number of fragments. The 8-bit fragment_counter is the number of MMTP payloads containing fragments of the same data unit that succeed the current payload; it is not a modulo sequence number. A complete FI=0 data unit MUST carry zero. For a fragmented data unit carried in N payloads, where 2 <= N <= 256, the FI=1 payload MUST carry N - 1, every succeeding payload MUST decrement the value by one, and the FI=3 payload MUST carry zero. The counter MUST NOT wrap or repeat within a data unit. The mfu mapping defined here carries exactly one data unit per MMTP payload, so aggregation_flag MUST be zero. The upstream MMTP packetizer produces conformant data units, and an input MMTP flow used by this mapping MUST already satisfy the 256-payload bound for every data unit. In this profile an FT=2 timed data unit carries one whole sample, or exactly one producer-authored subsample of it (Section 5.2.1). A sample whose media exceeds one data unit's capacity MUST be partitioned into subsample data units by the origin packetizer per Section 5.2.1, before this mapping applies -- never by a relay and never by this mapping, which does not repacketize or subdivide an input data unit. Such a sample MUST NOT be carried by wrapping or extending the counter, silently truncated, or split into a second MPU, and an access unit MUST NOT be split across multiple MPUs ( Section 6.4). A publisher MUST reject a purported data unit that exceeds the bound, has an invalid countdown, or uses aggregation. It MUST NOT wrap or extend the counter, divide one data unit's overflow between subgroups, or synthesize MoQ Object IDs to make a non-conformant MMTP data unit appear valid. Each MMTP packet maps to exactly one MoQ object, and the publisher MUST NOT reassemble MFU fragments:

1. The publisher MUST publish each MMTP packet of a data unit as a separate object within that data unit's subgroup (Section 4.3), preserving the MMTP packet header and the MPU-mode payload header. Those headers carry the Fragmentation Indicator and MPU sequence number. Object IDs identify the preserved source packets within the group (Section 4.6) but are not MFU identities or media timestamps.
2. The publisher MUST NOT reassemble or reorder fragments based on the Fragmentation Indicator. It routes each packet to (track, group, subgroup) by packet_id, MPU boundary, data-unit type, and the strict active-DU state of Section 5.3: a change of MPU sequence number starts the next group (Section 4.3), and each distinct data unit within the group maps to its own subgroup as defined in Section 5.3.
3. The receiver MUST reassemble each data unit from the objects of its subgroup before media processing. After restoring serial packet order (Section 5.3.3), it applies the FI/counter state machine of Section 5.3:
   • A single object with FI=0 is a complete, unfragmented data unit; for FT=2 that data unit is one MFU.
   • FT=2 objects with FI=1 (first), FI=2 (zero or more middle), and FI=3 (last) reassemble, in that restored MMTP order, into one MFU by concatenating each fragment's media bytes, delimited as defined below.
   • The receiver MUST validate the fragment_counter countdown with the state machine of Section 5.3.2. Any missing, repeated, wrapped, or non-decrementing count invalidates the entire MFU.
   • The reassembled MFU's RAP flag is taken from its FI=1 (or FI=0) object.

The bytes concatenated are each fragment's media (data unit) bytes only -- not everything after the MMTP packet header. Every fragment begins with a 12-or-more-byte MMTP packet header. The receiver MUST parse the C and X flags, packet-counter presence, and header-extension length to locate the following 8-byte MPU-mode payload header; it MUST NOT assume a fixed offset of 12 bytes. The MPU-mode payload header contains, by Clause 9.3.2.3 name with this document's alias in parentheses, length (payload_length, 16), FT (fragment_type, 4), T (timed_flag, 1), f_i (fragmentation_indicator, 2), aggregation_flag (1), fragment_counter (8), and MPU_sequence_number (32); both headers are stripped from every fragment. The 16-bit payload_length field MUST be encoded and interpreted as the number of bytes following that field within the MPU payload, as defined by . It therefore includes the remaining six bytes of the 8-byte MPU-mode payload header. For FT=2 packets, the declared lengths are: DU_header_octets is 14 for timed media and 4 for non-timed media, and the right-hand side MUST NOT exceed the 16-bit maximum of 65535. A trailing Source FEC Payload ID is outside the declared MPU payload and MUST NOT be counted. A publisher MUST NOT encode a media-only or DU-plus-media length convention. A receiver MUST require the declared MPU payload to end exactly at the protected MPU boundary before the Source FEC Payload ID, when present. It MUST reject a declaration that is too short, cannot contain the required header bytes, extends beyond the available MPU payload bytes, leaves undeclared bytes before the outer trailer, or consumes that trailer. The DU header ( Figures 12 and 13: 14 bytes for timed media -- movie_fragment_sequence_number (32), sample_number (32), offset (32), priority (8), dep_counter (8) -- or 4 bytes for non-timed media) follows the payload header on an FI=0 object and on the FI=1 first fragment; it is likewise stripped rather than concatenated into the media stream. When the packet's FEC Type is 1, the trailing 4-byte Source FEC Payload ID ( Section 8.5) is excluded as well. 4. FT=0 and FT=1 MUST each be unaggregated, complete FI=0 data units with fragment_counter zero. Their payload length is six plus the metadata octets; they have no DU header. Fragmented or empty metadata is rejected by this profile. 5. The receiver MUST bound both in-flight data-unit memory and pending FT=1 sample records. At either bound it MUST reclaim a slot by evicting the least recently admitted incomplete record (an open data unit or a parked continuation run) and admit the new one; it rejects only when no such record exists. A record that has already completed is never a candidate. An incomplete data unit is discarded on declared discontinuity or unrecoverable loss and is never emitted. For very large frames where FEC cannot recover the loss, receivers SHOULD support resolution-tier fallback (subscribe to a lower-resolution track of the switching set and upscale) rather than stalling.

Subsample Data Units At a given packet size, one data unit carries at most 256 MMTP payloads of media. A single intra-coded 4K or 8K sample routinely exceeds that capacity. This section defines the only conformant way to carry such a sample: the origin packetizer partitions it into subsample data units, using the offset field that Section 9.3.2.3 already defines in the timed-MFU DU header. The partition is producer-authored and wire-stated; nothing about it is inferred. A subsample data unit is an ordinary FT=2 timed data unit: it has its own DU header, its own FI chain, and its own fragment_counter countdown bounded by 256 payloads (Section 5.2). Its identity is (packet_id, MPU_sequence_number, movie_fragment_sequence_number, sample_number, offset), where offset is the authored byte position of the data unit's first media byte within the sample. Origin packetizer requirements:

1. A packetizer MUST emit a sample as a single whole-sample data unit (offset zero) whenever the sample fits within one data unit's capacity. Subsample partitioning of a sample that fits is not conformant.
2. When partitioning, the first subsample data unit MUST carry offset zero and each subsequent one MUST carry an offset equal to the sum of the media lengths of all preceding subsample data units of that sample: offsets are strictly increasing, with no gap and no overlap.
3. Each subsample data unit of one sample MUST be published as its own subgroup per Section 5.3.2, contiguously per Section 5.2.2.
4. priority and dep_counter describe the sample and SHOULD be identical across its subsample data units.

Relays and this mapping MUST NOT create, merge, or re-partition subsample data units. Receiver sample assembly: a subsample-partitioned sample completes only when every one of its subsample data units has completed under the state machine of Section 5.3.2 and, ordered by offset, the data units begin at zero, are byte-adjacent (each offset equals the preceding offset plus the preceding data unit's media length), and their total media length equals the sample's authored size from the FT=1 record. A gap, overlap, duplicate offset, or length mismatch invalidates the sample; the receiver MUST NOT emit a partial sample or synthesize missing bytes. Completion is a protocol event -- every constituent subgroup complete -- and on reliable transport a receiver MUST NOT substitute timers, cadence, buffer occupancy, or successor arrival for it. On lossy paths each subsample data unit completes, possibly after FEC recovery ( Section 9), or is discarded as incomplete (Section 5.2, item 5), like any other data unit; no additional sample-level timer is defined or permitted. The sample's RAP flag is the RAP flag of the FI=0 or FI=1 object of its offset-0 data unit. FEC is unaffected by the partition: source symbols are MMTP packets (), and the packet stream's block and interleave structure does not depend on data-unit boundaries.

Source Contiguity does not prohibit a packetizer from emitting an unrelated payload of the same packet_id between two fragments of one data unit. This profile does prohibit it. An origin packetizer MUST emit every multi-packet unit on consecutive packet_sequence_number values of its packet_id, in authored order, with no other payload of that packet_id between its packets: the fragments of a data unit in FI order, and the subsample data units of one sample (Section 5.2.1) in ascending offset order. The sequence numbers of the FI=1 fragment, of each FI=2 fragment, and of the FI=3 fragment MUST be successive values under modulo-2^32 arithmetic. A data unit of a different packet_id MAY be emitted at any point, and a further data unit of the same packet_id MAY be emitted once that data unit's FI=3 fragment has been emitted, subject to the sample-level contiguity above. The requirement constrains the packetizer's emission order only. Loss or reordering on the path does not violate it: the receiver restores serial packet order before reassembly (Section 5.3.3). Repair carried on its own flow bears a different packet_id and therefore cannot interleave. A violating data unit never completes at the receiver, which associates continuations only through active data-unit state (Section 5.3) and evicts the stranded records without a protocol error (Section 5.2, item 5). A receiver MUST NOT relax association to tolerate such a producer: a continuation admitted into the wrong data unit corrupts media that would otherwise have been discarded.

Active Data-Unit Association and Subgroup Derivation Object IDs are transport coordinates, not an MMTP continuation key. A fragment recovered below the MoQ object layer has no Object ID, and Object IDs from two delivery paths are not comparable. The MMTP DU header is also not a per-fragment coordinate: this profile carries it only in the FI=0 or FI=1 payload ( Clause 9.3.2 does not specify whether FI=2 and FI=3 fragments repeat it). FI=2 and FI=3 continuations carry media bytes but no movie-fragment sequence, sample number, or sample offset. Consequently a receiver MUST associate continuations through the ordered, bounded active-data-unit state defined here. It MUST NOT use an MMTP Timestamp, MoQ Object ID, signaling identifier, packet arrival time or order, inferred byte offset, recently completed identity, or a (stream, MPU sequence number) pair or fragment counter alone as a fallback association.

First-Fragment Identity For an FT=2 first or complete fragment, defines a transport-independent data-unit identity in the DU header:

Object class	Data-unit identity
Timed-media MFU	packet_id, MPU_sequence_number, movie_fragment_sequence_number, sample_number, offset	Section 9.3.2.3
Non-timed media MFU	packet_id, MPU_sequence_number, Item_ID	Section 9.3.2.3

For this timed-media profile, offset MUST be zero for a whole-sample data unit and MUST equal the authored subsample byte position for a subsample data unit (Section 5.2.1); movie_fragment_sequence_number and sample_number MUST be non-zero, and MPU_sequence_number MAY be zero (indeed, ISO/IEC 23008-1 requires zero for the first MPU in an Asset). The packet_id MUST be non-zero: packet_id 0 is the MMTP signaling flow (Section 3.1) and carries no media data unit, so a receiver MUST reject an MPU-mode packet (packet type 0x00) on packet_id 0 rather than admit it to active state. A non-zero packet_id is validated in the scope of its MMTP session; on multicast delivery it is validated against the packetId values the endpoint advertises ( Section 5). A continuation inherits the accepted first-fragment identity from active state; it does not reconstruct or guess another copy of the DU header.

Subgroup Derivation Section 4.3 assigns Subgroup 0 to FT=0. The publisher assigns every following FT=1 or FT=2 data unit the next unused Subgroup ID in source order. All packets from one FI=1 through FI=3 chain share that ID. An FI=2 or FI=3 packet therefore remains in the subgroup opened by the immediately preceding FI=1 packet on the same packet_id; a new data unit MUST NOT interleave before the chain closes (Section 5.2.2). The publisher and receiver each maintain at most one active fragmented data unit per (packet_id, MPU_sequence_number) while processing subgroups in order:

1. FI=0 requires fragment_counter == 0 and no active data unit. For FT=2 it requires a valid DU header and represents the complete sample. FT=0 and FT=1 are permitted only in this form.
2. FI=1 requires no active data unit, a counter c in 1..255, and, for FT=2, a valid DU header. It creates active state containing the data-unit type, timed flag, full first-fragment identity, destination subgroup, and next_expected_counter = c - 1.
3. FI=2 requires exactly one matching active state and a non-zero counter equal to the next expected counter. It appends only the declared media bytes and decrements the expected counter.
4. FI=3 requires exactly one matching active state, next_expected_counter == 0, and a wire counter of zero. It appends the declared media bytes, closes the state, and emits the complete data unit only after all size and authored-timing checks succeed.

An FI=0 or FI=1 while state is active is an overlap. An FI=2 or FI=3 without it is an orphan. A changed packet ID, MPU sequence, FT, timed flag, subgroup, skipped/repeated counter, FI=2 at zero, or FI=3 before the expected counter reaches zero is a mismatch or gap. The receiver MUST reject all of these and MUST NOT advance, replace, or consume valid state or pending sample timing on rejection. A new MPU arriving while the prior MPU has an incomplete data unit declares loss and discontinuity; the incomplete unit is discarded and never emitted.

Receiver Admission and Completion A receiver admits a fragment only after its declared MPU payload boundary, outer FEC trailer, stream scope, subgroup order, and active-DU transition all validate. Duplicate packets may be dropped by exact MMTP packet identity before admission, but a duplicate MUST NOT create or advance active state. Multi-path combining and FEC recovery MUST restore the same per-packet_id serial packet order before this state machine, using modulo-2^32 serial-number arithmetic across packet_sequence_number wrap within a bounded replay window. The MMTP-session and MoQ-track scope are part of that ordering state; neither mechanism may fabricate a missing transition. Completion is transactional. For a whole-sample data unit the receiver first validates the full FI chain and the matching unconsumed FT=1 sample record; the reassembled FT=2 media length MUST equal that sample's authored size. For a subsample-partitioned sample it additionally requires every constituent subsample data unit to have completed, with the byte-adjacency and total-length checks of Section 5.2.1. Only then may it emit the sample and consume that record. Every (sample, offset) data unit is admitted at most once, and every described sample is emitted at most once. A failed check leaves every pre-existing valid state and timing record unchanged, except that an explicitly declared discontinuity discards the incomplete prior unit.

Random Access and Priority An MPU begins at a Stream Access Point: the first access unit of an MPU is a random access point (RAP) ( Section 6.4; Section 4.3). Accordingly a receiver:

• SHOULD gate the start of media decoding on the availability of a complete RAP MFU, including a RAP MFU completed by FEC recovery; and
• SHOULD prioritize FEC recovery and retention of fragments whose DU header carries a higher priority or dep_counter value (Section 5.2; the subsample_priority and dependency_counter of Section 9.3.2.3), since these are decode-order roots upon which other access units depend.

On a multicast or Automatic Multicast Tunneling (AMT) leg, Section 11.4 specifies the receiver repair policy this implies.

Subscriber Join and Relay Behavior This section defines the join procedure for subscribers. A subscriber reaches its first decodable frame without waiting for the next group boundary by joining at the start of the current group with the fill mechanism of Section 3.5. The join needs no relay behavior beyond , and relays never parse MMTP (Section 6.2).

Subscriber Join Procedure A subscriber joins a live mmtp-packaged track as follows:

1. Catalog. Subscribe to the catalog track (the track named catalog, Section 12) as Section 5 requires, joining at the start of its current group ( Section 3.5), and validate the catalog. Validation includes the per-track REQUIRED fields of Section 12.1. A subscriber MUST NOT issue SUBSCRIBE for a track whose catalog entry fails validation. It also applies the switching-set agreement check of Section 4.4.2 and handles a disagreement as that section specifies.
2. Decoder initialization. If the catalog provides initialization data for the track (Section 4.5) and that data validates, initialize the decoder from it immediately. In all cases the subscriber MUST accept the authoritative FT=0 object in Subgroup 0 before admitting this group's FT=1 or FT=2 data units. An AL-FEC signaling object that precedes FT=0 in Subgroup 0 (Section 8) is not decoder initialization and does not satisfy this step.
3. Subscribe at a group boundary. Join at the start of the current group, as Section 3.5 describes. Send SUBSCRIBE with a LOCATION_FILTER of type 0x05 (Next Object) and a FILL_PARAMETERS parameter whose LOCATION_FILTER has type 0x01 (Relative Start) and StartGroup = 1 ( Sections 3.4, 9.20.9, and 9.20.15). The publisher sends the current group, from its start up to the Largest Object, on a fill fetch stream, and every later object on the subscription, so each object arrives once. The group start carries FT=0 initialization (Subgroup 0), the FT=1 metadata governing the first samples, and the RAP-bearing first FT=2 subgroup (Section 4.3); a subscription that starts mid-group without a fill yields objects that cannot be decoded until the next group. A data unit that was still open at the join arrives partly on the fill fetch stream and partly on its subgroup stream, and the receiver combines the two before reassembly (Section 5.2). If the fill fails or leaves a gap, the subscriber waits for the next group, which the subscription delivers from its start. A subscriber that does not want the current group sends SUBSCRIBE with a LOCATION_FILTER of type 0x01 and StartGroup = 0 instead. A NEW_GROUP_REQUEST ( Section 9.20.19) cannot shorten that wait (Section 4.4.1).
4. Repair track. If the subscriber wants FEC protection and the catalog signals FEC for the track, it SHOULD subscribe to the repair track (Section 8.2) at the same time as the source track, so that the first FEC block spanning the join point is repairable. Repair-track subscription is selective and optional ( Section 6.2).
5. Presentation gate. A subscriber MUST NOT submit media to the decoder until it has (a) accepted the authoritative FT=0 and FT=1 data units and (b) a completely reassembled FT=2 sample whose RAP flag is set (Section 5.2). Objects received before that point are buffered or discarded according to the receiver's reassembly bounds.
6. Loss and discontinuity. If a RAP MFU is discarded under unrepairable loss (Section 5.2), the subscriber MUST treat the track as discontinuous and MUST NOT resume presentation before the next completely reassembled RAP MFU (normally the start of the next group). The same holds when the group's FT=0 data unit, or the FT=1 data unit governing its RAP, is lost, since the RAP then cannot be admitted (Section 4.3). On a multicast or AMT leg, loss that spares those three data units does not make the track discontinuous; Section 11.4 specifies its handling.

Relay Retention for Late Joiners This section is informative. A relay serves the fill fetch stream of Section 6.1 from its cache, and fetches from upstream the objects it does not hold ( Sections 3.2.3 and 3.4). A relay that caches the current group of each track it serves can therefore start a late joiner without an upstream round trip. The join needs no mmtp-specific relay behavior. A fill fetch stream sends a group's objects in Object ID order, which is source order on an mmtp track (Section 4.6), so it delivers Subgroup 0 and each metadata subgroup before the FT=2 subgroups that depend on them, and the relay does not parse MMTP. Retention of groups older than the current group (for example to serve FETCH-based catch-up) is permitted but out of scope for this document.

FEC Integration MMT's AL-FEC framework supports multiple FEC schemes, with the MMT FEC codes specified in and parameters signaled via MMTP signaling messages (Section 8.3); neither the framework nor ATSC 3.0, which uses it for MMTP sessions ( Section 8.1.2.5), requires a particular code, so the codes are specified by : "reed-solomon", the Reed-Solomon code of Clause 6, is the mandatory-to-implement scheme, and RaptorQ is OPTIONAL ( Section 4.3). FEC repair uses the model defined in :

Interleaving Interleaving and typical interleave windows (interleaveDepthMs) follow Section 9. A positive interleaveDepthMs is the elapsed source/repair send-span bound for each actual FEC block; it does not select FEC block boundaries, derive a number of groups per block, or require a fixed relationship between an FEC block and a media Group. Absent and zero values follow Section 5.1 and do not supply an elapsed-time deadline. A typical window for ARIB STD-B60 content is 2000 ms.

OTI Signaling MoQ carries no RaptorQ Object Transmission Information (OTI, Section 3.3) in-session: receivers derive it per block from the catalog fec fields and the block's SSB_length per Section 4.2. The AL-FEC message of an MMTP session (Section 8.3) carries none either ( Section 7.3).

FEC Parameter Signaling FEC parameters for mmtp-packaged tracks are signaled in the catalog fec object, defined normatively in Section 5, which is authoritative for MoQ receivers ( Section 5.2). A MoQ receiver requires no in-session FEC signaling: the catalog carries every FEC parameter it needs. This document does not redefine the catalog fields but specifies MMT-specific considerations for their use. A publisher MAY also carry the MMTP AL-FEC signaling message of Section 8.3 on a MoQ mmtp source track, as an object whose payload is an MMTP signaling packet on packet_id 0 (Section 3.1). When present, it is published in Subgroup 0 of an MPU group as the object immediately before, and in the same subgroup as, that group's FT=0 object, and a group carries at most one such object (Sections 4.2 and 4.3). On a MoQ track such an object is a redundant in-band copy of catalog state: the message MUST NOT signal FEC parameters that contradict the track's catalog fec object, and where the two disagree the catalog governs. The object carries no media data unit and no repair symbol, so a MoQ receiver MUST NOT deliver it to a media or repair decoder (Section 3.1); a receiver that does not process MMTP signaling discards it. The signaling object is not an FEC source symbol. Its MMTP packet has FEC Type 0 and no Source FEC Payload ID; it is not protected by any repair symbol, is not counted in any FEC block or in sourceSymbols (K), and has no SS_ID and no Encoding Symbol ID. Because it occupies an Object ID (Object ID 0 of its group, Section 4.6), Object IDs on an mmtp source track are not positions in the FEC block: a receiver MUST take each source symbol's SS_ID from the Source FEC Payload ID that trails its FEC Type 1 packet ( Section 8.5), never from its Object ID, and places the symbol in its block by that SS_ID ( Section 8.3). A MoQ track carries only the signaling packets its publisher chose to place on that track, so the packet_sequence_number values it exhibits on packet_id 0 need not be contiguous. A receiver MUST NOT infer loss from a packet_sequence_number gap on packet_id 0 of a MoQ track, and MUST NOT defer any packet, including a later packet on packet_id 0, behind such a gap.

MMT-Specific FEC Parameters When used with MMT packaging, the catalog fec fields map as follows:

• algorithm: the value whose code point the MMTP AL-FEC message carries in fec_code_id_for_repair_flow (Section 8.3)
• blockProfile: "iso-ssbg1-v1" ( Section 5.1), the ISO 23008-1 Annex C block profile, for which an AL-FEC message carries the coding byte 0x14 (Section 8.3); REQUIRED when algorithm is not "none"
• sourceSymbols: The largest number of MMTP packets (source symbols) that an FEC block may hold; each block holds SSB_length of them ( Section 7.4). On the MMT path the canonical FEC source symbol is one whole MMTP packet, before its Source FEC Payload ID, framed with its length ( Section 7.3)
• interleaveDepthMs: When positive, the elapsed source/repair send span bound of each actual FEC block, as defined by Section 5.1; that section also defines absent and zero values. It is independent of groupDurationMs and does not imply a block count or block boundary from MoQ Groups. When ingesting broadcast content, use the ISO protection-window signaling or a known source/repair send-span bound. A source-frame count alone does not bound the actual packet send span.

See for the complete catalog field definitions, the algorithm registry, and the OTI derivation.

Repair Tracks A source track's repair tracks are the track its fec.repairTrack names and the tracks that name it in depends ( Section 5.1.1); Section 6.1 gives their conventional names. Subscription to them follows Section 6.2, and their priorities Section 10.

FEC Signaling for Multicast Delivery For SSM and Any-Source Multicast (ASM) delivery there is no bidirectional signaling channel. FEC parameters reach multicast receivers via:

1. MoQ Catalog Extension (authoritative for MoQ receivers, Section 5.2): out-of-band delivery in the catalog fec object (see the worked catalog of Section 5.1.2).
2. MMTP AL-FEC Signaling (message_id=0x0203): in-band delivery of the AL-FEC message of Clause C.6, with Table C.3 as replaced by , for ISO/IEC 23008-1 receivers that consume the flow without the catalog, such as native broadcast (ATSC 3.0, ARIB STD-B60) receivers. A publisher that sends this message MUST carry it in an MMTP signaling packet (packet type 0x02) on packet_id 0, the MMTP signaling flow, after the signaling message payload header of Clause 9.3.4.2 (Section 3.1); on multicast delivery it shares the multicast group of the media it describes, and on MoQ delivery it MAY be carried as an object of an mmtp source track under the rules of Section 8. No track is advertised on packet_id 0 ( Section 4.1), and a receiver does not deliver these packets to a media or repair decoder (Section 3.1; Section 5)

Each FEC source flow has one FEC encoded flow ( Clause C.6.3), so the message describes a source track's flow as one entry of the message's fec_flow_descriptor naming exactly one repair flow, the track's layer-0 repair track ( Section 6.3). For a track whose fec.blockProfile is "iso-ssbg1-v1", that entry carries:

• a number_of_assets of 1, the one Asset it lists being the source track's, the Asset whose packet_id is the track's: an FEC source flow of may carry the packets of several Assets (its Clause C.1), where an FEC instance of protects one source track (its Section 6.3);
• the coding byte 0x14, that is fec_coding_structure 0001 (one-stage), ssbg_mode 01, ffsrpts_flag 0 and fec_payload_id_mode 0 ( Section 7.3);
• as its fec_code_id_for_repair_flow, the code point that Table 1 assigns to the code that the track's fec.algorithm names: 3, the "6330 code" (RaptorQ), for "raptorq", and 1, the Reed-Solomon code, for "reed-solomon";
• as its repair_flow_id, the packet_id of the layer-0 repair packets. makes this field 16 bits in the one-stage branch, where the 2023 edition of Table C.3 gives it 8 bits and so cannot name a repair packet_id above 255;
• as its length_of_repair_symbol, the track's fec.symbolSize (T), the byte length of every repair symbol and, under ssbg_mode1, of every source symbol ( Sections 5.1, 7.1 and 7.3), and as its num_of_repair_symbol_per_packet 1, the one repair symbol each repair packet carries ( Section 7.1), a field whose semantics Clause C.6.3 gives for ssbg_mode2 alone;
• as its maximum_k_for_repair_flow, the track's fec.sourceSymbols: like that field, it bounds each block's SSB_length and is not the size of any particular block ( Section 7.4); and
• as its maximum_p_for_repair_flow, the RSB_length that every repair packet of the track's FEC instance carries: the total repair count over the published layers, which is the track's fec.repairSymbols while layer 0 is the only published layer ( Section 6.3.2). A publisher that appends a layer ( Section 6.3.9) raises that total and sends a new version of the message carrying it only after the last repair packet generated under the previous total, of whichever block: a block's RSB_length is the total in force when its repair symbols were generated ( Section 7.1), so every repair packet sent after the new version carries a value no lower than the field it names. The path keeps no order between the message, on packet_id 0, and the repair flow (Section 5.2.2), so a receiver of both can take a packet generated under the previous total after the new version; the blocks generated under the raised total follow every block generated under the previous one in the serial order of their SS_Start ( Section 7.5), as its Section 6.3.9 requires of the publisher, which the conversion rule of Section 12.2 relies on instead.

A publisher MUST NOT describe a repair layer above layer 0, or a keyframe overlay, in the message, whether in that entry or in an entry of its own: the one-stage coding structure names one repair flow per FEC encoded flow, the overlay protects a RAP subset that no packet_id identifies, and only the catalog declares either ( Sections 6.3, 6.4 and 8.5.1).

Multicast Integration MMT content can be delivered via IP multicast (SSM, AMT) and TreeDN . Platform-specific delivery paths, the multicast endpoint catalog extension, and TreeDN/AMT integration are defined in , and the multicast packet format in its Section 5.

ARIB STD-B60 Compatibility ARIB STD-B60 (Japan's MMT-based broadcasting standard) uses the same ISO 23008-1 foundation as ATSC 3.0. Publishers SHOULD preserve the original FEC parameters when ingesting ARIB STD-B60 content.

Clock Reference ARIB STD-B60 uses the MMTP Timestamp of Section 3.1: the UTC send time of the packet in NTP short format.

Transport Hierarchy Clients SHOULD attempt transports in the preference order that Section 3 defines for native and browser clients. AL-FEC (Section 7) is the loss recovery on SSM/AMT paths, which have no retransmission.

Catalog Signaling The MoQ catalog indicates MMT packaging and multicast endpoints. The catalog of this suite is an MSF catalog: the root object and its fields (version, generatedAt, tracks, ...), the requirement that parsers ignore fields they do not understand, and the base per-track fields are those of Section 5. The catalog is delivered as a MoQ track whose case-sensitive Track Name is catalog ( Section 5). The documents of this suite extend the base in the same manner as extends it: this document adds the packaging value mmtp and the mmtp track fields (Section 12.1), adds the per-track fec object and the fec-repair packaging value, and adds the root-level multicast member. Every catalog field this suite uses is defined either by or locally by a document of this suite (with cmaf tracks per ); no field is defined by any other catalog specification.

Packaging Value and Track Fields This document defines a single packaging value: carried in the per-track packaging field of the catalog ( Section 5.2.4). The value extends the allowed packaging values of that specification in the same manner as the cmaf value of Section 3.5.1; see Section 14 for the registry request. Object payloads of an mmtp-packaged track are whole MMTP packets per Section 4.2. Per-track catalog fields for mmtp packaging:

Field	Status	Type	Description
packaging	REQUIRED	String	MUST be "mmtp"
mmtpMode	REQUIRED	String	MUST be "mfu" (Section 5); defined by this document
timescale	REQUIRED	Number	Media timescale in Hz ( Section 5.2.21, profiled REQUIRED here; Section 4.4.2)
presentationAnchorTicks	REQUIRED for synchronized audio/video tracks	Signed integer	Track timestamp corresponding to shared presentation time zero (Section 4.4.1); defined by this document
groupDurationMs	Conditional	Number	REQUIRED without the tick form; positive integer ms (Section 4.4.2); informational when ticks are present
groupDurationTicks	OPTIONAL	Number	Positive exact group duration in track ticks; authoritative when present (Section 4.4.2); defined by this document
altGroup	OPTIONAL	Number	Switching-set membership key ( Section 5.2.12, profiled in Section 4.4)
keyframeIntervalMs	OPTIONAL	Number	Keyframe/GOP cadence, integer ms; video only (Section 4.4.3); defined by this document
keyframeIntervalTicks	OPTIONAL	Number	Integer-tick override for the keyframe interval (Section 4.4.3); defined by this document
initRef	OPTIONAL	String	id of the root initDataList entry, of type "inline", that holds the base64 ftyp+moov init segment ( Sections 5.1.7 and 5.2.13, profiled in Section 4.5)
fec	OPTIONAL	Object	AL-FEC parameters, defined in Section 5 (Section 8)

All other base track fields of Section 5.2 apply unchanged. In particular name and the rendition parameters -- codec ( Section 5.2.18; required for media tracks per that section), framerate, width, height, samplerate, channelConfig, bitrate, and lang -- are flat, top-level fields of the track object. mmtpMode selects the object layout and MUST be "mfu". It delivers one subgroup per FT=0, FT=1, or FT=2 data unit as defined in Sections 4.3 and 5. A subscriber MUST reject a track whose mmtpMode is absent or has any other value; the object layout cannot be inferred safely from received objects. Example, with the data value shortened:

MMTP Signaling to MoQ Catalog Conversion This section is informative: it documents how a converter that ingests an MMTP broadcast service, an ATSC 3.0 MMTP session ( Section 8.1.2.1) or an ARIB STD-B60 service, derives a MoQ catalog from the MMT signaling, and imposes no interoperability requirements on MoQ publishers or subscribers. A converter's output catalog is subject to the normative catalog requirements of Section 12.1 like any other catalog. The MP table gives the location of each Asset ( Clause 10.3.9) and the AL-FEC message the FEC parameters of each protected flow ( Annex C.6; Section 8.3 gives the fields a MoQ publisher sets, which a converter reads back). The multicast field in the output uses the multicast endpoint format of Section 4.1. Conversion rules:

• each MMTP session the MP table locates by its source address, destination address and destination port -> one multicast.endpoints[] entry (sourceAddress, groupAddress, port), and the Assets it carries -> that endpoint's tracks[]
• each Asset -> a track whose packetId is the Asset's packet_id, unique within the session ( Section 8.1.2.1.1) and carried by every packet of the flow, so a converter cannot renumber it. Section 4.1 requires each packetId value to denote one sub-flow across all endpoints of a sending entity and reserves 0 for the signaling flow, so a converter publishes sessions whose packet_ids collide under different namespaces, and never advertises a track on packet_id 0
• the AL-FEC message's entry for a flow -> the track's fec object: algorithm from fec_code_id_for_repair_flow, "reed-solomon" for code point 1 and "raptorq" for 3, symbolSize (T) from length_of_repair_symbol, sourceSymbols (K) from maximum_k_for_repair_flow, repairSymbols (P) from maximum_p_for_repair_flow, and a repair track, named in fec.repairTrack, whose packetId is the packet_id that repair_flow_id names (Section 8.3). The converter accepts an entry whose number_of_assets is 1, whose coding byte is 0x14 and whose fec_code_id_for_repair_flow is 1 or 3: a source flow of several Assets ( Clause C.1) is one block sequence over the packets of several packet_ids, which no FEC instance of protects (its Section 6.3 protects one source track), a flow under any other coding structure, ssbg_mode, FFSRP_TS or FEC payload ID mode is not one that "iso-ssbg1-v1" describes ( Section 7.3), a session whose message names any other code is outside until its registry lists that code (its Section 12), and the conversion of such a flow fails. The one repair flow the one-stage entry names is the track's layer 0, and maximum_p_for_repair_flow is its P while layer 0 is the only published layer, as in a one-stage session of , whose one repair flow carries the block's whole repair count. That field bounds the repair count of a block ( Clause C.6.3: the maximum allowed number of repair symbols in a repair symbol block) where "iso-ssbg1-v1" carries P as the RSB_length of every repair packet ( Section 7.1), on which every receiver holding the highest layer the converter lists (below) fails closed when a packet of that layer, where it is above 0, or of a block at or after (in the serial order of Section 7.5) one of which it has received a repair packet carrying at least the value, carries less than the O_i + P_i its catalog derives for that layer, the field itself (its Section 6.3.9), so the converter, which receives the flow's repair packets before it lists the repair track (below), lists it only once it has received a repair packet of the flow carrying an RSB_length of at least the field of the version it holds, and fails the conversion of a flow whose repair packets carry an RSB_length below that field on a block at or after, in the serial order of their SS_Start ( Section 7.5), one of which it has received a repair packet carrying at least the field: such a flow is not one "iso-ssbg1-v1" describes. A block before that one whose repair packets carry less was generated under the previous total, after whose last repair packet a publisher that appends a layer sends the raised field (Section 8.3) but which the path, keeping no order between the message and the repair flow (Section 5.2.2), can deliver after it; and a flow no block of which carries at least the field is one the converter never lists. Such a packet of an earlier block, below the repairSymbols the catalog gives layer 0 (below) where the layers the converter lists above 0 count less than the appended one, fails a receiver of the catalog closed on nothing: the clause of Section 6.3.9 for a packet of a layer's own track applies to layers above 0 alone, layer 0's coordinates depending on no count, and its anchored clause, which anchors a held layer on a block of which the receiver has received a repair packet carrying at least that layer's O_i + P_i, for layer 0 its repairSymbols (the field where the converter lists none above 0), treats such a packet as the conforming packet it is, every block generated under a total below a layer's O_i + P_i preceding, in the serial order of its Section 7.5, every block generated under one at or above it (its Section 6.3.9, which has a publisher apply a raised total from a block onward in that order and lower none), on the repair track the converter publishes as on the session's own endpoint, which carries the sender's packets and from which the converter withholds nothing. An RSB_length above the field is the append case of the next sentence. A MoQ publisher that appended a layer ( Section 6.3.9) sends the raised total in that field (Section 8.3) while the named flow carries only the P_0 symbols of each block ( Section 6.3.2), and neither the message nor the MP table describes the layers above, so the converter sets repairSymbols to maximum_p_for_repair_flow less the repairSymbols of every layer above 0 that it lists, and lists a layer it learns from provisioning only where provisioning places it, with every other layer it lists, above every layer it does not list, the topmost layers of the publisher's set: layer 0's repairSymbols is then the publisher's total below the lowest layer it lists above 0 (the whole field where it lists none) and each listed layer's O_i ( Section 6.3.2) is the publisher's, while listing a layer above which lies one the converter does not list would give it an O_i that is not the publisher's, which no check detects, and an O_i + P_i that its own-track packets generated before the append of the layer it does not list fall below (its Section 6.3.9). One that lists none publishes the whole field, which overstates layer 0's count, and the loss tolerance a receiver derives from it, by the layers it does not list. The converter keeps the repairSymbols it first published for a track, and those of every layer it has listed, for as long as it publishes the track: a later version of the message that raises maximum_p_for_repair_flow changes nothing in its catalog by itself, since Section 6.3.9 forbids changing the repairSymbols of a published layer while any receiver may still be consuming the source track, and says that a receiver reading the smaller bound excludes only symbols of layers it has not joined. A layer above 0 that the converter learns from provisioning after it published the track, one that provisioning places next above the highest layer the converter lists, the publisher having appended it after the converter read the field with no layer the converter has not learned below it, so that its O_i, the total of every layer below it ( Section 6.3.2), is the total the catalog derives for the highest layer listed before it, layer 0's repairSymbols plus those of every layer above 0 listed before it, and the field of the version it holds has risen by at least that layer's repairSymbols, it appends at the next index (its Section 6.3.9): its symbols' RS_IDs run upward from that total, and its O_i + P_i is at most the field, which every block generated under the raised total carries. The field's rise alone places no layer, a field risen by more than a layer's repairSymbols counting a layer the converter has not learned, which can lie below the learned one. A layer that provisioning does not so place, or whose symbols the field the converter first read already counted, it lists only by retiring the source encoding and publishing the source track and its repair tracks as a separate rendition that lists it, since appending it would give it an O_i that is not the publisher's, which no check detects, or an O_i + P_i above the wire RSB_length, on which every receiver joining it fails closed (that section), while lowering layer 0's repairSymbols to fit it is the change that section forbids. A later version that lowers maximum_p_for_repair_flow below the total its catalog derives for the highest layer it lists, layer 0's repairSymbols plus those of every layer above 0 it lists, is a change that section lets no publisher make, on which a receiver holding the highest layer it lists fails closed on the first packet of that layer, where it is above 0, or of a block at or after, in that serial order, one of which it has received a repair packet carrying at least that total, whose RSB_length falls below the O_i + P_i its catalog derives for that layer, which is that total, and one that no such packet reaches, the check anchored on no block it received or, holding that layer alone, reached by no repair packet after the change, learns of the change only at the next catalog refresh (that section), so the converter retires the source encoding and publishes the source track and its repair tracks as a separate rendition carrying the lowered value, as that section has a publisher that must retire a layer do; a repair packet whose RSB_length falls below that total once the track is published, on a block at or after, in that serial order, one of which it has received a repair packet carrying at least that total, is the same violation and has the converter retire the source encoding in the same way, the separate rendition listing the repair track as the first listing did, once a repair packet of the flow received after that one carries at least the field of the version it then holds, as the violating packet, below the field of the version held when it arrived, did not. The conversion of a flow fails where the fec object it would yield fails a catalog rule of Sections 5.1 and 6.3.4, on which a receiver fails closed: a maximum_p_for_repair_flow of 0 names no repair flow a catalog can publish ( Section 5.1 requires a repairSymbols of at least 1 when a repair track is published), a maximum_k_for_repair_flow of 0 names no block (a sourceSymbols of at least 1), and a length_of_repair_symbol below 14 names a symbol that protects no MMTP packet under the T - 2 construction of Section 7.3, whose protected packet begins with the 12-octet MMTP packet header of Section 3.1 (a symbolSize of at least 14 under "iso-ssbg1-v1"); an entry that names code point 3 with a length_of_repair_symbol that is not a multiple of 8 names a T no "raptorq" track can carry ( Section 4.2 fixes the Symbol Alignment at 8, which an MMTP session, carrying no OTI, does not impose on its symbol length), one with maximum_k_for_repair_flow above 56403 fails rule 6 of Section 6.3.4, and one with maximum_k_for_repair_flow plus maximum_p_for_repair_flow above 2^24 names an ESI no instance can produce (rule 5, which bounds K + totalP - 1 by 2^24 - 1, a sum the two 24-bit fields can exceed); and an entry that names code point 1 with maximum_k_for_repair_flow plus maximum_p_for_repair_flow above 255 names a block no "reed-solomon" instance can hold (rule 12, which bounds K plus the repair count of every layer). The conversion also fails for a flow whose repair_flow_id is 0, the signaling flow (Section 3.1), the flow's own packet_id, or the packet_id of another track of the session, a value that Section 4.1 requires to denote one sub-flow (a repair flow carries a packet_id of its own, Clause C.6.3), and for the flows of any two entries that name one repair_flow_id or list one Asset: two source tracks naming one repair track, or two fec objects for one track, are shapes no FEC instance of has, a repair packet belonging to the instance of the track it arrived on (its Section 6.4.1). The message names the repair flow by packet_id without a location, and the MP table does not list it ( Section 5), so the converter lists the repair track in the tracks[] of each endpoint on whose session it receives packets of that packet_id, which is where a receiver without the catalog finds them; a repair-only endpoint ( Section 6.3.6) is one the converter learns from provisioning, not from the signaling
• fec.interleaveDepthMs, the ISO protection-window send span from the first source or repair packet to the last: set only when the AL-FEC message's protection_window_time or an independently known source/repair send schedule supplies that span, as a positive integer millisecond upper bound that covers the complete span, never rounded down; when the span is unknown, or the message signals zero (the size-based case), the converter omits it
• a live service -> isLive = true ( Section 5.2.7) on each media track and on its repair track, which the converter publishes while it ingests the service
• the source composition/edit-list origin for each synchronized media track -> presentationAnchorTicks; a converter preserves one common presentation origin across audio and video, and does not emit zero merely because the source offset was unavailable
• bitrate ( Section 5.2.22) from whatever signaling carries it, or from another source, or the conversion of that track fails

Flows sharing one (sourceAddress, groupAddress, port) tuple collapse into a single endpoint whose tracks[] array lists them all. MMT signaling carries no networkSource ( Section 4.2). A converter that adds an AMT network source advertises "driad" discovery only for a source address whose reverse DNS zone carries an AMT relay record, and otherwise names a relay service hostname in relay with "dns" discovery ( Section 4.2.1). timescale, the group-duration field and mmtpMode are required fields (Section 12.1). The converter takes timescale from asset_timescale in the MP table when asset_timescale_flag is 1, and uses 90 000 Hz when that flag is 0, as specified by Clause 10.3.9.3. For each timed Asset, it obtains the presentation time of each MPU's first AU in presentation order from the PI document when PI is present; ISO/IEC 23008-1 Clause 10.5.2.1 says that the MPU timestamp descriptor is ignored in that case. Otherwise it decodes each descriptor's 64-bit NTP mpu_presentation_time value ( Clause 10.5.2) and does not treat the encoded NTP integer as a media tick count. It converts those presentation instants through the selected asset/media clock, retaining the authored media timing when NTP fractional quantization does not land on an integer media tick. That instant is not ticks (Section 4.4.1) when the MPU has leading pictures: ticks is that instant plus the difference between the authored composition times (Section 5.1) of the MPU's first AU in decode order and its earliest-presented AU, converted to the selected timescale as Section 4.4.1 requires. The converter derives the group duration from the authored MPU/media cadence and validates it against those ticks values. It may emit groupDurationMs only when the conversion to the selected timescale is an exact positive integer tick count; when the cadence is exact only in ticks it emits groupDurationTicks. The fixed-cadence profile cannot represent a source whose MPU cadence is not one constant positive duration, so conversion fails rather than rounding or inventing a cadence. It sets mmtpMode itself. The AL-FEC message does not name fec.blockProfile, which is required for a track whose fec.algorithm is not "none" ( Section 5.1); for such a track the converter sets it to "iso-ssbg1-v1", the profile whose entry carries the coding byte 0x14 that the converter accepts (Section 8.3; Section 7.3).

Security Considerations MMT content protection uses Common Encryption (CENC) which is preserved through MoQ transport. The MMTP packet and payload headers are not encrypted by CENC, so receivers, and MMTP gateways outside MoQ, can inspect packet type, sequence, and fragmentation metadata without accessing media sample content. A MoQ relay treats the object payload, MMTP headers included, as opaque ( Section 7.8) and never parses MMTP (Section 6.2).

Multicast Security Multicast-specific security considerations (source authentication, replay protection, AMT relay trust) are defined in Section 7.

IANA Considerations This document defines the catalog packaging value "mmtp" (Section 12.1), extending the allowed packaging values of the MOQT Streaming Format Section 5.2.4 in the same manner as . If a registry of packaging values is established for that format, this document requests registration of:

Value	Description	Reference
"mmtp"	MMTP packets carrying MPU/MFU payloads	This document

This document requests no MoQ message type registrations. FEC signaling uses no MoQ control message ( Section 5.2); no document in this suite requests a control-message codepoint.

References Normative References ISO/IEC ISO/IEC ISO/IEC ISO/IEC Blockcast Blockcast Informative References ARIB ATSC ISO/IEC

Changes Since draft-ramadan-moq-mmt-00 This appendix is informative. It is to be removed before publication as an RFC.

• Object IDs are numbered per group: 0 for the first object of a group and one more for each later object in source order, across subgroups, as Section 6.2 requires. In -00 they restarted at 0 in each subgroup, so several objects of one group shared an Object ID, which Section 2.1 does not allow (Sections 3.1, 4.1, 4.6, 5, 5.2, and 8). Section 4.6 is retitled "Object Identifier Assignment and Reconstruction".
• Section 4.1 states that an mmtp track maps one data unit, not one object, to a stream, unlike Section 6, and keeps the Group and Object numbering of its Sections 6.1 and 6.2.
• The join (Section 6.1, step 3) uses the current-group join of Section 3.5: SUBSCRIBE with a Next Object LOCATION_FILTER and FILL_PARAMETERS with StartGroup = 1. Section 6.2 is now an informative note. The relay replay and completeness requirements of -00 are removed, because a publisher must not send objects outside the requested range ( Section 3.3.1).
• Section 4.4.1: an mmtp publisher, whose Group numbers follow media time, does not set the DYNAMIC_GROUPS Track Property to 1, and Section 6.1 notes that NEW_GROUP_REQUEST cannot shorten a wait for the next group. A publisher that skips Group numbers on a restart signals the gap with PRIOR_GROUP_ID_GAP, as Section 6.1 recommends.
• Section 6.1, step 1: the catalog is read through a subscription that joins its current group, as Section 5 requires, and a switching-set disagreement is handled as Section 4.4.2 specifies.
• Section 4.3: objects of an mmtp track are sent in subgroups, not as datagrams. The permission for a relay to drop a subgroup under congestion is removed; Section 5.2 governs when objects go undelivered. Section 5.2.1 no longer refers to datagram paths: on a lossy path a subsample data unit completes, possibly after FEC recovery, or is discarded as incomplete, like any other data unit.
• Section 4.4: a repair track carries no altGroup, so it is not a member of a switching set. In -00 it carried the altGroup of the track it protects, although its Groups are FEC blocks, not media-time-aligned Groups.
• Catalog initialization data uses the initDataList and initRef fields of in place of the per-track initData field, which the current revisions of and do not define. A receiver may still accept initData from -00 implementations (Sections 4.5, 6.1, 12, and 12.1).
• Switching sets (Sections 4.4 and 4.4.2): an intra-only mmtp track may use a group duration that divides that of the GOP tracks a whole number of times. The exception applies to mmtp tracks only, so cmaf members keep the Group number alignment of Section 3.2. The g * n Group mapping is the alternate mechanism of Section 4.2, and the 10^-3 tolerance only classifies a track as intra-only.
• Section 4.4.2, Table 3: the optional timescale field of cmaf tracks is attributed to Section 5.2.21, not to . A loc switching-set member, like a cmaf one, carries a catalog timescale, which a TIMESCALE Property on the track must equal, so is now a normative reference. A track entry without packaging is malformed.
• Section 8.3: the AL-FEC message carries in fec_code_id_for_repair_flow the Table 1 code point of the track's algorithm: 3 for "raptorq" and 1 for "reed-solomon". Sections 7 and 8.1 follow , which now fully specifies "reed-solomon" and makes it the mandatory-to-implement scheme. RaptorQ is optional there. Section 7 states that neither the MMT AL-FEC framework nor , which uses it for MMTP sessions, requires a particular code, so the codes are those specifies. is now a normative reference. The message's length_of_repair_symbol carries the track's symbolSize, which Section 12.2 reads back, and num_of_repair_symbol_per_packet is 1; its maximum_p_for_repair_flow carries the RSB_length of the track's FEC instance, the block total, which Section 12.2 reads back as repairSymbols less the layers above 0 it lists, listing a layer it learns from provisioning only where provisioning places it, with every other listed layer, above every layer it does not list, keeping the value it first published for a track, and those of the layers it has listed, across later versions of the message that raise the field, retiring the source encoding under one that lowers the field below the total its catalog derives for the highest layer it lists ( Section 6.3.9), appending at the next index a layer it learns from provisioning after it published the track only where provisioning places it next above the highest layer it lists with no unlearned layer below it, the field's rise alone placing none, and listing one provisioning does not so place, or whose symbols the field it first read already counted, only by retiring the source encoding and publishing a separate rendition. Section 12.2 states that the field is a bound in where "iso-ssbg1-v1" carries P as every repair packet's RSB_length, lists the repair track only once a repair packet of the flow carries at least the field, and fails the conversion of a flow whose repair packets carry an RSB_length below the field on a block at or after, in the serial order of Section 7.5, one received carrying at least the field, since a publisher that appends a layer sends the new version only after the last repair packet generated under the previous total (Section 8.3) while the path keeps no order between the message and the repair flow (Section 5.2.2); once the track is published such a packet, below the total its catalog derives for the highest layer it lists, retires the source encoding, the separate rendition listing the repair track again as the first listing did; a previous-total packet of an earlier block fails a receiver of the catalog closed on nothing, the own-track clause of Section 6.3.9 applying to layers above 0 alone. Section 8.3 sets the entry's number_of_assets to 1, the one Asset being the source track's. Section 12.2 accepts only an entry with a number_of_assets of 1, the coding byte 0x14 and code point 1 or 3, and fails the conversion of a flow whose fec object would fail a catalog rule of Sections 5.1 and 6.3.4 (a maximum K or maximum P of 0, a symbol length below 14, a RaptorQ symbol length that is not a multiple of 8, a RaptorQ maximum K above 56403 or maximum K plus maximum P above 2^24, a Reed-Solomon maximum K plus maximum P above 255), of one whose repair flow is packet_id 0, the flow's own packet_id or the packet_id of another track of the session, and of the flows of two entries that name one repair flow or list one Asset.
• Section 1.1: the CARP row is removed. CARP (draft-law-moq-carp-00) has expired, and its content continues as . The FEC column names the block profile for each packaging, including "moq-object-v1" for loc and cmaf tracks. The section names MSF, LOC and CMSF with their references, and the cases that suit each packaging are no longer stated with BCP 14 keywords.
• Sections 12.2 and 12.3 and Appendix A of -00 (the S-TSID conversion example): the S-TSID conversion of -00 is removed, and this appendix of changes is now Appendix A. This document targets MMTP services and not ROUTE, so Section 12.2 now derives the catalog from MMTP signaling, the MP table and the AL-FEC message, there is no export to broadcast signaling, and the Abstract, Section 1, Section 2 and Section 7 no longer name S-TSID. Section 7.2 no longer cites the S-TSID fecOTI attribute and says the AL-FEC message carries no OTI, and the Section 8.1 algorithm rule reads the code point from fec_code_id_for_repair_flow alone, with no ROUTE-ingest case.
• Sections 4.4.2 and 12.1: the example catalogs carry the fields that requires.
• Section 13: a MoQ relay treats MMTP headers as opaque object payload.
• Editorial: abbreviations such as ISOBMFF, SSM, ASM, AMT, ABR, GOP and OTI are expanded, and Section 2 defines AU. Section 1 says "FEC" instead of "Unified FEC". Capitalized words that are not BCP 14 keywords (NOT, LOW, NO) are lowercased. Section 3.1 cites for the NTP short format, Section 9 cites for TreeDN, and Section 13 cites for Common Encryption. Section 14 uses the name "MOQT Streaming Format".
• (ISOBMFF) is a normative reference, and is dated.
• References to the companion drafts point to their -01 revisions.