Re: [core] Mirja Kühlewind's No Objection on draft-ietf-core-senml-etch-05: (with COMMENT)

Carsten Bormann <cabo@tzi.org> Thu, 29 August 2019 08:28 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 8F9F2120103; Thu, 29 Aug 2019 01:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 5dB44JQBR9jQ; Thu, 29 Aug 2019 01:28:06 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69EDE1200C7; Thu, 29 Aug 2019 01:28:06 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46JwjJ1pHbz10cP; Thu, 29 Aug 2019 10:28:04 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <8707800F-284D-41F7-8D98-8BAD55340DC5@ericsson.com>
Date: Thu, 29 Aug 2019 10:28:01 +0200
Cc: "draft-ietf-core-senml-etch@ietf.org" <draft-ietf-core-senml-etch@ietf.org>, "core-chairs@ietf.org" <core-chairs@ietf.org>, "core@ietf.org" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 588760080.34867-cb06ff2c950a7e998c60a53e74001686
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7BBA2A3-2FEB-494A-8700-828BCC23B1D5@tzi.org>
References: <156699900565.32507.5256098120423983260.idtracker@ietfa.amsl.com> <8707800F-284D-41F7-8D98-8BAD55340DC5@ericsson.com>
To: Ari Keränen <ari.keranen@ericsson.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/000zFKomaC5jPHk8FQo3EEFuui0>
Subject: Re: [core] Mirja Kühlewind's No Objection on draft-ietf-core-senml-etch-05: (with COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 29 Aug 2019 08:28:09 -0000

Off-IESG comment:

Do we know how a made-up example would be better?
It’s not like you need to learn the IPSO world to understand this example.
(But if you are reading the document, you may already know about IPSO anyway…)

Grüße, Carsten


> On Aug 29, 2019, at 10:13, Ari Keränen <ari.keranen@ericsson.com> wrote:
> 
> Thank you for the review Mirja!
> 
>> On 28 Aug 2019, at 16.30, Mirja Kühlewind via Datatracker <noreply@ietf.org> wrote:
>> 
>> Mirja Kühlewind has entered the following ballot position for
>> draft-ietf-core-senml-etch-05: No Objection
> [...]
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>> 
>> Just one minor comment: I guess it okay to use IPSO dimmable light smart object
>> as one real life example, however, one could also just use a made-up generic
>> example instead as I guess it's often done in RFCs.
> 
> We used IPSO object as an example here since the original design and requirements for this work come from the LwM2M protocol that commonly uses IPSO objects. 
> 
> That said, there's no strong need to do it that way and we could change that also to a more generic made-up example if that would be more suitable here.
> 
> 
> Cheers,
> Ari