Hi Each OCF 1.0 feature implementer,
By Jan, we had expected to finalized the OCF1.0 feature merge except security.
This is the current status.
- AllJoyn Bridge (Todd)
https://gerrit.iotivity.org/gerrit/#/q/status:merged+project:iotivity-alljoyn-bridge+branch:wip
- Not Merged to master yet
<https://gerrit.iotivity.org/gerrit/#/q/project:iotivity+owner:%22Todd+Malsbary+%253Ctodd.malsbary%2540intel.com%253E%22+status:pending>
https://gerrit.iotivity.org/gerrit/#/q/project:iotivity+owner:%22Todd+Malsbary+%253Ctodd.malsbary%2540intel.com%253E%22+status:pending
- not merged yet
- Introspection
<https://gerrit.iotivity.org/gerrit/#/c/16405/>
https://gerrit.iotivity.org/gerrit/#/c/16405/ - Merged
- Endpoint Information (MJ)
<https://gerrit.iotivity.org/gerrit/#/c/14123/>
https://gerrit.iotivity.org/gerrit/#/c/14123/ - Reviewing
<https://gerrit.iotivity.org/gerrit/#/c/10797/>
https://gerrit.iotivity.org/gerrit/#/c/10797/ - Reviewing
- Versioning (Ziran)
<https://gerrit.iotivity.org/gerrit/#/c/16505/>
https://gerrit.iotivity.org/gerrit/#/c/16505/ - Reviewing
- OCF 1.0 Security
Not yet.
To prepare the upcoming plugfest,
I?d like to create the tag to test start (Release Lead),
Start the Test against the OCF CTT by IoTivity QA team.
However, there are still some missed part from OCF1.0 feature. (Todd, MJ, Ziran)
Please merge them ASAP and notify for test start.
BR, Uze Choi
From: MyeongGi Jeong [mailto:[email protected]]
Sent: Wednesday, January 25, 2017 11:31 AM
To: DWARKAPRASAD DAYAMA; 'Malsbary, Todd'; 'Heldt-Sheller, Nathan'; 'Srikrishna
Gurugubelli'; Ziran Sun
Cc: Uze Choi
Subject: RE: [Ziran, Todd, Sri, MJ, Nathan] [Follow Up] OCF 1.0 implementation
status
Hi, Dwarka.
Actually, EndPoint implementation is finished.
But 2 patchsets are still staying in gerrit code-review.
<https://gerrit.iotivity.org/gerrit/#/c/14123/>
https://gerrit.iotivity.org/gerrit/#/c/14123/
<https://gerrit.iotivity.org/gerrit/#/c/10797/>
https://gerrit.iotivity.org/gerrit/#/c/10797/
I guess, the arguing point is related the conceptual issue, not the technical
one.( for the first patchset )
And the second one, Jenkins build returned failure by some memory leakage, but
it is not related this patchset.
Thanks.
Best Regards,
---
MyeongGi Jeong
Principle Engineer, Software Architect
Software R&D Center, Samsung Electronics Co., Ltd.
+82-10-3328-1130 | +82-2-6147-7699
--------- Original Message ---------
Sender : ???? <dwarka.dayama at samsung.com> ??/??????(S/W??)/????
Date : 2017-01-24 16:03 (GMT+9)
Title : [Ziran, Todd, Sri, MJ, Nathan] [Follow Up] OCF 1.0 implementation status
Hi OCF 1.0 Contributors,
IoTivity release management function lead is ready to create a tag for upcoming
PF in Feb?17. It will be helpful to know the status in regard to Gerrit code /
patch for each of these items.
- AllJoyn Bridge
- Introspection
- Endpoint Information
- Versioning
- OCF 1.0 Security
Starting Thursday, Korea has national holidays until next Tuesday. Hence we
should start the process at earliest.
Regards
Dwarka
----------------------------------------------------------------------------------
Software R&D Center | Software Strategy Team | Open Source Group
Open Connectivity Foundation ? OSWG ? Spec Coordination TG Chair
Iotivity Steering Group ? Advisory Committee
From: ??? [mailto:[email protected]]
Sent: Wednesday, January 18, 2017 10:46 AM
To: Malsbary, Todd <todd.malsbary at intel.com>; ??? <uzchoi at samsung.com>;
???? <dwarka.dayama at samsung.com>; 'Srikrishna Gurugubelli' <srikguru at
microsoft.com>; Ziran Sun <ziran.sun at samsung.com>; Habib Virji <habib.virji
at samsung.com>; ??? <myeong.jeong at samsung.com>; 'Dino Natucci'
<Dino.Natucci at microsoft.com>; Morrow, Joseph L <joseph.l.morrow at
intel.com>; Shetty, Mandeep <mandeep.shetty at intel.com>; jinchoe at
gmail.com; dthaler at microsoft.com; Ram.Jeyaraman at microsoft.com
Cc: Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com>; ???
<soohong.park at samsung.com>; ??? <moonki1.hong at samsung.com>; Mark Trayer
<m.trayer at samsung.com>; Kesavan, Vijay S <vijay.s.kesavan at intel.com>; ???
<jinguk.jeong at samsung.com>
Subject: RE: RE: RE: [Follow Up] OCF 1.0 implementation status
Todd
relieved.
yes, the OIC 1.1 client section still holds.
OCF 1.0 server differentiates /oic/res responses per requesting Client,
which indicates its preference with content-type
(e.g. /application/vnd.ocf+cbor for OCF 1.0 Client).
best regards
JinHyeock
--------- Original Message ---------
Sender : Malsbary, Todd < <mailto:todd.malsbary at intel.com> todd.malsbary at
intel.com>
Date : 2017-01-18 02:14 (GMT+9)
Title : RE: RE: [Follow Up] OCF 1.0 implementation status
To : ???< <mailto:jinchoe at samsung.com> jinchoe at samsung.com>, ???<
<mailto:uzchoi at samsung.com> uzchoi at samsung.com>, ????<
<mailto:dwarka.dayama at samsung.com> dwarka.dayama at samsung.com>,
'Srikrishna Gurugubelli'< <mailto:srikguru at microsoft.com> srikguru at
microsoft.com>, Ziran Sun< <mailto:ziran.sun at samsung.com> ziran.sun at
samsung.com>, Habib Virji< <mailto:habib.virji at samsung.com> habib.virji at
samsung.com>, ???< <mailto:myeong.jeong at samsung.com> myeong.jeong at
samsung.com>, 'Dino Natucci'< <mailto:Dino.Natucci at microsoft.com>
Dino.Natucci at microsoft.com>, Morrow, Joseph L< <mailto:joseph.l.morrow at
intel.com> joseph.l.morrow at intel.com>, Shetty, Mandeep<
<mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com>,
<mailto:jinchoe at gmail.com%3cjinchoe at gmail.com> jinchoe at
gmail.com<jinchoe at gmail.com>, <mailto:dthaler at microsoft.com%3cdthaler at
microsoft.com> dthaler at microsoft.com<dthaler at microsoft.com>,
<mailto:Ram.Jeyaraman at microsoft.com%3cRam.Jeyaraman at microsoft.com>
Ram.Jeyaraman at microsoft.com<Ram.Jeyaraman at microsoft.com>
CC : Heldt-Sheller, Nathan< <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>, ???< <mailto:soohong.park at samsung.com>
soohong.park at samsung.com>, ???< <mailto:moonki1.hong at samsung.com>
moonki1.hong at samsung.com>, Mark Trayer< <mailto:m.trayer at samsung.com>
m.trayer at samsung.com>, Kesavan, Vijay S< <mailto:vijay.s.kesavan at
intel.com> vijay.s.kesavan at intel.com>, ???< <mailto:jinguk.jeong at
samsung.com> jinguk.jeong at samsung.com>
Hi Jin,
Sorry, I should have clarified: section 6.1 of the bridging spec shows both
your response below for OCF 1.0 clients, and my response for OIC 1.1 clients.
I assume the OIC 1.1 client section still holds?
Thanks,
-Todd
From: ??? [ <mailto:jinchoe at samsung.com> mailto:[email protected]]
Sent: Monday, January 16, 2017 1:12 AM
To: Malsbary, Todd < <mailto:todd.malsbary at intel.com> todd.malsbary at
intel.com>; ??? < <mailto:uzchoi at samsung.com> uzchoi at samsung.com>; ???? <
<mailto:dwarka.dayama at samsung.com> dwarka.dayama at samsung.com>;
'Srikrishna Gurugubelli' < <mailto:srikguru at microsoft.com> srikguru at
microsoft.com>; Ziran Sun < <mailto:ziran.sun at samsung.com> ziran.sun at
samsung.com>; Habib Virji < <mailto:habib.virji at samsung.com> habib.virji at
samsung.com>; ??? < <mailto:myeong.jeong at samsung.com> myeong.jeong at
samsung.com>; 'Dino Natucci' < <mailto:Dino.Natucci at microsoft.com>
Dino.Natucci at microsoft.com>; Morrow, Joseph L < <mailto:joseph.l.morrow at
intel.com> joseph.l.morrow at intel.com>; Shetty, Mandeep <
<mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com>;
<mailto:jinchoe at gmail.com> jinchoe at gmail.com; <mailto:dthaler at
microsoft.com> dthaler at microsoft.com; <mailto:Ram.Jeyaraman at
microsoft.com> Ram.Jeyaraman at microsoft.com
Cc: Heldt-Sheller, Nathan < <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>; ??? < <mailto:soohong.park at samsung.com>
soohong.park at samsung.com>; ??? < <mailto:moonki1.hong at samsung.com>
moonki1.hong at samsung.com>; Mark Trayer < <mailto:m.trayer at samsung.com>
m.trayer at samsung.com>; Kesavan, Vijay S < <mailto:vijay.s.kesavan at
intel.com> vijay.s.kesavan at intel.com>; ??? < <mailto:jinguk.jeong at
samsung.com> jinguk.jeong at samsung.com>
Subject: RE: RE: [Follow Up] OCF 1.0 implementation status
Todd
For OCF 1.0 Client,
a Bridge Device returns /oic/res as a single array of Links,
even with multiple bridged Devices as below.
[
{
"href": "ocf://e61c3e6b-9c54-4b81-8ce5-f9039c1d04d9/oic/res",
"anchor": "ocf://e61c3e6b-9c54-4b81-8ce5-f9039c1d04d9",
"rel": "self",
"rt": "oic.wk.res",
"if": ["oic.if.ll", "oic.if.baseline"],
"eps": [{"ep": "coap://[fe80::b1d4]:55555"},
{"ep": "coaps://[fe80::b1d4]:11111"}],
"p": {"bm": 3}
},
{
"anchor": "ocf://e61c3e6b-9c54-4b81-8ce5-f9039c1d04d9",
"href": "/oic/p",
"rt": ["oic.wk.p"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:11111"}]
},
{
"anchor": "ocf://e61c3e6b-9c54-4b81-8ce5-f9039c1d04d9",
"href": "/oic/d",
"rt": ["oic.wk.d", "oic.d.bridge"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:11111"}]
},
{
"anchor": "ocf://e61c3e6b-9c54-4b81-8ce5-f9039c1d04d9",
"href": "/mySecureMode",
"rt": ["oic.r.securemode"],
"if": ["oic.if.w", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:11111"}]
}
{
"anchor": "ocf://88b7c7f0-4b51-4e0a-9faa-cfb439fd7f49",
"href": "/oic/p",
"rt": ["oic.wk.p"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:22222"}]
},
{
"anchor": "ocf://88b7c7f0-4b51-4e0a-9faa-cfb439fd7f49",
"href": "/oic/d",
"rt": ["oic.wk.d", "oic.d.fan"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:22222"}]
},
{
"anchor": "ocf://88b7c7f0-4b51-4e0a-9faa-cfb439fd7f49",
"href": "/myFan",
"rt": ["oic.r.switch.binary"],
"if": ["oic.if.a", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:22222"}]
},
{
"anchor": "ocf://dc70373c-1e8d-4fb3-962e-017eaa863989",
"href": "/oic/p",
"rt": ["oic.wk.p"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:33333"}]
},
{
"anchor": "ocf://dc70373c-1e8d-4fb3-962e-017eaa863989",
"href": "/oic/d",
"rt": ["oic.wk.d", "oic.d.light"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:33333"}]
},
{
"anchor": "ocf://dc70373c-1e8d-4fb3-962e-017eaa863989",
"href": "/myLight",
"rt": ["oic.r.switch.binary"],
"if": ["oic.if.a", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:33333"}]
},
{
"anchor": "ocf://2983844a-5893-468b-bac93957ddf7",
"href": "/oic/p",
"rt": ["oic.wk.p"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:44444"}]
},
{
"anchor": "ocf://2983844a-5893-468b-bac93957ddf7",
"href": "/oic/d",
"rt": ["oic.wk.d", "oic.d.light"],
"if": ["oic.if.r", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:44444"}]
},
{
"anchor": "ocf://2983844a-5893-468b-bac93957ddf7",
"href": "/myLight",
"rt": ["oic.r.switch.binary"],
"if": ["oic.if.a", "oic.if.baseline"],
"eps": [{"ep": "coaps://[fe80::b1d4]:44444"}]
}
]
as in "6.1 Resource Discovery" of
Bridging spec v0.3_r22.
<https://workspace.openconnectivity.org/apps/org/workgroup/bridging_tg/document.php?document_id=8223>
https://workspace.openconnectivity.org/apps/org/workgroup/bridging_tg/document.php?document_id=8223
Also please see
11.3.6.4 Resource discovery of
OCF Core v1.0.0_r0.03.docx
<https://workspace.openconnectivity.org/apps/org/workgroup/architecture_tg/document.php?document_id=8237>
https://workspace.openconnectivity.org/apps/org/workgroup/architecture_tg/document.php?document_id=8237
which describes
For OCF 1.0 Clients, /oic/res response includes OCF 1.0 Link
and anchor parameter has OCF URI. /oic/res response has the single array of
OCF 1.0 Links
to conform to RFC6690. Each Link shall carry "anchor" of the value OCF URI
where the authority component of <deviceID> indicates the Device hosting the
target Resource.
This has been a consensus between ATG & BTG for a while.
best regards
JinHyeock
--------- Original Message ---------
Sender : Malsbary, Todd < <mailto:todd.malsbary at intel.com> todd.malsbary at
intel.com>
Date : 2017-01-10 07:35 (GMT+9)
Title : RE: [Follow Up] OCF 1.0 implementation status
To : ???< <mailto:uzchoi at samsung.com> uzchoi at samsung.com>, ????<
<mailto:dwarka.dayama at samsung.com> dwarka.dayama at samsung.com>,
'Srikrishna Gurugubelli'< <mailto:srikguru at microsoft.com> srikguru at
microsoft.com>, Ziran Sun< <mailto:ziran.sun at samsung.com> ziran.sun at
samsung.com>, Habib Virji< <mailto:habib.virji at samsung.com> habib.virji at
samsung.com>, ???< <mailto:myeong.jeong at samsung.com> myeong.jeong at
samsung.com>, 'Dino Natucci'< <mailto:Dino.Natucci at microsoft.com>
Dino.Natucci at microsoft.com>, Morrow, Joseph L< <mailto:joseph.l.morrow at
intel.com> joseph.l.morrow at intel.com>, Shetty, Mandeep<
<mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com>
CC : Heldt-Sheller, Nathan< <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>, ???< <mailto:soohong.park at samsung.com>
soohong.park at samsung.com>, ???< <mailto:moonki1.hong at samsung.com>
moonki1.hong at samsung.com>, ???< <mailto:jinchoe at samsung.com> jinchoe at
samsung.com>, Mark Trayer< <mailto:m.trayer at samsung.com> m.trayer at
samsung.com>, Kesavan, Vijay S< <mailto:vijay.s.kesavan at intel.com>
vijay.s.kesavan at intel.com>, ???< <mailto:jinguk.jeong at samsung.com>
jinguk.jeong at samsung.com>
Hi Uze,
Sure, what the bridging spec wants is for /oic/res to return a separate entry
for each bridged device (in abbreviated form):
[
/* the bridge itself */
{
?di?: ?abc??,
?links?: [
{ ?href?: ?/oic/d?, ?rt:? [
?oic.wk.d?, ?oic.d.bridge? ] }
]
},
/* a bridged light */
{
?di?: ?def??,
?links?: [
{ ?href?: ?/a/light? }
]
},
/* a bridged fan */
{
?di?: ?ghi??,
?links?: [
{ ?href?: ?/a/fan? }
]
},
/* etc. */
]
In order to achieve this, I need a separate di and endpoints for each bridged
device. When I have that, I can re-use the resource directory work to have the
/oic/res response look like the above. The only way today to get a separate di
and endpoints is to start up a new instance of IoTivity, so I?ll need to do
something like the following:
? Parent bridge process: discovers AllJoyn devices and kicks off a
child process when it finds one.
? Child process for each bridged device: creates the virtual OCF
resources from the real AllJoyn device and publishes them to the parent process
resource directory. If real device goes away then delete resource directory
entries from parent process and exit.
Ideally I?d have an API along the lines of OCCreateVirtualHost() that I could
create resources off of, but implementing that will require cleaning up all the
global data used by IoTivity which I think is going to be a significant amount
of dev and test effort.
-Todd
From: ??? (Uze Choi) [ <mailto:uzchoi at samsung.com>
mailto:[email protected]]
Sent: Sunday, January 8, 2017 6:40 PM
To: Malsbary, Todd < <mailto:todd.malsbary at intel.com> todd.malsbary at
intel.com>; 'Dwarkaprasad Dayama' < <mailto:dwarka.dayama at samsung.com>
dwarka.dayama at samsung.com>; 'Srikrishna Gurugubelli' < <mailto:srikguru at
microsoft.com> srikguru at microsoft.com>; 'Ziran Sun' < <mailto:ziran.sun at
samsung.com> ziran.sun at samsung.com>; 'Habib Virji' < <mailto:habib.virji at
samsung.com> habib.virji at samsung.com>; '???' < <mailto:myeong.jeong at
samsung.com> myeong.jeong at samsung.com>; 'Dino Natucci' <
<mailto:Dino.Natucci at microsoft.com> Dino.Natucci at microsoft.com>; Morrow,
Joseph L < <mailto:joseph.l.morrow at intel.com> joseph.l.morrow at intel.com>;
Shetty, Mandeep < <mailto:mandeep.shetty at intel.com> mandeep.shetty at
intel.com>
Cc: Heldt-Sheller, Nathan < <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>; <mailto:soohong.park at samsung.com>
soohong.park at samsung.com; <mailto:moonki1.hong at samsung.com> moonki1.hong
at samsung.com; <mailto:jinchoe at samsung.com> jinchoe at samsung.com; 'Mark
Trayer' < <mailto:m.trayer at samsung.com> m.trayer at samsung.com>; Kesavan,
Vijay S < <mailto:vijay.s.kesavan at intel.com> vijay.s.kesavan at intel.com>;
??? < <mailto:jinguk.jeong at samsung.com> jinguk.jeong at samsung.com>
Subject: RE: [Follow Up] OCF 1.0 implementation status
Hi Todd,
Great progress.
Could you share the architecture or block diagram to look into process
structure or lifecycle.
BR, UZe Choi
From: Malsbary, Todd [ <mailto:todd.malsbary at intel.com>
mailto:[email protected]]
Sent: Saturday, January 07, 2017 7:36 AM
To: Dwarkaprasad Dayama; 'Srikrishna Gurugubelli'; 'Ziran Sun'; 'Habib Virji';
'???'; 'Dino Natucci'; Morrow, Joseph L; Shetty, Mandeep
Cc: '???'; Heldt-Sheller, Nathan; <mailto:soohong.park at samsung.com>
soohong.park at samsung.com; <mailto:moonki1.hong at samsung.com> moonki1.hong
at samsung.com; <mailto:jinchoe at samsung.com> jinchoe at samsung.com; 'Mark
Trayer'; Kesavan, Vijay S
Subject: RE: [Follow Up] OCF 1.0 implementation status
Hi Dwarka,
Here is the current status of the AllJoyn bridge work, broken down roughly by
the bridging spec sections:
? Deep translation ? not in scope of work I am doing.
? Resource discovery ? in progress. This has dependencies on resource
directory work under review. Additionally, this depends on running a separate
instance of IoTivity for each bridged device.
? Security ? not yet started.
? Exposing AllJoyn producer devices to OCF clients ? mostly complete.
? Exposing OCF resources to AllJoyn consumer applications ? mostly
complete.
? On-the-fly translation from D-Bus and OCF payloads ? mostly complete,
with exception of missing support for using OCF introspection data.
? Translation of introspection itself ? not yet started.
? Device type definition (oic.d.bridge) ? not yet started.
? Integration with plugin framework ? not yet started. This depends on
upcoming plugin framework work.
-Todd
From: Dwarkaprasad Dayama [ <mailto:dwarka.dayama at samsung.com>
mailto:[email protected]]
Sent: Thursday, January 5, 2017 11:41 PM
To: 'Srikrishna Gurugubelli' < <mailto:srikguru at microsoft.com> srikguru at
microsoft.com>; 'Ziran Sun' < <mailto:ziran.sun at samsung.com> ziran.sun at
samsung.com>; 'Habib Virji' < <mailto:habib.virji at samsung.com> habib.virji
at samsung.com>; '???' < <mailto:myeong.jeong at samsung.com> myeong.jeong at
samsung.com>; Malsbary, Todd < <mailto:todd.malsbary at intel.com>
todd.malsbary at intel.com>; 'Dino Natucci' < <mailto:Dino.Natucci at
microsoft.com> Dino.Natucci at microsoft.com>; Morrow, Joseph L <
<mailto:joseph.l.morrow at intel.com> joseph.l.morrow at intel.com>; Shetty,
Mandeep < <mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com>
Cc: '???' < <mailto:uzchoi at samsung.com> uzchoi at samsung.com>;
Heldt-Sheller, Nathan < <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>; <mailto:soohong.park at samsung.com>
soohong.park at samsung.com; <mailto:moonki1.hong at samsung.com> moonki1.hong
at samsung.com; <mailto:jinchoe at samsung.com> jinchoe at samsung.com; 'Mark
Trayer' < <mailto:m.trayer at samsung.com> m.trayer at samsung.com>; Kesavan,
Vijay S < <mailto:vijay.s.kesavan at intel.com> vijay.s.kesavan at intel.com>
Subject: RE: [Follow Up] OCF 1.0 implementation status
Hi MJ, Ziran & Sri,
Thank you sharing updates. I have created JIRA tickets with each of these items
for tracking purpose and have linked it to OCF Bugzilla for creating dashboard
(in process).
<https://jira.iotivity.org/browse/IOT-1735>
https://jira.iotivity.org/browse/IOT-1735
<https://jira.iotivity.org/browse/IOT-1736>
https://jira.iotivity.org/browse/IOT-1736
<https://jira.iotivity.org/browse/IOT-1737>
https://jira.iotivity.org/browse/IOT-1737
<https://jira.iotivity.org/browse/IOT-1738>
https://jira.iotivity.org/browse/IOT-1738
@Sri ? I could not find you on IoTivity JIRA, may be you did not register yet.
Hence assigned introspection to Dave.
Awaiting for status information from Todd for AllJoyn Bridge application item.
Regards
Dwarka
----------------------------------------------------------------------------------
Software R&D Center | Software Strategy Team | Open Source Group
Open Connectivity Foundation ? OSWG ? Spec Coordination TG Chair
Iotivity Steering Group ? Advisory Committee
From: Srikrishna Gurugubelli [ <mailto:srikguru at microsoft.com>
mailto:[email protected]]
Sent: Friday, January 06, 2017 1:43 AM
To: Ziran Sun < <mailto:ziran.sun at samsung.com> ziran.sun at samsung.com>;
'Dwarkaprasad Dayama' < <mailto:dwarka.dayama at samsung.com> dwarka.dayama at
samsung.com>; Habib Virji < <mailto:habib.virji at samsung.com> habib.virji at
samsung.com>; '???' < <mailto:myeong.jeong at samsung.com> myeong.jeong at
samsung.com>; 'Malsbary, Todd' < <mailto:todd.malsbary at intel.com>
todd.malsbary at intel.com>; Dino Natucci < <mailto:Dino.Natucci at
microsoft.com> Dino.Natucci at microsoft.com>; 'Morrow, Joseph L' <
<mailto:joseph.l.morrow at intel.com> joseph.l.morrow at intel.com>;
<mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com
Cc: '???' < <mailto:uzchoi at samsung.com> uzchoi at samsung.com>;
'Heldt-Sheller, Nathan' < <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>; <mailto:soohong.park at samsung.com>
soohong.park at samsung.com; <mailto:moonki1.hong at samsung.com> moonki1.hong
at samsung.com; <mailto:jinchoe at samsung.com> jinchoe at samsung.com; 'Mark
Trayer' < <mailto:m.trayer at samsung.com> m.trayer at samsung.com>; 'Kesavan,
Vijay S' < <mailto:vijay.s.kesavan at intel.com> vijay.s.kesavan at intel.com>
Subject: RE: [Follow Up] OCF 1.0 implementation status
Hi Dwarka,
Introspection patch is currently undergoing code review. I am addressing the
feedback I received so far and will submit another patch this week.
Thanks,
Sri
From: Ziran Sun [ <mailto:ziran.sun at samsung.com>
mailto:[email protected]]
Sent: Thursday, January 5, 2017 5:24 AM
To: 'Dwarkaprasad Dayama' < <mailto:dwarka.dayama at samsung.com> dwarka.dayama
at samsung.com>; Habib Virji < <mailto:habib.virji at samsung.com> habib.virji
at samsung.com>; '???' < <mailto:myeong.jeong at samsung.com> myeong.jeong at
samsung.com>; 'Malsbary, Todd' < <mailto:todd.malsbary at intel.com>
todd.malsbary at intel.com>; Dino Natucci < <mailto:Dino.Natucci at
microsoft.com> Dino.Natucci at microsoft.com>; 'Morrow, Joseph L' <
<mailto:joseph.l.morrow at intel.com> joseph.l.morrow at intel.com>;
<mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com; Srikrishna
Gurugubelli < <mailto:srikguru at microsoft.com> srikguru at microsoft.com>
Cc: '???' < <mailto:uzchoi at samsung.com> uzchoi at samsung.com>;
'Heldt-Sheller, Nathan' < <mailto:nathan.heldt-sheller at intel.com>
nathan.heldt-sheller at intel.com>; <mailto:soohong.park at samsung.com>
soohong.park at samsung.com; <mailto:moonki1.hong at samsung.com> moonki1.hong
at samsung.com; <mailto:jinchoe at samsung.com> jinchoe at samsung.com; 'Mark
Trayer' < <mailto:m.trayer at samsung.com> m.trayer at samsung.com>; 'Kesavan,
Vijay S' < <mailto:vijay.s.kesavan at intel.com> vijay.s.kesavan at intel.com>
Subject: RE: [Follow Up] OCF 1.0 implementation status
Hi Dwarka,
For versioning, around 70% functionalities are done and I?m hope the rest will
be done next week. After that I will put it in code review.
Best regards,
Ziran
From: Dwarkaprasad Dayama [ <mailto:dwarka.dayama at samsung.com>
mailto:[email protected]]
Sent: 05 January 2017 05:42
To: Habib Virji; 'Ziran Sun'; ???; 'Malsbary, Todd'; 'Dino Natucci'; Morrow,
Joseph L; <mailto:mandeep.shetty at intel.com> mandeep.shetty at intel.com;
'Srikrishna Gurugubelli'
Cc: ???; Heldt-Sheller, Nathan; <mailto:soohong.park at samsung.com>
soohong.park at samsung.com; <mailto:moonki1.hong at samsung.com> moonki1.hong
at samsung.com; <mailto:jinchoe at samsung.com> jinchoe at samsung.com; Mark
Trayer; Kesavan, Vijay S
Subject: [Follow Up] OCF 1.0 implementation status
Hi OCF 1.0 Contributors,
Wish you all a very Happy & Properous New Year !
OSWG-SCTG is supposed to present status for ongoing work related to OCF 1.0
features. It will be helpful to know where are we now for each of following Big
4 items.
- Introspection
- Endpoint Information
- Versioning
- AllJoyn Bridge Application
Apart from this, it will also be good to know who all will be present at F2F.
As I am not traveling and will be joining relevant sessions through WebEx.
Regards
Dwarka
----------------------------------------------------------------------------------
Software R&D Center | Software Strategy Team | Open Source Group
Open Connectivity Foundation ? OSWG ? Spec Coordination TG Chair
Iotivity Steering Group ? Advisory Committee
-------------- next part --------------
HTML ?????? ??????????????...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170131/b3ec13e8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 13402 bytes
Desc: ?????? ?? ????????.
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170131/b3ec13e8/attachment.gif>
