Mark Foltz

We investigated using PSK with TLS 1.3 and decided it wasn't suitable for this application. The current authentication proposal (in Section 8) is a mutual authentication handshake that generates a...

Based on TPAC discussion I'll take an action to share data on the success of SSDP and mDNS "in the field" and in particular how often one succeeds when the...

At the Berlin F2F I shared reliability data for SSDP and mDNS, and based on that we resolved to make mDNS mandatory for controllers and receivers, and make SSDP a...

Assuming that PR #59 is considered a good approach, we should apply it to mDNS as well (via a TXT record).

There was a proposal here from the Berlin F2F that apparently wasn't captured in GitHub: https://www.w3.org/2018/05/17-webscreens-minutes.html#x06 > For SSDP, make advertisement of supported schemes truly optional, in that controllers will...

Based on the thread in PR #56, we'll use this issue to cover a more general definition of "guest mode." Since that's out of scope for v1, marking as a...

I'll add this PR as a topic to the agenda document for TPAC.

Bumping this up for consideration at TPAC during rechartering discussions. Based on discussions with partners, interoperability with HbbTV 2.0 and related, shipped protocols would be an incentive to adopt the...

From https://www.w3.org/2017/11/06-webscreens-minutes.html#x18: ACTION: @louaybassbouss to investigate how to do HbbTV scheme with parameters, and look into HbbTV privacy aspects ACTION: @mfoltzgoogle to look into HbbTV communication channel requirements in general

Also clock synchronization and clock skew correction were mentioned as potential uses for connection messages. The HbbTV media synchronization spec may provide some inspiration.