[icnrg] IRSG review of draft-irtf-icnrg-pathsteering

"Brian Trammell (IETF)" <ietf@trammell.ch> Thu, 04 May 2023 12:53 UTC

Return-Path: <ietf@trammell.ch>
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 D2ED7C1519BE for <icnrg@ietfa.amsl.com>; Thu, 4 May 2023 05:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trammell.ch
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 VeoOqiVBpGXH for <icnrg@ietfa.amsl.com>; Thu, 4 May 2023 05:52:59 -0700 (PDT)
Received: from smtp-8faa.mail.infomaniak.ch (smtp-8faa.mail.infomaniak.ch [83.166.143.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 6B43CC13AE46 for <icnrg@irtf.org>; Thu, 4 May 2023 05:52:58 -0700 (PDT)
Received: from smtp-2-0000.mail.infomaniak.ch (unknown [10.5.36.107]) by smtp-3-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4QBtyb5JK5zMqJDT; Thu, 4 May 2023 14:52:55 +0200 (CEST)
Received: from unknown by smtp-2-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4QBtyb3F5GzMppq6; Thu, 4 May 2023 14:52:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=trammell.ch; s=20191114; t=1683204775; bh=dm9lq97oINYaZ4edilM7cLCE5VJ6P6wv5+jPAxqUoVw=; h=From:Subject:Date:To:From; b=uRYE4go147HVsmP5D3dGYWrdpEYXxBqu1Lj3PAZb2ErG3Fxgz93qX50wPBP9F2QJn hcUnSc0SnKGdZrep1wi8UOVLm3ZTs3Er1WTlZiW3g/rCMZWVULnIW7quHYKCiiQNoZ 9e9m8A70CamrOr51g92mRv9piXYwESIhJv67xHZQ=
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Message-Id: <F90A8A86-F599-4508-9A20-B39D3BF1839C@trammell.ch>
Date: Thu, 04 May 2023 14:52:44 +0200
To: Internet Research Steering Group <irsg@irtf.org>, icnrg@irtf.org
X-Mailer: Apple Mail (2.3731.500.231)
X-Infomaniak-Routing: alpha
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/0tAJW3euD6o31tUDfY0vZft_dZ0>
Subject: [icnrg] IRSG review of draft-irtf-icnrg-pathsteering
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.39
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: Thu, 04 May 2023 12:53:04 -0000

Greetings,

I’ve reviewed draft-irtf-icnrg-pathsteering for the IRSG.

IMO this document is ready for an IRSG ballot, with nits.

It describes a fairly straightforward way to add path awareness to (path-symmetric) CCNx (as an example of ICN approaches). It has somewhat less stringent security properties than other approaches in the path-aware networking space (e.g. SCION), but this seems perfectly reasonable in the ICN space. 

This document could be seen as “glue” between ICNRG and PANRG (note: I’m saying this with my PANRG chair hat off). At the risk of making an obligatory “you didn’t cite the reviewer” comment, which you can feel free to ignore, the document clearly answers the second and third questions (path discovery and selection, here called “steering”) posed by RFC 9217 (“Current Open Questions in Path-Aware Networking”) in an ICN context. I find it interesting that no mention was made of the first question (i.e., which properties of a path would a consumer use to make a decision about which paths to use?), aside from a mention in the abstract of potential uses. Given that the document essentially shows how to implement an externally specified design within CCNx, this is possibly reasonable, but might be worth addressing.

I have one editorial nit:

typo “in roder that the forwarders use that path” -> “in order”

Thanks, cheers,

Brian