Re: [core] Traffic characteristics (Re: I-D Action: draft-ietf-core-coap-pm-00.txt)

Giuseppe Fioccola <> Thu, 20 April 2023 09:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32912C15154F for <>; Thu, 20 Apr 2023 02:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id roHI1o-ieCkX for <>; Thu, 20 Apr 2023 02:04:08 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 96487C151524 for <>; Thu, 20 Apr 2023 02:04:08 -0700 (PDT)
Received: from (unknown []) by (SkyGuard) with ESMTP id 4Q2BTp4NnWz6J7DS; Thu, 20 Apr 2023 17:01:18 +0800 (CST)
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Thu, 20 Apr 2023 11:04:06 +0200
Received: from ([]) by ([]) with mapi id 15.01.2507.023; Thu, 20 Apr 2023 11:04:06 +0200
From: Giuseppe Fioccola <>
To: Carsten Bormann <>, "" <>
Thread-Topic: [core] Traffic characteristics (Re: I-D Action: draft-ietf-core-coap-pm-00.txt)
Thread-Index: AQHZcv92rw2sBeBFWUut/qHiGHrwsq8z2Xhw
Date: Thu, 20 Apr 2023 09:04:06 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [core] Traffic characteristics (Re: I-D Action: draft-ietf-core-coap-pm-00.txt)
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 20 Apr 2023 09:04:13 -0000

Hi Carsten,
Thank you for raising this point.
Yes, both spin bit and square bit methods enable the measurement on the traffic flowing between the endpoints. Therefore, it is possible to perform the measurements only if the packet stream is present. This can be acceptable, because it is more interesting to measure the traffic when the traffic is really flowing, instead of using synthetic traffic.
As an example, in the case of temperature updates once a minute, the measurements can be done accordingly once a minute and for the duration of the packet stream. But, if we want to perform the measurements more often and even if no traffic is flowing, it may be possible to consider to send keep-alive packets to have a more continuous flow.
Maybe it is worth mentioning these considerations in the next version of the draft.



-----Original Message-----
From: core <> On Behalf Of Carsten Bormann
Sent: Wednesday, April 19, 2023 10:42 PM
Subject: [core] Traffic characteristics (Re: I-D Action: draft-ietf-core-coap-pm-00.txt)

Thank you to the authors for contributing this work.

<no hat>

Given that we now have completed adoption, we should enter a discussion of technical considerations.

One issue that comes up in my mind is whether the characteristics of CoAP traffic tend to be close enough to the characteristics of traffic for which the Spin and Square bits have been developed.  Specifically, both of these bits seem to assume there is always some traffic flowing to which these bits can be attached.  But CoAP traffic can be very intermittent (getting a temperature update once a minute is on the frequent side…).  

How well do Spin/Square work with traffic of this kind?

Grüße, Carsten

> On 2023-04-19, at 15:33, wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories. This Internet-Draft is a work item of the Constrained 
> RESTful Environments (CORE) WG of the IETF.
>   Title           : Constrained Application Protocol (CoAP) Performance Measurement Option
>   Authors         : Giuseppe Fioccola
>                     Tianran Zhou
>                     Mauro Cociglio
>                     Fabio Bulgarella
>                     Massimo Nilo
>                     Fabrizio Milan
>   Filename        : draft-ietf-core-coap-pm-00.txt
>   Pages           : 16
>   Date            : 2023-04-19
> Abstract:
>   This document specifies a method for the Performance Measurement of
>   the Constrained Application Protocol (CoAP).  A new CoAP option is
>   defined in order to enable network telemetry both end-to-end and hop-
>   by-hop.  The endpoints cooperate by marking and, possibly, mirroring
>   information on the round-trip connection.
> The IETF datatracker status page for this Internet-Draft is:
> There is also an htmlized version available at:

core mailing list