Re: [icnrg] Adoption of draft-white-icnrg-ipoc as an ICNRG Draft

"Thomas C. Schmidt" <t.schmidt@haw-hamburg.de> Wed, 24 July 2019 18:09 UTC

Return-Path: <t.schmidt@haw-hamburg.de>
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 EF192120059 for <icnrg@ietfa.amsl.com>; Wed, 24 Jul 2019 11:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 BhKzB7Y3THXD for <icnrg@ietfa.amsl.com>; Wed, 24 Jul 2019 11:09:57 -0700 (PDT)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D0FB1203E5 for <icnrg@irtf.org>; Wed, 24 Jul 2019 11:09:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.64,303,1559512800"; d="scan'208";a="72086126"
Received: from hub02.mailcluster.haw-hamburg.de ([141.22.24.51]) by mail6.is.haw-hamburg.de with ESMTP/TLS/DHE-RSA-AES256-SHA; 24 Jul 2019 20:09:54 +0200
Received: from CAS03.mailcluster.haw-hamburg.de (2002:8d16:183e::8d16:183e) by HUB02.mailcluster.haw-hamburg.de (2002:8d16:1833::8d16:1833) with Microsoft SMTP Server (TLS) id 14.3.468.0; Wed, 24 Jul 2019 20:09:53 +0200
Received: from [172.16.148.203] (141.22.250.35) by haw-mailer.haw-hamburg.de (141.22.24.62) with Microsoft SMTP Server (TLS) id 14.3.468.0; Wed, 24 Jul 2019 20:09:53 +0200
To: <icnrg@irtf.org>
References: <3955cfa9278f4a1dab9cae339fa2839b@HUB02.mailcluster.haw-hamburg.de>
From: "Thomas C. Schmidt" <t.schmidt@haw-hamburg.de>
Message-ID: <1db5c479-61c3-f22a-0e39-d66c736790c7@haw-hamburg.de>
Date: Wed, 24 Jul 2019 14:09:52 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <3955cfa9278f4a1dab9cae339fa2839b@HUB02.mailcluster.haw-hamburg.de>
Content-Type: text/plain; charset="iso-8859-15"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [141.22.250.35]
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/HZ7tT-3nG1kXMUvBMYgYspK1taA>
Subject: Re: [icnrg] Adoption of draft-white-icnrg-ipoc as an ICNRG Draft
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: Wed, 24 Jul 2019 18:10:00 -0000

Hi,

I've participated in several presentations and had a (rather light) look 
at the document.

 From this, I believe the document addresses an important work and 
should be adopted.

Still I have a couple of immediate remarks that might bring up some 
additional thinking or work on this subject.

The draft states in its abstract:
   "By leveraging the
    elegant, built-in support for mobility provided by CCN or NDN, this
    protocol achieves performance on par with LTE-EPC, equivalent
    efficiency, and substantially lower implementation and protocol
    complexity."
Unfortunately, I could not find any substantiation nor justification for 
this claim, neither in the document nor in references.

As this is a research group document, I would further encourage to 
include a comparative discussion with Mobile IPv6 (RFC 6275) and - as 
the ICN approach is more closely related to Multicast - with Multicast 
Mobility (see RFC 5757).

Cheers,
  Thomas


On 24/07/2019 11:11, David R. Oran wrote:
> Folks,
> 
> At the ICNRG Interim meeting before IETF 105, the chairs proposed we
> adopt the IPOC work as a Research Group draft for progression. There was
> support for this at the meeting, so we are issuing this call on the list
> to confirm this decision. If we hear no objections by Friday July 26, we
> will adopt the draft. No need for ACKs; only NACK if anyone has
> objections to this course of action.
> 
> The current draft is at
> https://datatracker.ietf.org/doc/draft-white-icnrg-ipoc/.
> 
> Many thanks,
> 
> DaveO, Börje, and Dirk.
> 
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg
> 

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                  Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group   20099 Hamburg, Germany °
° http://inet.haw-hamburg.de/members/schmidt      Fon: +49-40-42875-8452 °