Skip to main content
Validation Tools

FLUTE Conformance Validator

At a glance
  • What it is: a validator that tests a FLUTE implementation against the FLUTE profiles of IETF RFC 3926, 3GPP TS 26.346 and 3GPP TS 26.517.
  • What it tests: rt-libflute, the FLUTE library of the Content Delivery Protocols and Tools, in a version you choose.
  • What a verdict means: it is a first version, built from a reading of the documents. No independent party has verified it yet.

What it does​

FLUTE (File Delivery over Unidirectional Transport, IETF RFC 3926) is used by 3GPP MBMS (TS 26.346) and MBS (TS 26.517) to deliver files. Each of these documents defines a profile: the values a sender may use and what a receiver must accept. The validator checks an implementation against those profiles.

For each profile it configures the library's transmitter with the values the profile supports, reads the packets on the wire with its own decoder, runs the library's receiver on the same session, and sends what the transmitter cannot be made to send, such as unknown extensions or invalid packets, to check that the receiver handles it as the profile requires. The result lists every failed "shall", every "should" that is not met, and the verdict on each normative statement of the profile's documents. How it works describes the method.

Profiles​

ProfileRests onReleases
Profile::NoneIETF RFC 3926none
Profile::MBMS::Download3GPP TS 26.346 annex L.413 to 19
Profile::MBS3GPP TS 26.517 clause 6.217 to 19

Each 3GPP profile is tested per release, against the latest edition of that release. Release 20 has no edition of either document yet (October 2026). Implementation status lists the editions.

Where it stands​

The validator tests rt-libflute only: its two test harnesses are built against the library's own interface, although the checks of the packets on the wire do not depend on the library. The reference it checks against is a reading of the documents, recorded in the repository, not a test specification published by 3GPP or the IETF. Some statements cannot be checked, for example those that oblige the network or the application, and each is listed with its reason.

The repository is available on request; see Early Access.

Contributors & How to Contribute​

What's Built​

FLUTE Conformance Validator
The FLUTE Conformance Validator and the FLUTE session it checks, with repositoriesA 5G-MAG drawing based on IETF RFC 3926, 3GPP TS 26.346 V19.3.0 (figures 9 and 10, annex L.4), 3GPP TS 26.517 V19.3.0 (clause 6.2) and the flute-conformance-validator README

This is a 5G-MAG drawing, not a redrawn specification figure. The validator tests rt-libflute only, as its README says; the sender and the receiver are the library's transmitter and receiver. Click the figure to enlarge it.

Repositories & Releases​

Early Access Early Access: available to members first

FLUTE Conformance Validatorflute-conformance-validatorEarly Access
no release yet

Standards implemented​

IETFRFC 3926
3GPPTS 26.346, TS 26.517

IETF RFC 3926 (FLUTE), 3GPP TS 26.346 annex L.4 (MBMS download profile) and 3GPP TS 26.517 clause 6.2 (MBS profile): see Profiles for the releases tested.

See FLUTE requirements by profile. For the technology background, see the Technology page. The library it tests is Content Delivery Protocols and Tools (rt-libflute).

Developer Updates​

Last Synced: 2026-11-14 03:44 UTC

Early Access Early Access: available to members first

0 views
3 clones
★ 0⎇ 0
Active

Open Pull Requests​