Re: [core] Using CoAP for P2P

Christer Holmberg <> Sat, 04 April 2020 12:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 15FD73A0B69 for <>; Sat, 4 Apr 2020 05:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id U13WFpldTakj for <>; Sat, 4 Apr 2020 05:26:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 45D5D3A0B68 for <>; Sat, 4 Apr 2020 05:26:06 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=RiqX7yoYWZPi3/ylpzLz5+ReUBVH5wrJr7La09mk/EVlPcYvtlWr2cmuobq+3+5n1uy5qkyjSbolm54xSpLINcfx1LLevEY2UTgFkQuc13tOylyPCP7M/yJiAnXEGoeDPIvqzNZAGVjMR2tX8wmzsXZy2IVtUNnwmQOFv6KiQMzLcEKoA7GePL7yMPXOdA0sBsOy5yoljBdf6m5wA419Ws35Uf1BDIwuJg477hSK4J78tOVvc/aJAlMeI+wxVChQqL81NSdPzsYKcTh1/FyMNCgGh36QBQ1LrW0CzSy1BS/N5VovXwdARlim+5CtwwdAV2Bw99pov+AufjPee9k9WQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wz+r5Os0vXykaN+VcX2Z1+Pv4/KUHQgkAXSEGoA4eSY=; b=XO+whClvk3KrY/Cu41ogHp8FN23RPlWHd0V971h3TIFELPvVz2ZavCSE/FswdPbPrFCndy73fFjRRdf6M/GRwh5kAY4orFocK+SuM7JRuhsUWFYpUACP8A82NSOF12gx3LhovpIKtLrZTYb+MVy9MV8erlvmTNN8rRjfaN1TKP0499ZbCQi89el31NFVNLpTtjX9HJwMEbQte4Jb6fix+HYZDTE4u9gqSeVpfOzyDwHoSAkKVoAiP8XEDLCTftXp3NKhkEUaN5Xlj45QiaS1I6jMv3VPrI7ao1oArR4uyTH3QNxLiZRKPc7BBXx7OMQ0Mi4hkWwR4QSh3r0M+enDUw==
ARC-Authentication-Results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wz+r5Os0vXykaN+VcX2Z1+Pv4/KUHQgkAXSEGoA4eSY=; b=fuuZsMsjjsEvL1sUyRupp2r8r6brdJHEoHZa25CwBf3Pb0g5JOamfG8/YeJVeJGprUlG5I3jXFHfmhWagdPmT0oxDMQfCgccNKvBgQET3AiYHfv6Dawe6m/IAR1QE5ioNLT/ptYhc8d/WhElEe34ZotlnSr59+HNh1YET4FrvKY=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.11; Sat, 4 Apr 2020 12:26:03 +0000
Received: from ([fe80::57b:b81e:33ec:5512]) by ([fe80::57b:b81e:33ec:5512%7]) with mapi id 15.20.2900.012; Sat, 4 Apr 2020 12:26:03 +0000
From: Christer Holmberg <>
To: Abhijan Bhattacharyya <>
CC: Thomas Fossati <>, core <>
Thread-Topic: [core] Using CoAP for P2P
Thread-Index: AQHWCMVROB2ppf3kDkGCzoMwIoGd3KhmXWeAgAEvGgCAAYynAA==
Date: Sat, 4 Apr 2020 12:26:03 +0000
Message-ID: <>
References: <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-GB
user-agent: Microsoft-MacOutlook/10.1e.0.191013
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b1f1527f-4465-43cf-164c-08d7d89357ac
x-ms-traffictypediagnostic: AM0PR07MB5139:
x-microsoft-antispam-prvs: <>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 03630A6A4A
x-forefront-antispam-report: CIP:; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM;; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(366004)(376002)(39860400002)(396003)(136003)(346002)(8676002)(66556008)(26005)(66446008)(66574012)(76116006)(91956017)(54906003)(5660300002)(186003)(66476007)(316002)(6506007)(71200400001)(66946007)(6916009)(53546011)(44832011)(966005)(64756008)(86362001)(478600001)(6512007)(33656002)(36756003)(6486002)(8936002)(81166006)(2906002)(81156014)(4326008)(2616005); DIR:OUT; SFP:1101;
received-spf: None ( does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +IGmAejH8RAZ5rMboPDZ5XTwdz5qAT95N+kOPr0VGOzV1DUE3rEsk8RIba9/sY0WFr4alddgPTSiDPQFW57brp9M+w2kZUT1ZL7ogq/cgdrrWYDPQyDXEgfUHPSLKUMC3LSDxv0ZeFN+g7a347QXUFV8ojxGrkm6X+UgNnsCedyokFccnH2Ofa5EcbpyC5G6xtjkcted3RrWAwBdrK52R9RqRcg8nAQI1vMbRjLRuYrlQESouh1sMrPwNVvQsIjYWPSa4W1/khseojUUX1wjGQRkcwtFSkVxkGKQSyXTco7SZnJKW5XxRos2xTdLveH7BPRIPGgcakXKn/kL/QNdpIeoEjSt78MBAvxATofDntDkD/rMFHee9f1eSoJKgY+LwmJZg1K1uwv+tWPqM/ZrjAvxVRznfJXuiPR95oPPeHhmXye+TiUCPXekOEdgqoV5yWtFr1xo36ssIFLi8IMeyisdi/JzYerLfIBUhrrpAKSjnAZvwWxbTWnrvfHRgWHZDvOQdkz0BffJQe18qVRt6Q==
x-ms-exchange-antispam-messagedata: cDlMTy1vyfzkAaMNpZeCeUUfZB9A07jY6pjLzZb5Bg/860Yh4NwHqwws/lJKdi4is6bRbkGQ0iUj1TH7Onz6rFU4viWmHz4LKjf8E+aMzCmLkOtyJ2ccC9tOdLmN5PDxktObzBCvbeHS1bRrYLat6Q==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CF1E6A23243F47A39DFBBB244E96302Bericssoncom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b1f1527f-4465-43cf-164c-08d7d89357ac
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2020 12:26:03.8082 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: jO9y6YKBgI1GzVIr8x1y7ZZLO4lWo/OarEhTDe2cww4b9hfw9ojW6LjVN1Lm3WVJM6ZMNEBo5xCUWQjcp9R6seX7KwVgn3rS/QtiHZ19EgQ=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5139
Archived-At: <>
Subject: Re: [core] Using CoAP for P2P
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 04 Apr 2020 12:26:09 -0000


>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:
>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" (

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.



On Fri, Apr 3, 2020 at 12:11 AM Christer Holmberg <<>> wrote:

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



From: core <<>> on behalf of Abhijan Bhattacharyya <<>>
Date: Thursday, 2 April 2020 at 11.04
To: Thomas Fossati <<>>
Cc: core <<>>
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?


On Wed, Apr 1, 2020 at 5:32 PM Thomas Fossati <<>> wrote:
Hi Abhijan,

On 01/04/2020, 12:31, Abhijan Bhattacharyya <<>> 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.


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.

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

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