Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-icntraceroute-06.txt

Junxiao Shi <> Wed, 13 July 2022 22:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 12261C15791D for <>; Wed, 13 Jul 2022 15:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bn4O1_8JL1Hd for <>; Wed, 13 Jul 2022 15:08:12 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::112d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id F3754C14F72B for <>; Wed, 13 Jul 2022 15:08:11 -0700 (PDT)
Received: by with SMTP id 00721157ae682-2ef5380669cso126866517b3.9 for <>; Wed, 13 Jul 2022 15:08:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=9IYwHrYYy3MQYRMZbspMp30Mkn2m+kCW3Xv4klMYoV4=; b=18PZGbXNYUmk/G54de1PSTyW5G8Eh4+esk3COOfue7SoUKA5DjnmXaBEYqEJpNE9sd fYlvlfHyxkyqgN+pjogOgsEvJ+WRu43fC6jnOldVEH/SjG4t7YizRPphjqm5GJvuPnUa azf5GM4cxS/5QNMtm7e9673cznWrCR6IANwtXFjI++go/yc29fXjBhfxoJvmZrydsK0m Tb1q78XP6HQ/j8o+tn1NDaXuzzjyXPzfVDcpai779NImYCsZKhZaQAD6JgUWop/HJc7L TJHJuWYk5aZUVIUz0phhr6sWaQwaHFvGc08yL6SDtPz0JQ4K/f8R4XqHKbRmPKbrgSBn vOPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=9IYwHrYYy3MQYRMZbspMp30Mkn2m+kCW3Xv4klMYoV4=; b=rTjwgQyzKqgd3bL3EpSq8rz60NvYFEwiauJWuGCqcVEjC02l55HerguUZ71Ud+9or0 tSCyWYUEsdTwGUQJS8LoX7IXxeuHhjwyXASVTrXgf7n6M/XtblpvizebcKje413xJ7ZT 4vHA7x342rgsQpaEoOC24JwIkjshYWuK14OhZPRkQK5yHaxHAf3ITdqKgDeRvgBV9cuD YwkarteJsn38HBRWM0jdYfmevFhMJPTnohASvJDG9Zufvg7kxHMGmpeI7Z8HwuGQKN/T jCUBlftZO/z7tg2ktmQn2S2qlyRCAaDUfbK2wPNiY/9Fbe3F+E5U/gCFagB1Y848YMQ3 klHA==
X-Gm-Message-State: AJIora+5gxMAsFowQd+XMzdpsKlxMLFh9PtlPJJSdHd/Z+omwh0lhlYF sYKMCxy3syV/AempAOzDs07YiJ4q1mX+JBdmMCO5idK/8bpfMHzFFckMDm+5Wy9IDFVmKIldh4k pkxsQWH0Kupe9pCJAmQ4=
X-Google-Smtp-Source: AGRyM1tulSX0Mmplb6so8ro7oaiHRsiJPXPo9EmPDFEmWYXGwwEdiVX1KL2Y+Dof1abpB8HbbYRYJoDv8fD6tHR2tAE=
X-Received: by 2002:a0d:f247:0:b0:31d:68b1:5a16 with SMTP id b68-20020a0df247000000b0031d68b15a16mr6652037ywf.191.1657750089195; Wed, 13 Jul 2022 15:08:09 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Junxiao Shi <>
Date: Wed, 13 Jul 2022 18:07:32 -0400
Message-ID: <>
Content-Type: multipart/alternative; boundary="00000000000031e49b05e3b705c0"
X-ua-ms: gsuite
Archived-At: <>
Subject: Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-icntraceroute-06.txt
X-Mailman-Version: 2.1.39
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: Thu, 14 Jul 2022 19:07:44 -0000

Dear folks

I had a look at this document for the parts related to NDN.

In Section 5.1, the MustBeFresh element is referred to as a "selector".
Since 2018-Feb, the concept of "selector" is eliminated in NDN packet
MustBeFresh is usually referred to as "the MustBeFresh element".

In Section 5.2 Figure 9, "Path label TLV" is indented too much so that it's
very easy to miss.

In Section 5.2, "the value of the ContentType TLV is 0".
Since ContentType defaults to zero, you may as well omit this element

In Section 5.2 Figure 11, TrReplyCode TLV-VALUE is defined as 2*OCTET.
This value is actually a non negative integer, not a bit field or byte
NDN's convention for encoding such numbers is to use NonNegativeInteger,
instead of a fixed-length field.

In Section 7 first approach, "a forwarder at the border of the region,
where an Interest name becomes routable has to remove the LINK Object from
the incoming Interests".
This statement is outdated.
Since 2017-Jun, the Interest carries a ForwardingHint, not the LINK Object
(that is itself a Data packet).
Since 2021-Dec, the ForwardingHint is simply a sequence of (supposedly
routable) names; Lixia's opinion is that it should contain a single name,
although the spec still permits multiple names.

In Section 7 second approach, "To ensure that the generated replies will
reach the client, the border forwarder has also to rewrite the name of a
reply and prepend the routable prefix of the corresponding request".
In NDN packet format, the Data name is part of its security envelope.
When the border forwarder rewrites the name of a traceroute reply (that is
a Data packet), the signature becomes invalid.
You need to specify how to handle this situation.
Possible solutions are:

   - The border forwarder must first verify the original signature, then
   re-sign the packet. Implication: the client cannot verify the signature of
   the traceroute reply originator, but must trust the border router.
   - The traceroute reply originator must sign the packet as if it carries
   the routable prefix. Implication: the traceroute reply originator must know
   the routable prefix.
   - The client must strip the routable prefix before verifying the
   signature. Implication: the client must know the routable prefix.

In Appendix A, "Moreover, the client application might not wish to receive
replies due to CS hits. In NDN, the exclude filter selector can be used".
Since 2018-Feb, the concept of "selector" is eliminated in NDN packet
format, so that there's no exclude filter anymore.

Yours, Junxiao

On Tue, May 3, 2022 at 10:26 AM <> wrote:

>         Title           : ICN Traceroute Protocol Specification
>         Authors         : Spyridon Mastorakis
>                           Jim Gibson
>                           Ilya Moiseenko
>                           Ralph Droms
>                           Dave Oran
>         Filename        : draft-irtf-icnrg-icntraceroute-06.txt
>         Pages           : 20
>         Date            : 2022-05-03
> The IETF datatracker status page for this draft is: