HTTP Random access and live content (status update) Craig Pratu, - - PowerPoint PPT Presentation

▶

Dec 24, 2022 40 likes •111 views

HTTP Random access and live content (status update) Craig Pratu, Barbara Stark, Darshak Thakore WG draft Review requested at IETF 98 No specifjc concerns/comments received Working on testjng the protocol Main focus on

SLIDE 1

HTTP Random access and live content (status update)

Craig Pratu, Barbara Stark, Darshak Thakore

SLIDE 2

WG draft

Review requested at IETF 98
No specifjc concerns/comments received
Working on testjng the “protocol”
Main focus on checking ”intermediary” behavior

SLIDE 3

Test framework

Creatjng a “contjnuous” live video stream
Hosted thru a
CDN
Caching proxy
Custom client that issues the “live” byte range requests
Test
that the implementatjon works as expected
Intermediaries (cdn, cache) work as expected
Send out observatjons/results

SLIDE 4

Next steps

Any feedback/questjons?
Issue LC ?
Keep it open tjll we fjnish the testjng

SLIDE 5

Background slides

SLIDE 6

How it works

Client uses Range semantjcs to determine accessible bytes
Client atuempts to “discover” live random access support

REQUEST RESPONSE HEAD /my_resource HTTP/1.1 HTTP/1.1 206 Partial Content Range: bytes=0- Content-Range: bytes 0-99408383/* Content-Length: 99398384 REQUEST RESPONSE GET /my_resource HTTP/1.1 HTTP/1.1 206 Partial Content Range: bytes=99400000-9223372036854775Content-Range: bytes 99400000-9223372036854775/* Transfer-Encoding: chunked Indicates representatjon length unknown Provides “large number” to indicate live random access Supportjng server “echoes” back same “large number”

SLIDE 7

“backward” compatibility

”non supportjng” server will respond as per RFC7233

REQUEST RESPONSE GET /my_resource HTTP/1.1 HTTP/1.1 206 Partial Content Range: bytes=99400000-9223372036854775Content-Range: bytes 99400000-99634867/* Transfer-Encoding: chunked Provides “large number” to indicate live random access Non-supportjng server sends back what it can support