[icnrg] RG adoption of draft-mastorakis-icnrg-icntraceroute

"Dirk Kutscher" <ietf@dkutscher.net> Wed, 19 February 2020 09:57 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 10E9A1208B0 for <icnrg@ietfa.amsl.com>; Wed, 19 Feb 2020 01:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 OQGS4-z-eC8t for <icnrg@ietfa.amsl.com>; Wed, 19 Feb 2020 01:57:06 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.130]) (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 B1E8F1208C5 for <icnrg@irtf.org>; Wed, 19 Feb 2020 01:57:05 -0800 (PST)
Received: from [139.13.88.219] ([139.13.88.219]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MryCb-1jpZ0s1BAb-00nwqj for <icnrg@irtf.org>; Wed, 19 Feb 2020 10:57:03 +0100
From: "Dirk Kutscher" <ietf@dkutscher.net>
To: ICNRG <icnrg@irtf.org>
Date: Wed, 19 Feb 2020 10:57:02 +0100
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <5F3D43C6-7CCE-43CC-84CA-C0B1E6F21390@dkutscher.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:oPEw0IuP6wvg51sj29IBJEirkOTpfvfRmEDgX7sLSFdyppr/hqT EpcFpTvfUqapXydjIv1IWPUh+ZaeENBF1t9cLDkognbxK9ConVzAsCVp4AilxiViTgqiuV7 VAclmnMTxsfOLqLtrsU834W8XmYRS6Dr6aIIDOx/a+9vrY8OygXb4dPvz1CCIZlcLoaD6Tp iinU0mN1sX0osWOwebZNg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:zLwNI/ZdW/Y=:EGndBbt4ifh8HCcCFEaMeA 4wDbvxdj16RbhZ8pFUxuUdDbxhG3sYnwPx/nRyvYIMoYPzKUB8lVJBIKGu4K+YvfHqavp3JHv vqko8ksAOk0qqH8FXZQ8ZLfLjChrc2ZvJpbwjUf19wKYE+0siy2a4aznqTtQpgrQYlqsjN0Yf e4a2nP/l8fcWzx7c1dyUDRBXnTL3yeaY4qraBvFLQ6Kb3QdHcV5aeo9oDiE5JNQt5nRZIT1NQ 0mKn37JPILdvBEnz5HFs+BgckyA+nY/dHYiZ2MiUt7wLKdjgph8+ZU9KmKN13wlf+nL0SifOL hUdnK6lqm1Yb1NPN7i12VD5R3eLqdQDZH5X22MsMbC7a51o1nGJfvCxD1jgT4ENUR7BJQ1Ds/ Nx2F8tFSSus8XsaF7frSXgsRF+HsUJ2bAcdKudVEGU49JeuG5sxlaxPCl+EDYek12niwjMoll 6AAv5AySgBRRiG1mD5F4ZLIv92y5q1vK72caSM6ca+hvjPGy7Ki00ka8aVatkIyo8eixQpBLz 2OcRKQM7MD8sPd39YoioybM7WiZu0XssNVw9Xzz5R4wrjrn/xfIk+zP6nOpvIZtCs1+HLNYza vNvxWNFdIeelwGPG3ZGRNQQB92aRk3uwdtgkMOfk2WtexOXWM4dWoEbb5PkwIZ8DhDp50dKMF K/JcXjC8wDzT2fHstyq8C93iEap9tWLHFzGixIgyVixVxxru9JfNhqfK3rxFgcTxNMOmSxlVk SoTpUIllq9UHQL8V2Ves/wpTkS+rs3widuYh1lb4bJXJ2tSAltvYTlxEwz04oc7gv6h9AY8K6 9NYVMydJbBtLWCK731y3fJjRlw3Z8JYte6HCPxXgkF1n+mobdQkz3WClc9PASfKJKMKCYTQ
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/oNlc1t2M2lLjMiSaCQX_fOZEjlg>
Subject: [icnrg] RG adoption of draft-mastorakis-icnrg-icntraceroute
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: Wed, 19 Feb 2020 09:57:17 -0000

Hello ICNRG,

The ICN trace route specification has been around for some time. It’s 
one of the useful (potentially) needed management/debugging tools for 
ICN networks, so the chairs think there is merit in publishing the 
document as an Experimental RFC at some point.

At this time, we would like to ask the group for feedback on the 
proposal of adopting this draft as a RG item.

Just as a reminder, RG adoption means that the specification will be 
progressed as an activity within ICNRG and that the authors would edit 
the document on behalf of the RG.

Adoption in an IRTF RG context does not mean that this is the only 
(ICNRG-endorsed…) way of (here:) ascertaining path characteristics in 
ICN . There could be other proposal that might be adopted as well (if 
perceived useful).

The draft:
https://datatracker.ietf.org/doc/draft-mastorakis-icnrg-icntraceroute/

Abstract:
This document presents the design of an ICN Traceroute protocol.
This includes the operations both on the client and the forwarder side.

Best regards,
Dirk and Börje (as managing co-chairs)