Re: [icnrg] I-D Action: draft-irtf-icnrg-nrsarch-considerations-07.txt

Jungha Hong <jhong@etri.re.kr> Fri, 17 December 2021 09:52 UTC

Return-Path: <jhong@etri.re.kr>
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 8EC6E3A19DA for <icnrg@ietfa.amsl.com>; Fri, 17 Dec 2021 01:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dooray.com
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 SWRz4giEWddi for <icnrg@ietfa.amsl.com>; Fri, 17 Dec 2021 01:52:38 -0800 (PST)
Received: from mscreen.etri.re.kr (mscreen.etri.re.kr [129.254.9.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CF073A19DB for <icnrg@irtf.org>; Fri, 17 Dec 2021 01:52:36 -0800 (PST)
Received: from unknown (HELO send001-relay.gov-dooray.com) (211.180.235.152) by 129.254.9.16 with ESMTP; 17 Dec 2021 18:45:51 +0900
X-Original-SENDERIP: 211.180.235.152
X-Original-MAILFROM: jhong@etri.re.kr
X-Original-RCPTTO: icnrg@irtf.org
Received: from [10.162.225.48] (HELO send008.gov-dooray.com) ([10.162.225.48]) by send001-relay.gov-dooray.com with SMTP id 89ad2d4d61bc5c4e; Fri, 17 Dec 2021 18:45:50 +0900
DKIM-Signature: a=rsa-sha256; b=NEbrv3m2EGmYJnZutMK+TqbYLnDTU4Cxbgs2ZcX5TREtqFjjImwstFe27/I+qwTT/3XODgdp2E d6LIQ5pKNSgaVZJ98B4Jxe1pwCDTnluriro8kY0gu0ycXZv4xXtlV1dgx3qLcWjO6oiGlHddRFVB m2f+iKwuU4+tNuaeNiAQ3QLvrWtqsylDFpGDqA7lXnPXLngyB448jI8AQHZmim8rqI0QCTHK/1cT 3DRU7GwXcQ2RasObmdio+7unk7ki6UynSGnzkOuw82SafihbajbBT5xTfLZM5dZnMZGCvb8XFJiT wxv1oTBv61RPwsU4umh2Nil67vxHU/lvLwF7EcUA==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=XuSiz0kJu27jbqnm8UK67efER1oLYTdnI1FdFHvEMnQ=; h=From:To:Subject:Message-ID;
Dooray-Meta-Signature: QMr7zmbo9sruJSHk9+5W3CSIiNLMbeEZZFrfnSZj+81gDVpCoeWaW QIIofMcpqKL6s915o7W1VucUCd+W2Cmmzb1Yz6hTpO6WkJGj6mVBaiigzlMafiLUfPLuVCEGghQN +5cTstoN1WoRuXFWogBccBT1l4Wg9FkzJXEZcHLl5cWZGY8UoqFBAVTx1tnfMaAv7J/zSsWMmqdg ckX8yGbv1QCLJlLwaqVKaS+iNvKi/Sg+kjelb3zJouvP7C4v1j5Wx73500OmDQrF4WLnesyvumIC plCfrM4uCKSP20sM0tK+BlQPWYtw2lGfvrRL/+wfX8e1lJdBk/LqDnQVI2ezvE6gGgAxAE6N86R6 ZYP/wM=
Received: from [129.254.29.11] (HELO 129.254.29.11) ([129.254.29.11]) by send008.gov-dooray.com with SMTP id 6494fba161bc5c4d; Fri, 17 Dec 2021 18:45:49 +0900
From: Jungha Hong <jhong@etri.re.kr>
To: Colin Perkins <csp@csperkins.org>
Cc: The IRSG <irsg@irtf.org>, icnrg@irtf.org, icnrg-chairs@ietf.org, draft-irtf-icnrg-nrsarch-considerations@ietf.org
Message-ID: <o1yu6jv26vq3.o1yu6juzxa4u.g1@dooray.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_331624_403699268.1639734348065"
X-Dsn-Request: true
X-Dooray-Agent: mail-api
X-Dooray-Mail-Id: 3166115235900404763
Importance: Normal
X-Priority: Normal
X-MSMail-Priority: Normal
X-Dooray-Attached: c3+LUOpPU/IB7Wl+oemm0lw5HiI/bJHHYClX72L8E3o=
Sender: jhong@etri.re.kr
Date: Fri, 17 Dec 2021 18:45:49 +0900
References: <163962737606.1215.8192397968831335665@ietfa.amsl.com> <o1tzi1juqus8.o1tzi1jurnbg.g1@dooray.com> <A2CE10A6-BAB6-4E6D-9F1C-B4E339D3B7AA@csperkins.org>
In-Reply-To: <A2CE10A6-BAB6-4E6D-9F1C-B4E339D3B7AA@csperkins.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/T45kEF0ZZydJKVcYdhXomII3kiE>
Subject: Re: [icnrg] I-D Action: draft-irtf-icnrg-nrsarch-considerations-07.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: Fri, 17 Dec 2021 09:52:45 -0000

Dear Colin,

Thanks for taking care of it.

Jungha Hong



-----Original Message-----
From: "Colin Perkins" &lt;csp@csperkins.org&gt;
To: "Jungha Hong" &lt;jhong@etri.re.kr&gt;;
Cc: "The IRSG" &lt;irsg@irtf.org&gt;; &lt;icnrg@irtf.org&gt;; &lt;icnrg-chairs@ietf.org&gt;; &lt;draft-irtf-icnrg-nrsarch-considerations@ietf.org&gt;;
Sent: 2021-12-17 (금) 03:27:00 (UTC+09:00)
Subject: Re: [icnrg] I-D Action: draft-irtf-icnrg-nrsarch-considerations-07.txt

Dear Jungha,

Thank you for updating the draft, and for the detailed response to the comments. I will give a few days for people to review the changes, then if there are no objections send this for IESG conflict review early next week.

Colin


On 16 Dec 2021, at 18:01, Jungha Hong &lt;jhong@etri.re.kr mailto:jhong@etri.re.kr&gt; wrote:
Dear Colin,We addressed all comments received during the ballot and submitted the updated document.&nbsp;We are sorry for taking so long.&nbsp;@Melinda ShoreThanks for your comment.&nbsp;Yes, the authenticity of the namespace is in consideration. The paragraph has been revised to clarify this issue.@Mirja KühlewindThanks for the comment.&nbsp;(1) This document describes considerations from the perspective of ICN architecture and routing systems when using an NRS in ICN.Its companion document (RFC9138) focuses on NRS itself as a service or a system in ICN.&nbsp;(2) FIB has been spelled out where it appears for the first time.(3) Yes, DNS may be used as an NRS. However, the requirements of frequent updates of NRS records due to the creations of a lot of new NDOs and changes&nbsp;in their locations in the network need to be considered. This statement has been inserted in Section 2.@Stephen FarrellThanks for the comment.&nbsp;(1) Yes, we have revised the first sentence in the "Security" bullet in Section 4 and deleted the last sentence.(2) Yes, in the security consideration section, we have added text to mention the QNAME minimization type of approach&nbsp;to the privacy protection of the NRS name resolution process and Passive DNS type of function for storing and analyzing&nbsp;the history of name resolution data to uncover potential security incidents or discover malicious NRS components.Thanks,Jungha Hong-----Original Message-----From: &nbsp;"" &lt;internet-drafts@ietf.org mailto:internet-drafts@ietf.org&gt;To: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;i-d-announce@ietf.org mailto:i-d-announce@ietf.org&gt;;&nbsp;Cc: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;icnrg@irtf.org mailto:icnrg@irtf.org&gt;;&nbsp;Sent: &nbsp;2021-12-16 (목) 13:03:20 (UTC+09:00)Subject: [icnrg] I-D Action: draft-irtf-icnrg-nrsarch-considerations-07.txtA 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.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Architectural Considerations of ICN using Name Resolution Service&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Authors &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Jungha Hong&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tae-Wan You&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Ved KafleFilename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-irtf-icnrg-nrsarch-considerations-07.txtPages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 13Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2021-12-15Abstract:&nbsp;&nbsp;This document describes architectural considerations and implications&nbsp;&nbsp;related to the use of a Name Resolution Service (NRS) in Information-&nbsp;&nbsp;Centric Networking (ICN). &nbsp;It explains how the ICN architecture can&nbsp;&nbsp;change when an NRS is utilized and how its use influences the ICN&nbsp;&nbsp;routing system. &nbsp;This document is a product of the Information-&nbsp;&nbsp;Centric Networking Research Group (ICNRG).The IETF datatracker status page for this draft is:https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrsarch-considerations/ https://datatracker.ietf.org/doc/draft-irtf-icnrg-nrsarch-considerations/There is also an htmlized version available at:https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-nrsarch-considerations-07 https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-nrsarch-considerations-07A diff from the previous version is available at:https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-nrsarch-considerations-07 https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-nrsarch-considerations-07Internet-Drafts are also available by rsync at rsync.ietf.org http://rsync.ietf.org::internet-drafts_______________________________________________icnrg mailing listicnrg@irtf.org mailto:icnrg@irtf.orghttps://www.irtf.org/mailman/listinfo/icnrg https://www.irtf.org/mailman/listinfo/icnrg

--&nbsp;Colin Perkinshttps://csperkins.org/ https://csperkins.org/