13:01:40 RRSAgent has joined #wot-pf 13:01:40 logging to http://www.w3.org/2017/10/25-wot-pf-irc 13:01:57 Meeting: WoT PlugFest 13:02:28 present+ Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool, Ryuichi_Matsukura, Takeshi_Sano, Taki_Kamiya, Toru_Kawaguchi 13:02:30 dape_ has joined #wot-pf 13:03:52 present+ Dainel_Peintner 13:06:21 present+ Uday_Davuluru 13:06:58 present+ Tomoaki_Mizushima 13:07:23 uday has joined #wot-pf 13:08:12 yamada has joined #wot-pf 13:08:43 ohura has joined #wot-pf 13:08:56 present+ Michael_Koster 13:09:01 https://www.w3.org/WoT/IG/wiki/PlugFest_WebConf 13:09:08 agenda 13:09:12 topic: Agenda 13:09:21 mjkoster has joined #wot-pf 13:09:25 taki has joined #wot-pf 13:09:54 kaz: agenda should include 13:10:12 ... Matsukura's update, Koster's input, McCool's update 13:10:33 https://github.com/mryuichi/documents 13:10:40 ... physical requirements, scenarios 13:10:48 topic: Matsukura-san's update 13:10:52 Mizushima has joined #wot-pf 13:11:14 matsu: shows slides 13:11:30 -> https://github.com/mryuichi/documents/blob/master/CollectionServientInfo2017r1.pptx 13:11:43 matsu: would like to see the information here is correct 13:11:50 ... starting with Panasonic 13:12:00 ... Siemens 13:12:04 ... Lemonbeat 13:12:12 present+ Kazuaki_Nimura 13:12:20 present+ Masato_Ohura 13:12:23 ... Intel 13:12:34 mm: details in my presentation 13:13:25 kaz: so you'd like to clarify which servient from Intel will get connected here 13:13:28 matsu: yes 13:13:40 mm: using SSH tunnel 13:13:51 ... not really specialized proxy 13:13:58 ... proxy and tunnerl 13:14:04 s/tunnerl/tunnel/ 13:14:18 present+ Takeshi_Yamada 13:14:28 present+ Keiichi_Tokuyama 13:14:31 tokuyama_ has joined #wot-pf 13:15:09 matsu: would like to clarify which servient can speak the WoT interface 13:15:25 mm: I have OCF devices 13:15:32 ... all those devices talk CoAP 13:15:56 ... they're WoT devices because they use TD 13:16:58 kaz: so we should clarify which servient exposes their capability how 13:17:05 ... e.g., exposeThing 13:17:31 matsu: which device from Intel can be connected here? 13:17:54 q? 13:18:20 q+ 13:18:41 ... what is the protocol for the OCF devices? 13:19:09 ... want to clarify which part of your servients would talk with the others' servients 13:19:13 q? 13:19:17 mk: agree 13:19:29 ... would add a point for interoperability 13:19:54 ... not all the servients have the capability of consuming, e.g., OCF devices 13:20:27 ... we really have to see the orchestration 13:20:41 ... planning to do that on proxies 13:20:51 ... adapt to every protocol 13:20:59 mm: points of connection 13:21:29 ... you can talk to devices using their consuming protocols 13:21:49 mk: just function as gateway 13:22:06 ack m 13:22:25 ... added local application servient by node-red to this diagram based on Koster's input 13:22:49 ... next [Servients and protocols (1 of 2)] 13:23:01 ... Lemonbeat by Uday 13:23:09 ... next [Servients and protocols (2 of 2)] 13:23:15 ... Intel and SmartThings 13:23:47 ... Fujitsu's application can run on either the remote/local side 13:23:51 q+ 13:24:02 mm: local link vs global link 13:24:13 ... global URL goes through the remote proxy 13:24:23 ... my plan is both of them in the TD 13:24:32 ... and try the local link first 13:25:08 ... local links wont' work outside 13:26:10 matsu: this time there is no remote device servient 13:26:18 mm: motion sensor, camera, etc. 13:26:23 s/servient/servient?/ 13:26:52 mk: endpoint app 13:26:57 ... happen on the cloud 13:27:02 ... remote device servient 13:27:09 ... expose REST api there 13:27:39 ... we can call that a remote device servient 13:27:49 ... how to make the protocol binding 13:27:56 ... doesn't require a bridge 13:28:04 ... could be done by software adaption 13:28:19 q+ 13:28:35 mm: my suggestion is definition based on the architecture document 13:28:45 ... definition could be operational 13:28:56 ... we can add additional protocols 13:29:08 mk: SmartThings API is REST API 13:29:35 mm: note that we avoided using "servient" in many places 13:29:45 ... a lot devices can expose their capability 13:30:12 q? 13:30:14 ack k 13:30:17 ack m 13:30:18 q+ 13:31:34 kaz: should we see Koster's proposal and McCool's proposal 13:31:53 ... and think which part could be connected which servient from Matsukura's diagram 13:32:02 s/should we/we should/ 13:32:46 mk: remote proxy and local proxy are connecting points 13:32:55 q+ McCool 13:33:26 ack k 13:33:54 matsu: Panasonic's device servient can be connected with the other's servient? 13:34:11 yama: please show the table (1 of 2) 13:34:14 ... some update 13:34:31 ... left column is only HTTP 13:34:54 ... right column is HTTPS+WSS 13:35:00 s/only HTTP/only HTTPS/ 13:35:22 mm: will bring Amazon Alexa 13:35:51 ... maybe it will be confused given Panasonic also will bring their Alexa 13:36:03 ... can change the command, though 13:36:14 ... we can discuss it during PlugFest 13:36:20 ... do you use Home Skill? 13:36:32 kawa: only custom skill 13:36:41 mm: can do either way 13:36:54 q? 13:36:56 ack m 13:37:08 uday: please show Lemonbeat 13:37:42 ... not water valve but binary actuator 13:38:10 mm: possible scenario... 13:38:56 kaz: which servient do you want to get connected? 13:39:03 uday: any ones 13:39:48 kaz: will you provide local proxy as well? 13:39:53 uday: no... 13:40:02 matsu: but local gateway might be a local proxy? 13:40:08 uday: ah, yes 13:40:45 mm: will use SSH traverse for AVS 13:41:09 mk: websocket works with SSH tunneling. right? 13:41:29 mm: you can tunnel the protocol through 13:42:47 kaz-win has joined #wot-pf 13:43:56 matsu: which part from your system would be connected as a servient? 13:44:23 mm: shows his updated slides 13:44:28 [slides tbd@@@] 13:44:51 mm: explains his setup 13:45:16 ... [1.5 Metadata Bridging] 13:45:26 ... can use other specialized solution 13:45:47 ... this framework includes just standard setting 13:46:33 ... 13:47:00 mk: local one vs global one 13:47:14 ... there are 2 resource directory 13:48:26 ... the global thing can be reachable from the local side 13:48:32 ... but... 13:49:04 mm: you want to use local things available 13:49:33 ... maybe orthogonal issue from proxy 13:49:50 matsu: there are a lot of issues unresolved 13:50:12 ... after the upcoming PlugFest, we need to clarify them 13:51:19 kaz: so we should ask McCool to think about which part from McCool's diagram could be connected with which part from Matsukura's diagram 13:51:32 mm: WoT-aware proxy and WoT-transparent proxy 13:51:57 ... not useful to worry too much about NAT 13:52:22 mk: possibly one separate proxy which pipes the other 13:52:49 matsu: what about Koster's proposal? 13:52:56 topic: Koster's configuration 13:53:19 -> https://lists.w3.org/Archives/Public/public-wot-ig/2017Oct/att-0028/wot-plugfest.pptx Koster's slides 13:53:32 mk: [Configuration] 13:54:10 ... ST could, Om2m, Remote Gateway, App Droplet 13:54:14 ... router 13:54:16 ... Lan 13:54:36 ... ST Hub, MQTT Sensor, IKEA Hub, OCF Bridge, Local WoT Gateway, Local WoT App 13:54:47 ... OCF, LWM2M, HTTP, HTTP/WS 13:55:16 ... [Configuration - OCF IKEA Bridge] 13:55:24 ... who finds what? 13:55:58 q+ 13:56:01 ... everything could be described using TD 13:56:08 ... update periodically 13:56:19 ... [Configuration - SmartThings] 13:56:47 ... SSH tunnel between ST Cloud and ST Hub 13:57:47 ... remote proxy (gateway) - local proxy (gateway) - local WoT App 13:58:55 s/OCF, /MQTT, OCF, / 13:59:14 ... [All Configurations] 13:59:26 ... my view for plugfests 13:59:36 mm: IETF collocated with OCF 13:59:47 ... OCF Melaga, Spain 13:59:57 ... one of the possible places for WoT 14:00:13 ... let's have discussion during TPAC 14:00:43 mk: TDTRG? 14:01:00 ... interoperability with others would be good 14:01:04 q? 14:01:08 ack u 14:01:34 uday: interoperability between IKEA hub and OCF bridge? 14:01:51 mk: node iotivity on rhaspvery pi 14:02:19 ... just doing easy way to expose to OCF 14:03:00 uday: not semantically interoperable 14:03:52 q? 14:04:23 (some more discussion) 14:04:55 kaz: Koster, are you aware which part of your diagram to be connected which part of Matsukura's diagram? 14:05:00 mk: yes 14:05:12 ... local gateway is local proxy 14:05:18 ... remote gateway is remote proxy 14:05:46 ... apps consuming proxy 14:06:20 ... IKEA hug has OCF bridge for local WoT proxy 14:06:27 matsu: thanks 14:06:44 ... will update my diagram 14:07:02 ... any other topics for today? 14:07:09 mm: schedule? 14:07:17 ... local/remote directory? 14:07:49 kaz: we can have another call on Nov. 1 14:08:01 ... but do we need another call before that? 14:08:14 mm: we can have discussion at TPAC as well 14:08:35 uday: fyi, Tue/Wed are holidays here 14:09:05 mm: next week have to work on implementation 14:09:22 dape: based on the FPWD 14:10:00 mm: can call in next week 14:10:11 [adjourned] 14:10:18 rrsagent, make log public 14:10:24 rrsagent, draft minutes 14:10:24 I have made the request to generate http://www.w3.org/2017/10/25-wot-pf-minutes.html kaz