Organisation internationale de normalisation

ISO/IEC 23009-1 AMD 2 Spatial Relationship Description, Generalized URL parameters and other extensions

This amendment to ISO/IEC 23009-1 adds the ability for MPD authors to express:

• 
  Spatial relationships between representations in the MPD;
  

• 
  Flexible parameter insertions in URLs used to query media segments;
  

• 
  Role @values compatible with the kind values used in the W3C HTML5 recommendation;
  

Different signaling of client authentication and content authorization methods

2. Contributions

Number	Session	Title	Source	Dispositions
m34837	DASH	Summary of Voting on ISO/IEC 23009-1:201x/DAM 1	SC 29 Secretariat	Refer 14859
m35150	DASH	CE-SAND: HTTP Communication Channel	Thomas Stockhammer	Accepted 14862
m34957	DASH	Clarification of MPD to Initialization Segment and ContentComponent Use	Bob Lund, Arianne Hinds, Cyril Concolato	Accepted 14856
m35055	DASH	Common template and decision process for SAND messages	Emmanuel Thomas, Ali C. Begen, Mary-Luc Champel, Thomas Stockhammer	Accepted 14855
m35069	DASH	CE SAND: comparison of protocols for altlist signaling	Remi HOUDAILLE, Charline TAIBI	Noted
m35074	DASH	CE SAND: update for parameters	Remi HOUDAILLE, Charline TAIBI	Noted
m35106	DASH	SAND prioritization based on 3GPP requirements	Imed Bouazizi	Noted
m35109	DASH	On SAND Metrics Reporting	Ozgur Oyman	Noted
m35212	DASH	DASH SAND CE: “Scenes’ Clustering” as a new parameter to DANE	Md. Jalil Piran, Doug Young Suh	Noted
m35314	DASH	Activity in IETF webpush Working Group Related to the SAND and FDH CEs		Noted
m34631	DASH	DASH sub-frame format of WebSocket	Tatsuya Igarashi, Yasuaki Yamagishi, Mitsuhiro Hirabayashi	Noted
m34632	DASH	[CE-FDH] Benefits of HTTP/2 Push feature for DASH	Franck Denoual, Frederic Maze	Noted
m34641	DASH	Client-requested push for DASH [CE-FDH]	Emmanuel Thomas (TNO), Jeroen Famaey (iMinds), Jeroen Schaballie (iMinds)	Noted
m34643	DASH	[CE-FDH] Dash over HTTP 2.0 using K-Push	Viswanathan (Vishy) Swaminathan, Sheng Wei, Kevin Streeter	Noted
m35107	DASH	DASH over WebSockets: implementation and sub-protocol specification	Imed Bouazizi	Noted
m35105	DASH	Client Behavior Control	Imed Bouazizi, Shaobo Zhang	Noted
m34913	DASH	Comment for DASH DAM 2: spatial_set_id parameter in SRD	Shuichi Watanabe, Takuya Iwanami, Yasuaki Tokumo	Noted
m35052	DASH	Live SRD-based tiled streaming of UHD video during 2014 Commonwealth Games	Lucia D'Acunto, Omar Niamut, Arjen Veenhuizen, Ray van Brandenburg, Emmanuel Thomas	noted
m34881	DASH	Signaling Schemes For Identifying Ownership Of Content Components	Luntian Mou, Tiejun Huang, Xin Wang, Yongliang Liu, Baocai Yin	Noted
m35051	DASH	Status of IETF-MPEG discussions around URI signing in DASH	Emmanuel Thomas, Xin Wang	Accepted 14858
m35077	DASH	Signaling associated services	Alex Giladi	Accepted 14861
m35078	DASH	Native ad tracking using template parameters	Alex Giladi	Accepted 14857
m35081	DASH	Clarifications on DASH EssentialProperty	Jean Le Feuvre, Cyril Concolato, Franck Denoual, Frédéric Mazé, Eric Nassor	Noted
m35082	DASH	Clarifications on DASH SubAssetIdentifier	Jean Le Feuvre, Cyril Concolato, Franck Denoual, Frédéric Mazé, Eric Nassor	Accepted 14857
m35088	DASH	Proposed corrections on DASH	Jean Le Feuvre, Cyril Concolato	Accepted 14858
m35100	DASH	Clarification on Representation Association in DASH	Shaobo Zhang, Xin Wang	Accepted 14861
m35135	DASH	On signaling Interoperability Points	Iraj Sodagar	Noted
m35151	DASH	DASH Errata Issues	Thomas Stockhammer	Accepted 14858
m35155	DASH	Period Continuity	Thomas Stockhammer	Accepted 14857
m35157	DASH	On DASH TuC	Thomas Stockhammer	noted
m35164	DASH	Clarification on URL Parameter Insertion	Shaobo Zhang, Xin Wang	Accepted 14861
m35262	DASH	DASH: Aggregated Temporal Quality Signalling for DASH Sub-representations	Zhu Li, Imed Bouazizi,	noted
m35347	DASH	Report on SAND	Ali C. Begen, Emmanuel Thomas, Mary-Luc Champel	Noted
m35356

3. Summary of discussions

1. m34631 DASH sub-frame format of WebSocket

Summary: summary of how the websocket works, server managing the session. Requires lots of protocol details to be built. A separate track from HTTP2.0.

Disposition: Noted. Since HTTP2.0 seems simpler protocol and is becoming more popular in implementations, the request from the proponents is to bring justification and benefits of using Webscocket instead of HTTP2.0. Also include the flow diagram for server-client interaction from start to end of streaming.

2. m35107 DASH over WebSockets: implementation and sub-protocol specification

Summary: Shows how the websocket is implemented. In this scheme, the client manages the session.

3. m34632 [CE-FDH] Benefits of HTTP/2 Push feature for DASH

Summary: showing the benefits of HTTP.2 push for reducing the start of delay. There are some question that the simulation shows one RTT delay saving. It also suggest an element to signal BaseURL that support push. Push can be two modes: leave to the server, or push k segments. Need a control sub-protocol between server and client for negotiation.

4. m34641 Client-requested push for DASH

Summary: a template approach in which clients provide to server and server push according the template. Need a dedicated module in server that translate the clients request to multiple HTTP GETS. Can do the same for HTT2.0. Three different functions are needed: 1) pipelining of the segment delivery of same media, 2) scheduling of delivery of each segment based on availability, 3) multiplexing multiple segment request from various media components/scalable layers.

5. m34643 [CE-FDH] Dash over HTTP 2.0 using K-Push

Summary: demonstrating how the push would reduce the start-up time. Signaling of k-push using header extension. The header extensions will go through proxies.
Summary of HTTP2.0: The following questions need to be addressed:

1. 
   DASH intelligences (segment availability, templates) required beyond the transport protocol on origin sever and network elements?
   
2. 
   Should the protocol signaling outside of MPD or inside? We agree that we prefer signaling be outside of MPD.
   
3. 
   How sophisticated the multiple request and control subprotocol should be? (Template vs list of URLs)?
   
4. 
   Can we do a generic solution that’s it is not tied to DASH
   
5. 
   Addressing the requirement?
   

Continue this CE. Update the CE description. Refine evaluation criteria.

6. m35314 Activity in IETF webpush Working Group Related to the SAND and FDH CEs

Summary: IETF is starting a WG on HTTP PUSH.

7. M35347 SAND CE Report

Summary: report

8. m35055 Common template and decision process for SAND messages

Summary: a template for SAND parameter submission.

Disposition: Accepted in CE description (with the minor change saying the JSON is an example). Only parameter submissions that are in this template will be reviewed at the next meeting. The existing parameters need to be resubmitted using this template for the next meeting.

9.