2.1.   Identivierse

We have a room for WG to use. Dima and Nat will be there. If there is an interest for doing a F2F, let us do it.

3.1.   Federation Draft-029 (Giuseppe)

Giuseppe introduced the new draft.

• Fixed #1921: brand new JWS Header parameter, trust_chain.
• Fixed #1879, #1881, #1883, #1885: introductory text, metadata section, editorials.

Giuseppe also introduced a requirement document as input to eIDAS expert group.

• https://docs.google.com/document/d/1Dk_8UmytCI4VhCx5VMnXmEzdXRvgJozGeq1GNHZOQik/edit#heading=h.d5t9f0upf26i

JWT-based solution (OpenID Federation spec) seems to be the only way to satisfy those requirements.

He may consider making it a blog post at openid.net.

3.2.   (NWIP) Core Extension: Extra Display Types for TVs and Modern Feature Phones (Kosuke)

Kosuke introduced a new work item proposal on "Core Extension: Extra Display Types for TVs and Modern Feature Phones".

OpenID Connect Core 1.0 has "wap" but modern feature phones have different rendering capabilities. Thus, it is suggesting "fone" as a new display parameter.

Similarly, "tv" is suggested as a new display parameter for smart TVs.

Giuseppe pointed out that in the Italian federation they are using SVG to cope with different display characteristics. He also mentioned the possibility of "ascii", which might be valid in the case of something like a thermometer.

There was no push back on the suggestion.

Kosuke is going to send a rendered version to the listserv and nat is going to make a call for adoption.

ref: https://bitbucket.org/openid/connect/issues/1927/core-extension-extra-display-types-for-tvs

4.1.   #1791 - [Federation] Address gaps and inconsistencies in the Trust Mark validation spec (Giuseppe)

• #1791

These changes are to be incorporated for -30.

There is another related issue that came up on the editor's call while discussing this issue. This is not yet filed.

The call adjourned at 23:37 UTC.