IETF Logo Mail Archive

Re: [EAT] [Rats] Attestation BoF charter updates?

Carl Wallace <carl@redhoundsoftware.com> Tue, 23 October 2018 17:34 UTC

Return-Path: <carl@redhoundsoftware.com>
X-Original-To: eat@ietfa.amsl.com
Delivered-To: eat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25EF2124C04 for <eat@ietfa.amsl.com>; Tue, 23 Oct 2018 10:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhoundsoftware.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 t69BYLOt8KaF for <eat@ietfa.amsl.com>; Tue, 23 Oct 2018 10:34:08 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 EA5231274D0 for <eat@ietf.org>; Tue, 23 Oct 2018 10:34:07 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id l41-v6so2459468qtl.8 for <eat@ietf.org>; Tue, 23 Oct 2018 10:34:07 -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=CBp/FuIMrmcWwZms8ibp9XnCDJNIhqxUAdiMbOFXeII=; b=DcsNt2VF16U3juVtVftAs81uRxP5LNsqfzW5pw4ctEG7w+1lYwtO1zLbXHjmrh732a wI+RJFax1FdwwMHHlAVOZUd5bZUc/ZfS6B/05sMMHkcYraaNVs4iYq9TuTYY7EIvTm37 HOCQzuFgSblo4snT/V9YPp1tXBCTMU1iOUd8s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=CBp/FuIMrmcWwZms8ibp9XnCDJNIhqxUAdiMbOFXeII=; b=iCEOxVs7aJesE1vHkDFy2ZOOX82WAoT1pfYazFoVPS/o8t2dxNvUEe4DEt22ewXNIB dnCM88jid2z8zYdSl/7clCJG5PJU5g2CqZzTayb74NnXqGteZCv9HowcRvhtG2n/6HP8 c1IrfMGcWn/r/2y/1+gjHNR0vw9ZbEnv2TSO0h7Z5etv2zCvtdq5JmpGxOcBfiyD6yLU fDFC+tPwdN0mrxGdpFrVUE/oN5qvOGBDfmYt/KJbQptMbu3wubpMwiu7hNFuByzwgKjh gsDJITG2EjLTNNPHeKBVsJIKxy9OVS/eu5/BMHtbYmsb76fANdlfBsjcXR3CpfC9rvof g0Fg==
X-Gm-Message-State: ABuFfojMPlM+Gz4+7tNwQCA7JxCVOPxhYIcnb21Cr1rRFxmifl69nIqR d17o48e7zsKE0wvd8N6yOZDqaKnw+4k=
X-Google-Smtp-Source: ACcGV60PAmtoidFhDVXizAJluhbsb4X2JLMeCIOcAvh27N+MLHvcyM2VGaBhFw6D9UZ2S3Y16/x73g==
X-Received: by 2002:a0c:fe11:: with SMTP id x17mr48560825qvr.150.1540316046890; Tue, 23 Oct 2018 10:34:06 -0700 (PDT)
Received: from [192.168.2.27] (pool-108-28-91-61.washdc.fios.verizon.net. [108.28.91.61]) by smtp.googlemail.com with ESMTPSA id k14-v6sm1741106qtk.28.2018.10.23.10.34.02 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 23 Oct 2018 10:34:06 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.7.6.170621
Date: Tue, 23 Oct 2018 13:33:56 -0400
From: Carl Wallace <carl@redhoundsoftware.com>
To: "Smith, Ned" <ned.smith@intel.com>, Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, "eat@ietf.org" <eat@ietf.org>, "rats@ietf.org" <rats@ietf.org>
Message-ID: <D7F4D350.C3CFF%carl@redhoundsoftware.com>
Thread-Topic: [EAT] [Rats] Attestation BoF charter updates?
References: <D7F4B1E4.C3BF8%carl@redhoundsoftware.com> <D0C08E47-DBB6-4AAD-95EF-F952155D3152@qti.qualcomm.com> <581DD29C-85D9-4BD8-A0EE-41761ED773B4@intel.com>
In-Reply-To: <581DD29C-85D9-4BD8-A0EE-41761ED773B4@intel.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3623146445_17423108"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/EFO9FAdRzRDuBqbUXsrHl450A6w>
Subject: Re: [EAT] [Rats] Attestation BoF charter updates?
X-BeenThere: eat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EAT - Entity Attestation Token <eat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eat>, <mailto:eat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eat/>
List-Post: <mailto:eat@ietf.org>
List-Help: <mailto:eat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eat>, <mailto:eat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2018 17:34:10 -0000

<snip>
>  
> 
> It would be interesting to understand your thinking a bit further. At one
> level it is fairly straightforward to define a claim whose value contains an
> X.509 certificate, but I suspect that binding may imply more than that.
> [nms] It is also reasonable to consider an X.509 certificate as being an
> object that contains a set of claims (rather than the other way around).
[cw] Not if the goal is to prevent issuance of a certificate because
provenance of a key cannot be confirmed. Having a self-issued cert contain
claims is fine, but this does not obviate the need to bind to issuance
protocols to inform CA issuance.

<snip>
>

v2.23.0 | Report a Bug | By Email