Re: [core] Using CoAP for P2P

Mehmet Adalier <madalier@antarateknik.com> Thu, 02 April 2020 19:24 UTC

Return-Path: <madalier@antarateknik.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555033A0FEA for <core@ietfa.amsl.com>; Thu, 2 Apr 2020 12:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h1GQHMQd7f3w for <core@ietfa.amsl.com>; Thu, 2 Apr 2020 12:23:58 -0700 (PDT)
Received: from sonic316-19.consmr.mail.bf2.yahoo.com (sonic316-19.consmr.mail.bf2.yahoo.com [74.6.130.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E6DD3A0FE9 for <core@ietf.org>; Thu, 2 Apr 2020 12:23:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1585855436; bh=blGaC12YsyjgVHy3uuT1nV/iaRwa3eZCTNDrKfT164A=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=ObQT/FBFQ4vr4Khzmlny3wG4+aBhE7etvyz6bCmwwcn54BOPsklQ7iSdGYJX7qDcDGybgekfsmVIfbWUNVnvS1RTenbRBnsXKdSrCC2k+/AFtR2Tm7f8Smbnr+EV3G1YCMsK6LaQq03GtQY4tUjVPYOUMderAUAbdUGHBo4+vW+KXveuTVEegd4DLmVn2GrbX2pf2PAMMN6Yz1IkfrAy8Pc33sM2mDnco0AjdaZs0CcyNc6JLd4VID871arKIM0ugL9tePLVGSUBFLCIAbzfDeQmXFof2rJ9uC6U2xP08PF4NB0SuZiPAInn+QFBWByKpAA0ngkE+OUobFNnPKHACw==
X-YMail-OSG: YVydqMMVM1kVzthflo244Uy_UEcZYiMDIrjfg5bjvxg6bzQlCU1yo9lDcF.QjdK y0J9rFNtGvoXy48bUhZmgDfeUiBDCebvPfKIFTYAi2zSC.UDs7Z9uR.rya_kVrTPWFmGnqVQor4k C.Yy447ubDpTn31deYIk8tjggzU1rx0vDNz67mNkWi2DpJgi06503X5XFmcTZnugxOzOcyxEmC0J Vw36JWtRtZELCtxE2TyXzzrIh3LGqY88DKCqf1B7copkdJmYwIrgse2d8OscaQbQLimixP9ZrPtn tntWH3cTs6wznxE420VQ_VIKB8c4y7fFAb0WNizeLzeYRutzjF1MZf.VtNrV9AWF7IGF0k6g4gPW tJc1idnIV_RJTJEOtktUuGAXsIN26jh5foFZIljsapUiJ6WMBLecOBf1l8tj0CAFFTPCn82YRn2F 98BdOxtWj1c3ofxtHAT0J5oW8O8k5HCcQHJaoxELl9_ZgBmZFy20iLgxMW44YkUkZcAOZxZs.5M5 EuXKNWwa_BRzwnQGmlb.6WJngcL5.rYfdjsK9OQgrcqoPFw_FpCpV.r6lx15gXowQ5IVW3bGG.Vp vh5O1Y3NI9JcXGH0SSRUyXGpfAVD4RNV60Np0L8lGXAc3kxKx6d907Yt3BelSiDDywhUtBBoyw4W XwwTJ7FI.4WoVGPrut3CfnoOahmQLszpeJsH5ztjQjoQ.c4zcXK35p4y5QrSFoqfvDuURHobg1F. A4JjCDB.VYij5k7qjVl6u7yHgwUsHL7Aa_.oF4KSzoOvbj5.QWqfQgQM.GZPVT7rLvYH6u0olDYv 2QdDIh5LSVJ56GcPPAxoAhdh5.vADY4FUkwT1pWxOLzEUQjDiM_IR3h0N59cc4.Pyd8X3AWMKuUj b0f9wG4_lLt8c6b2hsKrMye0SWJRLNoRzEpI6mT0FUlq9X7KJfamFS.vh2yumf2UVUbtoTntoRJG ImtWpsS8zwJwRxHSYPCPJiTQLS1BzDEMAn_SU9krBUhtfK4Lx61A1eRrPGpCvMobOUGwRplaGox8 G30LoiJoNGcdwr_30e_ekJSNyDOAKJaQffFQzkjZTdurje8GqTIRJIKVd5CpkvYtY9ZtgvhfnYLT 3231Oz5sZvHRZXs7PtSQhd52i56keLEyFL12PDNkxZ6.yX6Adp3E7PvdjQEUloInSjQkQZKGRnUH lmT4Za8QNHJobQYJuyj7wMiFCV8zaES9MrsR6Siuu4uUIPiNaaBHzMstILJWoYfF8eEToMy4BAzu 6WKcC3SbptZTBU5XAXwMO4OcTdo7Cnayo_3atBosWRnjOquaaUDE0ai17s3zvaTGADyzruub0NBB i.Gf74g4Nd.Uc.HomeIELOTgMyNdCyIvKJ__unbaInPj7edvhkOxfUHyUhpBr6degsm4O4txsT4h XXmTUI12GDn.YKFoVtA--
Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.bf2.yahoo.com with HTTP; Thu, 2 Apr 2020 19:23:56 +0000
Received: by smtp425.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 2e32dbf72d90c93a6239272075dea051; Thu, 02 Apr 2020 19:23:52 +0000 (UTC)
User-Agent: Microsoft-MacOutlook/10.20.0.191208
Date: Thu, 02 Apr 2020 12:23:49 -0700
From: Mehmet Adalier <madalier@antarateknik.com>
To: Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>, Abhijan Bhattacharyya <abhijan.bhattacharyya@gmail.com>, Thomas Fossati <Thomas.Fossati@arm.com>
CC: core <core@ietf.org>
Message-ID: <7D444BF0-FD37-4A97-A833-5DC9F3788A30@antarateknik.com>
Thread-Topic: [core] Using CoAP for P2P
References: <CAEW_hyzh3FAvHi1eTkbyGn99o4nFgcH1xP90FdQ6N9sHsAJVYQ@mail.gmail.com> <A8E6E9AA-2E34-439E-8761-53385086CDB9@arm.com> <CAEW_hyy+0fViN8dMWiCi_QHjeD5J4DUAnoRUg5MAKS6fQ3DzcQ@mail.gmail.com> <7B20E77F-CFF4-4735-A0C2-99121CD352D3@ericsson.com>
In-Reply-To: <7B20E77F-CFF4-4735-A0C2-99121CD352D3@ericsson.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3668675032_6601585"
X-Mailer: WebService/1.1.15585 hermes Apache-HttpAsyncClient/4.1.4 (Java/11.0.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/35qOptXTme5uDjVH5Pzzc9oJAm8>
Subject: Re: [core] Using CoAP for P2P
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2020 19:24:00 -0000

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 <core-bounces@ietf.org> on behalf of Christer Holmberg <christer.holmberg=40ericsson.com@dmarc.ietf.org>
Date: Thursday, April 2, 2020 at 11:41 AM
To: Abhijan Bhattacharyya <abhijan.bhattacharyya@gmail.com>om>, Thomas Fossati <Thomas.Fossati@arm.com>
Cc: core <core@ietf.org>
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 <core-bounces@ietf.org> on behalf of Abhijan Bhattacharyya <abhijan.bhattacharyya@gmail.com>
Date: Thursday, 2 April 2020 at 11.04
To: Thomas Fossati <Thomas.Fossati@arm.com>
Cc: core <core@ietf.org>
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 <Thomas.Fossati@arm.com> wrote:

Hi Abhijan,

On 01/04/2020, 12:31, Abhijan Bhattacharyya <abhijan.bhattacharyya@gmail.com> 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 core@ietf.org https://www.ietf.org/mailman/listinfo/core