IETF Logo Mail Archive

Re: [Rats] Where does a EAT end? - consensus?

Carl Wallace <carl@redhoundsoftware.com> Sat, 04 June 2022 15:14 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 0CE04C159486 for <rats@ietfa.amsl.com>; Sat, 4 Jun 2022 08:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 K8Z28HOO2MVw for <rats@ietfa.amsl.com>; Sat, 4 Jun 2022 08:14:32 -0700 (PDT)
Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 039B1C157B5F for <rats@ietf.org>; Sat, 4 Jun 2022 08:14:31 -0700 (PDT)
Received: by mail-qv1-xf2a.google.com with SMTP id j3so7554579qvn.0 for <rats@ietf.org>; Sat, 04 Jun 2022 08:14:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhoundsoftware.com; s=google; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=nxtwJXm6aTufmm/g7WDf8jbkOK68ysVSN09+soh3tTU=; b=nXOs0/IeCrjjG51OG5V5OkMiqxnOzJqIo2tsJjFhv2QOCRDg2ZyP8Vq6kidbQwFZdD HqW8zCX8ZYxGZ3k2Jrxrvl67H8OBOiu1oykKin349e+l+O6Ga9oNroQUtRROwZ8aMqtI 30sF7sIDkB401okVeoOqLS5HWb3LhglScu0cE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=nxtwJXm6aTufmm/g7WDf8jbkOK68ysVSN09+soh3tTU=; b=cok0Q4hBdejYyKYQV70efkX90TbJexNhOKuq08DxcK8gklUn4RSBWChb1ApSxD5BPf roFGfKYSkLyt10XbWjrpHRr0YluD+8DQmaJ5ONYX7XhKzx1XEvhQ39Sk5/OXhjbobR40 hHMypUqATFP4nLqHZm8qDYjzb7SK8vlLPVc8eERLAxbtHnIwhHolmcEVJcZrWPEVYHyA 6c4VkKTgBY498G4n41frcT5WKvbRMJsXguMVFoMITIH6kWB+C/dfP0O4rpIy1uFdZObP gMqHX+heRwnPByrEt0dn0TjH+IN8BLt7GdZsXieFLGN7nB+rdPNij+bC4ViqitpqSc38 4k4Q==
X-Gm-Message-State: AOAM532CBAC5Z4aNzhrT1Kd/Jsf0NuwtKJ8vBk+NNx7NRGCHsM9vq7cD 5jzFdq3EkDnZJ+rEdUN+fVFPKQ==
X-Google-Smtp-Source: ABdhPJzE6X1wjDNdc8hP8oFxrtUj3sU+n7xrRBbyr/9b4nTQjp4rxpri3ks0K1EMdmQIqCOMYUeMXg==
X-Received: by 2002:a05:6214:802:b0:462:4eb0:1ec2 with SMTP id df2-20020a056214080200b004624eb01ec2mr11363524qvb.92.1654355670274; Sat, 04 Jun 2022 08:14:30 -0700 (PDT)
Received: from [192.168.2.16] (pool-173-66-88-168.washdc.fios.verizon.net. [173.66.88.168]) by smtp.gmail.com with ESMTPSA id d27-20020a05620a205b00b0069fc13ce235sm6902649qka.102.2022.06.04.08.14.28 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Jun 2022 08:14:29 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.61.22050700
Date: Sat, 04 Jun 2022 11:14:28 -0400
From: Carl Wallace <carl@redhoundsoftware.com>
To: Thomas Fossati <Thomas.Fossati@arm.com>, "Smith, Ned" <ned.smith@intel.com>, Laurence Lundblade <lgl@island-resort.com>
CC: Giridhar Mandyam <mandyam@qti.qualcomm.com>, "rats@ietf.org" <rats@ietf.org>
Message-ID: <7111A53F-C5C9-4764-B4E7-FF7F1CC1A5B7@redhoundsoftware.com>
Thread-Topic: [Rats] Where does a EAT end? - consensus?
References: <5CCD6415-B43B-4BB5-BD05-E7A2B7839B3A@intel.com> <C857641A-8673-4F81-8D9B-D99D6529A836@island-resort.com> <D13E3D0F-CDEB-47F5-856B-A355CE464E55@intel.com> <DB9PR08MB6524D995AA5019EE917995E49CA09@DB9PR08MB6524.eurprd08.prod.outlook.com>
In-Reply-To: <DB9PR08MB6524D995AA5019EE917995E49CA09@DB9PR08MB6524.eurprd08.prod.outlook.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3737186068_1918918190"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/xmzCo3QRtEbLD5rfWmCZU_872Kg>
Subject: Re: [Rats] Where does a EAT end? - consensus?
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: Sat, 04 Jun 2022 15:14:36 -0000

 

 

From: RATS <rats-bounces@ietf.org> on behalf of Thomas Fossati <Thomas.Fossati@arm.com>
Date: Saturday, June 4, 2022 at 8:06 AM
To: "Smith, Ned" <ned.smith@intel.com>, Laurence Lundblade <lgl@island-resort.com>
Cc: Giridhar Mandyam <mandyam@qti.qualcomm.com>, "rats@ietf.org" <rats@ietf.org>
Subject: Re: [Rats] Where does a EAT end? - consensus?

 

<snip>

 

Laurence's one-line PR is roughly equivalent to RFC8126 "standards

action" policy, but without a registry - which I am quite convinced is

superfluous in this case.

 

[CW] Why would a registry be superfluous? All four of the options in RFC8126 section 4.9 have registries.

 

cheers, t

 

PS: we could add a postil "[...] MUST be defined in a IETF standards

track document _that updates this document_" to make an explicit

back-pointer in the RFC series.

 

[CW] The changes in the current section 1.2 over the past year and the recent addition of the collections spec suggests things may still be moving. Even if no registry, it seems premature to preclude use of the experimental track.

v2.23.0 | Report a Bug | By Email