From nobody Fri Jul 15 11:50:03 2022 Return-Path: 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 8B272C16ECD3 for ; Fri, 15 Jul 2022 11:50:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.908 X-Spam-Level: X-Spam-Status: No, score=-1.908 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] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=arizona-edu.20210112.gappssmtp.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bKgRwcdExF1r for ; Fri, 15 Jul 2022 11:50:00 -0700 (PDT) Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (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 ietfa.amsl.com (Postfix) with ESMTPS id A70C0C16ECB2 for ; Fri, 15 Jul 2022 11:49:59 -0700 (PDT) Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-31c9b70c382so55419087b3.6 for ; Fri, 15 Jul 2022 11:49:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arizona-edu.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=OqSk7H5mGs7YIfZ/18llWjyOF+34hLfwGrpxtHGNmaU=; b=kM2FHUXARgELFQDtUlMsV41V4UeF1aIb5yi6OD027jUWgvVeONW8umxrh90VEibZZ6 VNcU4vXWbZBvUei5nA58552W3oim72rZxrOPnrAMQLtgwaVrOGRzeilPrQy+JQUJRRWE cpm6IMiIsogJik+Npjh1tbKY5In5LZFER7z0LhMk7PWO69LCyPSN3SKxQGa8v/5PbM6o +mosj639BAcnT6Dj4/BR59N8F9AoLV8M33FnEKyXZyhD707wdy7ggkcYQsYCwPUhiWgb XhCkhCfJNpGNepDTbk4IihfkChegHoDcMGcHoX8UjBEyWa+LXS32Kc6eKcJ1AshNWXYZ vJnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=OqSk7H5mGs7YIfZ/18llWjyOF+34hLfwGrpxtHGNmaU=; b=wBcJDOq81xmzjzbgLTa6geZn8hXWJsSQDIsnDa00RXaZc8X4OpMmr28VZIbBrRzQiU UPvgF/y7/Z30DUxhOr0+q6QqJO63dv/+dUCjwu+fHySQfJL9T9ewMxk/z1BXxJMZLGDS YuVhSBQVla/oO087mYcvAFqwpZAr5hBRFt4lFwKvnC7PVCnneN6madMcc7UraR4ZSzZo 4SQESOn7V03NdYu0peLDC2Izbfc3t22viJOYN5J//UpG7j0O9VKnGjNh2FWzqLpGfb2n vnYyNOJ0S2dOPBKB77ull9sLZ//LmUezxhmBYQgSeRxXmOIsHc4bLuHo5zM6hXPq03vq tREA== X-Gm-Message-State: AJIora9qo2H/yFul/lyzixN2+vcZx4kDP6nyKzRIY1w2nFFW1RrN1Irg se1QNgmGTKhv1ykc8fOWdNLx4AlZwJ+X7vCOaL2SM/EeKgXg+Seea4SLnlQTLyfwGiKzliZy+UY X5xAqY+Uud41XHD+zXiqwQQ== X-Google-Smtp-Source: AGRyM1t6Y5N5XeYyYnCY+LK6TvrBN8Gg7j4FJe8bLvUcQT35Pciehf0e+0v0jpEiq9tkZ7ktcPuP/TFx2CYihV4Jf3o= X-Received: by 2002:a81:b810:0:b0:31c:8aa6:2e4b with SMTP id v16-20020a81b810000000b0031c8aa62e4bmr17840041ywe.216.1657910998637; Fri, 15 Jul 2022 11:49:58 -0700 (PDT) MIME-Version: 1.0 References: <165158805463.21170.251866085927208698@ietfa.amsl.com> In-Reply-To: <165158805463.21170.251866085927208698@ietfa.amsl.com> From: Junxiao Shi Date: Fri, 15 Jul 2022 14:49:22 -0400 Message-ID: To: icnrg@irtf.org Content-Type: multipart/alternative; boundary="00000000000025126e05e3dc7c3a" X-ua-ms: gsuite Archived-At: Subject: Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-icnping-06.txt X-BeenThere: icnrg@irtf.org 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: Fri, 15 Jul 2022 18:50:01 -0000 --00000000000025126e05e3dc7c3a Content-Type: text/plain; charset="UTF-8" Dear folks The 2022-07-15 NFD call discussed this ICN Ping protocol. We found a new issue regarding the placement of Path label TLV in Interests. Section 5.1 says: "The "ApplicationParameters" field of the Request contains a Path label TLV as specified in [I-D.oran-icnrg-pathsteering]." According to the NDN protocol, when ApplicationParameters is present, the Interest name must have a ParametersSha256DigestComponent whose value is the SHA256 digest of ApplicationParameters and any other elements after it. In draft-oran-icnrg-pathsteering-06, section 3.1 defines a procedure of encrypting and decrypting Path label TLV at certain forwarders. This permits a forwarder to overwrite the Path label TLV inside the ApplicationParameters element. To conform to the NDN protocol, the ParametersSha256DigestComponent TLV-VALUE must be re-computed to reflect the updated ApplicationParameters. This in turn changes the Interest name. It causes significant complication in PIT matching, because the incoming Interest and outgoing Interest would have different names. Participants of the 2022-07-15 NFD call believed that the Path label TLV should not be placed in the ApplicationParameters field. Instead, it could be placed in either: - NDNLPv2 header - middle of an Interest packet, somewhere after ForwardingHint and before ApplicationParameters, where it is not covered by ParametersSha256DigestComponent and does not require the presence of ParametersSha256DigestComponent Apart from this, I also noticed that the InterestLifetime field is mentioned in Appendix A but missing in Figure 8. Yours, Junxiao On Tue, May 3, 2022 at 10:28 AM wrote: > > Title : ICN Ping Protocol Specification > Authors : Spyridon Mastorakis > Jim Gibson > Ilya Moiseenko > Ralph Droms > Dave Oran > Filename : draft-irtf-icnrg-icnping-06.txt > Pages : 20 > Date : 2022-05-03 > > > --00000000000025126e05e3dc7c3a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear folks

The 2022-07-15 NF= D call discussed this ICN Ping protocol.
We found a new issue reg= arding the placement of Path label TLV in Interests.

Section 5.1 says: "The "ApplicationParameters" field of t= he Request contains a Path label TLV as specified in [I-D.oran-icnrg-pathst= eering]."
According to the NDN protocol, when=C2=A0Applicati= onParameters is present, the Interest name must have a=C2=A0ParametersSha25= 6DigestComponent whose value is the SHA256 digest of ApplicationParameters = and any other elements after it.

In=C2=A0draft-ora= n-icnrg-pathsteering-06, section 3.1 defines a procedure of encrypting and = decrypting Path label TLV at certain forwarders.
This permits a f= orwarder to overwrite the Path label TLV inside the ApplicationParameters e= lement.
To conform to the NDN protocol, the=C2=A0ParametersSha256= DigestComponent TLV-VALUE must be re-computed to reflect the updated Applic= ationParameters.

This in turn changes the Interest= name.
It causes significant complication in PIT matching, be= cause the incoming Interest and outgoing Interest would have different name= s.

Participants of the 2022-07-15 NFD call believe= d that the Path label TLV should not be placed in the ApplicationParameters= field.
Instead, it could be placed in either:
  • = NDNLPv2 header
  • middle of an Interest packet, somewhere after Forwar= dingHint and before ApplicationParameters, where it is not covered by Param= etersSha256DigestComponent and does not require the presence of=C2=A0Parame= tersSha256DigestComponent

Apart from thi= s, I also noticed that the InterestLifetime field is mentioned in Appendix= =C2=A0A but missing in Figure 8.

Yours, Junxiao
On = Tue, May 3, 2022 at 10:28 AM <internet-drafts@ietf.org> wrote:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:= ICN Ping Protocol Specification
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Spyr= idon Mastorakis
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Jim Gibson
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Ilya Moiseenko
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Ralph Droms
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 Dave Oran
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-irt= f-icnrg-icnping-06.txt
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:= 20
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 := 2022-05-03


--00000000000025126e05e3dc7c3a--