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

Carsten Bormann <cabo@tzi.org> Wed, 19 April 2023 20:41 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C97DC152D84 for <core@ietfa.amsl.com>; Wed, 19 Apr 2023 13:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level:
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjQszcMZnT2G for <core@ietfa.amsl.com>; Wed, 19 Apr 2023 13:41:42 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEE6CC151B3A for <core@ietf.org>; Wed, 19 Apr 2023 13:41:41 -0700 (PDT)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Q1t4K6VTDzDCbQ; Wed, 19 Apr 2023 22:41:37 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <168191123329.30918.12442488585488693919@ietfa.amsl.com>
Date: Wed, 19 Apr 2023 22:41:37 +0200
X-Mao-Original-Outgoing-Id: 703629697.320329-154b543e6ce075a66aa8493ee88cd775
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F997B01-372B-496C-BD18-A8CF329473E0@tzi.org>
References: <168191123329.30918.12442488585488693919@ietfa.amsl.com>
To: core@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/GJz2Qpjc_wcvYzsGMJXS6VozszI>
Subject: [core] Traffic characteristics (Re: I-D Action: draft-ietf-core-coap-pm-00.txt)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2023 20:41:47 -0000

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, internet-drafts@ietf.org 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:
> https://datatracker.ietf.org/doc/draft-ietf-core-coap-pm/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pm-00