Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: =?utf-8?Q?B=C3=B6rje_Ohlman?= <Borje.Ohlman@abc.se>
In-Reply-To: <CC6EAA4E-5467-473A-9B1C-E5EB41944F71@dkutscher.net>
Date: Thu, 5 Dec 2019 09:39:31 +0100
Cc: David R Oran <daveoran@orandom.net>,
 icnrg <icnrg@irtf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <90299A4E-A71A-4A86-917A-4B2BFAB30951@abc.se>
References: <157538642905.24883.16796734789691599459.idtracker@ietfa.amsl.com>
 <7ADE305D-C5AF-4F36-B5F8-5794B9C06A9D@orandom.net>
 <CC6EAA4E-5467-473A-9B1C-E5EB41944F71@dkutscher.net>
To: Dirk Kutscher <ietf@dkutscher.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/79yIMag9YiT-m6wPEHsg_yfmvOg>
Subject: Re: [icnrg] Progressing my QoSArch position paper
Precedence: list

I don=E2=80=99t have anything to add. I think this is the right way =
forward, but it is of course important what the ICNRG community at large =
thinks is the best way forward.

	B=C3=B6rje

> On 5 Dec 2019, at 09:04, Dirk Kutscher <ietf@dkutscher.net> wrote:
>=20
> On 3 Dec 2019, at 16:29, David R. Oran wrote:
>=20
>> After discussion with Dirk & B=C3=B6rje, 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.
>=20
>> I=E2=80=99ll leave to to Dirk and B=C3=B6rje to either confirm this =
course of action or suggest something different.
>=20
> Yes, I still think that=E2=80=99s a good way forward.
>=20
> 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.
>=20
> Best regards,
> Dirk
>=20
>=20
>>=20
>> Many thanks,
>> DaveO
>>=20
>> Forwarded message:
>>=20
>>> 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
>>>=20
>>> 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.
>>>=20
>>> 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=3Ddraft-oran-icnrg-qosarch-03
>>>=20
>>> 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.
>>>=20
>>>=20
>>>=20
>>>=20
>>> 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.
>>>=20
>>> The IETF Secretariat
>>=20
>> _______________________________________________
>> icnrg mailing list
>> icnrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/icnrg
>=20
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg