Re: [icnrg] Last Call: draft-oran-icnrg-qosarch

Hitoshi Asaeda <> Tue, 11 February 2020 11:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 36FB81200D6 for <>; Tue, 11 Feb 2020 03:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1tLvKkGs0X_R for <>; Tue, 11 Feb 2020 03:22:04 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 72B9F12007C for <>; Tue, 11 Feb 2020 03:22:04 -0800 (PST)
Received: by with SMTP id y73so5364589pfg.2 for <>; Tue, 11 Feb 2020 03:22:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2cPti3IGTLLCYIG7mM22dAT5T5carpc7yG3r/UBGnYA=; b=bsfDcT47+8RCCc7aBSObnLrZ00+5Q1xR9FXoHXbvHChumFFJCkLybSR+MwjAd9ycLS CNudeKFoeNOIQP5sLrrIQMomIJIWnNMKT+HI3jIQH07ODw87Oe29mo4/w7NeJE//Vz8f A56uRx/mzrJC4HEvClJl0o5lSO78VmSnP2IyU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2cPti3IGTLLCYIG7mM22dAT5T5carpc7yG3r/UBGnYA=; b=PNEx11mpiLuVf7N3IxlLZFvZ//X9mGNyzN/7wu8kG/oB0qCcRqqM+H8kOV8Be4p4XB Tm1NaK1GtavPLMFQPcaKQzBGutheoBIN10CKlyzwRGyhTIePw2j65dAiu3FX+9wWL8CX 1BJxWmsPqfPQGsWRBOB/ZM6KbiTJ8rM2A9edzr1r+9m/xOBJCKg5zBq65YW23AsgLNTw AAaRwkRVfwkO4yBpN+CtzfECidNcx6dp2cPgHscp1Y7WVF/WM5djzC8bEI+oPfWoQOy+ FBzX2zZk+iJSyTkYGNHJ+qBWgBD/NtXsMSy7PL3EeCbPiEkkGez8FfP76EvAHz9eY1GZ Cmcg==
X-Gm-Message-State: APjAAAXoyy23d0qjiaZeDTAbcx8/EbGbDTpAOqlnfNL8HHIUIM1MsTuc ucLTNRkoNm1bRGlFsAqeNCf0dw==
X-Google-Smtp-Source: APXvYqzkfZKKyy7Y+SbGLE18Gl+hNVgJje2ae87O9TKXeufOGpH65rk79VFuYQW8pqObab1wpCgoVg==
X-Received: by 2002:aa7:951c:: with SMTP id b28mr2707422pfp.97.1581420123677; Tue, 11 Feb 2020 03:22:03 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id l15sm3529163pgi.31.2020. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Feb 2020 03:22:03 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.\))
From: Hitoshi Asaeda <>
In-Reply-To: <>
Date: Tue, 11 Feb 2020 20:22:00 +0900
Cc: ICNRG <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Dirk Kutscher <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [icnrg] Last Call: draft-oran-icnrg-qosarch
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Feb 2020 11:22:06 -0000


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. 



> On Feb 11, 2020, at 20:00, Dirk Kutscher <> wrote:
> Thanks, Colin.
>> I think it’s 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)
> Yes, let’s do that. I will draft some lines from an ICNRG perspective that Dave could consider including here.
>> Also, the short title (“ICN QoS Architecture”) on each page can be read as perhaps implying a stronger status than intended. Is there space to change it to something like “Proposed ICN QoS Architecture” instead?
> Yes, good point. Dave already noted that “ICN QoS Architecture Considerations” (or something in that direction) is more appropriate and will change the draft accordingly.
> 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.
> Thanks,
> Dirk
>> Colin
>>> We (Dave as the author, and Börje & 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.
>>> 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.
>>> Best regards,
>>> Dirk
>>> _______________________________________________
>>> icnrg mailing list
>> -- 
>> Colin Perkins
>> _______________________________________________
>> icnrg mailing list
> _______________________________________________
> icnrg mailing list