[IRTF-Announce] 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:48 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: irtf-announce@ietfa.amsl.com
Delivered-To: irtf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D573A0DD8; 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 rnU6uRXshCTr; 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 7857E3A0DBE; 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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, icnrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220421214844.128F21E65D@rfcpa.amsl.com>
Date: Thu, 21 Apr 2022 14:48:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-announce/U3YNWYaftxGsANziUABZnWZiIq8>
Subject: [IRTF-Announce] RFC 9236 on Architectural Considerations of Information-Centric Networking (ICN) Using a Name Resolution Service
X-BeenThere: irtf-announce@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF-Announce <irtf-announce.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-announce/>
List-Post: <mailto:irtf-announce@irtf.org>
List-Help: <mailto:irtf-announce-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2022 21:48:49 -0000
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