Jinguk,
Of course, you are right. When I listed the two items, I did not intend the first (1) to block the second (2). The reason that contributors who are members should check with the standards group *is not* to get permission, it is to keep the standards group informed, avoid duplication of effort and ensure we do not conflict with the standards group?s direction. Pat From: ??? [mailto:[email protected]] Sent: Monday, March 02, 2015 7:48 PM To: Lankswert, Patrick; Habib Virji; iotivity-dev at lists.iotivity.org Cc: Bowden, George; Agerstam, Mats G; Subramaniam, Ravi; ??? Subject: Re: RE: Resource directory proposal Pat, I agree with you about following two parts; 1) Get the standards group to add it to the roadmap. 2) Add it to iotivity without a standard definition However, I don't think that we need to check with the standard group first. This mailing list is iotivity developer mailing list. All IoTivity developers can propose or contribute their tech. no matter whether it is related with OIC or not. OIC OSWG will just check whether there is mis-match between IoTivity and standard or not. BR Jinguk Jeong ------- Original Message ------- Sender : Lankswert, Patrick<patrick.lankswert at intel.com <mailto:patrick.lankswert at intel.com> > Date : 2015-03-03 00:55 (GMT+09:00) Title : RE: Resource directory proposal Habib, Thank you for your proposal. I agree with you regarding the value and I have been interested in RD for some time. I proposed it in December to the PPRTG group but it did not receive enough votes to be prioritized. I am passing your proposal onto the architects and planners. We have two paths: 1) Get the standards group to add it to the roadmap. 2) Add it to iotivity without a standard definition If we add it to iotivity without a standard, we need to review your design and determine who will do the work. In any case, we need to check with the standards group first. BTW, I would like to separate resource directory, proxy and caching. However, we can talk about the design after we find that path and schedule for feature. Pat From: Habib Virji [mailto:[email protected]] Sent: Monday, March 02, 2015 7:00 AM To: Lankswert, Patrick Subject: Resource directory proposal Hi Patrick I am interested in proposing a Resource Directory (RD) as part of Discovery and Connectivity. Why resource directory ? Unconstrained device such as mobile can be asleep and may miss multicast query packets. ? Some devices cannot keep listening to multicast packets due to power constraint. ? For unidirectional communication, an IP address of the other entity holding resource has to be known. ? Power drain on the devices which cannot handle replying to multicast queries. ? RD can act as a server for provisioning, bootstrapping and access control list. ? RD can assist in being an interface for remote communication . RD can hold all local device communication and then act as an interface for remote device to connect to local device. What will it address ? Discovery of resources offered by a constrained server is very important in M2M applications where there are no humans and static interfaces are fragile. ? Allows lookups to be performed for those resources which are located on the sleeping node or has an issue with multicast traffic. ? Mechanism to provide single point of communication and provide functionality to allow: ? Services/resources information to be registered. ? Services/resources information to be queried. ? Resource directory can be used to register: ? Resource type ? Device type ? Will facilitate in local or remote discovery of resource. ? Registration and finding query at one single address. ? Will facilitate authentication and identification of devices. ? Will act as a resource broker for the remote devices to communicate with the local devices. Have worked on the full description of how RD needs to be implemented, URI schema to use for finding and querying RD. If RD need and what it can benefit to the OIC sounds pragmatic, will like to share and discuss further on the proposal. Kind Regards Habib ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Jinguk Jeong, Software R&D Center, SAMSUNG ELECTRONICS CO., LTD Email : jinguk.jeong at samsung.com <mailto:jinguk.jeong at samsung.com> 010-3244-4110 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ <http://ext.samsung.net/mailcheck/SeenTimeChecker?do=61dd5ae2e408a716ce3aa2b9c0f91d8b295e70c64b8b46c4c02ed1e8db42db2188d6974bd2f79a3cb3b9c254041823979dd130b31b023ef15296970253332b3707805447a154a46fcf878f9a26ce15a0> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150303/1b8f0ee4/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150303/1b8f0ee4/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 7198 bytes Desc: not available URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150303/1b8f0ee4/attachment.p7s>
