[icnrg] review, Path Steering in CCNx and NDN
Rute Sofia <sofia@fortiss.org> Mon, 11 May 2020 15:24 UTC
Return-Path: <sofia@fortiss.org>
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 670DA3A040F for <icnrg@ietfa.amsl.com>; Mon, 11 May 2020 08:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 82H6hZqFj9YU for <icnrg@ietfa.amsl.com>; Mon, 11 May 2020 08:24:22 -0700 (PDT)
Received: from mail.fortiss.org (mail.fortiss.org [178.15.138.114]) (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 AD0D23A040B for <icnrg@irtf.org>; Mon, 11 May 2020 08:24:21 -0700 (PDT)
Received: from [192.168.16.27] (port=29079 helo=ms01.fortiss.fortiss.org) by mail.fortiss.org with esmtps (TLSv1.2:AES256-GCM-SHA384:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from <sofia@fortiss.org>) id 1jYAHv-0005Tq-2E for icnrg@irtf.org; Mon, 11 May 2020 17:24:15 +0200
Received: from ms01.fortiss.fortiss.org (192.168.16.27) by ms01.fortiss.fortiss.org (192.168.16.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 11 May 2020 17:24:15 +0200
Received: from ms01.fortiss.fortiss.org ([fe80::3928:e952:611b:9286]) by ms01.fortiss.fortiss.org ([fe80::3928:e952:611b:9286%12]) with mapi id 15.01.1913.010; Mon, 11 May 2020 17:24:15 +0200
X-CTCH-RefID: str=0001.0A782F24.5EB96DCC.0052, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
From: Rute Sofia <sofia@fortiss.org>
To: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: review, Path Steering in CCNx and NDN
Thread-Index: AdYnntiVuh/AWajlQsmtSsTrs+WSlg==
Date: Mon, 11 May 2020 15:24:15 +0000
Message-ID: <018e38b2a22b47ce853646ab4dd6debe@fortiss.org>
Accept-Language: en-US, de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [87.123.203.184]
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha-256"; boundary="----BDA9222CDD89D5FFCD4233F42757B905"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/q4SZHVLYK26hGy1KhwFH1HeRjWE>
Subject: [icnrg] review, Path Steering in CCNx and NDN
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: Mon, 11 May 2020 15:24:24 -0000
Hello Ilya, David, so here is a review for https://datatracker.ietf.org/doc/draft-oran-icnrg-pathsteering/?include_text=1. The draft is quite clear given that it has as basis an ACM ICN (2017) paper. Some suggestions : - If possible, Figure 1 should be revised, as ideally the reader should understand the difference when applying this specific proposal of path steering (where, since a first Interest packet follows a path, all subsequent ones directed to the same object/session will do the same)...The figure on the paper is similar, so a suggestion would be to have a fig exemplifying what would happen in forwarder 2, if the conditions in between Interest 1 and Interest 2 would change (for path discovery in ICN vs path steering). - Even though you state that the paper should be a normative reference, the fact is that the reader may or may not read the paper. Therefore, IMO it would be good to have up front a list of definitions (end to end path discovery, path label, etc). - Applicability. A summary for the applicability of path steering is provided in the intro (accurate measurement; monitoring and discovery of multipath). However, the draft would benefit from a section on specific applicability aspects, beyond measurement, and also considering application of ICN on wireless environments IMO. And an additional question: - This specific proposal for path steering builds the path for a session/chunks of an object) based on the first Interest packet for that specific object, correct? Would it be possible/make sense to debate on an approach which would consider a set of first Interest packets, i.e., so that the path would be built on a "best" path instead of on a "first" path? BR, Rute Sofia -- fortiss · Landesforschungsinstitut des Freistaats Bayern An-Institut Technische Universität München Guerickestraße 25 80805 München Germany Tel.: +49 (89) 3603522 170 Fax: +49 (89) 3603522 50 E-Mail: sofia@fortiss.org<mailto:sofia@fortiss.org> https://www.fortiss.org/ Amtsgericht München: HRB: 176633 USt-IdNr.: DE263907002, Steuer-Nr.: 143/237/25900 Rechtsform: gemeinnützige GmbH Sitz der Gesellschaft: München Geschäftsführer: Dr. Harald Rueß, Thomas Vallon Vorsitzender des Aufsichtsrats: Dr. Manfred Wolter
- [icnrg] review, Path Steering in CCNx and NDN Rute Sofia
- Re: [icnrg] review, Path Steering in CCNx and NDN David R. Oran