Re: [Rats] About current RATS drafts

H Y <yuuhei.hayashi@gmail.com> Fri, 01 November 2019 23:27 UTC

Return-Path: <yuuhei.hayashi@gmail.com>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8045D1208D2 for <rats@ietfa.amsl.com>; Fri, 1 Nov 2019 16:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DC_PNG_UNO_LARGO=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 oxS-2GoSuEfc for <rats@ietfa.amsl.com>; Fri, 1 Nov 2019 16:27:24 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 6DF99120861 for <rats@ietf.org>; Fri, 1 Nov 2019 16:27:23 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id q64so11749514ljb.12 for <rats@ietf.org>; Fri, 01 Nov 2019 16:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=V7XmUzgjnE2SId/lxJ2TfHKL09RBXmHlBH9KxBzlkoA=; b=MDmZ7n7c659JEJxWx91hkXFGKcDfrnIfIBbZTvv3ga2rsgopywhopmnrnIudnBfyl6 LwTT+VROiPoOx8syMXzlLq3qI3AcQ5y/glNk93cMvGApBTywLEt29+iWpmXi1gjiG1kf rwt3ErR4wpVLgMYhLP/4FqQ9/xOb5vbiwwSaYuum4Qkfeql1AnUmuptI/zmA7foGdxlo mKakLDCOjPQhH6BHxV6JRmkWl/k22lcqVr4a5kWq3NKwExADgaXxx1rkdqm4QzVDjpZL DmM2CAxOfUDyiTplGTL1hHJaAI1BnMoz0WELa7N09xuOkhz6NxEiJ7qNq2xEFoNgN2/X +eXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=V7XmUzgjnE2SId/lxJ2TfHKL09RBXmHlBH9KxBzlkoA=; b=cK9Ekp5ezt2sqvWnNjOarhMojQWiDj+2vBDkUC/W/qNEpzVwebWdlA9qPCGyu+QfRI PQF7JZFFTuB4UbJu6HjsOa3jzxqo1Yje6ADGRKl+ZpjIdFHSo49QYuzNbyb0GrZUhkvm TT42xMQoYt16lRR/WXahrruROeMNU0s9eQyjRuoiGpAp3eX+KgdMMyqinXBypodGXn3z za7Qr4TS/31GRdUFvqV+V0u6Czc7dHfYBI9rIOEJnKS+y3FVymy+h7v5OAboyNI1+x39 1Bcf6nfbySNiWEeh9ufwl2mCqxb/pWPmYbDAfVFPhIVn3KCszRZGj2STCeNoFCb42wIR ayIw==
X-Gm-Message-State: APjAAAW5nPDQfZqUesjp1+bQXXvAdvJoZw4Er7rA4BoPuot+U7hHwxh7 twp6GSScnLvBQqDXh8JRsvA4ounnvvQtt/1XhpJVHhgLJVI=
X-Google-Smtp-Source: APXvYqzX/SUk31ZUmdKTd3s3e6x5qKHY98FQHGOdHBR67lhZJUpuypbmd05heicoub/Z1cCJX6LSp1+/CSHnVxlsY3w=
X-Received: by 2002:a2e:9107:: with SMTP id m7mr9805695ljg.113.1572650841214; Fri, 01 Nov 2019 16:27:21 -0700 (PDT)
MIME-Version: 1.0
References: <CAA8pjUMnQ7defSFS8Wz6uw5V1ahiGZMUdSrgmwM6Bh25WN8Ohw@mail.gmail.com> <26A6D463-2635-456F-B0F9-78075B07FDC4@island-resort.com>
In-Reply-To: <26A6D463-2635-456F-B0F9-78075B07FDC4@island-resort.com>
From: H Y <yuuhei.hayashi@gmail.com>
Date: Sat, 2 Nov 2019 08:27:09 +0900
Message-ID: <CAA8pjUMkvA7j2U8-g42fust-Vj=OXH5uuRxNm9bhwWfrR-kv9g@mail.gmail.com>
To: Laurence Lundblade <lgl@island-resort.com>, henk.birkholz@sit.fraunhofer.de
Cc: rats@ietf.org
Content-Type: multipart/related; boundary="000000000000bf2d5a0596514e48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/q0x49KRUiw66pH3GJdr3MQo8PpY>
Subject: Re: [Rats] About current RATS drafts
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Nov 2019 23:27:26 -0000

Hi Henk, Laurence,

Thank you for confirming my understandings. Your comments really help me to
read current drafts. :-)

Thanks,
Yuhei

2019年11月1日(金) 23:25 Laurence Lundblade <lgl@island-resort.com>om>:

> Hello,
>
> A frame up that works for me is to think about 1) the claims, the
> attestation format and its details and 2) the transport / conveyance and
> its details.
>
> In the TPM/TCG world the claims and attestation format is locked down by
> what TPM chips do today. It is a set of registers that hold hash values
> used to measure software.  In the EAT world, which typically implements on
> fully functional CPUs, the claims and attestation format is not at all
> locked down and our work is to define it (the eat draft).
>
> A lot of the network and router folks have been putting TPMs into their
> routers and now need a way to get the TPM output off the router to the
> network management center. This world runs off of Yang protocols. The main
> interest there is a very specific Yang-based way to move TPM output. This
> is the yang, tuda and pubsub drafts.
>
> The EAT use cases are more about TEE’s and lining up with
> end-user-application-oriented uses like FIDO and the Android key store.
> They make use of all the existing transports used by application protocol
> (mainly HTTP) so there’s no worry about defining transport.
>
> I think a few of us see EAT as the more general and flexible attestation
> format that will eventually replace the TPM format. Because EAT can use
> CBOR and COSE which are carefully designed for constrained devices there is
> some hope that it can go into TPM-like HW.
>
> The architecture draft is trying to tie the two together in a sort of
> unified field theory. Seems possible, but hard to me.
>
> LL
>
>
>
>
>
> On Nov 1, 2019, at 5:08 AM, H Y <yuuhei.hayashi@gmail.com> wrote:
>
> Hi all,
>
> I'm Yuhei Hayashi, network security researcher of NTT in Japan. I
> learned about the existence of RATS WG at IETF 105.
>
> I'm interested in the work of RATS WG and I'm trying to understand it.
> So, I'm firstly trying to understand which drafts contain the
> standards listed in the charter.
>
> I will attach the result of organizing it from my own point of view.
> I'm glad if you confirm that my understanding is correct, if possible.
>
> Thanks,
> Yuhei
> --
> ----------------------------------
> Yuuhei HAYASHI
> yuuhei.hayashi@gmail.com
> ----------------------------------
> <RATS_drafts.pdf>_______________________________________________
> RATS mailing list
> RATS@ietf.org
> https://www.ietf.org/mailman/listinfo/rats
>
>
>

-- 
----------------------------------
Yuuhei HAYASHI
08065300884
yuuhei.hayashi@gmail.com
iehuuy_0220@docomo.ne.jp
----------------------------------