FLUTE feature by feature in its three profiles: what each one requires, permits or excludes. The Standards page lists the clauses behind every requirement.
Each profile takes FLUTE from a different set of documents, and the columns follow them:
- Unprofiled FLUTE: the IETF documents (RFC 3926 section 1; TS 26.346 V19.3.0 clause 7.1). Version 1 (RFC 3926, with ALC and LCT) unless version 2 is named.
- MBMS download: RFC 3926 with the ALC and LCT features FLUTE inherits, TS 26.346 clause 7.2, the session description of clause 7.3, the MBMS Download Profile of annex L.4 and the requirement levels of annex A.
- MBS Object Distribution: the MBMS Download Profile of annex L.4, the Profiled FDT Schema of annex L.6, the session description of TS 26.346 clause 7.3 with the restrictions of TS 26.517, and TS 26.517 clause 6.2. TS 26.346 clause 7.2 binds it only where annex L.4 repeats it.
At a glance
- What it covers: how unprofiled FLUTE, MBMS download and MBS Object Distribution differ in what they require.
- Unprofiled FLUTE leaves most choices open; the MBMS and MBS profiles narrow it for a network without congestion control.
- Releases: Release 19 raises both FDT schema versions and adds repair features; in TS 26.346 Release 18 changes none of the clauses read, and in TS 26.517 Release 18 changes the SDP timing rule.
The features
| Feature | Unprofiled FLUTE | MBMS download | MBS Object Distribution |
|---|---|---|---|
| Sessions (RFC 3450 section 1.3; TS 26.346 V19.3.0 clause 7.2.7; TS 26.346 V19.3.0 clause 7.3.2.1; TS 26.346 V19.3.0 clause L.4.8) | TSI in every packet; the receiver demultiplexes on sender address and TSI | 16-bit TSI; exactly one source address per session | Exactly one source address per session |
| LCT header (RFC 3451 section 5.1; TS 26.346 V19.3.0 clause 7.2.7; TS 26.346 V19.3.0 clause L.4.7) | As RFC 3451; A and B flags optional for the sender | 32-bit CCI set to zero, 16-bit TSI, TOI of 16 bits, T and R set to zero | Sender Current Time and Expected Residual Time not used |
| FDT schema (RFC 3926 section 3.4.2; TS 26.346 V19.3.0 clause 7.2.10.1; TS 26.346 V19.3.0 clause L.6.1; TS 26.517 V19.3.0 clause 6.2.1) | RFC 3926 | Extended FLUTE FDT schema | Profiled FLUTE FDT schema of annex L.6 |
| Mandatory FDT data (RFC 3926 section 3.4.2; TS 26.346 V19.3.0 clause 7.2.9; TS 26.346 V19.3.0 clause L.4.4; TS 26.346 V19.3.0 clause L.4.2; TS 26.517 V19.3.0 clause 6.2.1) | Expires; per file TOI and Content-Location | Also Content-Length, Content-Type, FEC Encoding ID and FEC Object Transmission Information | Content-Type, FEC Object Transmission Information, Content-Location, TOI, Content-Length; objects described with Expires |
| FEC (TS 26.346 V19.3.0 clause A; TS 26.346 V19.3.0 clause 7.2.2; TS 26.346 V19.3.0 clause L.4.7; RFC 3926 section 5.1) | Compact No-Code at the receiver; other schemes optional | Compact No-Code, and Raptor (FEC Encoding ID 1) decoded by every UE | Compact No-Code and Raptor mandatory to support by the UE, optional for the sender |
| Congestion control (RFC 3450 section 2.2; RFC 3926 section 4; TS 26.346 V19.3.0 clause 7.2.4; TS 26.346 V19.3.0 clause L.4.7) | Required: multiple-rate, feedback-free (none in a controlled network, RFC 3926 section 4) | Not used: one channel, single rate | Not used: one channel, single rate |
| Content encoding (RFC 3926 section 3.4.3; TS 26.346 V19.3.0 clause 7.2.5; TS 26.346 V19.3.0 clause 7.2.8; TS 26.346 V19.3.0 clause L.4.2; TS 26.346 V19.3.0 clause A) | Optional, for files and FDT Instances | gzip only, for files; never for FDT Instances; every UE decodes gzip | gzip only, supported by the receiver |
| FDT expiry (RFC 3926 section 3.3; TS 26.346 V19.3.0 clause 7.2.9; TS 26.517 V19.3.0 clause 6.2.1) | The receiver should not use an expired FDT Instance | The UE shall not | As unprofiled; the expiry of the latest FDT Instance ends an object's transmission |
| Session description (RFC 3926 section 6; TS 26.346 V19.3.0 clause 7.3; TS 26.346 V19.3.0 clause L.4.8; TS 26.517 V19.3.0 clause 6.2.2) | Parameters listed; their discovery out of scope | SDP (TS 26.346 V19.3.0 clause 7.3), with the profile of TS 26.346 V19.3.0 table L.4.8-1 | SDP with restrictions, and the mbs-servicetype attribute |
| Operating modes (TS 26.346 V19.3.0 clause 7.2.0; TS 26.517 V19.3.0 clause 6.2.3.2; TS 26.502 V19.6.0 clause 6.1) | Not defined | Promiscuous, one-copy and keep-updated reception | OBJECT_SINGLE, OBJECT_COLLECTION, OBJECT_CAROUSEL, OBJECT_STREAMING |
| Caching directives (TS 26.346 V19.3.0 clause 7.2.13; TS 26.346 V19.3.0 clause L.4.4; TS 26.346 V19.3.0 clause L.6.1; TS 26.517 V19.3.0 clause 6.2.3.5) | Not defined | no-cache, max-stale and Expires | Cache-Control in the Profiled FDT Schema; Expires gives the end of availability in streaming |
| Repair (TS 26.346 V19.3.0 clause 9.3.1; TS 26.346 V19.3.0 clause 9.4B.1; TS 26.517 V19.3.0 clause 6.2.4.2; TS 26.517 V19.3.0 clause 6.2.4.3) | Not defined | Post-delivery and, from Release 19, in-session unicast file repair | Post-session and, from Release 19, in-session Object Repair |
Sessions, objects and packets
Unprofiled FLUTE
- A Transport Session Identifier (TSI) is associated with each session and carried in the LCT header of each ALC packet (RFC 3450 section 2.1; RFC 3450 section 4.4). The pair of sender IP address and TSI uniquely identifies the session, and the sender uses the same TSI for all packets of the session.
- A receiver joined to several sessions demultiplexes on the IP address of the sender and the TSI (RFC 3450 section 1.3; RFC 3450 section 4.5). It verifies each packet's header, sender address and TSI, and discards a packet that does not match a session it has joined.
- Each file is associated with a Transport Object Identifier (TOI) greater than 0; the TOI is carried in the packets of the session (a payload-free packet that closes the session does not carry it); TOI 0 is reserved for the FDT Instances (RFC 3926 section 3.1).
- Before joining, a receiver obtains the session description; a receiver that cannot process the ALC header drops from the session, and one that cannot implement the congestion control of the session does not join (RFC 3450 section 2.4; RFC 3450 section 4.5).
MBMS download
- The TSI is 16 bits long (S=0, H=1) and the TOI should be 16 bits long (O=0, H=1) (TS 26.346 V19.3.0 clause 7.2.7).
- A session has exactly one sender IP address, given by one
source-filterattribute at session level; each TSI identifies its session for that source address while it is active, and long before and after (TS 26.346 V19.3.0 clause 7.3.2.1; TS 26.346 V19.3.0 clause 7.3.2.4).
MBS Object Distribution
- The session description of TS 26.346 clause 7.3 applies, so a session has exactly one source address and one TSI. The 16-bit field lengths of clause 7.2.7 are not repeated in the MBMS Download Profile.
LCT header and extensions
Unprofiled FLUTE
- The default LCT header of RFC 3451 is used; reserved bits are set to zero by the sender and ignored by the receiver (RFC 3450 section 4.1; RFC 3451 section 5.1).
- The sender may set the Close Session (A) and Close Object (B) flags as the end of the session or of an object approaches; a receiver should then assume no more packets follow (RFC 3451 section 5.1).
- Every packet of an FDT Instance carries the FDT Instance Header (EXT_FDT) (RFC 3926 section 3.4; RFC 3451 section 5.2). All implementations support EXT_NOP and recognise EXT_AUTH.
MBMS download
- Header fields: a 32-bit CCI with value zero (C=0), a 16-bit TSI, a TOI that should be 16 bits, TOI 0 used only for FDT Instances, and HDR_LEN giving the header length in 32-bit words (TS 26.346 V19.3.0 clause 7.2.7).
- Flags: the Close Session (A) and Close Object (B) flags may signal the end of a session and of an object; the Sender Current Time (T) and Expected Residual Time (R) flags are set to zero (TS 26.346 V19.3.0 clause 7.2.7; TS 26.346 V19.3.0 clause A). EXT_TIME, if included, carries the Expected Residual Time. Annex A sets the levels for client and server, with a note on the A flag.
- Extensions: EXT_FTI in every packet carrying an FDT Instance and never in packets carrying files; EXT_CENC is not used (TS 26.346 V19.3.0 clause 7.2.8).
MBS Object Distribution
- The MBMS Download Profile does not use the Sender Current Time and Expected Residual Time, either as the T and R flags or in EXT_TIME: the network should set them to zero and the UE should ignore them (TS 26.346 V19.3.0 clause L.4.7).
- EXT_FTI should be used in packets carrying FDT Instances; the FEC Object Transmission Information of files should be conveyed in the FDT (TS 26.346 V19.3.0 clause L.4.7).
The File Delivery Table
Unprofiled FLUTE
- The FDT is local to its file delivery session, and provides a file description entry mapped to a TOI for each file in the session (RFC 3926 section 3.2).
- The FDT-Instance element contains the Expires attribute (RFC 3926 section 3.4.2). Each File element contains at least the TOI and Content-Location attributes. Content-Type, Content-Length, Content-Encoding and Content-MD5 are used as HTTP/1.1 defines them, where present.
- A TOI may be described more than once, but later FDT Instances do not change the parameters already described for it (RFC 3926 section 3.3). The sender uses an expiry time in the future; the receiver should not use an FDT Instance after it expires.
MBMS download
- Schema: the extended FLUTE FDT instance schema of TS 26.346 clause 7.2.10.1, based on the RFC 3926 schema, with its schemaVersion element; it imports the 3GPP extensions of Releases 6, 7, 8, 9, 11, 13 and, from Release 19, 19.
- Mandatory beyond RFC 3926: Content-Length, Content-Type, the FEC Encoding ID, and the FEC Object Transmission Information of the FEC scheme in use (TS 26.346 V19.3.0 clause 7.2.9). With Compact No-Code FEC, the maximum source block length does not exceed 65535.
- Optional: Complete, Content-Encoding, Content-MD5 (indicated when several versions of a file are expected), IndependentUnitPositions, File-ETag, and, from Release 19, Repair-Start and Repair-Limit-Percentage (TS 26.346 V19.3.0 clause 7.2.9).
- 3GPP extensions: file grouping (clause 7.2.6), the MBMS session identity of a file (7.2.11), caching directives (7.2.13), FullFDT for a full snapshot of the objects scheduled (7.2.14), the decryption key of a protected file (7.2.15), and the FEC redundancy level of a file (7.2.16) (TS 26.346 V19.3.0 clause 7.2.6; TS 26.346 V19.3.0 clause 7.2.11; TS 26.346 V19.3.0 clause 7.2.13; TS 26.346 V19.3.0 clause 7.2.14; TS 26.346 V19.3.0 clause 7.2.15; TS 26.346 V19.3.0 clause 7.2.16).
- Expiry: the UE shall not use an FDT Instance to interpret packets received after it expires, which strengthens the RFC 3926 "should not". (TS 26.346 V19.3.0 clause 7.2.9)
- The MBMS Download Profile (annex L.4) constrains this set, as in the next column (TS 26.346 V19.3.0 clause L.4.1).
MBS Object Distribution
- The MBMS Download Profile: the sender carries Content-Type and the FEC Object Transmission Information at the FDT-Instance or File level, and Content-Location, TOI and Content-Length for every file; Content-MD5 should be included for non-DASH services and may be for DASH Segments (TS 26.346 V19.3.0 clause L.4.2; TS 26.346 V19.3.0 clause L.4.3; TS 26.346 V19.3.0 clause L.4.4). It does not use a Content-Encoding other than gzip, FEC-OTI-FEC-Instance-ID, Group, Complete, FullFDT, MBMS-Session-Identity-Expiry, Transfer-Length, Decryption-KEY-URI, FEC-Redundancy-Level or MBMS-Session-Identity. The receiver supports every attribute the sender carries.
- The Profiled FDT Schema (annex L.6) describes the objects currently transmitted, with its own schemaVersion; delimiter elements are set to 0 and ignored (TS 26.517 V19.3.0 clause 6.2.1; TS 26.346 V19.3.0 clause L.6.2; TS 26.346 V19.3.0 clause L.6.3).
- TS 26.517: objects are described with Expires; Content-MD5 and File-ETag are optional, File-ETag carrying the HTTP entity tag. In OBJECT_STREAMING mode, each Content-Location matches the object's URL in the object list, File@Expires is no later than its latest availability start time, and Cache-Control@Expires gives its availability end time.
FEC and blocking
Unprofiled FLUTE
- Every packet carries an FEC Payload ID, which the receiver uses to place the encoding symbols it carries (RFC 3450 section 2.3).
- The FEC Object Transmission Information is delivered in band (RFC 3926 section 5). The receiver supports it in EXT_FTI for FDT Instances, and both in EXT_FTI and in the FDT for files; the two carry the same values.
- Compact No-Code (FEC Encoding ID 0, RFC 3695) is required at the client and the default at the server; other FEC schemes, such as Raptor (RFC 5053) and RaptorQ (RFC 6330), are optional (TS 26.346 V19.3.0 clause A; RFC 3926 section 5.1.2.3). The RFC 3926 blocking algorithm is recommended.
MBMS download
- Compact No-Code shall be supported, with a 16-bit Source Block Number and a 16-bit Encoding Symbol ID in the FEC Payload ID (TS 26.346 V19.3.0 clause 7.2.2; TS 26.346 V19.3.0 clause 7.2.7).
- A UE that supports MBMS User Services supports a decoder for the Raptor FEC scheme (FEC Encoding ID 1, the MBMS FEC scheme of clause 7.2.12); given a mathematically sufficient set of encoding symbols, it recovers the entire source block (TS 26.346 V19.3.0 clause 7.2.2; TS 26.346 V19.3.0 clause 7.2.12.1).
- Blocking: the RFC 3926 algorithm with Compact No-Code, the RFC 5053 algorithm with Raptor; the sub-block size stays below 256 KB (TS 26.346 V19.3.0 clause 7.2.3).
- The FEC-Redundancy-Level of a transport object may be given in the FDT (clause 7.2.16) (TS 26.346 V19.3.0 clause 7.2.16).
MBS Object Distribution
- In the MBMS Download Profile, Compact No-Code and Raptor are optional to implement by the sender and mandatory to support by the UE. Blocking should follow the algorithm of RFC 3695 for Compact No-Code and should comply with the recommendations of RFC 5053 for Raptor (TS 26.346 V19.3.0 clause L.4.7).
- The repair procedures handle both schemes: with Compact No-Code the MBS Client considers the source symbols already received, with Raptor the source and repair symbols already received (TS 26.517 V19.3.0 clause 6.2.4.5).
Congestion control and channels
Unprofiled FLUTE
- Implementors of ALC implement a multiple-rate, feedback-free congestion control building block in accordance with RFC 2357, applied to all packets of a session (RFC 3450 section 2.2). In FLUTE version 2, implementations of ALC support at least WEBRC (RFC 3738), a multiple-rate congestion control scheme (RFC 6726 section 1.1.4).
- RFC 3926 allows a single channel, or multiple channels, without the congestion control of ALC only in a controlled network where flow and congestion control are provided by other means (RFC 3926 section 4).
MBMS download and MBS Object Distribution
- Congestion control is not appropriate in the environment MBMS download is provided in, and is not used (TS 26.346 V19.3.0 clause 7.1; RFC 3450 section 1.3).
- FLUTE channelisation is a single FLUTE channel with single rate transport (clause 7.2.4 for MBMS download, clause L.4.7 for both) (TS 26.346 V19.3.0 clause 7.2.4; TS 26.346 V19.3.0 clause L.4.7).
Content encoding
Unprofiled FLUTE
- FDT Instances and other files may be content encoded (RFC 3926 section 3.4.3; RFC 3926 section 3.4.2). EXT_CENC signals the encoding of an FDT Instance, in every packet of that instance.
MBMS download
- Files may be gzip encoded for transport, and UEs support gzip decoding (TS 26.346 V19.3.0 clause 7.2.5; TS 26.346 V19.3.0 clause 7.2.8). FDT Instances are not content encoded, so EXT_CENC is not used.
MBS Object Distribution
- Content-Encoding set to gzip may be carried and is supported by the receiver; any other Content-Encoding is excluded (TS 26.346 V19.3.0 clause L.4.2).
- The repair object of a gzip-encoded object is hosted on the MBS AS in its gzip form, with a ".gz" extension added to its location (TS 26.517 V19.3.0 clause 6.2.4.4).
Session description
Unprofiled FLUTE
- RFC 3926 lists what a receiver needs before joining: the source IP address, the number of channels, the destination address and port of each channel, the TSI and an indication that the session is a FLUTE session; optionally, the start and end times of the session (RFC 3926 section 6). How the receiver discovers them is out of its scope.
MBMS download
- An SDP file describes the session (TS 26.346 clause 7.3): the source filter, the channel, the TSI, the timing, the MBMS bearer mode and TMGI, the FEC capabilities, the bandwidth,
FLUTE/UDPas protocol andapplicationmedia with format0. - Table L.4.8-1 of the MBMS Download Profile lists which SDP parameters are required, optional or not applicable (TS 26.346 V19.3.0 clause L.4.8; TS 26.346 V19.3.0 clause L.4.1). The profile excludes OMA Push and RTSP.
MBS Object Distribution
- The Session Description document follows TS 26.346 clause 7.3 with restrictions: no mode of MBMS bearer per media, no QoE metrics, no service language and no alternative TMGI. Its timing covers the service schedule descriptions, if any.
- The
mbs-servicetypeattribute declares whether the MBS Distribution Session uses a broadcast or a multicast MBS Session, with the TMGI, for examplea=mbs-servicetype:broadcast 123869108302929(TS 26.517 V19.3.0 clause 6.2.2.2).
Reception and operating modes
MBMS download
- A UE application instructs the FLUTE receiver to receive every file available (promiscuous), one copy of specific files (one-copy), or specific files and every update to them (keep-updated) (TS 26.346 V19.3.0 clause 7.2.0).
MBS Object Distribution
- OBJECT_SINGLE: a single object (TS 26.517 V19.3.0 clause 6.2.3.2).
- OBJECT_COLLECTION: several objects listed in an object manifest, each distributed once (TS 26.517 V19.3.0 clause 6.2.3.3). Each FDT Instance should describe all objects of the collection.
- OBJECT_CAROUSEL: one or more objects from an object manifest, distributed repeatedly; the manifest may be replaced over time (TS 26.517 V19.3.0 clause 6.2.3.4).
- OBJECT_STREAMING: a sequence of objects, typically timed segments, recommended for DASH or HLS (TS 26.517 V19.3.0 clause 6.2.3.5). The last packet of each object reaches the MBSTF Client by its availability start time, and an FDT Instance describing the objects not yet fully transmitted should be sent frequently.
Caching directives
MBMS download
- A file download service may indicate, per file, whether it is not to be cached (no-cache), cached for an indefinite period if possible (max-stale), or cached until a given time (Expires) (TS 26.346 V19.3.0 clause 7.2.13). The directives are recommended with the promiscuous and keep-updated modes.
MBS Object Distribution
- The MBMS Download Profile lets the sender carry the Cache-Control element, and the receiver supports it (TS 26.346 V19.3.0 clause L.4.4; TS 26.346 V19.3.0 clause L.6.1; TS 26.346 V19.3.0 clause L.6.2). The Profiled FDT Schema declares Cache-Control, with the same three directives, in its own namespace.
- In OBJECT_STREAMING mode, Cache-Control@Expires gives the availability end time of each object (TS 26.517 V19.3.0 clause 6.2.3.5).
Repair
MBMS download
- Post-delivery file repair (TS 26.346 clause 9.3): MBMS Download receivers support it. It repairs lost or corrupted file fragments, and spreads the repair requests in time and across servers. Reception reporting follows in clause 9.4.
- In-session unicast file repair (TS 26.346 V19.3.0 clause 9.4B, Release 19): MBMS Download receivers support it if the UE permits concurrent use of MBMS bearer services and unicast reception. Its procedures are those of TS 26.517 clause 6.2.4.3.
MBS Object Distribution
- Post-session Object Repair: the MBS Client supports it. It is aligned with the file repair of TS 26.346 clause 9.3, and uses byte-range requests to the MBS AS.
- In-session object repair (Release 19; for further study in Release 18): the object delivery client requests missing data, or the whole object, over HTTP from the object repair server once a repair start time is reached, within a limit of repairs per 100 objects (TS 26.517 V19.3.0 clause 6.2.4.3.3; TS 26.517 V19.3.0 clause 6.2.4.3.2).
- Not with OBJECT_STREAMING: the Object Repair mechanism is not used with the OBJECT_STREAMING mode in this release (TS 26.517 V19.3.0 clause 6.2.3.1).
Security
Unprofiled FLUTE
- The RFCs recommend an integrity check of each reconstructed object and FDT Instance, packet-level authentication, and measures that keep receivers from accepting an incorrect session description (RFC 3926 section 7; RFC 3450 section 5). The FLUTE receiver should not have write access to system files.
MBMS download and MBS Object Distribution
- A protected download file can name its decryption key file with the Decryption-KEY-URI attribute (TS 26.346 clause 7.2.15). The MBMS Download Profile excludes that attribute from the FDT the sender carries.
FLUTE version 2
RFC 6726 changes some of these rules for version 2, which the 3GPP profiles do not use: (RFC 6726 section 11.1; TS 26.346 V19.3.0 clause 7.1)
- The receiver must not use an FDT Instance after it expires (version 1: should not) (RFC 6726 section 3.3; RFC 3926 section 3.3).
- When the FEC Object Transmission Information is delivered in the FDT, the FEC-OTI-FEC-Encoding-ID attribute and the Codepoint field of all packets for that TOI must have the same value (RFC 6726 section 5).
- Senders do not reuse the ID of an FDT Instance that has not expired, and receivers handle FDT Instance ID wraparound (RFC 6726 section 3.4.1).
- Content-Type should be included, and Content-Encoding is included whenever content encoding is applied (RFC 6726 section 3.4.2).
- Version 2 uses ALC (RFC 5775) and LCT (RFC 5651), whose header differs from version 1 (RFC 6726 section 3.1; RFC 6726 section 11.1).
By release
| Feature | Release 17 | Release 18 | Release 19 |
|---|---|---|---|
| Extended FDT schema (MBMS download) (TS 26.346 V17.6.0 clause 7.2.10.1; TS 26.346 V18.2.0 clause 7.2.10.1; TS 26.346 V19.3.0 clause 7.2.10.1) | schemaVersion 4 | schemaVersion 4 | schemaVersion 5, importing the Release 19 extensions |
| Profiled FDT Schema (MBS) (TS 26.346 V17.6.0 clause L.6.3; TS 26.346 V18.2.0 clause L.6.3; TS 26.346 V19.3.0 clause L.6.3; TS 26.346 V19.3.0 clause L.6.2) | schemaVersion 2; File@Expires, taking precedence over FDT@Expires | As Release 17 | schemaVersion 3; File@Expires removed; Repair-Start and Repair-Limit-Percentage added |
| Optional FDT data (MBMS download) (TS 26.346 V18.2.0 clause 7.2.9; TS 26.346 V19.3.0 clause 7.2.9) | As listed | As listed | Repair-Start and Repair-Limit-Percentage added |
| Repair | Post-delivery and post-session repair | In-session object repair for further study (TS 26.517) | In-session unicast file repair (TS 26.346 clause 9.4B) and in-session object repair (TS 26.517 clause 6.2.4.3) |
| Session description (MBS) (TS 26.517 V17.11.0 clause 6.2.2.1; TS 26.517 V18.7.0 clause 6.2.2.1; TS 26.517 V19.3.0 clause 6.2.2.1) | SDP timing as a superset of the MBS Schedule Description | SDP timing related to the service schedule descriptions | As Release 18 |
The documents read are TS 26.346 V17.6.0, V18.2.0 and V19.3.0, and TS 26.517 V17.11.0, V18.7.0 and V19.3.0.
Sources for this page
- Base documents: TS 26.346 V19.3.0, clauses 7.2.0 and L.4.1; TS 26.517 V19.3.0, clauses 6.2.1 and 6.2.2.1.
- Sessions: RFC 3450, sections 1.3, 2.1, 4.4 and 4.5; RFC 3926, sections 3.1 and 3.3; TS 26.346 V19.3.0, clauses 7.2.7, 7.3.2.1 and 7.3.2.4.
- LCT header: RFC 3450, sections 4.2 and 4.3; RFC 3926, section 3.3; TS 26.346 V19.3.0, clauses 7.2.7, 7.2.8, L.4.7 and annex A (table A.1 and note).
- The File Delivery Table: RFC 3926, sections 3.2, 3.3 and 3.4.2; TS 26.346 V19.3.0, clauses 7.2.6, 7.2.9, 7.2.10.1, 7.2.11, 7.2.13 to 7.2.16, L.4.2 to L.4.5, L.6.1 to L.6.3; TS 26.517 V19.3.0, clauses 6.2.1 and 6.2.3.5.
- FEC and blocking: RFC 3450, section 2.3; RFC 3926, section 5; TS 26.346 V19.3.0, clauses 7.2.1 to 7.2.3, 7.2.7, 7.2.12, 7.2.16, L.4.7 and annex A (table A.1); TS 26.517 V19.3.0, clause 6.2.4.5.
- Congestion control: RFC 3450, section 2.2; RFC 3926, section 4; TS 26.346 V19.3.0, clauses 7.1, 7.2.4 and L.4.7.
- Content encoding: RFC 3926, section 3.4.3; TS 26.346 V19.3.0, clauses 7.2.5, 7.2.8 and L.4.2, and annex A (table A.1); TS 26.517 V19.3.0, clause 6.2.4.4.
- Session description: RFC 3926, section 6; TS 26.346 V19.3.0, clauses 7.3, L.4.1 and L.4.8; TS 26.517 V19.3.0, clauses 6.2.2.1 and 6.2.2.2.
- Operating modes: TS 26.346 V19.3.0, clause 7.2.0; TS 26.517 V19.3.0, clauses 6.2.3.2 to 6.2.3.5.
- Caching directives: TS 26.346 V19.3.0, clauses 7.2.13, L.4.4 and L.6.1; TS 26.517 V19.3.0, clause 6.2.3.5.
- Repair: TS 26.346 V19.3.0, clauses 9.1, 9.3.1, 9.4 and 9.4B.1; TS 26.517 V18.7.0 and V19.3.0, clauses 6.2.3.1 and 6.2.4.1 to 6.2.4.3.
- Security: RFC 3926, section 7; RFC 3450, section 5; TS 26.346 V19.3.0, clauses 7.2.15 and L.4.4.
- FLUTE version 2: RFC 6726, sections 3.1, 3.3, 3.4.1, 3.4.2 and 5 (RFC 6726 section 3.1; RFC 6726 section 3.3; RFC 6726 section 3.4.1; RFC 6726 section 3.4.2; RFC 6726 section 5).
- By release: TS 26.346 V17.6.0, V18.2.0 and V19.3.0, clauses 7.2.9, 7.2.10.1, 9.4B and L.6.1 to L.6.3; TS 26.517 V17.11.0, V18.7.0 and V19.3.0, clauses 6.2.2.1 and 6.2.4.3.