IETF Logo Mail Archive

Re: [icnrg] Reminder: ICNRG Last Call on Ping and Traceroute Drafts

Dirk Kutscher <ietf@dkutscher.net> Mon, 10 January 2022 20:52 UTC

Return-Path: <ietf@dkutscher.net>
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 EB38F3A08D0 for <icnrg@ietfa.amsl.com>; Mon, 10 Jan 2022 12:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lv24Ni_avkkb for <icnrg@ietfa.amsl.com>; Mon, 10 Jan 2022 12:52:18 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (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 44FF53A08CD for <icnrg@irtf.org>; Mon, 10 Jan 2022 12:52:17 -0800 (PST)
Received: from [192.168.1.50] ([95.89.114.110]) by mrelayeu.kundenserver.de (mreue107 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MIxqu-1mnq4720cc-00KNUg; Mon, 10 Jan 2022 21:51:57 +0100
From: Dirk Kutscher <ietf@dkutscher.net>
To: "David R. Oran" <daveoran@orandom.net>
Cc: ICNRG <icnrg@irtf.org>
Date: Mon, 10 Jan 2022 21:51:54 +0100
X-Mailer: MailMate (1.14r5852)
Message-ID: <850E8734-2DC0-4C0A-A371-DF8245A6B909@dkutscher.net>
In-Reply-To: <7E304C46-37B9-4B79-AE7D-A2CFE1A3E106@orandom.net>
References: <BFBDF3D5-F65A-41D0-8D35-36FBE1FDC37A@orandom.net> <7E304C46-37B9-4B79-AE7D-A2CFE1A3E106@orandom.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_CE3BEF5B-DB5E-43A1-9F7E-803263F00E66_="; micalg="sha-256"; protocol="application/pkcs7-signature"
X-Provags-ID: V03:K1:g/HzPFmpxFCtYlZCihTYiZFAiMqJooyRK1fk+tPa50BqwrAPpBE mkAyOMQM3fl6400lyAuNF3I/YGz7Fi5oiuTTgtXWJ0tSRzSK2iFemvZAog5CFKdKMAhx4lr DOeQ7Tfqb4fU1tjGnWH87V0XdjnwQUIeHZ8ww1eJvvUNY6V8Dl0GjIisHQh2hVDgJZeZWVG xHElj2FwMpXiC9sYtuWmw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:ljew7hDV61M=:OyGfUhNjuxKFR6FsHeS03z bzCQft4rrkVEXVI6eY1ZUvWcXsnGCmjrp4CH4S5JDbq2Tia84YtqB2uF4IICE6LpUkXhPyZJP hA7mWobMDymoUzNVK298rZHSAHll6cPfZ+lkjawxpxNf/kpHV9VaT+UPpL/Bzjg/ifbOuPyL/ 48YW291a37Oh8k3moMxd8CtVLGMePEG32bLTnpYz8BhXNmBfIk405I1jVmLZAvzXV0zH+L1ny xBtX/u8+h/yQPRVmNO77dUcpiLrsJu6084FBLdHtUmfadcZx8PbtwRl5ADdBWXTG7rZ2sto1n agvuH3uIYOQYqja3iFaRiknm3+jZJiUOh2wtOKL6xOSwvrYjCLUMHz0I9sUSjkdCErIAym2Ow joRBKeQ4m+K9uJmrgmBQMFz126llWxjSxi4lCg2g9ibVZ9w93u57kCJYd5DQe5947mKaguwdi h3oD3rsFkAd66pTjZ6ATsf3WjgCq9HEhSUDj87bElgNSJYcWvE+RVXabK1tkJnc9Pyn4Jht9B hwYb24JUPAKmpTmyIDsiQesnsT7Eag+C+j0n/dAV4HY4qTBuYQGmY1KTEpLG9SiEjqEotw0QE 3/NhDsGBK+Q8ud7WJ2CVExvJfzyhRaBQyA2496cdiLJkPVbh0xOCFYZ1c8mK+XDb6HCyeabpy lLQY1bE6yZ7JUOWiWC6WTHv37woS8qbXKPMTPTqJl9ZB6l6+T+W32z6uoAFxiNqlTNTk=
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/ulGpqKzz51EhUoqVjHCy83pZWsE>
Subject: Re: [icnrg] Reminder: ICNRG Last Call on Ping and Traceroute Drafts
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: Mon, 10 Jan 2022 20:52:23 -0000

Thanks – some comments on both drafts:

The specs look complete to me – maybe one optimization for clarity: when describing the overall operation before the sections with the packet formats, would it make sense to explicitly say that this is relying on path steering (as a mechanism)?

Currently, we say "To this end, it is important to have a mechanism to steer consecutive ping echo requests for the same name towards an individual path. Such a capability was initially published in [PATHSTEERING]...".

Maybe just be more explicit about path steering?

Currently, path steering is also not listed as a normative reference – is that on purpose?

Dirk






On 5 Jan 2022, at 17:40, David R. Oran wrote:

>> We are issuing **ICNRG last call** on our other two instrumentation drafts, Ping and Traceroute. These can be found in the usual data tracker list, at
>>
>> https://datatracker.ietf.org/doc/draft-irtf-icnrg-icnping/
>> and
>> https://datatracker.ietf.org/doc/draft-irtf-icnrg-icntraceroute/
>>
>> Please review these in full and send comments to the mailing list.
>>
>> Given the holidays, we have an extended last call period, which will close on **Friday January 14, 2022**.
>>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg

v2.23.0 | Report a Bug | By Email