W3C

WoT Security

21 Sep 2020

Agenda

Attendees

Present
Daniel_Peintner, David_Ezell, Elena_Reshetova, Kaz_Ashimura, Michael_McCool, Oliver_Pfaff, Tomoaki_Mizushima
Regrets
Chair
McCool
Scribe
Oliver, Kaz

Contents


scribenick: Oliver

Agenda

Review planned agenda: no objection/changes

Prev minutes

<inserted> Sep-14

Minutes of the WoT Security call on 2020-09-14 reviewed with no objections; will be made public

Lifecycle

Discussion on thing lifecycle: feedback from calls with architecture. Improved alignment with T2TRG proposed. Updated description exists in form of a PR. Status: work-in-progress

<McCool> wot-architecture PR 539

Reviewers are welcome to provide comments (Issue#539 in wot-architecture)

F2F topics

<kaz> Proposed topics

Next discussed and drafted an agenda for WoT Security for upcoming F2F meeting

Currently planned topics (1h altogether): TD changes, OAuth, lifecycle

TD-related issues

wot-thing-description changed rendering script for its main document. That resulted in the need to double-check security-specific sections

Double-check result: structurally okay but let's TODO surface. Need to resolve or remove them

<McCool> https://github.com/w3c/wot-thing-description/issues/965

This problem is captured in issue#965 in wot-thing-description

Suggestion is to comment them out, no objection

Joint calls

<inserted> Issues for the joint call agenda

Joint calls are planned with W&N, JSON-LD, DID groups

Preparation work is addressed by issue#932-934 in WoT

Also call with MEIG group planned

New additional issue#936 created for prep'ing joint call with MEIG

Review remaining issues

<kaz> wot-security issues

McCool:(quickly skims the remaining issues)

Joint call agenda - revisited

<inserted> Issues for joint meeting agenda

Demands for joined call discussion topics are welcome. Bring proposals up in the above mentioned issues

<McCool> https://github.com/w3c/wot/labels/agenda

scribenick: kaz

Testing

(will be discussed during the Testing call)

issues and PRs

<kaz> Issue 138 - Review Lifecycle model

scribenick: Oliver

Issue#138 is superseded by issue#169 (now closed). So issue#138 gets closed

scribenick: kaz

Kaz: will we create another (smaller) issue to review the updated lifecycle section from the Architecture draft then?

McCool: can create a new issue for that purpose

scribenick: Oliver

(New issue#192 created to review updated thing lifecycle in Architecture)

scribenick: kaz

<kaz> new issue 192 for cross-reference with wot-architecture

McCool: any other issues you think done?

<kaz> Issue 65 - Consider moving Thing lifecycle discussion to Architecture

McCool: not sure this is done, let's check next time.

[adjourned]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/11/16 08:27:31 $