Subject: Re: [core] Using CoAP for P2P: thin-ICE

From: Christer Holmberg <[email-masked]>
Date: Sat, 4 Apr 2020 12:23:11 +0000

Hi,

> Thanks for sharing the slides.
> So, if both the nodes host a resource which the other one is interested in, then, following the diagram in the slides, Device #2 should
> also post and create a resource and Device #1 should do a GET. Then both the devices can access each other, right?

Correct.

(Of course, when Device #1 has received the GET from Device #2, Device #1 could try to reach Device #2 using the address from where the GET was received. That is referred to as a peer reflexive candidate in ICE, but we have not looked into that in detail yet.)

> Can we then think of a situation when the RD and the TURN server merges together?

Not sure what you mean be “merges together”, but multiple devices can for sure use the same RD and/or T-STUN server. That is how it normally works.

(When you say TURN server, I assume you refer to the T-STUN server. The slides don’t describe the usage of a TURN server/relay, but that would for sure be possible)

>One thing that I find special in this case than usual P2P establishment scenario is that, the TURN server has the responsibility of notifying the URI as well and
>not only the ip:port mapping. This is because of the RESTful semantics.

Not sure I understand. The T-STUN server only provides the public IP address:port of the device. The device creates the URI.

>Can we find any document elaborating these slides?

At the moment there is no IETF draft describing this, mostly because so far people haven’t shown too much interest in it.

It is described in my thesis, so if you want I can give you the link for that :)

>And, is there any opensource implementation available of this proposal please?

Currently not, unfortunately, as far as I know.

Regards,

Christer

On Fri, Apr 3, 2020 at 12:11 AM Christer Holmberg <[email-masked]<mailto:[email-masked]>> 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 <[email-masked]<mailto:[email-masked]>> on behalf of Abhijan Bhattacharyya <[email-masked]<mailto:[email-masked]>>
Date: Thursday, 2 April 2020 at 11.04
To: Thomas Fossati <[email-masked]<mailto:[email-masked]>>
Cc: core <[email-masked]<mailto:[email-masked]>>
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 <[email-masked]<mailto:[email-masked]>> wrote:
Hi Abhijan,

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