Re: [core] Using CoAP for P2P

[Christer Holmberg <[e-mail]>]

Hi,

>A bit of more inputs:
>We proposed a delay-sensitive time-series streaming mechanism by extending CoAP and presented in last Bangkok IETF. We called it A-REaLiST (Adaptive RESTful Real-time Live Streaming for Things).
>The draft is here: https://tools.ietf.org/html/draft-bhattacharyya-core-a-realist-00
>The relevant research work was published in 2018 Globecom workshop: Abhijan Bhattacharyya, Suvrat Agrawal, Hemant Kumar Rath, Arpan Pal: "Improving Live-Streaming Experience for Delay-Sensitive IoT >Applications: A RESTful Approach" (https://ieeexplore.ieee.org/document/8644521).

What exactly do you want to standardize? As long as one device acts as a client, and the other as a server, the current mechanisms should work.

Now, if you want to send GETs etc in both directions, I assume that each endpoints would act as both client and server.

Regards,

Christer





On Fri, Apr 3, 2020 at 12:11 AM Christer Holmberg <[e-mail]<mailto:[e-mail]>> wrote:
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<https://protect2.fireeye.com/v1/url?k=7a432dea-26972098-7a436d71-86859b2931b3-a91f2d2ed99da951&q=1&e=b329b088-d6d0-4446-8ddf-5589a9e3abcd&u=https%3A%2F%2Fgithub.com%2Ft2trg%2F2019-11-singapore%2Fblob%2Fmaster%2Fslides%2F44-thin-ICE-151119-Singapore.pdf>

Regards,

Christer


From: core <[e-mail]<mailto:[e-mail]>> on behalf of Abhijan Bhattacharyya <[e-mail]<mailto:[e-mail]>>
Date: Thursday, 2 April 2020 at 11.04
To: Thomas Fossati <[e-mail]<mailto:[e-mail]>>
Cc: core <[e-mail]<mailto:[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]<mailto:[e-mail]>> wrote:
Hi Abhijan,

On 01/04/2020, 12:31, Abhijan Bhattacharyya <[e-mail]<mailto:[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]


--
Regards,
Abhijan Bhattacharyya,
Technologist by profession [IoT| Internet Protocols| 5G]