Re: [core] Using CoAP for P2P

[Mehmet Adalier <[e-mail]>]

As far as I know, a CoAP node can be provisioned to provide both client and server functionality and change the behavior as required (i.e. act as a client when it is doing client work and act as a server/resource when doing server work). Our implementation runs a daemon that can instantiate multiple clients/servers on a single computing node.

 

If you do not want to set up a Broker/Intermediary as a separate node (e.g., pubsub), then you can make one of your nodes also a “a broker”

and create your topics on that one (e.g., chatboard topic). Then each node can subscribe to the topic as well as publish to the topic. 

The described approach will support P2P and reduce traffic.

 

mehmet

 

From: core <[e-mail]> on behalf of Christer Holmberg <christer.holmberg=[e-mail]>
Date: Thursday, April 2, 2020 at 11:41 AM
To: Abhijan Bhattacharyya <[e-mail]>, Thomas Fossati <[e-mail]>
Cc: core <[e-mail]>
Subject: Re: [core] Using CoAP for P2P

 

Hi,

 

If you are interested in P2P, you might be interested in the thin-ICE presentation that was given at the T2TRG meeting in Singapore:

 

https://github.com/t2trg/2019-11-singapore/blob/master/slides/44-thin-ICE-151119-Singapore.pdf

 

Regards,

 

Christer

 

 

From: core <[e-mail]> on behalf of Abhijan Bhattacharyya <[e-mail]>
Date: Thursday, 2 April 2020 at 11.04
To: Thomas Fossati <[e-mail]>
Cc: core <[e-mail]>
Subject: Re: [core] Using CoAP for P2P

 

Hi Thomas, 

What I am looking at is a situation where I have two nodes each having a time-varying resource. Both want to push the states of the respective resource to the other node within a common application context. However, these exchanges are naturally asynchronous. May be I can think of it more like a chat. A typical client-server or observe relationship will not serve the purpose. Actually both should have a client and server instance running under a common application. Then either each can *observe* the other, or can *post* the other. That is how we can do that without a central server.

 

If my understanding is right, according to CoAP specification, the nodes which can have both server and client (to the origin server) are "intermediary" nodes. The only example of "intermediary" considered in the spec is the proxy node. But, anyway the situation in this case does not concern with intermediary. Both are origin server and end-client together.

 

Is there any standardized mechanism to handle this situation?

 

Thanks.

 

On Wed, Apr 1, 2020 at 5:32 PM Thomas Fossati <[e-mail]> wrote:

Hi Abhijan,

On 01/04/2020, 12:31, Abhijan Bhattacharyya <[e-mail]> wrote:
> Is there any standardized mechanism to use CoAP for a P2P connection?

Not sure whether RFC 7650 would fit your needs but worth having a
look -- if you haven't already.

cheers
--




IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


 

-- 

Regards,

Abhijan Bhattacharyya,

Technologist by profession [IoT| Internet Protocols| 5G]

_______________________________________________ core mailing list [e-mail] https://www.ietf.org/mailman/listinfo/core