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

Colin Perkins <csp@csperkins.org> Thu, 16 December 2021 18:26 UTC

Return-Path: <csp@csperkins.org>
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 4D4D73A0C21; Thu, 16 Dec 2021 10:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=csperkins.org
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 CQxTJlam1WyV; Thu, 16 Dec 2021 10:26:53 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (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 2EE633A0C15; Thu, 16 Dec 2021 10:26:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:From:Subject; bh=TuuUNrhEt1ypWE2eJOv1scCGctbyK8DifYCpRb0+X8U=; b=uN8sS2Zt9BW2pRnAwjPnHMkEbr Sh6iGI4pZS7hkfUik9VJFTGWVjmZZAW8ObPIZAmZgR+k0cT2p2Ayr964M48kD5bivJ+GemhQG/aWW 0Uc/V3WVoUStGC0hCeNUeNHLZh0sFB+n0YZvpimEox49mCzmXA7OhBb8nutA6oofAC44T3TfRo09n GqPdZY4lDh3pApgOXKEYaK2RC4zc6bgmou0lpqV+JvnT44SOG7n4uOR0h2BHWcHbjpbvzHxStrFs1 3S8S4khx6TCSSC5FIoAqaTgeFGNcDHKwSV9XNthUK8SsqJbDQ77ueFEUpInJTE9LS4MUi2pZf2uPF fSZRe6Jg==;
Received: from [81.187.2.149] (port=36853 helo=[192.168.0.67]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1mxvSs-0001Ix-7k; Thu, 16 Dec 2021 18:26:50 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_F9447B03-1E2A-4B6E-9A07-D652F98EE40F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Colin Perkins <csp@csperkins.org>
X-Priority: Normal
In-Reply-To: <o1tzi1juqus8.o1tzi1jurnbg.g1@dooray.com>
Date: Thu, 16 Dec 2021 18:26:32 +0000
Cc: The IRSG <irsg@irtf.org>, icnrg@irtf.org, icnrg-chairs@ietf.org, draft-irtf-icnrg-nrsarch-considerations@ietf.org
Message-Id: <A2CE10A6-BAB6-4E6D-9F1C-B4E339D3B7AA@csperkins.org>
References: <163962737606.1215.8192397968831335665@ietfa.amsl.com> <o1tzi1juqus8.o1tzi1jurnbg.g1@dooray.com>
To: Jungha Hong <jhong@etri.re.kr>
X-Mailer: Apple Mail (2.3445.104.21)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/zlIYwJCzNfK7494zlwWxLhn-LmM>
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:27:00 -0000

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 <jhong@etri.re.kr> wrote:
> 
> 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 <mailto:internet-drafts@ietf.org>>
> To:      <i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>>; 
> Cc:      <icnrg@irtf.org <mailto: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 <mailto:icnrg@irtf.org>
> https://www.irtf.org/mailman/listinfo/icnrg <https://www.irtf.org/mailman/listinfo/icnrg>


-- 
Colin Perkins
https://csperkins.org/