Re: [T2TRG] [irsg] draft-irtf-t2trg-iot-seccons ready to publish

Mohit <mohit.sethi@nomadiclab.com> Tue, 22 May 2018 07:12 UTC

Return-Path: <mohit.sethi@nomadiclab.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F00D512EABA; Tue, 22 May 2018 00:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=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 57d_jSCWVE0Y; Tue, 22 May 2018 00:12:04 -0700 (PDT)
Received: from gw.nomadiclab.com (gw.nomadiclab.com [193.234.218.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4DAC812EAB4; Tue, 22 May 2018 00:12:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 62BBD5006E5; Tue, 22 May 2018 10:12:02 +0300 (EEST)
Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TW7xvM6jO9As; Tue, 22 May 2018 10:12:00 +0300 (EEST)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTP id 0EAAB500042; Tue, 22 May 2018 10:11:59 +0300 (EEST)
To: Mohit Sethi <mohit.m.sethi@ericsson.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Jim Schaad <ietf@augustcellars.com>, irtf-chair@irtf.org
Cc: t2trg@irtf.org, irsg@irtf.org
References: <00ed01d3efd8$50af5a80$f20e0f80$@augustcellars.com> <930a5bdf-1f29-0944-d198-ea21044f9490@cs.tcd.ie> <3958f461-63a1-971f-babd-49b068667056@ericsson.com>
From: Mohit <mohit.sethi@nomadiclab.com>
Message-ID: <499092b6-11ad-d84e-0db4-b54d321f6be1@nomadiclab.com>
Date: Tue, 22 May 2018 10:11:59 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <3958f461-63a1-971f-babd-49b068667056@ericsson.com>
Content-Type: multipart/alternative; boundary="------------2D779C622C0389198D79608D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/hsek3z2LodHco4g0E_PlYB0_GBo>
Subject: Re: [T2TRG] [irsg] draft-irtf-t2trg-iot-seccons ready to publish
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 07:12:09 -0000

Hi Stephen:

I blame the early morning coffee jitters for the misspelling your name. 
Sorry :)

On 05/22/2018 10:09 AM, Mohit Sethi wrote:
>
> Hi Stefan,
>
> My co-author, Oscar knows and understands homomorphic encryption well 
> so perhaps he can comment more. This is all the text we have on 
> homomorphic encryption in the draft (listed as one of the many options 
> of end-to-end security in presence of middleboxes):
>
>>     4.  Homomorphic encryption techniques can be used in the middlebox to
>>         perform certain operations.  However, this is limited to data
>>         processing involving arithmetic operations.  Furthermore,
>>         performance of existing libraries, for example, SEAL [SEAL 
>> <https://tools.ietf.org/html/draft-irtf-t2trg-iot-seccons-15#ref-SEAL>] is
>>         still too limited and homomorphic encryption techniques are not
>>         widely applicable yet.
>
> The way I read this: homomorphic encryption exists, can only work on 
> arithmetic operations, performance is still too limited and 
> homomorphic techniques are not widely applicable yet? I don't see how 
> this text is optimistic about homomorphic crypto?
>
> --Mohit
> On 05/20/2018 01:50 PM, Stephen Farrell wrote:
>> Hi Jim,
>>
>> Thanks for the comprehensive and nicely objective write-up. Seems like a
>> good example for us all.
>>
>> On 20/05/18 02:17, Jim Schaad wrote:
>>> Stephen Farrell did a review of the document back in February.  He made many
>>> suggestions to the document which were mainly adopted, but still expressed
>>> some skepticism about the final worth of the document.   What I read as his
>>> major reservations were 1) A worry that this document was expressed as a
>>> sales pitch and as such might have some limited long term applicability,  2)
>>> A worry that some of the references to current work (SUIT and OSCORE being
>>> two) in a long term document may not be useful, and 3) Some of the document
>>> might be better if it were re-organized.
>> That's a bit more negative than I ended up. Point 3 still stands yes,
>> but definitely ought not be any barrier to publication. IIRC, my main
>> outstanding issue was the unfounded optimism wrt homomorphic crypto.
>> Note that I'm not asking that the document not be published on that
>> basis. (I do predict that everyone will regret the current text on
>> that down the road though;-)
>>
>> S.
>>
>>
>> _______________________________________________
>> T2TRG mailing list
>> T2TRG@irtf.org
>> https://www.irtf.org/mailman/listinfo/t2trg
>
>
>
> _______________________________________________
> T2TRG mailing list
> T2TRG@irtf.org
> https://www.irtf.org/mailman/listinfo/t2trg