An idea for another key that I would like to get feedback on possible for v2 of the spec.
When thinking about using CMCD data in content steering requests, it might be useful to include a location (loc?) key. Up to the player to determine what loc means (country, state, city, POP, geo region, etc). But might be usefully info for the content steering service to direct traffic to. I realize some of that could be inferred from the ip address, with more private relay stuff it is becoming less reliable.
Good idea!
We may need multiple. Imagine one loc provided by an ISP and identifying network topology (e.g. eNB for mobile, service group for Cable), another calculated by client (GPS + accuracy).
An idea for another key that I would like to get feedback on possible for v2 of the spec. When thinking about using CMCD data in content steering requests, it might be useful to include a location (loc?) key. Up to the player to determine what loc means (country, state, city, POP, geo region, etc). But might be usefully info for the content steering service to direct traffic to. I realize some of that could be inferred from the ip address, with more private relay stuff it is becoming less reliable.