[icnrg] FW: New Version Notification for draft-azgin-icnrg-ni-00.txt

Ravi Ravindran <ravi.ravindran@huawei.com> Mon, 31 October 2016 22:31 UTC

From: Ravi Ravindran <ravi.ravindran@huawei.com>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: New Version Notification for draft-azgin-icnrg-ni-00.txt
Thread-Index: AQHSM6cGrqh+kB4uJ0mgrzHse6Gu/KDDI7NQ
Date: Mon, 31 Oct 2016 22:31:40 +0000
Message-ID: <D96E28F4A22C864DBC6C871B5B1C4CC3216B6CEB@dfweml501-mbb>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/PaVlK8ex87sMz-CBuVF1FkXC1gM>
Subject: [icnrg] FW: New Version Notification for draft-azgin-icnrg-ni-00.txt
Precedence: list

Hi,

The draft below focuses on the requirements and challenges of using names (or application identifiers as used in the draft) for routing and forwarding, for which forwarding label https://tools.ietf.org/html/draft-ravi-ccn-forwarding-label-02

was proposed. Capturing some of the discussions during the harmonization discussion, we also present a comparison between forwarding label and link object in this draft. 

We request the chairs a slot to discuss this during the ICNRG meeting.

Regards,
Ravi

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, October 31, 2016 11:46 AM
To: Ravi Ravindran; Ravi Ravindran; Aytac Azgin
Subject: New Version Notification for draft-azgin-icnrg-ni-00.txt


A new version of I-D, draft-azgin-icnrg-ni-00.txt
has been successfully submitted by Aytac Azgin and posted to the
IETF repository.

Name:		draft-azgin-icnrg-ni
Revision:	00
Title:		Enabling Network Identifier (NI) in Information Centric Networks to Support Optimized Forwarding
Document date:	2016-10-31
Group:		Individual Submission
Pages:		14
URL:            https://www.ietf.org/internet-drafts/draft-azgin-icnrg-ni-00.txt
Status:         https://datatracker.ietf.org/doc/draft-azgin-icnrg-ni/
Htmlized:       https://tools.ietf.org/html/draft-azgin-icnrg-ni-00


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.  These considerations also require
   enabling a network based name resolution service for efficient and
   scalable routing.

   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