Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-icnping-03.txt
Spyridon Mastorakis <smastorakis@unomaha.edu> Sun, 06 March 2022 23:52 UTC
Return-Path: <prvs=006449a59c=smastorakis@unomaha.edu>
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 41A6C3A0E58 for <icnrg@ietfa.amsl.com>; Sun, 6 Mar 2022 15:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=unomaha.edu header.b=ArEoPmny; dkim=pass (1024-bit key) header.d=unomaha.edu header.b=KXlON1Oz
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 2CfWfF71Ld9n for <icnrg@ietfa.amsl.com>; Sun, 6 Mar 2022 15:52:49 -0800 (PST)
Received: from mx0b-00246402.pphosted.com (mx0b-00246402.pphosted.com [148.163.143.147]) (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 A03CE3A0E57 for <icnrg@irtf.org>; Sun, 6 Mar 2022 15:52:49 -0800 (PST)
Received: from pps.filterd (m0136271.ppops.net [127.0.0.1]) by mx0a-00246402.pphosted.com (8.16.1.2/8.16.1.2) with ESMTP id 226At5Qg009483; Sun, 6 Mar 2022 17:52:46 -0600
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unomaha.edu; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=pppod; bh=y3rKR4j9hGbJ+APIkng+8lkSe/GYuWLJRnCvZ1AryaU=; b=ArEoPmnySb2FNJ6tb0nOmrd3EIHH/vjd9OaHF/Ksrpl0Z7fgY00xLklv0ZmD4ksZO3pT BB608UzZKg5nKpPJCWQfsqMJ9C3uG1unBp6mjHkOrYhPR2KGsJ6Tzh7/UHkEoPw/0HWU O7BSZb07S824U0Btm6kx56XfuzHCCob9KK8eIR4t+tQIk1ZZg5JqBR2bw5VZI4CrLT9l RQKxRoJHNIrsUY5ncQNvxPdxlqN0lcs9t1/RawRsRugCU9JxNZPrv0K23NAd6K0XVXEA CUDSwy06Tcx7t7pvjOWBqdFf7GmsFT96gPPmsiGEe7/srU3Gb8KA1893YbLlBp5ReIXm 5A==
Received: from nam12-mw2-obe.outbound.protection.outlook.com (mail-mw2nam12lp2046.outbound.protection.outlook.com [104.47.66.46]) by mx0a-00246402.pphosted.com (PPS) with ESMTPS id 3emr94j15u-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 06 Mar 2022 17:52:46 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I5yOB2+3QR2oPTusY7Lx3f3lG4TKfcY78y391iPEiyl606krd3VjXWuoiidrIlPW6u9TCiXqHyy3qhXgG91EWwkSllZecK+KsvLHDMcZmZ5nOQFnVdDI1c0FWGGL3xRmOIsLZR/80WUrGrQl/FhUo27uzD1UszCjkpbdQNKHt65F9BA4QvX1+1GadlPHkafHG88G7quDipR8vy7RRSqUZ53NLkz+4+UhVTXoTcPrxk3Wfj1WA+zpGYzDOqK2aKva6CO541BaR+1XiPfSOe1ILImYANwOAJ7pCzA1ZQrDcbpe/QS9SfkBFJuE5DJQNqU6TWXCSjH64YQ3i263Ndc/GA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=y3rKR4j9hGbJ+APIkng+8lkSe/GYuWLJRnCvZ1AryaU=; b=FG2jKzaQO+REj829tbgvBA36Z0TXKtmbrFDSh4IE5slzJ848VlqppEUrhBlWhtx9k2pa7K+yzlGXKZbvfpp+UzPWaSRBKa+XJ7rlzKA0NDu4/6G9w7zO/AHCV9rI+pyEdMhkg/UxhUvAdt75JZ06JjGHNCR7UwEeKDgk6bkJ/NqrEebQk8FT5eT9MAQ/RUkOCOFyMsIWHaNUCxA5rPZJqCHDzba+DRIQv2v/u7rWOf3N+uT3hCMl7373hRwIMRKI404/PXDpzGjgUJRRPoc3Hxw1U7APC7BiYNhXlYm0zMg5eWLk0H8SYIi23KcRrtdKSzgBctHeAd/Pl9earW2Saw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=unomaha.edu; dmarc=pass action=none header.from=unomaha.edu; dkim=pass header.d=unomaha.edu; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unomaha.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=y3rKR4j9hGbJ+APIkng+8lkSe/GYuWLJRnCvZ1AryaU=; b=KXlON1OzZYaBm2FajbVa0ukghaVOQwMyPMBGbHeuSXu8v+icqYgBEc3WEUVooExBONYgcUpF2Aupl1rWebpOXxZp1X5Va+NlbhCJXEaGJUAv3nhSnOMk6/MSlPGtuahzgFNNeJtT9mxG1A3kVgkRaW4J2TuftkkkjA3m4I6Rbms=
Received: from BYAPR07MB5960.namprd07.prod.outlook.com (2603:10b6:a03:134::10) by MN2PR07MB7199.namprd07.prod.outlook.com (2603:10b6:208:1dd::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5038.14; Sun, 6 Mar 2022 23:52:40 +0000
Received: from BYAPR07MB5960.namprd07.prod.outlook.com ([fe80::7cc4:5885:3e66:751]) by BYAPR07MB5960.namprd07.prod.outlook.com ([fe80::7cc4:5885:3e66:751%3]) with mapi id 15.20.5038.026; Sun, 6 Mar 2022 23:52:40 +0000
From: Spyridon Mastorakis <smastorakis@unomaha.edu>
To: Junxiao Shi <shijunxiao@email.arizona.edu>
CC: "icnrg@irtf.org" <icnrg@irtf.org>
Thread-Topic: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-icnping-03.txt
Thread-Index: AQHX8DJNVgxsgJw5dUmPYzyEhFff5KyziiGA
Date: Sun, 06 Mar 2022 23:52:40 +0000
Message-ID: <2D588ADD-F5F2-47F5-9C7C-A15113395CF9@unomaha.edu>
References: <163519291458.16034.1879568644895811832@ietfa.amsl.com> <CAOFH+Oaq-it9CV3T82Vm9uHVWGyc4yzu8_qTMwR3WzVtdE13FQ@mail.gmail.com>
In-Reply-To: <CAOFH+Oaq-it9CV3T82Vm9uHVWGyc4yzu8_qTMwR3WzVtdE13FQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3693.60.0.1.1)
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8abb5910-d59b-4b38-e7db-08d9ffcc6686
x-ms-traffictypediagnostic: MN2PR07MB7199:EE_
x-microsoft-antispam-prvs: <MN2PR07MB7199194BDFD3C3A7FB3568CDA4079@MN2PR07MB7199.namprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +LgWzOc9xKIidzPSHWZohqojfR070sPp6DfYVkxALd9jKENikYjQRTL0kkyXhokrKYrdcGo0aht2W2jzZssVKN85G/TvCIh7NET5eNG8sRIJ+mU+WHh7F5NvNyQ5PdMQ5aieQVHQ7Ir2q+T+ee9CqQy7/KrH+IZ7OUCngYbnbEgJ8t4WtAEM+fRUNAX5U8ChTBwtV3Cbglb1hxXRliRU70P90YPYk6n547fSeBE2WjOjS/Ka31JgBBAjggPf5hEWmopfjXnNKcwvVvBMLYZ2wBxD2Os5IEH/hYCTyLrNBn6h5jHaut8rWM5wRzKTcgRfZjWxJLnyuaNKM1lVozkprOV4Ypt4IC3uM5il/pEzecnE0vEx37JP/i9vcbPrVMDDphNZHrSeStTIZ76FfqQeE0SVO21i2VaQ0Ec+1dQcS4ddQfYFGuTumZmLOimUlrEVgDAVVB1LubcpyyK3vAkseM1yhAryMBVuQ7nZKNmWpWG6cBHIs3/BZ/OpmXw7mRpVAH4ChDazBPJsFY4Zcz568i38jFskrCHMvzPi7cYhAG/XLrIFtUB3atYMnRM/dEBsWTCraRSV/qGsnjPiD8PDBOUoaQp0NPUkhVCd76qf0nUt7ZE5JZZq4zAWTyKaXMYmcLxzDFeoF0IZa3SZZhQuU0jZlbfZUOi5mr9ZicQma04IScPo3OqrAtnCcwTSTEZ7OVgcX+pW0uvZeCw4LddEdBY3dVciVVBx0B7qgi8GBcgzaN56dvNlB+FgJIr3yUak5XzFmnmj/+t9MzQd0hhulWVKb6Ua3lZ1objLnP8vcwy2f62/ebNF1BpGiLX0FjF4
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR07MB5960.namprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230001)(4636009)(366004)(6486002)(33656002)(122000001)(786003)(316002)(19627235002)(6916009)(91956017)(66446008)(66476007)(64756008)(8676002)(83380400001)(966005)(76116006)(66946007)(66556008)(4326008)(86362001)(75432002)(38070700005)(166002)(71200400001)(36756003)(26005)(186003)(508600001)(4001150100001)(38100700002)(6506007)(2906002)(53546011)(5660300002)(66574015)(8936002)(6512007)(2616005)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: 5IOfeckswIosVEZslC0tz60rxWKNw2RR41DElIreFRGp4PeDzHX+DAloxgxlb87LFou2tTJ9aFjrdow+2ju7Cq89aAfZTRk5Y7rRpZjznbsO3wuoEVlf89WmMDa+go6XWaGiGS0RZOHz+yp6lymaHfIgmPjfGnFhnoBY0pnLnRP5knpwimCkiAARfbk21evfdg97zMzpETIAYFa0NbTxzcLMl6xmCwKKX5r5vm2g60/Aeh+UD3Midj9F9y/YgbvBj/V5q/EI/xLBT1kdhRrpCqcWnO/6TnFmVRA4+bZeaf7UH60KTNa2P3PHlKcIdt/nhy6I1sGKa199ImTO5QupuEz/HxbPrHWzc2QOgLDFPZXTmblWJeDpUDbLElm5Kc2BwYxEL/BphaiY0eQ+i+ItkugcpPjFXeYfYEdPgX2v4DMA94kxahwuFe72Le/kHCgH34ENYH+7wZXH5TNfoHgaAJkWicMPMsH/UExm7qHSyNGqw6pdWgX9IXDU4OEQOrEueBihQKK59DmGLwFWHsQpC60vWn6Bh3A0n/+TyKWvpYCRVFRQujCVnwUcPTDrNYk1EYJYqI5+ytkFnNXffBS/qmsVc3Ec3AEfrvpyFYfbl1YZp5K8+LoYgQwjDl8Fkh+4MRbOmCrllmLbVud2bURBd+L3FdZi/jsmC2+q/F20oSRxE6cO+CSadbuBfXOReKPkKnOk+MAcK4zJngIZqSNz1+le4alDa4Qrv/ZNiO+E7zZWV44l1Bm0drSWZIzteqmgdl8c6qrkiI+m57qWBpqQ1zajfjidavr1zn7baAcB4CUGs+AuHgDeH3QTMfeXISxLQw6oXHeSq/ahqbXVoWlH5lVETs/4Vx+1J3FAdtLBP59JOPmAiq0VRhTnmCxKC1ljvOEr4iTRivwOE2v/Ic1BNnqLXD1ODHrEoeMiX1o80lt/dmeGmCTE0jKQ4Z91KxoBIJDXWwCyinqLVkBCROPA7ISSLJEB3OCpugAOAP9H27rEAS5KzJJT3bvFncKDwO24B7wAS9F9/IP7clI4eNRiXAfzFMgiwZ5o9HSpdyEDg86/O7q6hrJkMSwnO7STEmEp752oI7Uuyv2lbHmTN/BGZnfO8WZjeDFVbdeK7b+bZfNrMIdnH/nYrj/xz8sFsLaOr07vdSIteI94dv4g58pwGhlWgQHjECh9eRs5d5y7KDwzIaQ7eRvugr4g7XEtcxHLwn/TpJYxqE5Gk/Qoq+CnLtQCaTYOh6OTNVDrmIRtGGGtHGHAvMDNbOaI7MLyNAv4wY5/74a29Ft9YfM53fZa0rabjR1MI4bTH/aWj6FoMo5NfKMFgPACimXPr22XPIJC4suB3YlZ/jcAflx5jk5VRrM2OCubAd1CqzgiIG4J7P2JbUlFOtvAhMgkNslludN8y6g8LfzH0fNkKvfVtlJYhXWwDIMgNDnefQedBkOkeJAusbQ/doq+ql/TeyXgkwyOk2tufgLXTpVAuXBzboIEhSRgHC+TRAnxTNJazpx73lVphj6NnKpn8qC8FJQmLotyxZJQ9bvvmtlzrJCjhpVoQ2IwtLEfEWfi1jh7N33ZNpTAHUqHozkXLut32vHXiTAtftQPUn2xCc6hFKtQwf0uwdzp6OR2hcof0V8zJCgM3dk=
Content-Type: multipart/alternative; boundary="_000_2D588ADDF5F247F59C7CA15113395CF9unomahaedu_"
MIME-Version: 1.0
X-OriginatorOrg: unomaha.edu
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR07MB5960.namprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8abb5910-d59b-4b38-e7db-08d9ffcc6686
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Mar 2022 23:52:40.7539 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f1f4be86-d048-47e8-aa26-15b01dcdb13d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2XOMvquknPXNu4OhytatHNUBqmy3lQ6cYzLmmpimOXg16jvPZ4Q8CK6oN7Q8pKeQVeH2AXZMQUxJbwei7D5ttA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR07MB7199
X-Proofpoint-GUID: vxO-ExZlVSo-7noO-7P8y7q1Tj0qpUJP
X-Proofpoint-ORIG-GUID: vxO-ExZlVSo-7noO-7P8y7q1Tj0qpUJP
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1011 spamscore=0 adultscore=0 suspectscore=0 impostorscore=0 malwarescore=0 mlxscore=0 lowpriorityscore=0 priorityscore=1501 mlxlogscore=999 phishscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2203060160
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/EElVMgnJCDMsiBULqBKNeYu7Ymc>
Subject: Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-icnping-03.txt
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: Sun, 06 Mar 2022 23:52:57 -0000
Dear Junxiao, Thank you for your comments. We have addressed them in the updated versions of our drafts that we just uploaded. Please see below for more details: On Dec 13, 2021, at 9:00 AM, Junxiao Shi <shijunxiao@email.arizona.edu<mailto:shijunxiao@email.arizona.edu>> wrote: Non-NU Email ________________________________ Dear folks I had a look at the NDN encoding for ICN Ping Protocol rev03. It seems that the protocol partially assumes NDN packet format v0.2, and is incompatible with the current NDN packet format. As of 2019-May<https://urldefense.com/v3/__https://redmine.named-data.net/issues/4853__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWKR6IgjQ$>, the NDN packet encoding is written with IETF ABNF syntax. However, ICN Ping still specifies its encoding with W3C EBNF syntax, which could lead to confusion. Fixed. We converted the packet encoding to the ETF ABNF syntax. Section 5.1 defines that the Name of a Ping Echo Request should have a "ping" suffix, so that it can be identified as a Ping Echo Request. Since NDN packet format v0.3, name components that require special processing should use a KeywordNameComponent (TLV-TYPE 0x20) rather than a GenericNameComponent. This helps to avoid conflicts with existing protocols, such as the ndnping application<https://urldefense.com/v3/__https://github.com/named-data/ndn-tools/tree/585e18a5e3be4d2d33053dbad2223e5d986d65fa/tools/ping*ndnping-protocol__;Iw!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWF1AnGgy$>. Fixed. Section 5.1 defines Ping Echo Request to be an Interest with MustBeFresh "selector". NDN packet format has eliminated the concept of selectors. It's called "MustBeFresh element" now. Fixed. Section 5.1 mentions a "Parameters" element. It's been renamed to "ApplicationParameters". Also, the inclusion of an ApplicationParameters requires the inclusion of a ParametersSha256DigestComponent somewhere in the Name (it does not have to be the last component). It's necessary to specify where this component should be placed. We have addressed this comment in Section 5.1. The Parameters element is meant to contain PathSteering TLV. As suggested below, it may make sense to move it to the NDNLPv2 header. Section 5.2 defines Ping Echo Reply to be a Data packet with ContentType=0 and FreshnessPeriod=0. Since ContentType defaults to 0 and FreshnessPeriod defaults to 0, neither field is necessary. Importantly, the NDN protocol specifies<https://urldefense.com/v3/__https://named-data.net/doc/NDN-packet-spec/current/data.html*freshnessperiod__;Iw!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWGIoTdsr$>: If the Data does not have a FreshnessPeriod or if it has a FreshnessPeriod equal to zero, it MUST be immediately marked “non-fresh”. If an Interest contains MustBeFresh element, a node MUST NOT return “non-fresh” Data in response to this Interest. This rule applies to not only the Content Store, but also the forwarding pipelines. Based on this rule, the Ping Echo Reply packet does not satisfy the Ping Echo Request packet, making the ICN Ping incompatible with the current NDN packet format. We aim to avoid fetching cached responses from the network (unless a request’s base name matches the name of a content object in the CS of a forwarder and the client is ok with receiving a cached response). To do that in the first place, the operation of a forwarder needs to be different than how NFD works right now. So we do not think this is an issue with the packet format per se, but rather the operation of the forwarder, which needs to be extended/modified to handle ping and traceroute traffic. Section 5.2 inserts a "PathSteering TLV" in the Data packet, which appears before the Name element. The TLV evolvability guidelines of the NDN protocol does not permit adding new elements before the Name element. New elements should be added later in the packet; to exclude an element from the security envelope, it should appear after the SignatureValue element. Good point. We have moved the PathSteering TLV after the Signature TLV. In the case of PathSteering TLV that "might be modified in a hop-by-hop fashion", it does not belong in the network layer, but should be added as a link layer header in NDNLPv2 or another link layer protocol. The "PathSteering TLV" cites draft-oran-icnrg-pathsteering, but that document only defines a "Path label TLV". Its TLV-TYPE number assignment is 0x09, but that number is a "critical" TLV-TYPE number that would cause a forwarder that does not understand this feature to drop the packet; this choice needs justification. Moreover, 0x09 is marked as reserved<https://urldefense.com/v3/__https://named-data.net/doc/NDN-packet-spec/current/types.html__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWM33PpJJ$> because it conflicts with the former Selectors element in NDN packet format v0.2, so that you may need to choose a different number. You can then propose a change<https://urldefense.com/v3/__https://gerrit.named-data.net/admin/repos/NDN-TLV__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWA18J1X7$> to reserve the number in NDN network layer protocol or edit this page<https://urldefense.com/v3/__https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWIEfRn16$> to reserve the number in NDNLPv2. To some extent, this sounds like an open question to us (i.e., whether PathSteering TLV should be a part of the encoding of the base NDN protocol or should be included in NDNLPv2). Nevertheless, we believe that since a field like HopCount (whose value changes on a hop-by-hop basis) is in the base NDN protocol rather than NDNLP, path steering should also be in the base protocol, since it too is a hop-by-hop field independent of a particular single hop. Thanks, Spyros — Spyridon (Spyros) Mastorakis, Ph.D. Assistant Professor Computer Science Department University of Nebraska at Omaha Peter Kiewit Institute Room 174E Associate Editor, IEEE Internet of Things Journal Director, Ph.D. Program in Information Technology Website: https://sites.google.com/site/spyridonmastorakis Yours, Junxiao On Mon, Oct 25, 2021 at 4:17 PM <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> wrote: External Email A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Information-Centric Networking RG of the IRTF. Title : ICN Ping Protocol Specification Authors : Spyridon Mastorakis Jim Gibson Ilya Moiseenko Ralph Droms Dave Oran Filename : draft-irtf-icnrg-icnping-03.txt Pages : 20 Date : 2021-10-25 Abstract: This document presents the design of an ICN Ping protocol. It includes the operations of both the client and the forwarder. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-irtf-icnrg-icnping/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-irtf-icnrg-icnping/__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWDngDz72$> There is also an HTML version available at: https://www.ietf.org/archive/id/draft-irtf-icnrg-icnping-03.html<https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-irtf-icnrg-icnping-03.html__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWHAoh8T7$> A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-icnping-03<https://urldefense.com/v3/__https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-icnping-03__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWNsF9P5L$> Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/<https://urldefense.com/v3/__ftp://ftp.ietf.org/internet-drafts/__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWEPncuiM$> _______________________________________________ icnrg mailing list icnrg@irtf.org<mailto:icnrg@irtf.org> https://www.irtf.org/mailman/listinfo/icnrg<https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/icnrg__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWOFH0Dtj$> _______________________________________________ icnrg mailing list icnrg@irtf.org<mailto:icnrg@irtf.org> https://urldefense.com/v3/__https://www.irtf.org/mailman/listinfo/icnrg__;!!PvXuogZ4sRB2p-tU!R1XTGYwBlOXYUAzHhlV6sAyjq-Qz47wI4GLKSybSpxaQ2vKKrLONq9piKdxFWOFH0Dtj$
- [icnrg] I-D Action: draft-irtf-icnrg-icnping-03.t… internet-drafts
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Junxiao Shi
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… David R. Oran
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Spyridon Mastorakis
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Junxiao Shi
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… David R. Oran
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Spyridon Mastorakis
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Dirk Kutscher
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Junxiao Shi
- Re: [icnrg] [EXT] I-D Action: draft-irtf-icnrg-ic… Dirk Kutscher