Re: [icnrg] Heads-up: RG adoption of terminology draft
"Michael Kowal (mikowal)" <mikowal@cisco.com> Tue, 24 October 2017 19:04 UTC
Return-Path: <mikowal@cisco.com>
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 9667C139EF2 for <icnrg@ietfa.amsl.com>; Tue, 24 Oct 2017 12:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 lJTNqrwKl5mc for <icnrg@ietfa.amsl.com>; Tue, 24 Oct 2017 12:04:40 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64969139F5C for <icnrg@irtf.org>; Tue, 24 Oct 2017 12:04:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3766; q=dns/txt; s=iport; t=1508871876; x=1510081476; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=j78/7smPvNYeRrn9+2gtbZ08Wsb7LhmskWxoPFjxFgo=; b=A0sR1tvBz+McDQVyNLtGn7ArVUJ3jv0+YgC1sHvsdlZhpB9KvT4sMjXh etmZPDlN3m7qwd8jPfVUFEUKcC6D9oo0VaMLxTEzEbZGCGbxlaTSFJueP BgRZuN7qI3wIqcpWBTpRJFcI8ruYyFGo3My3vw+CCbtErYDv6R3ogpW6l A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CiAABjje9Z/5tdJa1aGQEBAQEBAQEBAQEBBwEBAQEBg19kbicHgzBDih+PSYF6ljqCEQoYDYUWAhqERz8YAQIBAQEBAQEBax0LhR0BAQEBAwEBChcROgsMBAIBBgIRAwECAwImAgICJQsVCAgCBA4FiiAQihGdZ4IniyMBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYEPgh+CB4FQghKDAYMyhGcvgjIFkVCHI4h6AodjjRCTJZVSAhEZAYE4AR84gVt6FR8qLQGCNoRfdgGKX4ERAQEB
X-IronPort-AV: E=Sophos;i="5.43,429,1503360000"; d="scan'208";a="311816082"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Oct 2017 19:04:35 +0000
Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v9OJ4Z0u030571 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 24 Oct 2017 19:04:35 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 24 Oct 2017 14:04:34 -0500
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1320.000; Tue, 24 Oct 2017 14:04:34 -0500
From: "Michael Kowal (mikowal)" <mikowal@cisco.com>
To: "ietf@dkutscher.net" <ietf@dkutscher.net>
CC: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: [icnrg] Heads-up: RG adoption of terminology draft
Thread-Index: AQHTTPrtmX7TvtA/F0OWEC5bJUDf6A==
Date: Tue, 24 Oct 2017 19:04:34 +0000
Message-ID: <D929BB54-AF11-44DD-AD81-BDBF382E1196@alumni.stevens.edu>
References: <FBCAC64E-9C95-481D-98B5-59AE789695C5@dkutscher.net>
In-Reply-To: <FBCAC64E-9C95-481D-98B5-59AE789695C5@dkutscher.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.98.98.55]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0AF1BD3A8326F64294900A0B03120FDA@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/xwgVrTyOlWg2sibP0MXyF3mbN94>
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: Tue, 24 Oct 2017 19:04:47 -0000
Hi all, I support. One nit: the ‘x’ in ‘CCNx’ is never defined. -----Original Message----- From: icnrg <icnrg-bounces@irtf.org> on behalf of Dirk Kutscher <ietf@dkutscher.net> Date: Tuesday, October 24, 2017 at 5:20 AM To: <icnrg@irtf.org> Subject: [icnrg] Heads-up: RG adoption of terminology draft 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
- [icnrg] Heads-up: RG adoption of terminology draft Dirk Kutscher
- Re: [icnrg] Heads-up: RG adoption of terminology … Thomas C. Schmidt
- Re: [icnrg] Heads-up: RG adoption of terminology … Matthias Waehlisch
- Re: [icnrg] Heads-up: RG adoption of terminology … Rahman, Akbar
- Re: [icnrg] Heads-up: RG adoption of terminology … Mayutan A.
- Re: [icnrg] Heads-up: RG adoption of terminology … Michael Kowal (mikowal)
- Re: [icnrg] Heads-up: RG adoption of terminology … Jungha Hong
- Re: [icnrg] Heads-up: RG adoption of terminology … S Samar
- Re: [icnrg] Heads-up: RG adoption of terminology … Dirk Kutscher