Re: [icnrg] Heads-up: RG adoption of terminology draft

"Dirk Kutscher" <ietf@dkutscher.net> Wed, 25 October 2017 08:06 UTC

Return-Path: <ietf@dkutscher.net>
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 E7BA313AB12; Wed, 25 Oct 2017 01:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5] 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 LI_jVUaHAUpv; Wed, 25 Oct 2017 01:06:25 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (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 43CC3138467; Wed, 25 Oct 2017 01:06:25 -0700 (PDT)
Received: from [192.168.43.233] ([89.204.135.146]) by mrelayeu.kundenserver.de (mreue103 [212.227.15.183]) with ESMTPSA (Nemesis) id 0Lfp8c-1dNovX3F6Y-00pIax; Wed, 25 Oct 2017 10:06:14 +0200
From: Dirk Kutscher <ietf@dkutscher.net>
To: S Samar <s.samar@tcs.com>
Cc: icnrg@irtf.org, icnrg <icnrg-bounces@irtf.org>
Date: Wed, 25 Oct 2017 10:06:09 +0200
Message-ID: <56D194A5-12DA-48B9-8063-E2DA532EDE23@dkutscher.net>
In-Reply-To: <OF0CE84F61.190DA687-ON652581C4.00192841-652581C4.001954D4@tcs.com>
References: <FBCAC64E-9C95-481D-98B5-59AE789695C5@dkutscher.net> <OF0CE84F61.190DA687-ON652581C4.00192841-652581C4.001954D4@tcs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_A91907FB-CAB8-41DB-A85F-48D8B305EA77_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[1547, 5914], "plain":[222, 3290], "uuid":"828E5FD4-2401-429D-8ECC-BE7238D6FAA0"}]
X-Mailer: MailMate (1.9.7r5425)
X-Provags-ID: V03:K0:jLLnFxbB6AR4szYnMka4t0oq2JJQmtwZnYOaW+DoWXyNU66kxnX Z5GlZCgbt+ap87lW0LZneDC+s8IOUKbSrfyoiw5SD/cC6wsgVu0TCpDw52G5+Y+WPafR5LL 4mSB/A3wEmV22joci1bUlre9emvv4DHs2PzRgN0DjrydZjQraf3f2Jsi5V+2PRVxhcXFE/H 9l+6Cf096GaHwNyfUug7g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:lNE7bhQ+Vmk=:N6WBKdsuubStSB7Nn29Snn hdsY/kaciSCaOzBaBN3aGAvn4ArmcDyVj6nWwisaMxWIZwhGEMbodurInlgQHqFTD6pwZWSCV PIrlLH9V5RfH9Lex5Ln4XLkFA9e1pPTLLd2MaFDdo0HQavDl/Kic9hBn53M8HZZ7fJ7BLUFSA ol2SIkIaeUQXsV9RxZRCD9bXihscglfINK/nNyzkreA9ssxhPDc6aYD9tIDyBGshwWc5cTOs0 wCiYknX4iy6kLI1DbUkFrApasRN4Glg5xXS4J6WFrG2RlZmNb5WxnLoVlKDSOsmqCA0eGj6G5 HcGmnf+UCsb89SxaP2lmCG7A8Rva477/jdnypIUD2SEY6hg/LPrVJizZR3o6wo5Aa7ncbVBAc AXwMMyRdUlAc9KJb+IOAbU39Qr9yZi5XOPqXIdyDN5r/B1MrAiZU2X3aKJhXSvVOYe3ikgEZQ H3qoOxm/1oz2azDV467IgbxJgGkp83ws7mQZRIr6Pix8DT0tFhCQusgEw201y+wF/sFSVa+0Z q15WU5eR+JFBR5agevfUSxQgzPUNn75ON+LZwYWZplva5ybdEQhe/fR6D4R1QvYY8XR+amMLm naBSy1ahS7tzX8aLj+sR0N8hhO8WVqFusz60eEK57JRFrjn7txTdKASE2bK1gIeo6JD8Q47An AqBvWugnvWI9gLSN6o3N+UxitVGbp87v3ef+O6xJbwLL8hwUGq3m6WAUP7zPwpho91Fxhb79n hb+yt2XQk1gI0kASXj2t9GLXT5OVrRzWcm3m70jlJfmEDILQakJEYZ3Ep98=
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/bxmYiGlXPy02UhEtQYeEXQqvdA8>
Subject: Re: [icnrg] Heads-up: RG adoption of terminology draft
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, 25 Oct 2017 08:06:28 -0000

Thanks for all the feedback so far!

Since we want to talk about the draft in Singapore, it would also be 
great to hear some suggestions for fixes and additions.

Thanks,
Dirk



On 25 Oct 2017, at 6:36, S Samar wrote:

> I agree and support the terminology adoption.
>
> Best Regards
> Samar
>
> Dr. Samar Shailendra
> TCS Research & Innovation
> Website: http://www.tcs.com
>
>
>
> From:   "Dirk Kutscher" <ietf@dkutscher.net>
> To:     icnrg@irtf.org
> Date:   10/24/2017 02:50 PM
> Subject:        [icnrg] Heads-up: RG adoption of terminology draft
> Sent by:        "icnrg" <icnrg-bounces@irtf.org>
>
>
>
> Hi all,
>
> the ICNRG Chairs would like to initiate a discussion on the adoption 
> of
> the terminology draft:
>
> Name:                            draft-wissingh-icnrg-terminology
> Revision:                03
> Title:                           Information-Centric Networking (ICN): 
> CCN
> and NDN Terminology
> Document date:           2017-09-11
> Group:                           Individual Submission
> Pages:                           18
> URL:
> https://www.ietf.org/internet-drafts/draft-wissingh-icnrg-terminology-03.txt
>
> Status:
> https://datatracker.ietf.org/doc/draft-wissingh-icnrg-terminology/
> Htmlized:
> https://tools.ietf.org/html/draft-wissingh-icnrg-terminology-03
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-wissingh-icnrg-terminology-03
> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-wissingh-icnrg-terminology-03
> 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.
>
>
>  From the chairs?s perspective, this draft has seen some review in the
> group, and the general feedback suggests that this is useful work.
>
> It?s not quite ready for publication of course, but now could be a
> good time to discuss whether think that this is sufficiently mature,
> aiming at the right content and whether it could become a useful and
> relevant product of ICNRG at some point.
>
> Process-wise, at this point, we are essentially trying to motivate you
> to look into it, share your thoughts on the list or at the meeting at
> IETF-100 where we are going to talk about it. The actual decision will
> be taken after IETF-100, on the mailing list as usual.
>
> Thanks,
> Börje, Dave, Dirk
>
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you