Hi Ben, all,
Thank you for zooming on these two points.
Please see below.
Cheers,
Med
> -----Message d'origine-----
> De : Dots <dots-bounces@xxxxxxxx> De la part de Benjamin Kaduk
> Envoyé : mercredi 26 janvier 2022 01:59
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@xxxxxxxxxx>
> Cc : last-call@xxxxxxxx; gen-art@xxxxxxxx; draft-ietf-dots-
> telemetry.all@xxxxxxxx; dots@xxxxxxxx; Robert Sparks
> <rjsparks@xxxxxxxxxxx>
> 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@xxxxxxxxxx
> wrote:
> > Hi Robert,
> >
> > Many thanks for the careful review.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De : Robert Sparks via Datatracker <noreply@xxxxxxxx> Envoyé :
> > > samedi 22 janvier 2022 00:01 À : gen-art@xxxxxxxx Cc :
> > > dots@xxxxxxxx; draft-ietf-dots-telemetry.all@xxxxxxxx; last-
> > > call@xxxxxxxx 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.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
