Re: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen Core Architecture" (draft-ravi-icnrg-5gc-icn-04)

Ravi Ravindran <ravi.ravindran@gmail.com> Fri, 20 September 2019 02:44 UTC

Return-Path: <ravi.ravindran@gmail.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 A4A00120124 for <icnrg@ietfa.amsl.com>; Thu, 19 Sep 2019 19:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 cTT7dAV0wn-u for <icnrg@ietfa.amsl.com>; Thu, 19 Sep 2019 19:44:34 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 68AA1120871 for <icnrg@irtf.org>; Thu, 19 Sep 2019 19:44:34 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id q11so3846968lfc.11 for <icnrg@irtf.org>; Thu, 19 Sep 2019 19:44:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7uLq9SRLzwIf+9W1hPTd7mZBOw48m8e4KclBldaMLag=; b=mxkI+xXg1QLckAB9auGjqylFC2uVDq8AVfedjblH4HbRsdWrGc+T5pSOfhZ+XFXHbh zM3XbDmZaGa6kKanxXb0SMn7DMLroiwhjMy/P2qRLwU0/SZdo1LFuwlL7oGZYbbv2hRK g3xRlMa+6JO+dgAmTQI635yzMxYkqvECNMGiVpAGppAc0riYWWArr5m49hFSsKwx3tal 8vPTONMwY2GbmuwLM7cDRDw5/SPkeC+WADRf03AHKRvi8R/uN1k33Q7s54eFMCXQEf6M c+jcjcphmRxoUCpWpZi6dosQGN2+BeAq2QpsUyjM8vfDOaLtzr86fkDdezodClSuITvE tBZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7uLq9SRLzwIf+9W1hPTd7mZBOw48m8e4KclBldaMLag=; b=H2CUPjGj1rZ8bFzBIBOZ8g3C3pm5BivohKSapHDcBRd7AkXemDErbM7L0X3+ZY0f1u oZYuknyZrFhqtoXyBRDNB9S9UPiO4QgPuhaWU+0O5mpYulW8BR8uAIfc19pVa+pN4EsH 2XvPaN0oJFlXdjiK4wl0AX32J3cxXYzZE5YVA2q09+puEJS5q/TEehNtsVeKLLzhw2wR U+9uIfUzx+1IUeOBXh5GztOzMYbXOfZfvwjLy/REWMxqJFzUuF9egnrfoq91+Qc3bFy2 67PHzYHUxn/1zlhGdSB6abQWlunon3YUx0ZM3kfqwEc7IpckS5bV72xWeWd3/hzZOqVh Zwwg==
X-Gm-Message-State: APjAAAWgF9WgjbHKqit8KEYpsDow2IiJ4PH/Xi2ZGIo2MFzeSm3QRBio cAuQi6o4m1EuX41b9W6ZVpDDeuwYkfMq8msawLg=
X-Google-Smtp-Source: APXvYqwNH9HZnQzBOU4I7G+s/r5WFo/mPr7NIYeedQzFhYf32NJhAbZHjIutUJ/jb73OaqEgm67PyCW/EUNlkNmfefI=
X-Received: by 2002:ac2:5dd6:: with SMTP id x22mr6769333lfq.71.1568947472260; Thu, 19 Sep 2019 19:44:32 -0700 (PDT)
MIME-Version: 1.0
References: <BD080723-2E02-4C21-AD7C-3D7329ABB9F3@dkutscher.net> <CAGhfKzfku+CDW02GZhKYxGKfKAQyOqGBk2Wftj2OvN-3vLZrGA@mail.gmail.com> <CAG9K2Pk1SHz_BEYdf5dACPhxgLZQ6uSkRHqiWr-ctEBkMc__Gw@mail.gmail.com> <CY4PR1301MB1927495C1DCC7D766EB5222CFF890@CY4PR1301MB1927.namprd13.prod.outlook.com>
In-Reply-To: <CY4PR1301MB1927495C1DCC7D766EB5222CFF890@CY4PR1301MB1927.namprd13.prod.outlook.com>
From: Ravi Ravindran <ravi.ravindran@gmail.com>
Date: Thu, 19 Sep 2019 19:44:20 -0700
Message-ID: <CAGhfKzcDRCxOZyMu7=cC=n1KHWfgZTMbwR-9Qeb-5k9wm=RNWw@mail.gmail.com>
To: Cedric Westphal <cedric.westphal@futurewei.com>
Cc: Dirk Kutscher <ietf@dkutscher.net>, icnrg <icnrg@irtf.org>
Content-Type: multipart/alternative; boundary="000000000000c163b00592f30c46"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/_SZJrKD9p0SzcVdmCGRRt8Bl474>
Subject: Re: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen Core Architecture" (draft-ravi-icnrg-5gc-icn-04)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
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: Fri, 20 Sep 2019 02:44:41 -0000

Thanks Cedric, we will address the corrections in the next review.

Regards
Ravi



On Thu, Sep 19, 2019, 11:18 Cedric Westphal <cedric.westphal@futurewei.com
wrote:

> Hi Dirk,
>
>
>
> I support adoption of this draft. It is a very interesting discussion on
> how to enable ICN over the 5G architecture.
>
>
>
> A couple editorial comments:
>
>    - “where 5G technology is considered as one of the promising
>    alternatives.” -> alternative to what?
>    - “realtime” -> real time or real-time
>    - “application- bound identifier and name resolution split principle
>    considered for the ICN is shown to handle host mobility quite efficiently”
>    -> unclear sentence. Maybe: “ICN uses a split between the application
>    identifier and the name resolution that is known to handle host mobility
>    efficiently”
>    - “design principals” -> “design principles”
>    - “utilize API design” -> “an API design”
>
>
>
> Best,
>
>
>
> C.
>
>
>
>
>
> ---------- Forwarded message ---------
> From: *Dirk Kutscher* <ietf@dkutscher.net>;
> Date: Mon, Sep 16, 2019 at 11:36 AM
> Subject: [icnrg] Possible adoption of "Enabling ICN in 3GPP's 5G NextGen
> Core Architecture" (draft-ravi-icnrg-5gc-icn-04)
> To: ICNRG <icnrg@irtf.org>;
>
>
>
> Hi ICNRG,
>
> At the ICNRG meeting at IETF-105 in Montreal, we discussed the possible
> adoption of https://datatracker.ietf.org/doc/draft-ravi-icnrg-5gc-icn/
> <https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ravi-icnrg-5gc-icn%2F&data=02%7C01%7Ccedric.westphal%40futurewei.com%7C1278917ce119463ea73a08d73c5fa868%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637044253849499323&sdata=y6MacrSUa056iZsRKSGr5O3t%2BqDRdY31fgGR4ECr0aE%3D&reserved=0>
> .
>
> During the meeting, no objection was raised, but not many people had
> read the latest version of the draft. As usual, we would like to follow
> up on the mailing list, so we are looking for statements indicating
> support for adoption or concerns against it from people who are 1) not
> co-authors and 2) have read the latest version.
>
> Thanks and best regards,
>
> Chairs
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
> <https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.irtf.org%2Fmailman%2Flistinfo%2Ficnrg&data=02%7C01%7Ccedric.westphal%40futurewei.com%7C1278917ce119463ea73a08d73c5fa868%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637044253849499323&sdata=vaqzel4d%2BDaViQaXlm5LsUCXhcA8HpqUBI3KGzA4IOM%3D&reserved=0>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
>