Re: [EAT] [Rats] Rats and EAT

Yaron Sheffer <yaronf.ietf@gmail.com> Sun, 15 July 2018 21:05 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: eat@ietfa.amsl.com
Delivered-To: eat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 628E4130E4D; Sun, 15 Jul 2018 14:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.457
X-Spam-Level:
X-Spam-Status: No, score=-0.457 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_06_12=1.543, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 T02Dr3MUNAA6; Sun, 15 Jul 2018 14:05:18 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 D9071130EEB; Sun, 15 Jul 2018 14:05:16 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id n17-v6so13861603wmh.2; Sun, 15 Jul 2018 14:05:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=R2szMuRtkbJtZS0gF6UEcXxiqWER2uzcHLKSvpCcDzk=; b=lBqV/dXprFx9vxshD+fyEVn/suPmQOtjMcrCzHTzFVXWmWrH300VBA+X0LMRZSgL40 DqHLWrdlfvmaMJCoFB69K3LVL6IcBircTFUbbmceI0SRa7oJC7B08458DsWj56co3/nN Ym+TYWyD0mRvlL2E70IwMvhDaRyoLrSEKkDZmSh5s4tDSSR9KYZbOxR6xWDzdB0j5x8Y m/7vyo5vcloYryfst3c6LttkChVt7PUW01NcKCe/tyuOIjcLhv+rKART3eF+LKuLWUiM HV0Jt9dVbKvfFFoMNYCYgIz3DbhhU/Y2Iq/qUKDpm8xuH1IzlGYyrTC4QWsutkOR4+wx bGgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=R2szMuRtkbJtZS0gF6UEcXxiqWER2uzcHLKSvpCcDzk=; b=bUYwxbjwt2gqVExo0sU/qh2YiaVS4b/kZoPSh0YRjZnHrboWCmQlH8q5Kg6ODgmGAA pGPWMAa+TgqOAvVmjTTTxDkAju6G1DnP54H3ae7FvdCexOHibPcTwfif9CRH1V3KrOWS ilSW0HpCOc7txxX5qg2udpab6A067jk2Q+JVg34wC9CCilSEi9ch0Nsvulircqg4Ifxv dlUA2Z05uywIOjYEK4vsM0yRGczgPNwuWAXs7Arj1HqzMfD9ANDKd0RIEm2rvRje6RMD f79N1RI38aAo7Re0N13OHIeWXLpmOGVNNGLXc14mcKL6gRJqy6vh6BMfefkUrrr2Fuvs ukQQ==
X-Gm-Message-State: AOUpUlGHrXUQSD853TfN6M9lBHH6CWCN6wkODAKfdvSukwqv85ferjaZ YimPZhiintZBziDn1av/Jjp6/EcS
X-Google-Smtp-Source: AAOMgpdXqEKqI3vHxAW9fhSDPm7x8RkFmSFToXNNWmI7KwrSQrDLMTIjlKRAW0D0e6Qwc1sR/aLjXQ==
X-Received: by 2002:a1c:a813:: with SMTP id r19-v6mr7950494wme.100.1531688715124; Sun, 15 Jul 2018 14:05:15 -0700 (PDT)
Received: from [192.168.43.74] ([2.53.27.241]) by smtp.gmail.com with ESMTPSA id h7-v6sm17616010wrq.41.2018.07.15.14.05.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Jul 2018 14:05:14 -0700 (PDT)
To: Laurence Lundblade <lgl@island-resort.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "eat@ietf.org" <eat@ietf.org>, "rats@ietf.org" <rats@ietf.org>
References: <eb1d952b-1e73-4c41-bf12-82299b44ff3d@me.com> <0FE06C34-D430-451C-834B-0A39082160BA@island-resort.com> <32302.1531356373@localhost> <678D5903-580B-4AD7-87D9-5A779A005194@island-resort.com>
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <e55daa1f-1158-d226-f35a-0244ea4a1016@gmail.com>
Date: Sun, 15 Jul 2018 15:50:20 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <678D5903-580B-4AD7-87D9-5A779A005194@island-resort.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/0cxXqAaGViBjbzoVnDaPei1ykpU>
Subject: Re: [EAT] [Rats] Rats and EAT
X-BeenThere: eat@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: EAT - Entity Attestation Token <eat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eat>, <mailto:eat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eat/>
List-Post: <mailto:eat@ietf.org>
List-Help: <mailto:eat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eat>, <mailto:eat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jul 2018 21:05:21 -0000

On 12/07/18 19:20, Laurence Lundblade wrote:
> On Jul 11, 2018, at 5:46 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>>
>> Laurence Lundblade <lgl@island-resort.com> wrote:
>>> NEA is oriented around network management, trying to track the security
>>> posture of devices in an enterprise's network. EAT is broadly targeted
>>> at establishing trust between entities, often consumer devices (phones,
>>> refrigerators, cars...) and servers/services (online banking, IoT
>>> services, enterprise authentication…).
>> That's a surprising claim that EAT is going to broker trust between my phone
>> and my refrigerator.    Will it do this via third parties, or directly?
> This is not any direct goal of EAT. Let me say it better:
>
> EAT is broadly targeted at providing some basis for establishing trust in scenarios like this:
>   - An online banking website trusting the phone and app used to show account balance
>   - A Fortune 500 corp trusting the phone and web browser to allow access to corp data
>   - An IoT backend trusting some refrigerators that it is to provide service to (e.g. shopping, milk expiration…)
>
> Maybe someday EAT will be part of a phone-fridge trust solution, but one step at a time.
>
I don't see how in this day and age we can consider a solution that 
covers IOT and phones but not other devices that run an operating 
system, such as laptops and servers.

So maybe NEA was too complex or ambitious, and we should scale these 
ambitions down. But desktops and servers, both physical and virtual, 
should be in scope.

Thanks,
     Yaron