m32283 Next segment signaling via HTTP HEAD requests – TuC
Summary: Proposes the http head request to be used instead of http header extension. Header extension is part of HTTP1.1. Also the current solution doesn’t require a new request, while head request needs a new separate request. The header extension also doesn’t require the CDN to take any specific action, while head request needs a response by CND.
Resolution: Move this section of TuC to SAND CE to further evaluate.
-
Summary:
1) Annex E conflict: how to use URL query parameter insertion with Annex E, by defining the order: first apply TuC and then Annex E.
2) hashing conflict: the right order: 1) TuC 2) Annex E 3) Signature/hashing.
3) MPD update: we didn’t identify any problem
4) xlink process is not an issue.
5) Suggest to use essential/supplementary property to convey query information instead of using an explicit element such as UrlQueryString.
Dostları ilə paylaş: |