[icnrg] IRTF Chair review of draft-irtf-icnrg-icnping-05

Colin Perkins <csp@csperkins.org> Fri, 22 April 2022 15:57 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 007883A1769 for <icnrg@ietfa.amsl.com>; Fri, 22 Apr 2022 08:57:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Status: No, score=-2.105 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_BLOCKED=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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id l5wKFuICf8kN for <icnrg@ietfa.amsl.com>; Fri, 22 Apr 2022 08:57:41 -0700 (PDT)
Received: from mx1.mythic-beasts.com (mx1.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (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 905C93A176A for <icnrg@irtf.org>; Fri, 22 Apr 2022 08:57:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=ErVVuL8a2yAw5IuB/UzPJ59SfTPtDzJxD4VzqtGmMeg=; b=k53B0Ahrv+iIp9SUvQxTr4Tp7c TuVI6cjcY36vfsxF3DbafgDSDsYfjZYAqJVoxuaii7UAmcTuryxj9XNV2EZdoHzbIT8hh03MEWJSM 7hZ4ZPn0tm1WSV0M1j781cxUcF6+crGDU+HAfJ2w6YKgAn9WYcVdhipOsyfcTV2vPoPNjt9m/MoXs TMdeyvfPxlfhj/84czv7l1+O6PCdFC+IewHguo55kY6nYbtGbMyDTpzLIiTlPofQ8cNaQ+Za1pOFP xsJDqjQKeydocOb74yLeusVzag+S239C+9UoisYT/30xaX7MFPaqTm2aGZou/3yiG07mnP/mYW2bI 1KcqI2EA==;
Received: from [] (port=32855 helo=[]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1nhvf8-00062t-Ce; Fri, 22 Apr 2022 16:57:39 +0100
From: Colin Perkins <csp@csperkins.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Message-Id: <83997A51-A16E-4303-A203-50C42D6AAF4F@csperkins.org>
Date: Fri, 22 Apr 2022 16:57:33 +0100
Cc: icnrg@irtf.org
To: draft-irtf-icnrg-icnping@ietf.org
X-Mailer: Apple Mail (2.3445.104.21)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/pc5zSNzD0TAGye9gJfJ82bPG_Wo>
Subject: [icnrg] IRTF Chair review of draft-irtf-icnrg-icnping-05
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: Fri, 22 Apr 2022 15:57:48 -0000

The ICNRG chairs have requested that draft-irtf-icnrg-icnping-05 be published as an RFC on the IRTF stream. The IRTF publication process is described in RFC 5743, and comprises a review by the IRSG to ensure technical and editorial quality, followed by a check by the IESG to ensure the work does not conflict with IETF standards activities.

As IRTF Chair, I perform an initial review of all drafts submitted for publication on the IRTF stream before sending them for detailed review by the IRSG. This note provides my review comments, for discussion.

Authors, please can you also respond to this message to confirm that any needed IPR disclosures, as described on https://irtf.org/policies/ipr, have been made? 

* Ready with nits

RFC 5743 compliance: 
* The draft does not follow the guidelines in RFC 5743


Thank you for preparing this draft. The work looks to be in good shape, but I have a number of minor procedural issues to consider.

1. The draft does not appear to follow the guidelines in RFC 5743 Section 2.1. Please review and add the required statements to the Abstract and Introduction.

2. There are various message types that need to be registered, but the draft doesn’t contain an IANA Considerations section giving these registrations. Is this needed, or have the registrations been made elsewhere?

3. The draft is targeting publication as an experimental RFC, but doesn’t include discussion to explain why it’s experimental. Does it need a couple of sentences in the Introduction to highlight that this is a management and debugging tool for the experimental deployments of ICN protocols, or similar?

Colin Perkins
IRTF Chair

Colin Perkins