<scribe> scribenick: kaz

Online PlugFest

McCool: several PRs

PRs

PR 527 - Preparation doc by Intel

McCool: to be merged

(and merged now)

PR 519 - converter fixes, revised Festo-Simulator TD

Kaz: related to the Bundang f2f?

McCool: combined content
... Bundang report and new scenario proposal
... (merged it)
... one more PR by Soumya

PR 506 by Soumya

Online PlugFest prep. doc

preparation-Intel.md

McCool: would like to contribute to the network setting
... 2 Thing Directories, one OAuth server
... also VLAN servers
... all the machines can join one specific network
... also will work to make local network secure
... 1.2 Public Proxies
... authentication available
... OCF service, camera service, speech service, etc.
... 1.3 Public Tools
... don't have to recreate accounts
... two paths: W3C and GitHub
... hoping to enable that
... btw, which GH group/repo includes everybody?
... w3c/wot?

Kaz: w3c/wot should be the largest one
... but not sure if everybody is included
... maybe we can create a specific repo and/or team for plugfest effort

McCool: ok
... authentication information should be distributed via W3C email and/or use OAuth2
... and validation service
... 2. Participants and Servients
... information on Intel servients
... 3. Checking points for the next plugfest
... 3.1, 3.2, ...
... what kind of eventing model to be used?
... e.g., HTTP+Webhooks

<mlagally> ML: have HTTP+Webhooks on my todo list

McCool: 3.2.7 Security
... last time: basic and digest
... would work on oauth2 and apikey as well
... for CoAPS: psk cert, public
... maybe we need some mechanism to handle HTTPS local for HTTPS-based connection
... hopefully node-wot would be updated to work with CoAPS
... 4. Use Cases
... don't have use cases yet
... 5. Requirements for PlugFest Environment
... any questions?

Kaz: we can start with technical topics and existing/expected servients
... and during or after the online plugfest, we can think about integrated use cases and scenarios

McCool: right
... we can concentrate on technical features for the online plugfest
... and think about usecase scenarios for TPAC later
... Lagally has some use case scenarios here

Lagally: best to show industry adaption
... many people are interested and look at W3C work
... it is important to show integration among different companies to other interested parties

Scenarios

Koster: we need invent some subprotocol for websocket
... also strong need for webgook
... and patterns for actions
... TD fragment media-type
... action/event description
... plug existing pattern
... also uri template
... handling multiple events
... can write up those features

McCool: we can have a list

Koster: we should have that at the main call

McCool: you have write access to this repo. right?
... please add new features here at "Goals" section

Koster: fine

Kaz: btw, the current topics within the "Goals" section are actually "Target features"

McCool: can make it a subsection of "Goals" section and make it "Target Features" subsection

Kaz: good

McCool: (also adds "Out of Scope Features" subsection to the "Goals" section)

Kaz: good

McCool: any other comments?

Lagally: good

McCool: two scenarios here
... home integration and industrial integration
... could classify the latter into several subsections?

Lagally: what do you mean?

McCool: maybe could add "Enterprise integration scenario"?
... just a proposal

Kaz: do you want to categorize those possible use case scenario based on the security viewpoint?

McCool: one or several aspects

Lagally: when I generated those use case scenarios, I was thinking about what we could do using the existing modules generated by the current participants

Kaz: maybe it would be easier to understand if we simply think about several possible modes for each use case scenario?
... e.g., free-mode vs. enterprise-mode

<mlagally> for the markdown table try the following syntax:

<mlagally> | Left Aligned | Center Aligned | Right Aligned |
|:------------- |:---------------:| -------------:|
| col 3 is | some wordy text | $1600 |
| col 2 is | centered | $12 |
| zebra stripes | are neat | $1 |

Toru: question about the authorization server
... what would be the procedure?

McCool: can provide a reverse proxy and an OAuth server
... need to investigate the GH server as well
... would like to put the information together as a one pager

Toru: would be appreciate if you could document that

McCool: will do HTTPS stuff first
... and then CoAP and MQTT

Testing

McCool: updated the testing plan
... let's discuss the detail next week

Action for the next call

McCool: the number one task for everybody is generating a preparation-YOU.md file under plugfest/2018-sept-online for the next call

[adjourned]