Clearport/MPEG-DASH

MPEG-DASH

MPEG-DASH is the ISO/IEC standard for adaptive delivery of media presentations and segments over HTTP. Clients fetch a Media Presentation Description and then request media segments from web servers or CDNs, normally over HTTPS.

Scope: MPEG-DASH — select the deployed product/version; optional services require separate selection.

protocol · Catalog reviewed 2026-10-22

Related requirements

Review these entries for the services used in your design.

http https websocket dns dns sd

By ISO/IEC MPEG · ISO/IEC 23009-1

Video TransportOpen Standardlanwaninternet

Infrastructure Requirements

HTTP origin/CDN
HTTPS certificates
DNS
sufficient egress bandwidth
supported codecs and container profiles

Network & Physical Requirements

Port / allocation	Transport	Connection / signal flow	Feature and requirement	Evidence
80 (default)	TCP	Player → Origin / CDN	Profile requirement · Core HTTP manifests and segments DASH resources carried by HTTP/1.1 or HTTP/2 over TCP; URI-selected origin DASH-IF describes client HTTP segment retrieval (https://dashif.org/Guidelines-TimingModel/). Use each MPD/segment/authentication URI host and explicit port where present. HTTP/3/QUIC is a separate optional transport profile.	Source checked 2026-10-22 Section 4.2.1 http URI Scheme: default TCP port 80; DASH-IF timing model section 9.2.1 identifies HTTP segment retrieval RFC 9110, June 2022; DASH-IF timing model, 2024-10-24
443 (default)	TCP	Player → Origin / CDN	Profile requirement · Core HTTPS manifests and segments DASH resources carried by HTTPS over TCP; URI-selected origin DASH-IF describes client HTTP segment retrieval (https://dashif.org/Guidelines-TimingModel/). Use each MPD/segment/authentication URI host and explicit port where present. HTTP/3/QUIC is a separate optional transport profile.	Source checked 2026-10-22 Section 4.2.2 https URI Scheme: default TCP port 443; DASH-IF timing model section 9.2.1 identifies HTTP segment retrieval RFC 9110, June 2022; DASH-IF timing model, 2024-10-24

Port / allocation

Transport

Connection / signal flow

Feature and requirement

Evidence

80 (default)

TCP

Player → Origin / CDN

Profile requirement · Core

HTTP manifests and segments

DASH resources carried by HTTP/1.1 or HTTP/2 over TCP; URI-selected origin

DASH-IF describes client HTTP segment retrieval (https://dashif.org/Guidelines-TimingModel/). Use each MPD/segment/authentication URI host and explicit port where present. HTTP/3/QUIC is a separate optional transport profile.

Source checked 2026-10-22

Section 4.2.1 http URI Scheme: default TCP port 80; DASH-IF timing model section 9.2.1 identifies HTTP segment retrieval

RFC 9110, June 2022; DASH-IF timing model, 2024-10-24

443 (default)

TCP

Player → Origin / CDN

Profile requirement · Core

HTTPS manifests and segments

DASH resources carried by HTTPS over TCP; URI-selected origin

Source checked 2026-10-22

Section 4.2.2 https URI Scheme: default TCP port 443; DASH-IF timing model section 9.2.1 identifies HTTP segment retrieval

RFC 9110, June 2022; DASH-IF timing model, 2024-10-24

Gotchas & IT Notes

⚠MPD, segments, authentication and DRM may use different hosts. HTTP/3 is an optional carrier, not a mandatory DASH service.

Source: https://dashif.org/guidelines/