|
| Re: Type of bootstrapping Architechture in OM2M [message #1487237 is a reply to message #1486906] |
Tue, 25 November 2014 17:39  |
 Scott Lewis
Messages: 1038
Registered: July 2009 |
Senior Member |
|
|
Saurabh Dewani wrote on Tue, 25 November 2014 06:37I am trying to create security features in the OM2M platform. For that I need to know whether it is GBA or EAP based architecture.
If the Architecture is not any one of the two then kindly specify which one is it.
Hi Saurabh,
It's not completely clear from your posting whether you are asking for information about OM2M security, or whether you are interested in the Eclipse Communication Framework project (ECF). ECF is a separate project from OM2M, and this forum is for ECF specifically.
So assuming you are asking these questions about ECF, here are a few answers:
1) ECF provides a set of protocol-independent APIs for standardized communications services (e.g. OSGi Remote Services, asynchronous file transfer, messaging channels, etc).
2) Underneath these APIs are individual protocols/providers based upon/using various protocols and their associated security. These providers are implemented as (modular) OSGi bundles.
Here's a diagram showing this architecture wrt the OSGi Remote Services standard (OSGi Alliance R6 Enterprise Specification chapters 100 and 122):
http://wiki.eclipse.org/OSGi_Remote_Services_and_ECF
To try to answer your question directly: ECF is agnostic about the transport-level security architecture (GBA or EAP), meaning that either could be used to implement a remote services distribution provider.
In fact, I would very much like to see a remote services distribution provider based upon OM2M bundles...such a provider would make it possible to run all the remote service examples shown here:
http://wiki.eclipse.org/ECF#Introductory_Materials
on OM2M, without *any* application-level code modifications. Applications would be able to simply discover and use standardized OSGi Remote Services. It is even possible to develop and test in one protocol/transport environment, and deploy in another.
So, again, I would very much like to see an ECF distribution provider that uses/based upon OM2M, and my guess is this would be very straightforward to create. I personally have created providers based upon MQTT (Paho)
https://github.com/ECF/Mqtt-Provider
JMS
https://github.com/ECF/JMS
JavaGroups
https://github.com/ECF/JGroups
and others
These show that it is possible to straightforwardly use different protocols and authentication approaches for provider implementations.
As ECF project lead, I'm willing to participate, inform, and assist the effort to create a distribution (and/or discovery) provider based upon OM2M. If you want to pursue this, it would be very helpful if you would bring it up on the ecf-dev mailing list so that other committers can/could know about such an effort and participate:
https://dev.eclipse.org/mailman/listinfo/ecf-dev
Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.03124 seconds
] 
Search
Help
Register
Login
Home
