Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-19

mohamed.boucadair@orange.com Wed, 26 January 2022 14:26 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827193A11D5; Wed, 26 Jan 2022 06:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3MAi_Q1hH7gC; Wed, 26 Jan 2022 06:26:50 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E48443A11CC; Wed, 26 Jan 2022 06:26:49 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar23.francetelecom.fr (ESMTP service) with ESMTPS id 4JkQyc011PzBrm9; Wed, 26 Jan 2022 15:26:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1643207208; bh=PTVKSLVHogo84HjISl9eoF9p4IjlsIkTEmt0DfN6MuM=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=F/dPho4Vc85A7U7COZxPUuPy4Wrq5fqp/ER8uY+9hAcv0HIGS/WOOyWeLVJB4scP0 JujkdBUyBBhXEZPsb6XXMHewvAjvjhlqgBFEHxlfHpE11Ho0oWt+AAev0y4ymAPngS nx2rHK4Hymk3r6RU+ahe4eyfVBJryz1W0WKzJx16oMehjV/LCF5lQucQgqu6KXPmJC zHUMuAuMo6B3WZT3x5yx0itPqOCNzhefRc8x4EI/Q2P5ZhQ8nXzzzmihrMvDSgmoTN lvT0/4zlLyvsiva5ACjbWC8bHyMX/8KWygB3YooIhJsLycz1PYJjbgKX6vzgjdG7kq UeM1L3CIlKLGQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar00.francetelecom.fr (ESMTP service) with ESMTPS id 4JkQyb5dyGzCqnc; Wed, 26 Jan 2022 15:26:47 +0100 (CET)
From: mohamed.boucadair@orange.com
To: Benjamin Kaduk <kaduk@mit.edu>
CC: "last-call@ietf.org" <last-call@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dots-telemetry.all@ietf.org" <draft-ietf-dots-telemetry.all@ietf.org>, "dots@ietf.org" <dots@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
Thread-Index: AQHYEk/sxauU7vDzkU+2swdyv6P6Eax1Wh3Q
Content-Class:
Date: Wed, 26 Jan 2022 14:26:46 +0000
Message-ID: <4705_1643207207_61F15A27_4705_162_1_787AE7BB302AE849A7480A190F8B9330354873A2@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <164280608786.26256.18141980913416166060@ietfa.amsl.com> <21506_1643026113_61EE96C1_21506_165_1_787AE7BB302AE849A7480A190F8B93303548581B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20220126005843.GV11486@mit.edu>
In-Reply-To: <20220126005843.GV11486@mit.edu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-01-26T14:17:02Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=8e5a05c1-6a68-4cf9-9948-7e2991aae84a; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/mfSX0mL6tbW3qs_i2qwZEW9E0xI>
Subject: Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-19
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2022 14:26:55 -0000

Hi Ben, all, 

Thank you for zooming on these two points. 

Please see below. 

Cheers,
Med

> -----Message d'origine-----
> De : Dots <dots-bounces@ietf.org> De la part de Benjamin Kaduk
> Envoyé : mercredi 26 janvier 2022 01:59
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc : last-call@ietf.org; gen-art@ietf.org; draft-ietf-dots-
> telemetry.all@ietf.org; dots@ietf.org; Robert Sparks
> <rjsparks@nostrum.com>
> Objet : Re: [Dots] Genart last call review of draft-ietf-dots-telemetry-
> 19
> 
> Hi Med, Robert,
> 
> I echo the thanks to Robert for the review.
> A few notes inline (trimming as needed)...
> 
> On Mon, Jan 24, 2022 at 12:08:32PM +0000, mohamed.boucadair@orange.com
> wrote:
> > Hi Robert,
> >
> > Many thanks for the careful review.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Robert Sparks via Datatracker <noreply@ietf.org> Envoyé :
> > > samedi 22 janvier 2022 00:01 À : gen-art@ietf.org Cc :
> > > dots@ietf.org; draft-ietf-dots-telemetry.all@ietf.org; last-
> > > call@ietf.org Objet : Genart last call review of
> > > draft-ietf-dots-telemetry-19
> > >
> [...]
> > > In 6.1.2, I'm confused by the requirement that "'tsid' values MUST
> > > increase monotonically when a new PUT is generated"
> >
> > [Med] The full context is:
> >
> >       " (when a new PUT is generated
> >         by a DOTS client to convey new configuration parameters for
> the
> >         telemetry). "
> 
> I think I see how this causes Robert to be confused.
> In particular, a PUT is just a single CoAP request, but what we really
> mean here is the persistent configuration object on the server that's
> identified by the 'tsid'.  So, we should impose the requirement not on a
> "new PUT"
> being generated, but rather that when we allocate a new tsid value for a
> new configuration object, we must make that allocation in the monotonic
> manner.
> 

[Med] We made this change:

OLD:
   tsid:  Telemetry Setup Identifier is an identifier for the DOTS
        telemetry setup configuration data represented as an integer.
        This identifier MUST be generated by DOTS clients.  'tsid'
        values MUST increase monotonically (when a new PUT is generated
        by a DOTS client to convey new configuration parameters for the
        telemetry).

NEW:
   tsid:  Telemetry Setup Identifier is an identifier for the DOTS
        telemetry setup configuration data represented as an integer.
        This identifier MUST be generated by DOTS clients.  'tsid'
        values MUST increase monotonically whenever new configuration
        parameters need to be conveyed by the DOTS client.

(also tweaked a similar text for tmid)

I hope this removes the confusion. 


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.