IETF Logo Mail Archive

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

Carl Wallace <carl@redhoundsoftware.com> Thu, 11 October 2018 20:56 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 DAC33127598 for <eat@ietfa.amsl.com>; Thu, 11 Oct 2018 13:56:45 -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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Hn4eIMM7eRxt for <eat@ietfa.amsl.com>; Thu, 11 Oct 2018 13:56:44 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 0A6B2124C04 for <eat@ietf.org>; Thu, 11 Oct 2018 13:56:43 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id e22-v6so11592469qto.6 for <eat@ietf.org>; Thu, 11 Oct 2018 13:56:42 -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:content-transfer-encoding; bh=HKCbH/mE3TJXOBo/x2l5Vz1zLEBbt5ZnHGCHNgbjmfs=; b=pnrtGWBa+7ePtqpLHzWMpJ1mXCwET7atjQ+t9nRwmb6IeFCVL+8xnZmKIcUBVE6lat RbXRFaA+8ZC+J5fE1Galwuoenu3E+VEMZTqePY3LFcWvRcfGJgdWV5tYLVIWquASQBNC owbd1ghzwFqDXUnhLB0WfgOELB2mIAquIYtII=
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 :content-transfer-encoding; bh=HKCbH/mE3TJXOBo/x2l5Vz1zLEBbt5ZnHGCHNgbjmfs=; b=cuY0eBmqcCPkfaA1SVLa33pjDhuB53OyA8irt49fHqpVknEFxEBGSLqlTZzj3DDb3w 9j7FAEPOQBlS8DboiCAiIbgjrlX8bUiaaGdfxsTBPPyg2KOVvOaq9lM83Zu2s+SQJZlI OTmxjbnCq9hVXcT+t0LtgRBaacErjzKPOKsQALy+s4/WZTqSIHrKgvc6HaDqNiozjtLj 15uxzRNRhBQS5rx0OsOn1uVtWMlXewO0twlytyyNDIN0Lr0j7A1MXDbXFCyhGJtnNP/1 svHK+p0NkqByxEuLSEOrpvD2WOm2pooDlIlERGRg362TjCVvgskrAYCw8IvOWtPYDQVt at1w==
X-Gm-Message-State: ABuFfojmjQOfY3gMps3UnaqcsXmGiC6svfNa96WsOm/I7nPxQbKRPsIt YNd2KC77Fg3xpgO20S4S8X4KuQ==
X-Google-Smtp-Source: ACcGV63DNbhaedj9bdtX898xxnAsCs0RWJWfZzH94SYFSUKS3JO4742Y3xt+UIgfHmcgVFL+QyEx6Q==
X-Received: by 2002:aed:2867:: with SMTP id r94-v6mr3235324qtd.112.1539291402098; Thu, 11 Oct 2018 13:56:42 -0700 (PDT)
Received: from [10.73.240.229] (pat_11.qualcomm.com. [192.35.156.11]) by smtp.googlemail.com with ESMTPSA id 140-v6sm14300067qkj.13.2018.10.11.13.56.36 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 11 Oct 2018 13:56:41 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.7.6.170621
Date: Thu, 11 Oct 2018 13:56:30 -0700
From: Carl Wallace <carl@redhoundsoftware.com>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "rats@ietf.org" <rats@ietf.org>
CC: "eat@ietf.org" <eat@ietf.org>, Laurence Lundblade <lgl@island-resort.com>
Message-ID: <D7E5069D.C2E65%carl@redhoundsoftware.com>
Thread-Topic: [Rats] Attestation BoF charter updates?
References: <5D773C02-5083-4B10-A705-782E28FD8ADB@island-resort.com> <f84515dd-2e1a-7e66-7c23-b16f8f425d2a@sit.fraunhofer.de>
In-Reply-To: <f84515dd-2e1a-7e66-7c23-b16f8f425d2a@sit.fraunhofer.de>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/Ahj_OhLE36mWqSloHaSytm11CVY>
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: Thu, 11 Oct 2018 20:56:46 -0000

As with the earlier draft, there are many references to verify and
verifier in the lead up to the deliverable but no deliverables describing
verification rules. I'd like to see rules in one of these documents and
think it worth citing in the deliverables. Are bindings to certificate
management protocols out of scope?

On 10/11/18, 9:49 AM, "RATS on behalf of Henk Birkholz"
<rats-bounces@ietf.org on behalf of henk.birkholz@sit.fraunhofer.de> wrote:

>Hi all,
>
>sorry for the delay. Please find an updated charter proposal here:
>
>> https://github.com/ietf-rats/charter/blob/RC2/ietf-rats-charter.md
>
>The BoF proponents tried to merge all comments and proposals on
>keystores, existing solutions, provenance & device characteristics, etc
>that were raised on the list - and align them in homogeneous fashion.
>
>This draft is intended to focus the discussion and improve the wording.
>
>Viele Grüße,
>
>Henk
>
>On 10/06/2018 08:23 AM, Laurence Lundblade wrote:
>> Hi Henk,
>> 
>> Bangkok IETF is getting close, will you be able to update the charter
>>for the attestation BoF to properly include EAT?  I sent you some text
>>that just needs to be pasted along with some comments. It doesn’t look
>>like there’s been any updates.
>> 
>> LL
>> 
>
>_______________________________________________
>RATS mailing list
>RATS@ietf.org
>https://www.ietf.org/mailman/listinfo/rats

v2.23.0 | Report a Bug | By Email