[icnrg] RFC 8884 on Research Directions for Using Information-Centric Networking (ICN) in Disaster Scenarios

rfc-editor@rfc-editor.org Fri, 23 October 2020 18:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 7941B3A10E2; Fri, 23 Oct 2020 11:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SrInn--_RqOS; Fri, 23 Oct 2020 11:47:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3AE3A10E0; Fri, 23 Oct 2020 11:47:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3A7FFF4073A; Fri, 23 Oct 2020 11:47:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20201023184730.3A7FFF4073A@rfc-editor.org>
Date: Fri, 23 Oct 2020 11:47:30 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/o-ltHuzJezc2Tjrz9lC7Y6-1OEA>
Subject: [icnrg] =?utf-8?q?RFC_8884_on_Research_Directions_for_Using_Info?= =?utf-8?q?rmation-Centric_Networking_=28ICN=29_in_Disaster_Scenarios?=
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, 23 Oct 2020 18:47:38 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8884

        Title:      Research Directions for Using Information-Centric 
                    Networking (ICN) in Disaster Scenarios 
        Author:     J. Seedorf, 
                    M. Arumaithurai,
                    A. Tagami,
                    K. Ramakrishnan,
                    N. Blefari-Melazzi
        Status:     Informational
        Stream:     IRTF
        Date:       October 2020
        Mailbox:    jan.seedorf@hft-stuttgart.de, 
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-icnrg-disaster-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8884

        DOI:        10.17487/RFC8884

Information-Centric Networking (ICN) is a new paradigm where the
network provides users with named content instead of communication
channels between hosts. This document outlines some research
directions for ICN with respect to applying ICN approaches for coping
with natural or human-generated, large-scale disasters. This document
is a product of the Information-Centric Networking Research Group

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

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