[icnrg] FW: New Version Notification for draft-azgin-icnrg-ni-02.txt
Ravi Ravindran <ravi.ravindran@huawei.com> Tue, 18 July 2017 04:26 UTC
Return-Path: <ravi.ravindran@huawei.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 BA9C812ECBE for <icnrg@ietfa.amsl.com>; Mon, 17 Jul 2017 21:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 HTJzFyqYCWB4 for <icnrg@ietfa.amsl.com>; Mon, 17 Jul 2017 21:26:30 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0C97126C0F for <icnrg@irtf.org>; Mon, 17 Jul 2017 21:26:30 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml702-cah.china.huawei.com) ([172.18.9.243]) by dfwrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CGB00527; Mon, 17 Jul 2017 23:26:29 -0500 (CDT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by dfweml702-cah.china.huawei.com (10.193.5.176) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 17 Jul 2017 21:26:23 -0700
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.153]) by SJCEML703-CHM.china.huawei.com ([169.254.5.240]) with mapi id 14.03.0301.000; Mon, 17 Jul 2017 21:26:14 -0700
From: Ravi Ravindran <ravi.ravindran@huawei.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-azgin-icnrg-ni-02.txt
Thread-Index: AQHS/3yRY2Su1vrJzEK/RKUyHfklsKJY/N0g
Date: Tue, 18 Jul 2017 04:26:14 +0000
Message-ID: <D96E28F4A22C864DBC6C871B5B1C4CC322AF5EF3@SJCEML702-CHM.china.huawei.com>
References: <150035135782.11364.17867596733281145263.idtracker@ietfa.amsl.com>
In-Reply-To: <150035135782.11364.17867596733281145263.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.210.165.229]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/Sw07fNDC6UyIssvqB4M1vBoMFYI>
Subject: [icnrg] FW: New Version Notification for draft-azgin-icnrg-ni-02.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: Tue, 18 Jul 2017 04:26:33 -0000
This is the AI/NI draft we presented during the interim. Regards, Ravi -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: Tuesday, July 18, 2017 6:16 AM To: Ravi Ravindran <ravi.ravindran@huawei.com>; Aytac Azgin <aytac.azgin@huawei.com>; Ravi Ravindran <ravi.ravindran@huawei.com> Subject: New Version Notification for draft-azgin-icnrg-ni-02.txt A new version of I-D, draft-azgin-icnrg-ni-02.txt has been successfully submitted by Aytac Azgin and posted to the IETF repository. Name: draft-azgin-icnrg-ni Revision: 02 Title: Enabling Network Identifier (NI) in Information Centric Networks to Support Optimized Forwarding Document date: 2017-07-17 Group: Individual Submission Pages: 17 URL: https://www.ietf.org/internet-drafts/draft-azgin-icnrg-ni-02.txt Status: https://datatracker.ietf.org/doc/draft-azgin-icnrg-ni/ Htmlized: https://tools.ietf.org/html/draft-azgin-icnrg-ni-02 Htmlized: https://datatracker.ietf.org/doc/html/draft-azgin-icnrg-ni-02 Diff: https://www.ietf.org/rfcdiff?url2=draft-azgin-icnrg-ni-02 Abstract: The objective of this proposal is to introduce the notion of network identifier (NI) in the ICN architecture. This is in addition to the existing names (i.e., content identifiers, CIs, or application identifiers, AIs, in general) that are currently used for both naming and routing/forwarding purposes. Network identifiers are needed considering the requirements on future networking architectures such as: (i) to support persistent names (or persistently named objects) and large-scale and high-speed mobility of any network entity (i.e, devices, services, and content), (ii) to accommodate different types of Internet of Things (IoT) services, many of which require low- latency performance, and enabling edge computing to support service virtualization, which will require support for large scale migration and replication of named resources, and (iii) to scale the ICN architecture to future Internet scale considering the exponentially increasing named entities. If information on AI-to-NI mappings are not directly accessible to the consumers, for instance, using specific datasets like manifests, these considerations may require enabling a name resolution service, which can be network based or application driven, to support efficient and scalable routing. Current document do not impose any restrictions on the name resolution architecture, regarding its scope. In the current draft, we begin by highlighting the issues associated with ICN networking when utilizing only the AIs, which include persistently named content, services, and devices. Next we discuss the function NI serves, and provide a discussion on the two current NI-based proposals, along with their scope and functionalities. This is with the objective of having a single NI construct for ICN that is flexible enough to adapt to different networking contexts. 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
- [icnrg] FW: New Version Notification for draft-az… Ravi Ravindran