[icnrg] Do we need an ICMP for ICN?
"Thomas C. Schmidt" <t.schmidt@haw-hamburg.de> Wed, 19 July 2017 14:44 UTC
Return-Path: <t.schmidt@haw-hamburg.de>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 907DA131C60 for <icnrg@ietfa.amsl.com>; Wed, 19 Jul 2017 07:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 H8hKtyUAewcW for <icnrg@ietfa.amsl.com>; Wed, 19 Jul 2017 07:44:08 -0700 (PDT)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A4C2131C57 for <icnrg@irtf.org>; Wed, 19 Jul 2017 07:44:07 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,381,1496095200"; d="scan'208";a="54036244"
Received: from post.haw-hamburg.de (HELO HUB02.mailcluster.haw-hamburg.de) ([141.22.24.51]) by mail6.is.haw-hamburg.de with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jul 2017 16:44:06 +0200
Received: from CAS04.mailcluster.haw-hamburg.de (2002:8d16:183f::8d16:183f) by HUB02.mailcluster.haw-hamburg.de (2002:8d16:1833::8d16:1833) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 19 Jul 2017 16:44:05 +0200
Received: from [31.133.128.169] (141.22.250.35) by haw-mailer.haw-hamburg.de (141.22.24.63) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 19 Jul 2017 16:44:05 +0200
To: "icnrg@irtf.org" <icnrg@irtf.org>
From: "Thomas C. Schmidt" <t.schmidt@haw-hamburg.de>
Message-ID: <2355d31b-c21c-3ede-60ae-68469d5a623f@haw-hamburg.de>
Date: Wed, 19 Jul 2017 16:44:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-15"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [141.22.250.35]
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/Kspqwu--LkUdwxnMahZ9lTjzRSk>
Subject: [icnrg] Do we need an ICMP for ICN?
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 14:44:10 -0000
Hi, we want to continue the lively discussion of today's meeting on "how to do control messaging" in ICN. We made the case for a new message kind in ICN that * is unidirectional + stateless * carries simple control state (e.g., names) * is strictly link-local * follows FIB (or broadcast) So it's something like a restricted, tiny ICMP (or IGMP/MLD). Key arguments for this are * most appropriate for transporting control information * does not twist/overload Interest semantics (or even syntax) * clearly (and cleanly) treatable in the stack * preserves the CCN/NDN request-response logic on the network * does not introduce push-based threats (except for link jamming, which Interests could also do) Key counterarguments are now requested from the group ;) Best, Thomas -- Prof. Dr. Thomas C. Schmidt ° Hamburg University of Applied Sciences Berliner Tor 7 ° ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° ° http://www.haw-hamburg.de/inet Fon: +49-40-42875-8452 ° ° http://www.informatik.haw-hamburg.de/~schmidt Fax: +49-40-42875-8409 °
- Re: [icnrg] Do we need an ICMP for ICN? David Oran
- Re: [icnrg] Do we need an ICMP for ICN? Dirk Kutscher
- [icnrg] Do we need an ICMP for ICN? Thomas C. Schmidt
- Re: [icnrg] Do we need an ICMP for ICN? Thomas C. Schmidt
- Re: [icnrg] Do we need an ICMP for ICN? David Oran
- Re: [icnrg] Do we need an ICMP for ICN? christian.tschudin
- Re: [icnrg] Do we need an ICMP for ICN? Thomas C. Schmidt
- Re: [icnrg] Do we need an ICMP for ICN? christian.tschudin
- Re: [icnrg] Do we need an ICMP for ICN? Thomas C. Schmidt
- Re: [icnrg] Do we need an ICMP for ICN? christian.tschudin
- Re: [icnrg] Do we need an ICMP for ICN? Cenk Gündoğan
- Re: [icnrg] Do we need an ICMP for ICN? Dirk Kutscher