Re: [Rats] should Evidence containers be explicit about Personally Identiable Information?

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 04 July 2020 23:14 UTC

Return-Path: <mcr+ietf@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 0646C3A11D6 for <rats@ietfa.amsl.com>; Sat, 4 Jul 2020 16:14:13 -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 10maZPlqRwUN for <rats@ietfa.amsl.com>; Sat, 4 Jul 2020 16:14:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 250AE3A11D4 for <rats@ietf.org>; Sat, 4 Jul 2020 16:14:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 30112389BC; Sat, 4 Jul 2020 19:11:19 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EaPm68w-bzZS; Sat, 4 Jul 2020 19:11:18 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 77663389BB; Sat, 4 Jul 2020 19:11:18 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2434164F; Sat, 4 Jul 2020 19:14:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ira McDonald <blueroofmusic@gmail.com>, Thomas Fossati <Thomas.Fossati@arm.com>, "rats@ietf.org" <rats@ietf.org>
In-Reply-To: <CAN40gStqDh2wDWmJkp5kmk5RxVK8ftTOJczW26OECYVAQYZEjw@mail.gmail.com>
References: <ietf-rats-wg/architecture/issues/116@github.com> <28098.1593568476@localhost> <8AA2FB69-6E91-431A-BD57-354C65DAEE76@arm.com> <CAN40gStqDh2wDWmJkp5kmk5RxVK8ftTOJczW26OECYVAQYZEjw@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sat, 04 Jul 2020 19:14:09 -0400
Message-ID: <23224.1593904449@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/vevS0aTYi4lAj4jMycAvi3s_iU0>
Subject: Re: [Rats] should Evidence containers be explicit about Personally Identiable Information?
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: Sat, 04 Jul 2020 23:14:13 -0000

Ira McDonald <blueroofmusic@gmail.com> wrote:
    > +1

    > Only the Attester (with advice from the real human owner/user and/or system
    > administrator) can decide what is actually PII.  Various standards and
    > regulations
    > have failed miserably to crisply define what is PII.

*WHAT* is PII is not at all relevant.
  I'm not asking for any determination of that, and if you got that impression,
  then I have failed to present the discussion well.

I am asking the question,
    [having determined that something is (or isn't) PII, ]
does the Attester need a way to signal this in-band to the Verifier?


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