IETF Logo Mail Archive

Re: [Rats] EAT Profiles

Carl Wallace <carl@redhoundsoftware.com> Mon, 19 September 2022 14:11 UTC

Return-Path: <carl@redhoundsoftware.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 9FBB3C1524B1 for <rats@ietfa.amsl.com>; Mon, 19 Sep 2022 07:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhoundsoftware.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4feIEKWVKgK for <rats@ietfa.amsl.com>; Mon, 19 Sep 2022 07:11:25 -0700 (PDT)
Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A53A2C14F607 for <rats@ietf.org>; Mon, 19 Sep 2022 07:11:25 -0700 (PDT)
Received: by mail-pj1-x1032.google.com with SMTP id bu5-20020a17090aee4500b00202e9ca2182so6818242pjb.0 for <rats@ietf.org>; Mon, 19 Sep 2022 07:11:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhoundsoftware.com; s=google; h=content-transfer-encoding:mime-version:in-reply-to:references :thread-topic:message-id:to:from:subject:date:user-agent:from:to:cc :subject:date; bh=yXD3RWETtouiSuWymiEIXqoh0/T3dgr85RxV18C8LzU=; b=o7GYYlsbStpPG5CmSyM96S9ZhPSyrGSDyuPCm3ivNw/aPExI3t56llqDoc4fF6sNwQ xiF4m7uo3ZgEeZYgFQ3fWFOwQ3KbmRycae2VJI5llDdMgDf3+z2EHRUuXuxi5NzFj227 un5e9lQHJcCiMCcC9hMFFVBAMwPjW9ZlkIb0I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:in-reply-to:references :thread-topic:message-id:to:from:subject:date:user-agent :x-gm-message-state:from:to:cc:subject:date; bh=yXD3RWETtouiSuWymiEIXqoh0/T3dgr85RxV18C8LzU=; b=EbHz597AdnVrLvKDDDfWciEMCD9KfjwCoJq9mqllOcLPErWmOY2TKJGx+Y49vUhoAK bwgOVrHBkCWJNm13aPqMwsNkfqAIaEM3HZvuCkG71EnbcyhxmncDCcNu5KJx/fod1vyb ypq2/UTPBXgEer61BwoM0/CdbrdjAvIm8rWuQian/XEwA0bts3gSc89DPxxEBFop3RLl PkdIEMO63btg67NFpRXm71/5SlC+r4FQ8NvyzTX/ruj0DWF41CxS91lBSlZ4wJCRLl0y MnY33tjECo4/0sacnNTz495oJI66DV3T8NSPF1Ik46pQ3EqZVdkLZvjshaVhS9FVjNGb AXlA==
X-Gm-Message-State: ACrzQf1YVlb9cppmuba7yxYBBhCcmyUY3n2UBsFQN2c3uAZK6Gsvx+QW i0Pa2GQXsYPmnDAgJZV88jhYvA==
X-Google-Smtp-Source: AMsMyM4E/JRjiXfvp5uymbCFMaxpzEbcJNVZWrzWUYdCPOyK6H+kly/HRWgZYYt8je0rK3o6LXacJA==
X-Received: by 2002:a17:90b:4a43:b0:202:7706:73d7 with SMTP id lb3-20020a17090b4a4300b00202770673d7mr20088537pjb.137.1663596684763; Mon, 19 Sep 2022 07:11:24 -0700 (PDT)
Received: from [192.168.1.2] ([2600:1010:b12f:db4f:ddeb:37a6:f74f:be4d]) by smtp.gmail.com with ESMTPSA id p129-20020a622987000000b0053e84617fe7sm20384793pfp.106.2022.09.19.07.11.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Sep 2022 07:11:24 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.65.22091101
Date: Mon, 19 Sep 2022 07:11:17 -0700
From: Carl Wallace <carl@redhoundsoftware.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "rats@ietf.org" <rats@ietf.org>
Message-ID: <73263C15-D995-404D-843D-13C2ED4B0BC5@redhoundsoftware.com>
Thread-Topic: [Rats] EAT Profiles
References: <71934.1663019954@dooku> <DBBPR08MB5915AC23726BF997EB9E44C4FA489@DBBPR08MB5915.eurprd08.prod.outlook.com> <19805.1663344806@dooku> <AS8PR08MB5911DB2FE9608541698983B0FA4D9@AS8PR08MB5911.eurprd08.prod.outlook.com> <636099.1663593501@dooku>
In-Reply-To: <636099.1663593501@dooku>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/rs4M63Ltlk2O409uS-u-Ax2uOGQ>
Subject: Re: [Rats] EAT Profiles
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 19 Sep 2022 14:11:29 -0000

Inline...

On 9/19/22, 6:18 AM, "RATS on behalf of Michael Richardson" <rats-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:


    Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
        > [Hannes] We have created a library that produced an EAT based on our
        > profile and it was not too complex.

    You missed the point.
    You create *A* library that deals with *your* profile.

[CW] Why is it a problem for a product vendor to produce a library for *their* profile but not *someone else's* profile? 

    So, we need N libraries for N-profiles, and since the EAT document has quite
    a large number of possible combinations, each use of EAT will wind up with
    its own library.  There will be no reuse, which was the point of doing this work.

[CW] This does not follow from Hannes' statement. Another vendor may use some library to produce EATs for their profile and yet another vendor may use the same library to produce EATs for a different profile. From elsewhere in the threads, I also do not see why a cookbook of profiles (i.e., your yellow, brown, red, etc. examples) could not be produced referencing EAT as a base specification.

<snip>

v2.23.0 | Report a Bug | By Email