[core] Fwd: New Version Notification for draft-gundogan-core-icncoap-00.txt

Cenk Gündoğan <mail+ietf@gundogan.net> Mon, 22 February 2021 23:23 UTC

Return-Path: <mail+ietf@gundogan.net>
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 BE26C3A21DD for <core@ietfa.amsl.com>; Mon, 22 Feb 2021 15:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=gundogan.net
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 83DhODlj-diG for <core@ietfa.amsl.com>; Mon, 22 Feb 2021 15:23:39 -0800 (PST)
Received: from mail.localdomain (trantor.gundogan.net [37.120.167.193]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC0E33A21BB for <core@ietf.org>; Mon, 22 Feb 2021 15:23:38 -0800 (PST)
Received: from localhost (unknown [84.242.29.158]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.localdomain (Postfix) with ESMTPSA id 3BA623C73A for <core@ietf.org>; Tue, 23 Feb 2021 00:01:57 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gundogan.net; s=201712; t=1614034917; bh=jBqt+D1j6JzREVxbv4+v67GxRU+lj66vYF6VqCFN4Ow=; h=References:From:To:Subject:Date:From; b=jFVWNa22uZBOeDo/kReKWM+LfIRHOPiLjBbeBhbynVW5rrY5KU+j8IjTZBTjFFuMi ONSXVmUBxedmAYCK0itGWPcYTZjBt/qLEQ/7rgwDq/vNEb5LkYxVL56fuZ0x4RY039 fNbjvFGU3XQoZ7bL1FIuAl1422w06hOVvZiHxtO8CPJvdastuJLrg+U/6XU/muLqiZ YHyJYxKA6AbJlPDYPDkLrNe5HWvjRDUa6TEVos3ZtcZvIsR0+4WNaW5QGV1PIZfM6g TIu7KKGoz2LN5sLQlO5pYwhE2Ov+qo93O6fmwKiLRdO/grS5icpP0bv5QbIWZDmZw3 5elL+EpoxBrJg==
References: <161403502389.25152.13184178509630896225@ietfa.amsl.com>
User-agent: mu4e 1.4.15; emacs 28.0.50
From: Cenk =?utf-8?B?R8O8bmRvxJ9hbg==?= <mail+ietf@gundogan.net>
To: core@ietf.org
Date: Tue, 23 Feb 2021 00:23:36 +0100
Message-ID: <877dmzit53.fsf@gundogan.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/0Y0tPELLnrvb9G3eIUg07pqEuno>
Subject: [core] Fwd: New Version Notification for draft-gundogan-core-icncoap-00.txt
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: Mon, 22 Feb 2021 23:23:47 -0000

Hello CoRE WG,

for quite some time, we have been investigating information-centric
networking (ICN) approaches (mainly CCNx [1], NDN [2]) for use in
constrained IoT setups.

ICN deployments reveal synergistic effects that increase the reliability
in low-power, lossy networks and reduce network resource demands due to
their (i) stateful forwarding fabric, (ii) on-path caching, (iii)
hop-wise retransmissions, and (iv) content object security properties.

While we formerly argued for an IoT based on CCNx or NDN, we are now
revisiting another idea.  We teamed up with Christian Amsüss and
discovered that CoAP already supports many features to construct an IoT
of data-centric nature; and it replicates the very same ICN performance
benefits [3,4] using a pure CoAP deployment with its proxy, caching, and
OSCORE capabilities.

We regularly report our findings to the ICN community (e.g., at ICNRG
[5]) and we think that this particular work might also be of interest to
CoRE.  The attached -00 draft is a condensed rundown on the topic .. and
if there is interest, then we would gladly discuss more on the mailing
list, or in form of a presentation in a next meeting slot; if agenda
permits.

Cheers,
Cenk Gündoğan

[1] https://tools.ietf.org/html/rfc8569
[2] https://named-data.net/project/
[3] https://ieeexplore.ieee.org/document/9142731
[4] https://dl.acm.org/doi/10.1145/3405656.3418718
[5] https://datatracker.ietf.org/rg/icnrg/about/

On Tue, Feb 23 2021 at 00:03 +0100, internet-drafts@ietf.org wrote:

> A new version of I-D, draft-gundogan-core-icncoap-00.txt
> has been successfully submitted by =?utf-8?b?Q2VuayBHw7xuZG/En2Fu?= and posted to the
> IETF repository.
>
> Name:		draft-gundogan-core-icncoap
> Revision:	00
> Title:		A Data-centric Deployment Option for CoAP
> Document date:	2021-02-22
> Group:		Individual Submission
> Pages:		7
> URL:            https://www.ietf.org/archive/id/draft-gundogan-core-icncoap-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-gundogan-core-icncoap/
> Html:           https://www.ietf.org/archive/id/draft-gundogan-core-icncoap-00.html
> Htmlized:       https://tools.ietf.org/html/draft-gundogan-core-icncoap-00
>
>
> Abstract:
>    The information-centric networking (ICN) paradigm offers replication
>    of autonomously verifiable content throughout a network, in which
>    content is bound to names instead of hosts.  This has proven
>    beneficial in particular for the constrained IoT.  Several
>    approaches, the most prominent of which being Content-Centric
>    Networking (CCNx) and Named-Data Networking (NDN), propose access to
>    named content directly on the network layer.  Independently, the CoRe
>    WG developed mechanisms that support autonomous content processing,
>    on-path caching, and content object security using CoAP proxies and
>    OSCORE.
>
>    This document describes a data-centric deployment option using
>    standard CoAP features to replicate information-centric properties
>    and benefits to the host-centric IoT world.
>
>                                                                                   
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat

-- 
Cenk Gündoğan

Hamburg University of Applied Sciences
Dept. of Computer Science / Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
Fon: +49 40 42875 - 8426
Mail: cenk.guendogan@haw-hamburg.de
Web: https://www.inet.haw-hamburg.de/