Re: [icnrg] Progressing my QoSArch position paper

"Dirk Kutscher" <ietf@dkutscher.net> Thu, 05 December 2019 08:05 UTC

Return-Path: <ietf@dkutscher.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 B44551200F4 for <icnrg@ietfa.amsl.com>; Thu, 5 Dec 2019 00:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 kYyIduv1VUmd for <icnrg@ietfa.amsl.com>; Thu, 5 Dec 2019 00:05:12 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD3C11200B3 for <icnrg@irtf.org>; Thu, 5 Dec 2019 00:05:11 -0800 (PST)
Received: from [139.13.88.219] ([139.13.88.219]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MEmAV-1iWwIq46od-00GFwH; Thu, 05 Dec 2019 09:04:52 +0100
From: "Dirk Kutscher" <ietf@dkutscher.net>
To: "David R. Oran" <daveoran@orandom.net>
Cc: ICNRG <icnrg@irtf.org>
Date: Thu, 05 Dec 2019 09:04:49 +0100
X-Mailer: MailMate (1.13.1r5669)
Message-ID: <CC6EAA4E-5467-473A-9B1C-E5EB41944F71@dkutscher.net>
In-Reply-To: <7ADE305D-C5AF-4F36-B5F8-5794B9C06A9D@orandom.net>
References: <157538642905.24883.16796734789691599459.idtracker@ietfa.amsl.com> <7ADE305D-C5AF-4F36-B5F8-5794B9C06A9D@orandom.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:ciw7lkYU/4tA0+hBVfwQR48PhpHzXiLyxH3fwM8Umnt4WSHW8rp tKfUlIj1RvXzrA2XLv8Ezne6iZ08PaWeast5e1BtUH1+4fX5B1GU/boNE6CIV/LEzY4pF0k NHQmxppYwK788xKmx3Hrbe7Q1t8MH2enJF1LD5TSbACK4vgblknoSytmnKNeLlX08bY+R2R d1jmTTbX1dQt4NMVR2ivA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:rpNky7ViTRQ=:hCgau9sOKLiMYHy2BHZy/T BVpqvlaYOP5XGfgsOD2ZtYaJeAVhtiUjKopjQaI5JWjsal6j4kMtGcxKcaI2wcWCu3K4xQzrd FsAAt8/4/xKJE4VOqWLt9ZXZeZtwouaKmdFnfOi+gRUFQjgJSel7UtJ2KdoS12jxRPQtMBYm2 if/AYo/wQsIWsRwyrYk3Fn1GziWJ9JH6KOH8q+eF0Jse+v/wHvKwf4TUBU+wr2TBUGEn33K8/ s87j1kYpAZF5cYbfHuU1GiN6cDEq/u4+HpbrMfESSbnu7DleyhRQJDr6ri2XNYytMf5AFxkbT HgTFLtS0eUGc6EZ0+ZdJwNI8Sdk444VUeaUXRd7mtpDmRhPqqWW7hoiCwiWDdTy50UTyC4/S3 0Ook2zVfec6pMmb6xXrweZF8fDZwuCXuAh7us1rbXYxPXV8uhdGIA3wSf6caUxwsJHtaUqZ0S NDemHpAS4YcL2OGFYMTX+SYjAxh7pwWaw0lNUdCWzdRVxCYQv9BxAYQsYGqZxhFz2wGt5v746 9jirNRN+I83jgO19CTBmkLqRZ6qN/gdqC1wlaYhxFtD0cdfGBEg8mParEYcu3HBJTSyDC+i97 5Gov9XUXjsAoJ3NDIdesCiPenfiuNLFwQra1p6kkpGT42Ye0xnsmn3RFtGCyNZeacCopv2mha k0+E7997kuqtxWwHrE9xRxIH2NAHI7cZNwnOGvQ/O30Tn88SaiJyyS08PBllKCTLGzyqRgdAD lJIFXM0/gqqDpy0Kj2wDtKYdFi4UaQIZKlppbQvvqO//l+0xLra+mgNRsr1FP73IqjQWFZgdb uK9MKBXTnjbVLifVXXMCKCgGKyD9XYkBeUk1ERUp9TBkSLKpR53l9hOPnXk4Xk5Dua75l8XWe 8TWOUgmSJT+G/WoQ3+NgHAdZ+m7OxtnAPAGfHSJcA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/665ZVFr42-D7vYN7oABlNxtn7uY>
Subject: Re: [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: Thu, 05 Dec 2019 08:05:14 -0000

On 3 Dec 2019, at 16:29, David R. Oran wrote:

> 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 
> document.

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

Yes, I still think that’s a good way forward.

And, of course, this is just the beginning for QoS work in ICNRG. We are 
hoping that getting this published now would help people to start 
writing specific proposals, share experimentation results.

Best regards,
Dirk


>
> Many thanks,
> DaveO
>
> Forwarded message:
>
>> From: internet-drafts@ietf.org
>> To: Dave Oran <daveoran@orandom.net>et>, 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
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg