Re: [icnrg] FW: New Version Notification for draft-wissingh-icnrg-terminology-01.txt
christian.tschudin@unibas.ch Wed, 22 March 2017 06:06 UTC
Return-Path: <christian.tschudin@unibas.ch>
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 754ED126B7F for <icnrg@ietfa.amsl.com>; Tue, 21 Mar 2017 23:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 eh6YhVsBoPXF for <icnrg@ietfa.amsl.com>; Tue, 21 Mar 2017 23:06:09 -0700 (PDT)
Received: from mx2-priv.urz.unibas.ch (mx2-priv.urz.unibas.ch [131.152.226.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8907112420B for <icnrg@irtf.org>; Tue, 21 Mar 2017 23:06:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx2-priv.urz.unibas.ch (Postfix) with ESMTP id CE5AD2201FF; Wed, 22 Mar 2017 07:06:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at unibas.ch
Received: from smtp-ext.unibas.ch ([131.152.226.167]) by localhost (mx2-mgnt.urz.unibas.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FkvSHnd73Nqe; Wed, 22 Mar 2017 07:06:06 +0100 (CET)
Received: from dmi-sinus.dmi.unibas.ch (dmi-sinus.dmi.unibas.ch [131.152.54.173]) by smtp-ext.unibas.ch (Postfix) with ESMTPSA id BA8FA22016A; Wed, 22 Mar 2017 07:06:06 +0100 (CET)
Date: Wed, 22 Mar 2017 07:06:08 +0100
From: christian.tschudin@unibas.ch
X-X-Sender: tschudin@dmi-sinus.dmi.unibas.ch
To: Boubakr NOUR <n.boubakr@bit.edu.cn>
cc: icnrg@irtf.org, "Wissingh, B.F. (Bastiaan)" <bastiaan.wissingh@tno.nl>
In-Reply-To: <0f3b1b25-0e27-5bce-d961-1356aa66098e@bit.edu.cn>
Message-ID: <alpine.OSX.2.20.1703220659130.52181@dmi-sinus.dmi.unibas.ch>
References: <148943936021.20433.4593561964018345656.idtracker@ietfa.amsl.com> <6010D6BF-D49E-420F-8874-85131835CDCD@tno.nl> <0f3b1b25-0e27-5bce-d961-1356aa66098e@bit.edu.cn>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-454555491-1490162768=:52181"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/VRdwymy34Emju6KP-oq5MTW0ZwA>
Subject: Re: [icnrg] FW: New Version Notification for draft-wissingh-icnrg-terminology-01.txt
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, 22 Mar 2017 06:06:12 -0000
On Wed, 22 Mar 2017, Boubakr NOUR wrote: > In the following draft (Information-Centric Networking (ICN): Terminology), I found the > following paragraph, I am confusing about the Name-Content binding phase. > > “In ICN, verification of a data packet’s name-to-content binding is achieved through > cryptographic means, either by (1) a cryptographic signature that explicitely binds an > application-chosen name to a data packet’s content, or (2) relying on an implicit name > (cryptographic hash of the data packet) that the data consumer obtained through other means.” > > Is this means that the same content with different names should have the same signature or > hash. Is the cryptographic signature/hash applied only on content without taking in > consideration other parameters such us: name itself, owner of content, timestamps…? No: as soon as one element changes, so will the signature as well as the packet's implicit name because both cover the whole packet. But this is ok: what remains a constant in this picture of moving parts is the trust model, for example the key used to sign the packet; or the trust in the source from where the hash value of the packet was obtained (an example source could be a manifest, which would be signed). best, christian > > Best regards, > > > On 3/20/2017 7:05 PM, Wissingh, B.F. (Bastiaan) wrote: > > Hi all, > > We’ve uploaded a new version of the draft regarding ICN Terminology in which we’ve been address > ing comments we received on the first version of the draft, so please have a look at the docume > nt. See details below. > > Best, > Bastiaan > > Op 13-03-17 22:09 heeft internet-drafts@ietf.org <internet-drafts@ietf.org> geschreven: > > > A new version of I-D, draft-wissingh-icnrg-terminology-01.txt > has been successfully submitted by Bastiaan Wissingh and posted to the > IETF repository. > > Name: draft-wissingh-icnrg-terminology > Revision: 01 > Title: Information-Centric Networking (ICN): Terminology > Document date: 2017-03-13 > Group: Individual Submission > Pages: 15 > URL: https://www.ietf.org/internet-drafts/draft-wissingh-icnrg-terminology-01.tx > t > Status: https://datatracker.ietf.org/doc/draft-wissingh-icnrg-terminology/ > Htmlized: https://tools.ietf.org/html/draft-wissingh-icnrg-terminology-01 > Diff: https://www.ietf.org/rfcdiff?url2=draft-wissingh-icnrg-terminology-01 > > Abstract: > Information Centric Networking (ICN) is a new paradigm where network > communications are accomplished by requesting named content, instead > of sending packets to destination addresses. Named Data Networking > (NDN) and Content-Centric Networking (CCN) are two prominent ICN > architectures. This document provides an overview of the terminology > and definitions that have been used in describing concepts in these > two projects. While there are other ICN architectures, they are not > part of the NDN and CCN vision and as such are out of scope for this > document. > > > > > 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 > > > > This message may contain information that is not intended for you. If you are not the addressee > or if this message was sent to you by mistake, you are requested to inform the sender and dele > te the message. TNO accepts no liability for the content of this e-mail, for the manner in whic > h you use it and for damage of any kind resulting from the risks inherent to the electronic tra > nsmission of messages. > _______________________________________________ > icnrg mailing list > icnrg@irtf.org > https://www.irtf.org/mailman/listinfo/icnrg > > > -- > Boubakr NOUR (Ph.D Candidate) > School of Computer Science > Beijing Institute of Technology > >
- [icnrg] FW: New Version Notification for draft-wi… Wissingh, B.F. (Bastiaan)
- Re: [icnrg] FW: New Version Notification for draf… Boubakr NOUR
- Re: [icnrg] FW: New Version Notification for draf… christian.tschudin