Mark Foltz

Proposal by David Schinazi in code review: > It sounds like the OpenScreenProtocol specification is using SNI incorrectly. The host name in the SNI should be the "Service Instance Name"...

It could be useful in situations where multiple agents are sharing a IP:port, because of proxies, or firewall rules preventing binding of multiple ports. However it's not strictly necessary.

I have gone ahead and filled in the fields for `secp384r1` and `ecdsa-with-SHA384`. Please take a look to see if you have any additional comments.

Tagging @tidoust in case he didn't see my last comment :)

The current protocol allows the agent starting remote playback to send HTTP headers to the agent fetching the resource with the `remote-playback-start-request`. https://w3c.github.io/openscreenprotocol/#remote-playback-protocol If we want to require specific headers...

Would be great for someone in the group to investigate and report back here on the possibilities for the mDNS sleep proxy.

We have moved away from mDNSResponder and onto our own mDNS stack, so the earlier length limits are no longer an issue. Still, should keep an eye on overall TXT...

We also need to fix the certificate subject name not to refer to the certificate fingerprint.

> Regarding the subject name, similarly replacing it with the serial number could look as follows: That sounds like a great approach. bakkem@, do you have the capacity to put...

> It seems "Issuer Name" also has problem. According to the spec, "Issuer Name" is set as the model-name from the agent-info message This should be same as the the...