RFC 9064 on Considerations in the Development of a QoS Architecture for CCNx-Like Information-Centric Networking Protocols

rfc-editor@rfc-editor.org Wed, 30 June 2021 17:40 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4117A3A2447 for <ietf-announce@ietfa.amsl.com>; Wed, 30 Jun 2021 10:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ymGn_EAn30bz for <ietf-announce@ietfa.amsl.com>; Wed, 30 Jun 2021 10:40:32 -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 B9A033A2449 for <ietf-announce@ietf.org>; Wed, 30 Jun 2021 10:40:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 14553F40757; Wed, 30 Jun 2021 10:40:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: =?UTF-8?B?UkZDIDkwNjQgb24gQ29uc2lkZXJhdGlvbnMgaW4gdGhlIERldmVsb3BtZW50IG9mIGEgUW9TIEFyY2hpdGVjdHVyZSBmb3IgQ0NOeC1MaWtlIEluZm9ybWF0aW9uLUNlbnRyaWMgTmV0d29ya2luZyBQcm90b2NvbHM=?=
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20210630174010.14553F40757@rfc-editor.org>
Date: Wed, 30 Jun 2021 10:40:10 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/PHUbhduD-HUIB53wUscOxpX7AQI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2021 17:40:37 -0000

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

        RFC 9064

        Title:      Considerations in the Development of 
                    a QoS Architecture for CCNx-Like Information-Centric 
                    Networking Protocols 
        Author:     D. Oran
        Status:     Informational
        Stream:     IRTF
        Date:       June 2021
        Mailbox:    daveoran@orandom.net
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-oran-icnrg-qosarch-06.txt

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

        DOI:        10.17487/RFC9064

This is a position paper. It documents the author's personal views on
how Quality of Service (QoS) capabilities ought to be accommodated in
Information-Centric Networking (ICN) protocols like Content-Centric
Networking (CCNx) or Named Data Networking (NDN), which employ
flow-balanced Interest/Data exchanges and hop-by-hop forwarding state
as their fundamental machinery. It argues that such protocols demand
a substantially different approach to QoS from that taken in TCP/IP
and proposes specific design patterns to achieve both classification
and differentiated QoS treatment on both a flow and aggregate basis.
It also considers the effect of caches in addition to memory, CPU,
and link bandwidth as resources that should be subject to explicitly
unfair resource allocation. The proposed methods are intended to
operate purely at the network layer, providing the primitives needed
to achieve transport- and higher-layer QoS objectives. It explicitly
excludes any discussion of Quality of Experience (QoE), which can
only be assessed and controlled at the application layer or above. 

This document is not a product of the IRTF Information-Centric
Networking Research Group (ICNRG) but has been through formal Last
Call and has the support of the participants in the research group
for publication as an individual submission.

This document is a product 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