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

Jungha Hong <jhong@etri.re.kr> Thu, 16 December 2021 18:01 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 E918D3A096F for <icnrg@ietfa.amsl.com>; Thu, 16 Dec 2021 10:01:39 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 pJiLnw0SYNmF for <icnrg@ietfa.amsl.com>; Thu, 16 Dec 2021 10:01:34 -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 73A993A096C for <icnrg@irtf.org>; Thu, 16 Dec 2021 10:01:30 -0800 (PST)
Received: from unknown (HELO send002-relay.gov-dooray.com) (211.180.235.153) by 129.254.9.16 with ESMTP; 17 Dec 2021 03:01:27 +0900
X-Original-SENDERIP: 211.180.235.153
X-Original-MAILFROM: jhong@etri.re.kr
X-Original-RCPTTO: icnrg@irtf.org
Received: from [10.162.225.109] (HELO send002.gov-dooray.com) ([10.162.225.109]) by send002-relay.gov-dooray.com with SMTP id d08e5ae861bb7ef7; Fri, 17 Dec 2021 03:01:27 +0900
DKIM-Signature: a=rsa-sha256; b=dzPecHhw4FH1xAg7tiNcFBbwSEQZXAlVwp8KzMf0HACdKhO4eSC2m08lVqeD+n2DAGs3YC1lip 4KZ/w3ush4f9sDvZoNaXpf7nUNbeLRQyC+lnwsJxumfR7sUFP+Axg5fu7+XNnkk+dCgjLMySlHJd zDo2s16XGGr2qB2gLi60OPtIdd6dtYKzeKm2CDJmxQMC5NkvhTEC0Oz4z9/NCmdzdA7q7+mfKqCH lqVRj9Avb6Xa0gLrn2gcdUVgUCKl1FTrL+EZ/dTEE2zSfpy+1jmPLoLYA3OrmBzsWNOZJPDK8hnF fe2e2CiowuBKEPT74umHHltTWGCEmaQCtDh5leUA==; c=relaxed/relaxed; s=selector; d=dooray.com; v=1; bh=H0jrsG1ttzqAbkLpTmH2u9i2s2Hrq0xKz/h5sBdgLR8=; h=From:To:Subject:Message-ID;
Dooray-Meta-Signature: YMj7a9aoEU9KLV/lL29lxki6lFEyWd/N1KM+uZwjibhEE/SMF09Fi gLGwVKM3ht46s915o7W1VucUCd+W2Cmmzb1Yz6hTpO6WkJGj6mVBaiigzlMafiLUfPLuVCEGghQN +5cTstoN1WoRuXFWogBccBT1l4Wg9FkzJXEZcHLl5cWZGY8UoqFBAVTx1tnfMaAA94uSCJdQwscS fw+isaV8qoUg7A79Ts44yc/gJWo9OKg+kjelb3zJouvP7C4v1j5Wx73500OmDQrF4WLnesyvumIC plCfrM4uCKSP20sM0tK+BlQPWYtw2lGfvrRL/+wfX8e1lJdBk/LqDnQVI2ezvE6gGgAxAE6N86R6 ZYP/wM=
Received: from [129.254.29.11] (HELO 129.254.29.11) ([129.254.29.11]) by send002.gov-dooray.com with SMTP id 72dfb2fd61bb7ef6; Fri, 17 Dec 2021 03:01:26 +0900
From: Jungha Hong <jhong@etri.re.kr>
Cc: icnrg@irtf.org, icnrg-chairs@ietf.org, draft-irtf-icnrg-nrsarch-considerations@ietf.org
Message-ID: <o1tzi1juqus8.o1tzi1jurnbg.g1@dooray.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Dsn-Request: true
X-Dooray-Agent: mail-api
X-Dooray-Mail-Id: 3165622442176854104
Importance: Normal
X-Priority: Normal
X-MSMail-Priority: Normal
X-Dooray-Attached: c3+LUOpPU/IB7Wl+oemm0lw5HiI/bJHHYClX72L8E3o=
To: Colin Perkins <csp@csperkins.org>, The IRSG <irsg@irtf.org>
Sender: jhong@etri.re.kr
Date: Fri, 17 Dec 2021 03:01:25 +0900
References: <163962737606.1215.8192397968831335665@ietfa.amsl.com>
In-Reply-To: <163962737606.1215.8192397968831335665@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/J6SYFQF8C8WSBbqKYou7dmb3rfI>
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: Thu, 16 Dec 2021 18:01:40 -0000

Dear Colin,

We addressed all comments received during the ballot and submitted the updated document. 
We are sorry for taking so long. 

@Melinda Shore
Thanks for your comment. 
Yes, the authenticity of the namespace is in consideration. The paragraph has been revised to clarify this issue.

@Mirja Kühlewind
Thanks for the comment. 
(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. 
(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 
in their locations in the network need to be considered. This statement has been inserted in Section 2.

@Stephen Farrell
Thanks for the comment. 
(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 
to the privacy protection of the NRS name resolution process and Passive DNS type of function for storing and analyzing 
the history of name resolution data to uncover potential security incidents or discover malicious NRS components.

Thanks,
Jungha Hong

-----Original Message-----
From:  "" <internet-drafts@ietf.org>
To:      <i-d-announce@ietf.org>; 
Cc:      <icnrg@irtf.org>; 
Sent:  2021-12-16 (목) 13:03:20 (UTC+09:00)
Subject: [icnrg] I-D Action: draft-irtf-icnrg-nrsarch-considerations-07.txt


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           : Architectural Considerations of ICN using Name Resolution Service
        Authors         : Jungha Hong
                          Tae-Wan You
                          Ved Kafle
	Filename        : draft-irtf-icnrg-nrsarch-considerations-07.txt
	Pages           : 13
	Date            : 2021-12-15

Abstract:
   This document describes architectural considerations and implications
   related to the use of a Name Resolution Service (NRS) in Information-
   Centric Networking (ICN).  It explains how the ICN architecture can
   change when an NRS is utilized and how its use influences the ICN
   routing system.  This document is a product of the Information-
   Centric Networking Research Group (ICNRG).


The IETF datatracker status page for this draft is:
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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-irtf-icnrg-nrsarch-considerations-07


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
icnrg mailing list
icnrg@irtf.org
https://www.irtf.org/mailman/listinfo/icnrg