IETF Logo Mail Archive

Re: [Rats] Review of draft-ietf-rats-eat-01

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 23 July 2019 16:39 UTC

Return-Path: <mcr@sandelman.ca>
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 252FC1203E7 for <rats@ietfa.amsl.com>; Tue, 23 Jul 2019 09:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 nc3lIE6MXc3o for <rats@ietfa.amsl.com>; Tue, 23 Jul 2019 09:39:12 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F54A120378 for <rats@ietf.org>; Tue, 23 Jul 2019 09:39:05 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:1232:144:6e88:14ff:fe34:93bc]) by relay.sandelman.ca (Postfix) with ESMTPS id 018C81F44B for <rats@ietf.org>; Tue, 23 Jul 2019 16:39:04 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 99CCD1BBF; Tue, 23 Jul 2019 12:39:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "rats@ietf.org" <rats@ietf.org>
In-reply-to: <87C82D04-59AD-4729-AFC7-68207CD91A35@intel.com>
References: <D95268DC.E2D3B%carl@redhoundsoftware.com> <5CBB3ED3-0CD6-443D-B80F-EE426F7905C3@island-resort.com> <D95316BE.E2E33%carl@redhoundsoftware.com> <D8B4A43F-8654-468F-8A93-9D8E44236784@island-resort.com> <D9538DB1.E2F9F%carl@redhoundsoftware.com> <87C82D04-59AD-4729-AFC7-68207CD91A35@intel.com>
Comments: In-reply-to "Smith, Ned" <ned.smith@intel.com> message dated "Mon, 22 Jul 2019 17:55:46 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 23 Jul 2019 12:39:25 -0400
Message-ID: <8940.1563899965@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/RqtsOrRjBKDoOEHPvSPUVlNgMpY>
Subject: Re: [Rats] Review of draft-ietf-rats-eat-01
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: Tue, 23 Jul 2019 16:39:14 -0000

Smith, Ned <ned.smith@intel.com> wrote:
    > Right now the scope of RATS focuses on Attester to Verifier and
    > Verifier to 
    > Relying Party flows. Flows from Asserter (supply chain entity) to Verifier
    > are out of scope currently. The use cases for counter signing and multiple
    > signing may relate more to supply chain than Attester to Verifier.

(I don't know yet if I agree with you)

Should the use case document explain use cases like this, in order to clearly
mark them as out-of-scope?  (And to avoid repeating the conversation)?


-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email