Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Hitoshi Asaeda <asaeda@ieee.org>
In-Reply-To: <56D947E2-9A9F-4B93-A2FC-70A53BB7466C@dkutscher.net>
Date: Tue, 11 Feb 2020 20:22:00 +0900
Cc: ICNRG <icnrg@irtf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FD59F5F-6050-48E7-8685-2875B3D25A0D@ieee.org>
References: <E35749ED-CFB8-4352-BE66-724BC2C49B64@dkutscher.net>
 <9BCFBA67-509A-41BD-8351-334AF844C5F5@csperkins.org>
 <56D947E2-9A9F-4B93-A2FC-70A53BB7466C@dkutscher.net>
To: Dirk Kutscher <ietf@dkutscher.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/bVuSy-kBL2dysVDTkAPJiD-C1Zs>
Subject: Re: [icnrg] Last Call: draft-oran-icnrg-qosarch
Precedence: list

Hi,

Sorry for the late response.
I have no concern about moving this forward, yet suggest to consider one =
thing.

For the effective use of in-network cache, network coding is also =
helpful to improve the data transmission quality. I therefore recommend =
to add some statement explaining the way of its use or adoption with =
some references already discussing the advantages (or even difficulties) =
for ICN.=20

Regards,

Hitoshi



> On Feb 11, 2020, at 20:00, Dirk Kutscher <ietf@dkutscher.net> wrote:
>=20
> Thanks, Colin.
>=20
>> I think it=E2=80=99s reasonable to publish this as a position paper, =
provided the RG is okay with that, but would it be possible to add a few =
words to the Introduction to explain why the ICN RG thinks this is best =
published as a position paper? (To be clear that the points in RFC 5743 =
Section 2.1 are explicitly addressed)
>=20
> Yes, let=E2=80=99s do that. I will draft some lines from an ICNRG =
perspective that Dave could consider including here.
>=20
>> Also, the short title (=E2=80=9CICN QoS Architecture=E2=80=9D) on =
each page can be read as perhaps implying a stronger status than =
intended. Is there space to change it to something like =E2=80=9CProposed =
ICN QoS Architecture=E2=80=9D instead?
>=20
> Yes, good point. Dave already noted that =E2=80=9CICN QoS Architecture =
Considerations=E2=80=9D (or something in that direction) is more =
appropriate and will change the draft accordingly.
>=20
> Again, the last call period for this draft is over. If people have =
other comments, please share them now. We will move to IRSG review when =
the new version is ready.
>=20
> Thanks,
> Dirk
>=20
>=20
>=20
>> Colin
>>=20
>>=20
>>=20
>>=20
>>> We (Dave as the author, and B=C3=B6rje & myself as chairs) think =
that the draft is useful and mature enough so that we can move it =
towards publication, and I would therefore like to last-call it. Please =
read it and let us know if you think there are issues. The last call =
ends on February 7th, i.e., 2.5 weeks from today.
>>>=20
>>>=20
>>> https://datatracker.ietf.org/doc/draft-oran-icnrg-qosarch/
>>>=20
>>> Abstract
>>>=20
>>>  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
>>> Best regards,
>>> Dirk
>>>=20
>>> _______________________________________________
>>> icnrg mailing list
>>> icnrg@irtf.org
>>> https://www.irtf.org/mailman/listinfo/icnrg
>>=20
>>=20
>>=20
>> --=20
>> Colin Perkins
>> https://csperkins.org/
>>=20
>>=20
>>=20
>>=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