[icnrg] Beach reading!

"David R. Oran" <daveoran@orandom.net> Fri, 09 August 2019 20:21 UTC

Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3E512018D for <icnrg@ietfa.amsl.com>; Fri, 9 Aug 2019 13:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WuGLZXV6Ktee for <icnrg@ietfa.amsl.com>; Fri, 9 Aug 2019 13:21:21 -0700 (PDT)
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 AB7E2120178 for <icnrg@irtf.org>; Fri, 9 Aug 2019 13:21:21 -0700 (PDT)
Received: from [66.31.201.96] ([IPv6:2601:184:4081:19c1:2840:bc20:39ae:ab3d]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id x79KLIFN007620 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <icnrg@irtf.org>; Fri, 9 Aug 2019 13:21:19 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: ICNRG <icnrg@irtf.org>
Date: Fri, 09 Aug 2019 16:21:17 -0400
X-Mailer: MailMate (1.12.5r5643)
Message-ID: <B33F9286-1E5E-4C8A-818B-B2BA3565113A@orandom.net>
References: <156538181743.29332.6627670069769912013@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/lAgpQrfvj9RCaDu2zfP3uzoXitY>
Subject: [icnrg] Beach reading!
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, 09 Aug 2019 20:21:23 -0000

Happy August, ICNRGers.

I just submitted the draft below on constructing an architecture for 
achieving QoS for ICN protocols. It’s an expansion of the stuff I’ve 
been pounding into people’s heads at multiple ICNRG meetings as a 
presentation. I thought formalizing it as a document for consideration 
by ICNRG to guide our work might be timely. Please take a look and post 
feedback and comments.

It might be good beach reading, especially if you like to nod off in the 
sun :-)

DaveO

Forwarded message:

> From: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-oran-icnrg-qosarch-00.txt
> Date: Fri, 09 Aug 2019 13:16:57 -0700
>
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
>
>
>         Title           : Considerations in the development of a QoS 
> Architecture for CCNx-like ICN protocols
>         Author          : Dave Oran
> 	Filename        : draft-oran-icnrg-qosarch-00.txt
> 	Pages           : 18
> 	Date            : 2019-08-09
>
> 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
>    un-fair 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.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-oran-icnrg-qosarch/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-oran-icnrg-qosarch-00
> https://datatracker.ietf.org/doc/html/draft-oran-icnrg-qosarch-00
>
>
> 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.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt