<trackbot> Date: 13 August 2015

[agenda discussion]

Joint meeting with security coming

William presenting Sensei/IoT

William: billions of devices and many services are using XMPP today
... new extensions to XMPP for IoT
... barcodes/QR codes being incorporated to be used for IoT identification
... Sensei/IoT using XMPP, broker service, single-sign-on, EXI for compression, etc.
... various IoT XEPs being worked on
... new provisional URI schema: iotdisco. Send meta data with URI and can be used for QR-code, RIFD, etc. Enables thing registries.
... Sensei enables scalable SOA. Also allows owner of the device to authorize access to information (better). More trust than encryption. Achieving scale with traditional centralized approaches does not work.
... IoT provisioning (XEP-0324) largely implemented at Sweden and used by major telcos.
... More discussion on TEDS etc tomorrow
... adding SHA-3 hash codes for TEDS. Important for integrity.
... setting up federated cloud for charing and testing. More info at www.sensei-iot.org
... OPC UA: process control. Used in data systems, industrial control etc. Way to talk to legacy systems using modbus etc. opcfoundation.org

Soumya: at the slide about thing registries (iotdisco), how is it different from CoRE weblinks?

William: thing registry is separate capability. Validates that the format of your device is correct. Then can register through provision server. Main idea is to validate the message and IDs are correct. Today hundreds of ways to identify things. [...]

Soumya: plan to support JSON payload in XMPP?

William: XMPP can be used to setup security, but for actual data can use something else.

[review of f2f discussion at Sunnyvale]

Soumya: conclusions: organization of technology landscape and init set of requirements
... need joint sessions with security TF. Next steps: evaluation criteria and conduct evaluation of discovery techs

[see details on slides]

Arne presenting interaction patterns

[see wiki for Tech Landscape]

Arne: "things around me" for discovering things in physical vicinity. Client listens for messages and Thing sends advertisements.
... "Finding things in network". Multicast technologies (CoAP etc), WS-discovery, XMPP SD

<Soumya> scribenick: Ari_Keranen

Arne: "Searching directories", CoAP RD, etc. Pattern: thing registers to directory and client queries the directory
... "Searching across Peers". Only research efforts so far
... "Accessing thing metadata". CoRE link format, HATEOAS, Sensor Observation Service

Ari: have you looked into P2PSIP WG's RELOAD work?

Arne: not yet, will do

See: https://tools.ietf.org/html/draft-jimenez-p2psip-coap-reload-10

[evaluation criteria for tech landscape discussion]

Soumya: is the current aspect list sufficient?

Ari: important to have re-usable parts that are used not only for discovery but application etc (so that we will not end up with many). Will send e-mail about that.

Soumya: will have separate brainstorming session on this on following sessions

[security issues discussion]

Soumya: pick up most important issues for now. Are the listed points good as start (access control, privacy, trust, authorization)?

No objections

Soumya: this will start as input to next week discussion. All OK with that?

No objections

Arne: at the mailing list several people have proposals for work items for actual WG following up IG. Do we have work items from this TF that we want to formulate?

Soumya: preparing couple of points. Joerg said each proposal should have few main points. Will send proposal to group soon. Also to wiki. Maybe discussion on that in next meeting. Encourage all to think issues on discovery side and submit to discover TF wiki.

Arne: anyone sees definite work items already?

Soumya: one item could be joint item with security: access control for discovery. Very important for e.g. e-health and smart home. Depending on access control in place, can discovery different things.
... also discovery API aspects.

Arne: access control would be part of web based API

[meeting ended]

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/security/discovery/
Found ScribeNick: Ari_Keranen
Inferring Scribes: Ari_Keranen

WARNING: No "Topic:" lines found.

Present: Soumya Ari_Keranen

WARNING: Fewer than 3 people found for Present list!

Found Date: 13 Aug 2015
Guessing minutes URL: http://www.w3.org/2015/08/13-wot-di-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report