Re: [Ace] Working group adoption of draft-vanderstok-ace-est

peter van der Stok <stokcons@xs4all.nl> Fri, 02 February 2018 08:45 UTC

Return-Path: <stokcons@xs4all.nl>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA84E1275F4 for <ace@ietfa.amsl.com>; Fri, 2 Feb 2018 00:45:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 xmWvl9CuvXUk for <ace@ietfa.amsl.com>; Fri, 2 Feb 2018 00:45:27 -0800 (PST)
Received: from lb1-smtp-cloud7.xs4all.net (lb1-smtp-cloud7.xs4all.net [194.109.24.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BF8A1200FC for <ace@ietf.org>; Fri, 2 Feb 2018 00:45:27 -0800 (PST)
Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:212]) by smtp-cloud7.xs4all.net with ESMTPA id hWyKeX5Dg3A62hWyKeTB6L; Fri, 02 Feb 2018 09:45:25 +0100
Received: from AMontpellier-654-1-119-113.w90-0.abo.wanadoo.fr ([90.0.134.113]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Fri, 02 Feb 2018 09:45:24 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Date: Fri, 02 Feb 2018 09:45:24 +0100
From: peter van der Stok <stokcons@xs4all.nl>
To: "Beck, Stefan" <S.Beck@osram.com>
Cc: ace@ietf.org
Organization: vanderstok consultancy
Reply-To: consultancy@vanderstok.org
Mail-Reply-To: consultancy@vanderstok.org
In-Reply-To: <DB6PR07MB341528B44D1320B3525C005C85FA0@DB6PR07MB3415.eurprd07.prod.outlook.com>
References: <010f01d39a08$255723c0$70056b40$@augustcellars.com> <DB6P121MB005604AACB19B414668CE0FF8DFA0@DB6P121MB0056.EURP121.PROD.OUTLOOK.COM> <B36EFBB4-DC5F-456A-9BC0-4D75617BC7B5@ri.se> <DB6PR07MB341528B44D1320B3525C005C85FA0@DB6PR07MB3415.eurprd07.prod.outlook.com>
Message-ID: <1e58208aba210d1473afd8ed6b56508a@xs4all.nl>
X-Sender: stokcons@xs4all.nl
User-Agent: XS4ALL Webmail
X-CMAE-Envelope: MS4wfEpk8aRM4yO/Cl/PbTT26dSHIdsQoJY/jnejnurdpxKHUOz4CzEeF394QFevlr996wLQtSDPOdZdJySZjGaXE7zpQGiY9IbNZ5gumbszhcW8qSyc4aRT crnoUMp8J6fsr5eLwM6QQBm5aZYz6oc93fBhrmogNf5BLBpoe/CYdrgRS1IzN4dbtAIKkb5hvsVJS9KHO5POlU7QzUGz/YSf7706NBKop48cvOu25BaRDD3C
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/a8UrBCZNmkIionUYlBFgkLGmn_s>
Subject: Re: [Ace] Working group adoption of draft-vanderstok-ace-est
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Feb 2018 08:45:31 -0000

Hi Stefan,

Thanks for the support.
I see your point of view; We will look at the text to avoid suggesting 
that EST/https and EST/coaps cannot exist together.

Peter

Beck, Stefan schreef op 2018-02-01 12:51:
> +1
> I support adoption, as it perfectly complements the existing EST work.
> 
> So far, just one general comment:
> The draft could emphasize (e.g. in the intro) that coexistence of EST
> and EST-coaps is supported in target deployments. And you even may
> have a combination of constrained devices in a non-constrained network
> and vice versa.
> If that matches the authors’ view, then some general statements need
> to be adapted. Two examples see below
> 
> Stevie
> 
> 
> 1. Abstract:
>  "This allows low-resource constrained devices to re-use existing EST
> functionality. Example low-resource use cases for EST are: secure
> bootstrapping and certificate enrollment."
> 
> Well, to me those are the two main use cases for non-constrained
> devices using EST, too. So I would write:
>  "This allows low-resource constrained devices to re-use existing EST
> functionality to implement use cases such as secure bootstrapping and
> certificate enrollment."
> 
> 
> 2. Chapter 3.5 (Deployment limits):
> 2a. " Although EST-coaps paves the way for the utilization of EST for
> constrained devices on constrained networks..."
> --> s?on?and/or?
> 
> 2b. " EST-coaps is intended to ensure that EST works for networks of
> constrained devices that choose to limit their communications stack to
> UDP/CoAP."
> --> Remove "networks of"
> 
> ---------------------
> From: Ace [mailto:ace-bounces@ietf.org] On Behalf Of Shahid Raza
> Sent: Thursday, February 01, 2018 11:56 AM
> To: Sandeep Kumar <sandeep.kumar@philips.com>
> Cc: Jim Schaad <ietf@augustcellars.com>; ace@ietf.org
> Subject: Re: [Ace] Working group adoption of draft-vanderstok-ace-est
> 
> As a co-author, I also strongly support the adoption of this draft as
> a WG document. Recall that , we already have an implementation of this
> draft, both in constrained devices (SICS Contiki) and in the Nexus CA
> software. Recently, we have also implemented the "integration of this
> draft into LwM2M", which is part of the latest LwM2M release.
> 
> Best,
> Shahid
> 
> Shahid Raza, PhD
> Director Security Lab and Expert Researcher
> RISE - Research Institutes of Sweden
> Division ICT - RISE SICS
> 
> Isafjordsgatan 22 / Kistagången 16
> 16440, Kista Stockholm
> Mobile: +46 768831797
> shahid.raza@ri.se
> http://www.shahidraza.net
> http://www.sics.se
> The RISE institutes Innventia, SP and Swedish ICT have merged in order
> to become a stronger research and innovation partner for businesses
> and society.
> 
> 
> On 1 Feb 2018, at 11:40, Sandeep Kumar <sandeep.kumar@philips.com> 
> wrote:
> 
> As co-author, I support adoption of the draft as WG document. There is
> need in industry and multiple standardization bodies for this draft.
> 
> Regards
> Sandeep
> 
> -----Original Message-----
> From: Ace [mailto:ace-bounces@ietf.org] On Behalf Of Jim Schaad
> Sent: Tuesday, January 30, 2018 9:23 PM
> To: ace@ietf.org
> Subject: [Ace] Working group adoption of draft-vanderstok-ace-est
> 
> This is the start of a two week call for input on the adoption of the
> WG of the document draft-vanderstok-ace-est.  The document has been
> presented at the last two meetings and has some significant recent
> updates to respond to feedback.  There seemed to be support at the
> last F2F to adopt.
> 
> Please provide feedback to the list/chairs if you believe that this 
> document
> should be adopted as a WG document.    The adoption call will end on 
> Feb 13
> 2018.
> 
> Jim
> 
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
> 
> ________________________________
> The information contained in this email may be confidential and/or
> legally protected under applicable law. The message is intended solely
> for the addressee(s). If you are not the intended recipient, you are
> hereby notified that any use, forwarding, dissemination, or
> reproduction of this email is strictly prohibited and may be unlawful.
> If you are not the intended recipient, please contact the sender by
> return e-mail and destroy all copies of the original email.
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace
> 
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace