Re: [icnrg] [irsg] IRSG review request draft-irtf-icnrg-ccninfo-08

Hitoshi Asaeda <> Fri, 08 April 2022 09:58 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF7E53A1A4A; Fri, 8 Apr 2022 02:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Jhz_yA5gsT_r; Fri, 8 Apr 2022 02:58:36 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1CD1D3A1A78; Fri, 8 Apr 2022 02:57:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; h=Content-Type: Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding: Message-Id:References:To;;s=20200225.smx;t=1649411854;x= 1650621454; bh=i09jC2lvRHJNZbQB7OwG6R0bEPu4k6fzsD+Q68kHKvE=; b=FpDmOo3iPOr3z/OF ae2i5Lxi/IhVE+34Z1NeOrgWgjJcm0Aksm06+nADK38/GRjwL24yZeEZadBccahUW2bpBAvwfwpeU QOnMMiJ3iKnX+TgZmVlYsqhQ6yxaZRIMl7jLFrSba8Tv6KHu86fjrkfjA0N3XonfCgGmXTvVaYBXq kql9s5mBrUlibaPuqyAvZnfZ0j+FjM7qXyUefDfC/d6+hdKC+mYkqOgphmh53a7nrJy5gQR/KSuWr fbejVMGpyfpHc43w/l+30QC5qwVU0lGTwbVcpmDHJ/agNmFXwpn+5eEjRFHkTJEy1mPrU7O/y7BJi XpReqzUUXCEK7XsWkQ==;
Received: by (mx-mo-csw1516) id 2389vX3G010750; Fri, 8 Apr 2022 18:57:33 +0900
X-Iguazu-Qid: 34trQigfs04P2B0GCg
X-Iguazu-QSIG: v=2; s=0; t=1649411853; q=34trQigfs04P2B0GCg; m=WlPSOQ75lXLpcRM7n5ttVOaeQRR4oHAnIRCJqVrP/m0=
Received: from ( []) by (mx-mr1513) id 2389vVGa021327 (version=TLSv1.2 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 8 Apr 2022 18:57:31 +0900
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (NICT Mail Spool Server2) with ESMTPSA id 00340B1C90; Fri, 8 Apr 2022 18:57:30 +0900 (JST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
From: Hitoshi Asaeda <>
In-Reply-To: <>
Date: Fri, 08 Apr 2022 18:57:28 +0900
Cc: Colin Perkins <>, The IRSG <>,,
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Jérôme François <>
X-Mailer: Apple Mail (2.3693.
Archived-At: <>
Subject: Re: [icnrg] [irsg] IRSG review request draft-irtf-icnrg-ccninfo-08
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 08 Apr 2022 09:58:43 -0000

Dear Jérôme,

Thank you so much for your careful review.
We'll address your comments in the revision and reply to your question in a short time.



> On Apr 8, 2022, at 16:21, Jérôme François <> wrote:
> Dear Colin, IRSG members and draft authors,
> Sorry for  providing my review late but below are my comments for draft-irtf-icnrg-ccninfo-08.
> Best regards
> Jérôme
> -----------------
> In general, the draft is well written but there some parts would merit clarification. Below are my comments, suggestions and questions (which actually reflects some lack of clarity IMHO).
> Section 3 about the message formats is not easy to follow because it is unclear how these messages will be used. Of course, answers comes in the next section 4 but as section 3 is quite long I think this could be improved by extending a bit the overview given in section 1 to “prepare” the reader for section 3. For instance in section 1, we can easily understand the flow of request and reply messages but with not so much regarding their content. My suggestions are to comment more on figure 1 and 2 in order to highlight the different structures used in messages afterwards (request header blocks, report blocks, reply  blocks) and when they are added. At a first glance, when I read report block I was thinking this was related to reply (somehow I thought reply = report). Of course when I read again I saw this is not but as the term can be little confusing, clarifying and emphasizing would avoid confusion. You can for example distinguish what information would be set in the request message and the information set in the reply. For replies, there are possibly multiple reply sub-blocks but it remains unclear for me what each sub-block should contain. I guess when there are multiple objects matching the prefix in the request but I’m not sure this is clearly stated somewhere (even in other sections).
> Some detailed comments per section below:
> Section 2.1 (definition):
> - add the definitions of publisher and consumer as these terms are widely used in the text then
> - CCNinfo user is also a node but a node (based on your definition) can be router, publisher or consumer. So, is CCNinfo user a consumer node? Or something different?
> - router definition: Unclear what is meant by “facilitates”. Facilitates would suppose that is something not mandatory but which can help. Without router, content retrieval cannot be done I guess so the routers enable content retrieval ?
> Section 3:
> - page 9: “the Request and Reply Type values in the fixed header are”: use “PacketType values” to refer to packet format in figure 3
> - page 9 “The CCNinfo Request and Reply messages MUST ...”: move/merge this sentence as first in the previous paragraph as this sounds a bit redundant here.
> - Figure 6: I was wondering if there is a particular reason to have the request block TLV apart from other blocks (request header and report). If yes, you could mention it in the doc.
> - page 11: “and __THE__ Request block TLV (Figure 7)”
> - page 12 SkipHop: “Routers corresponding to the value specified” → “The number of routers corresponding...” (as this is a value not a set of routers right ?). State that this will correspond to the first routers in the paths toward the publisher.
> - “request arrival time” is used both in request block and report blocks with the same definition.  My understanding is that request block is inserted by the initiator (CCNinfo user), so the request arrival time in that case seems to not be “the timestamp specifying the arrival time of the CCNinfo Request packet at a specific router” but the timestamp the CCNinfo user create the request (section 4,1, p. 21). If if I’m right, you could also think changing the term “request arrival time” by something more relevant in Request block TLV.
> - page 23 and page 24: “it it terminates the Request...”: remove one “it”
> - section 5.6: I appreciate this section as I have in mind this kind of complex example when reading previous sections.
> - section 8,2: precise what is meant by “identified”. I understand that if a router hides itself you can just know there was a router but you cannot know its id (so IMHY it is not really identify but you can detect there is a hidden router)?