[rfc-dist] RFC 9236 on Architectural Considerations of Information-Centric Networking (ICN) Using a Name Resolution Service
rfc-editor@rfc-editor.org Thu, 21 April 2022 21:50 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5867D3A110E; Thu, 21 Apr 2022 14:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1650577828; bh=K+WRhJy2R+YqOuQQwaW/++NvDmEtkM9/fDmuhTzcZfA=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=FoM0YwrBG0du1D69CL5o0UoWFEN/yGzDNjetwBltDjQ+ijyF10dMnMeSXVAzOYJL5 GeTY/Yr5Bnq6Oh4pWi68YISLXtInCtkpKLGRhjADxZWUZUMzvj7JwMDIg4Jck5ZRfW h3tj6JPLFlU76tS0PQre5h1zzmkyBSM4ptEzWIdk=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Thu Apr 21 14:50:21 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C56A3A0DF7; Thu, 21 Apr 2022 14:48:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1650577736; bh=K+WRhJy2R+YqOuQQwaW/++NvDmEtkM9/fDmuhTzcZfA=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=SfJWlzq9YKDt4sFSUyvjkN2rzmCSp2sS3XoqHA0b3WjdOQeWPpjioKHAo/9P3pECx 6Md9mRY+4JIc2b+RyvIfSbgEjSmTRVwjpV7W39ZvfjcxTgYCD7LLUplMy6OM0xHbGX FBUPJ4FbKAu7NgBSZpFFvjHT63d8dFU/vGV+Syic=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C453A0DD4; Thu, 21 Apr 2022 14:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Level:
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 ItZX-QDmcXvv; Thu, 21 Apr 2022 14:48:44 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A14A3A0DBF; Thu, 21 Apr 2022 14:48:44 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 128F21E65D; Thu, 21 Apr 2022 14:48:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
From: rfc-editor@rfc-editor.org
Message-Id: <20220421214844.128F21E65D@rfcpa.amsl.com>
Date: Thu, 21 Apr 2022 14:48:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/2_tYU2cJ3aqu0IE91gfjvRa3QLY>
Subject: [rfc-dist] RFC 9236 on Architectural Considerations of Information-Centric Networking (ICN) Using a Name Resolution Service
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, icnrg@irtf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries. RFC 9236 Title: Architectural Considerations of Information-Centric Networking (ICN) Using a Name Resolution Service Author: J. Hong, T. You, V. Kafle Status: Informational Stream: IRTF Date: April 2022 Mailbox: jhong@etri.re.kr, twyou@etri.re.kr, kafle@nict.go.jp Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-icnrg-nrsarch-considerations-07.txt URL: https://www.rfc-editor.org/info/rfc9236 DOI: 10.17487/RFC9236 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). This document is a product of the Information-Centric Networking Research Group of the IRTF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist https://www.irtf.org/mailman/listinfo/irtf-announce For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org