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

Carl Wallace <carl@redhoundsoftware.com> Tue, 23 October 2018 19:57 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 77D71130E1B for <eat@ietfa.amsl.com>; Tue, 23 Oct 2018 12:57:48 -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 spNn7viy8fh4 for <eat@ietfa.amsl.com>; Tue, 23 Oct 2018 12:57:46 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 71C0D130E5C for <eat@ietf.org>; Tue, 23 Oct 2018 12:57:46 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id e4so1685157qkh.6 for <eat@ietf.org>; Tue, 23 Oct 2018 12:57:46 -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=jNiKkWafRS0glpa4DRE7oRdfs87Nq1XcQHfNzF3k3XU=; b=PjfJvWxudmUq9YHjLyIV7Hma4BPrbG62DTnIAeB6BrO0kfzESeWRwzzbhYl6PTp2yt 6VDR9N6sobs8aH7/lKpTDKr5yJEGWLe8L8tKCdGOZ7ctMYl2LjSq7cEFrzz5um9Gwogt C6jx6R7Zz7jBKLeNxSmB2FB7aIcqdwcYiYY+A=
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=jNiKkWafRS0glpa4DRE7oRdfs87Nq1XcQHfNzF3k3XU=; b=DTOv53SXxik2tkrW9xjlJC/QtlP2grZqOve8NX2ZK9sv87AvUZ2ueWygpEr3MK3hrl z9y7SYHwfUc06hscAk8o6KMtnAWxuJrlwSEG8d6/2wtb4WTdqzkbapKwEcMc98nHSMYf J5s7tocARNeQSnRCyrOMSQ8p+eXYkeW97OBrJqf9gXTnTFHXqhwmDQgalql7YqhkGjvf 32SNyBHAlGGmE0Y3TQsmRBm8MNE2j+ivvC3SNI3+kDcDu8XyJuP3R3D40+tQnXuESssT +0xPHMYLZ9Z7qPbZl2QbcUAfoLT2mQ++pa0n8kxuA5rCYJ2mlBKtRmEpYX7q4fNauAJr Obag==
X-Gm-Message-State: ABuFfoivq5QOCwC5/a+EyqdJVoTJL79rYV6rmoLsJesx8/C/BPdENRSv 8YmYO1+FTccOseocNhNMCih+1ENOtZw=
X-Google-Smtp-Source: ACcGV63+Q06GdgFb6azhp2x+g35YDwc8ABLEit+ywCeOXcunD0DacHu/RRKW9xBr1qUWhUomApYE5w==
X-Received: by 2002:ae9:e00c:: with SMTP id m12-v6mr47710280qkk.303.1540324665402; Tue, 23 Oct 2018 12:57:45 -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 l28-v6sm1681878qkj.33.2018.10.23.12.57.40 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 23 Oct 2018 12:57:44 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.7.6.170621
Date: Tue, 23 Oct 2018 15:57:35 -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: <D7F4F54C.C3DB8%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> <D7F4D350.C3CFF%carl@redhoundsoftware.com> <FFA0BB14-48AB-45CE-8D7A-53D43821FC7D@intel.com> <D7F4E84F.C3D97%carl@redhoundsoftware.com> <FCF1711D-4936-4D35-A75D-84B88C076151@intel.com>
In-Reply-To: <FCF1711D-4936-4D35-A75D-84B88C076151@intel.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3623155063_17955261"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/pfGFVSKKfKRzHbFuNkc_mLS49UM>
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 19:57:49 -0000

<snip>
> [nms] Right. In order for the CA (verifier) to distinguish the certifying key
> is an ‘attestable key’ vs. a traditional CSR. The CA should look for a
> signature from the mfg cert over the CSR (certificate management message?)
> containing the generated public key. I’m still not seeing where there is a
> self-signed (issued) certificate in the equation.
This began with request to codify binding to certificate request protocols,
not for a self signed certificate.