That?s because BLE is not supported in any OCF spec. From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of ??? Sent: Tuesday, August 2, 2016 6:41 PM To: JinHyeock Choi <jinchoe at gmail.com>; ??? <bg.chun at samsung.com> Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] OCF Endpoint Implement on iotivity
Hi JinHyeock I have some doubt about the endpoint spec. since I can't find that how to express BLE MAC address in "eps". most of BLE platforms is not supporting Public API to get own address. it means that 'eps' will not be added own BLE address of CoAP server. To conclude, the spec will not be useful for all of plarforms. if you have any idea upper issue. please let me know. Regrads, Jihwan =================================================================================== Looks fine. This is the current Endpoint specification https://workspace.openconnectivity.org/apps/org/workgroup/architecture_tg/email/archives/201608/msg00004.html which ATG has just reviewed & is planned for 0.3 spec. best regards JinHyeock On Mon, Aug 1, 2016 at 5:45 PM, ??? <bg.chun at samsung.com<mailto:bg.chun at samsung.com>> wrote: Hi, All I will implement OCF Endpoint on iotivity. Endpoint is Information which indicate available messaging protocol about each resource on server. and resource can has one or multiple Endpoints. Below is example of "oic/res" with "eps" parameter which represented endpoint on resource. { "href": "/a/light", "rt": ["core.light", "core.brightlight"], "if": ["oic.if.baseline", "oic.if.ll"], "p" : {"bm" : "3", "sec" : "false",}, "eps": [ {"ep": "coap://[fe80::a4ca:5493:e96:3cea]:1111", "ttl": 86400, "pri": 2}, {"ep": "coaps://[fe80::a4ca:5493:e96:3cea]:1112", "ttl": 86400, "pri": 1}, {"ep": "coap+tcp://[2001:db8:a::123]:2222", "ttl": 86400, "pri": 3} ] } More detail in jira task(IOT-1207) https://jira.iotivity.org/browse/IOT-1207 Plz see concept of endpoint on attached documents on jira, and feedback on jira or mai. thank you. [cid:image001.png at 01D1ECEF.206E6660] _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev --------- Original Message --------- Sender : JinHyeock Choi <jinchoe at gmail.com<mailto:jinchoe at gmail.com>> Date : 2016-08-02 01:36 (GMT+9) Title : Re: [dev] OCF Endpoint Implement on iotivity To : ???<bg.chun at samsung.com<mailto:bg.chun at samsung.com>> CC : iotivity-dev at lists.iotivity.org<iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org%3ciotivity-dev at lists.iotivity.org>> _______________________________________________iotivity-dev mailing listiotivity-dev at lists.iotivity.orghttps://lists.iotivity.org/mailman/listinfo/iotivity-dev<mailto:listiotivity-dev at lists.iotivity.orghttps://lists.iotivity.org/mailman/listinfo/iotivity-dev> [cid:image001.png at 01D1ECEF.206E6660] [http://v70ext.samsung.net/mail/ext/v1/external/status/update?userid=jihwan.seo&do=bWFpbElEPTIwMTYwODAzMDE0MTAzZXBjbXMxcDU1NWUxOTRkNTE0MDQ3NzUzM2E1ZjZkNjY5OGFlMDc2MCZyZWNpcGllbnRBZGRyZXNzPWlvdGl2aXR5LWRldkBsaXN0cy5pb3Rpdml0eS5vcmc_] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160803/ee7c45f6/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 33527 bytes Desc: image001.png URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160803/ee7c45f6/attachment.png>
