[icnrg] Progressing my QoSArch position paper

"David R. Oran" <daveoran@orandom.net> Tue, 03 December 2019 15:29 UTC

Return-Path: <daveoran@orandom.net>
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 64BD41200CC for <icnrg@ietfa.amsl.com>; Tue, 3 Dec 2019 07:29:29 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SmdFjiJ2sWpr for <icnrg@ietfa.amsl.com>; Tue, 3 Dec 2019 07:29:27 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 47F3912006B for <icnrg@irtf.org>; Tue, 3 Dec 2019 07:29:27 -0800 (PST)
Received: from [] ([IPv6:2601:184:407f:80ce:54dc:7ace:daa6:1152]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id xB3FTMFh014240 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <icnrg@irtf.org>; Tue, 3 Dec 2019 07:29:24 -0800
From: "David R. Oran" <daveoran@orandom.net>
To: ICNRG <icnrg@irtf.org>
Date: Tue, 03 Dec 2019 10:29:17 -0500
X-Mailer: MailMate (1.13r5667)
Message-ID: <7ADE305D-C5AF-4F36-B5F8-5794B9C06A9D@orandom.net>
References: <157538642905.24883.16796734789691599459.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/JGcE5L3eXYHaeXEfkkE6CDMrKEc>
Subject: [icnrg] Progressing my QoSArch position paper
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: Tue, 03 Dec 2019 15:29:29 -0000

I just submitted the update below. It reflects comments by a number of 
people and the discussion we had at the QoS side meetings in Singapore. 
Many thanks to those who commented, especially Thomas, Luca, Anil, 
Milan, and Prakash.

<Chair Hat off, purely Author hat on>

After discussion with Dirk & Börje, and with the IRTF chair, it seems 
we can move this through to publication without a formal adoption as an 
ICNRG RG work item. This to me is the appropriate course given the 
individual nature of the material and opinions contained in the 

My personal view as author is that this is about as “cooked” as 
it’s going to be so I’d like to ask that we just do an ICNRG last 
call to assess people’s views on its readiness for IRTF review 
followed by publication.

Doing so will allow us to freeze this material and, as we discussed at 
the QoS side meetings, perhaps use it as reference/background material 
in the construction of a new RG-developed document on ICN QoS 

I’ll leave to to Dirk and Börje to either confirm this course of 
action or suggest something different.

Many thanks,

Forwarded message:

> From: internet-drafts@ietf.org
> To: Dave Oran <daveoran@orandom.net>, David Oran 
> <daveoran@orandom.net>
> Subject: New Version Notification for draft-oran-icnrg-qosarch-03.txt
> Date: Tue, 03 Dec 2019 07:20:29 -0800
> A new version of I-D, draft-oran-icnrg-qosarch-03.txt
> has been successfully submitted by Dave Oran and posted to the
> IETF repository.
> Name:		draft-oran-icnrg-qosarch
> Revision:	03
> Title:		Considerations in the development of a QoS Architecture for 
> CCNx-like ICN protocols
> Document date:	2019-12-03
> Group:		Individual Submission
> Pages:		25
> URL:            
> https://www.ietf.org/internet-drafts/draft-oran-icnrg-qosarch-03.txt
> Status:         
> https://datatracker.ietf.org/doc/draft-oran-icnrg-qosarch/
> Htmlized:       
> https://tools.ietf.org/html/draft-oran-icnrg-qosarch-03
> Htmlized:       
> https://datatracker.ietf.org/doc/html/draft-oran-icnrg-qosarch
> Diff:           
> https://www.ietf.org/rfcdiff?url2=draft-oran-icnrg-qosarch-03
> Abstract:
>    This is a position paper.  It documents the author's personal views
>    on how Quality of Service (QoS) capabilities ought to be 
> accommodated
>    in ICN protocols like CCNx or 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 as a resource in addition to
>    memory, CPU and link bandwidth 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 both 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.
> Please note that it may take a couple of minutes from the time of 
> submission
> until the htmlized version and diff are available at tools.ietf.org.
> The IETF Secretariat