[icnrg] I just submitted an update to my ICN QoSArch draft
"David R. Oran" <daveoran@orandom.net> Sat, 12 October 2019 15:35 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 812CD12003F for <icnrg@ietfa.amsl.com>; Sat, 12 Oct 2019 08:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 YZE4jpil_6UP for <icnrg@ietfa.amsl.com>; Sat, 12 Oct 2019 08:35:47 -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 72AFD120019 for <icnrg@irtf.org>; Sat, 12 Oct 2019 08:35:47 -0700 (PDT)
Received: from [24.60.31.220] ([IPv6:2601:184:4081:19c1:88b3:8c87:22c5:21be]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id x9CFZgpC022093 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <icnrg@irtf.org>; Sat, 12 Oct 2019 08:35:44 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: ICNRG <icnrg@irtf.org>
Date: Sat, 12 Oct 2019 11:35:42 -0400
X-Mailer: MailMate (1.13r5655)
Message-ID: <5C68D385-F901-4A3A-88C9-350234E7C162@orandom.net>
References: <157089431975.1372.17365919232442804449@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/TcTe_SpvMqlYAn2cT-kbcAzNY24>
Subject: [icnrg] I just submitted an update to my ICN QoSArch draft
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: Sat, 12 Oct 2019 15:35:50 -0000
This has a number of edits based on comments received so far (not enough!) and offline discussions with a few people. The major addition is a discussion of what the implications of incorporating INTserv-like QoS features into CCNx or NDN might be. Comments please!!!!! DaveO Forwarded message: > From: internet-drafts@ietf.org > To: i-d-announce@ietf.org > Subject: I-D Action: draft-oran-icnrg-qosarch-02.txt > Date: Sat, 12 Oct 2019 08:31:59 -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-02.txt > Pages : 24 > Date : 2019-10-12 > > 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. > > > 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-02 > https://datatracker.ietf.org/doc/html/draft-oran-icnrg-qosarch-02 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-oran-icnrg-qosarch-02 > > > 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
- [icnrg] I just submitted an update to my ICN QoSA… David R. Oran
- Re: [icnrg] I just submitted an update to my ICN … Anil Jangam (anjangam)
- Re: [icnrg] I just submitted an update to my ICN … Thomas C. Schmidt
- Re: [icnrg] I just submitted an update to my ICN … David R. Oran
- Re: [icnrg] I just submitted an update to my ICN … David R. Oran
- Re: [icnrg] I just submitted an update to my ICN … Luca Muscariello
- Re: [icnrg] I just submitted an update to my ICN … David R. Oran
- Re: [icnrg] I just submitted an update to my ICN … Luca Muscariello
- Re: [icnrg] I just submitted an update to my ICN … David R. Oran