Mark Foltz

For ciphers, there is basically nothing to do here. The required ciphers for TLS 1.3 cover both newer and older hardware: * For anything with ARMv8 and newer (i.e. anything...

Point of reference: [Comparison of TLS implementations](https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations#Defined_curves_in_RFC_8446_(for_TLS_1.3)_and_RFC_8422,_7027_(for_TLS_1.2_and_earlier))

I suggest closing this issue and opening new ones for items that deserve further discussion. > extended mime types in source tag? This is already included in the current spec....

@louaybassbouss wrote in Issue #23: > Yes we can do this by using these node modules peer-ssdp, peer-upnp and peer-dial (all available on npm) to make an experiment with different...

Tagging @GrumpyOldTroll, who mentioned they have a contact who could comment on whether an SNI was *required* by current TLS implementations.

Re-reading the public-webscreens@ thread - there seem to be two possible behaviors that need to be clarified: 1. Do we need a mechanism for a presentation to tell the user...

Going to re-review this for possible followup at TPAC.

From https://www.w3.org/2017/11/06-webscreens-minutes.html#x18: ACTION: @anssiko to add v2 feature in #32 provisionally to the Charter 2018

@igarashi50 - this looks like the most relevant issue to the [comment you made at the Berlin F2F](https://www.w3.org/2018/05/17-webscreens-minutes.html#x03): > Last TPAC, I asked whether the API would support connection to...

Actually it's part of the steps to [reconnect to a presentation](https://w3c.github.io/presentation-api/#reconnecting-to-a-presentation): > 6.9: Establish a presentation connection with newConnection. Which already defers to the user agent on the mechanism to...