IETF Logo Mail Archive

Re: [EAT] [Rats] Attestation BoF charter updates? - Program of Work section

Carl Wallace <carl@redhoundsoftware.com> Thu, 25 October 2018 13:47 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 47A1F130E5F for <eat@ietfa.amsl.com>; Thu, 25 Oct 2018 06:47:16 -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=ham 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 BEBnqFR6Bg8I for <eat@ietfa.amsl.com>; Thu, 25 Oct 2018 06:47:14 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 BB437120072 for <eat@ietf.org>; Thu, 25 Oct 2018 06:47:14 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id e4so5708428qkh.6 for <eat@ietf.org>; Thu, 25 Oct 2018 06:47:14 -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=7QSh1INakwlKADKpzIr7S00HO9wGfoUdeylm3h99Lmg=; b=XB1VzuWM7kxw0SuhoK9jqB6h5q/cqItEDADG3/DEfm56cVjKDrSeVpeT+8rnyWUdbm m2EXYuGMKCR7xTPG2joismi2xCLL86qjRo4gpEc146siMBuxHTz3chCqAEL/NtKYzFjX Qvz3taTbuiLWk0nPDepZnlSD41r5ZJ8LRVHuk=
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=7QSh1INakwlKADKpzIr7S00HO9wGfoUdeylm3h99Lmg=; b=LaBkyiOP80IUL2eA7Pxd5ehR/Mz52lw6CQybPtEX270iYEwuErlcaN15777QX2YOvI dXSAdB6J5zlFijhp7xiAYvJsDjiZKaujYlUAjHbuwINC6LFW4Mck/DA/pmjfo6N53cva IOgNmjPpbisowg//n8AWyvUOT47UyYMbyCTTEPqj6xGlM9EaEmAiZ+eN1aj+JtrXcvrt seArzy2TVuteIHjQ5pVPqXL35USE7DqmMps7ofqZTx/MGk8Y+isk6w2Ohqv1+ZYcmLMY KScHAlGT2P5aiUft5jI0z1stk4HYDPicz0CNe3B6NPW8ncZKTT+dTki+T/jDj+yjyJKt GOQQ==
X-Gm-Message-State: AGRZ1gJP/119kDq6MQG7oMIb5kgM5sBUM4Yj13eUog3P+NeSQL90EmCG 20uc25bHZFhVStmuAygnIfM3Ew==
X-Google-Smtp-Source: AJdET5e9RdAbvZj+LUkhggqfjrS4+tvXb0aj0811tI7kq1lCvtgVL2lBMuFt0rVukv73uC7OUMevTQ==
X-Received: by 2002:a37:b345:: with SMTP id c66-v6mr1507046qkf.47.1540475233606; Thu, 25 Oct 2018 06:47:13 -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 w53-v6sm6069079qtw.87.2018.10.25.06.47.10 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 25 Oct 2018 06:47:12 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.7.6.170621
Date: Thu, 25 Oct 2018 09:47:06 -0400
From: Carl Wallace <carl@redhoundsoftware.com>
To: Laurence Lundblade <lgl@island-resort.com>, "Smith, Ned" <ned.smith@intel.com>
CC: "Eric Voit (evoit)" <evoit@cisco.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "eat@ietf.org" <eat@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "rats@ietf.org" <rats@ietf.org>, Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
Message-ID: <D7F73FD8.C4179%carl@redhoundsoftware.com>
Thread-Topic: [Rats] [EAT] Attestation BoF charter updates? - Program of Work section
References: <0199DB00-E76E-4664-BE02-E2AF4F4B6AEC@intel.com> <526BB5AC-60A8-4CD3-95F4-39F210E4D2FB@island-resort.com>
In-Reply-To: <526BB5AC-60A8-4CD3-95F4-39F210E4D2FB@island-resort.com>
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/WACSXWBx67Eny6PS3wObijhcIdo>
Subject: Re: [EAT] [Rats] Attestation BoF charter updates? - Program of Work section
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, 25 Oct 2018 13:47:16 -0000

On 10/25/18, 9:15 AM, "RATS on behalf of Laurence Lundblade"
<rats-bounces@ietf.org on behalf of lgl@island-resort.com> wrote:

><snip>
>
>So I am making some argument against ASN.1 and anything beyond JSON and
>CBOR.  The more formats there are the more work the relying parties will
>have to do and of course some won’t implement all the formats and then
>we’ll have less interop.

[CW] At least where the claims are related to cryptographic keys, ASN.1 is
likely unavoidable as it's part of the environment. Avoiding it is not
likely to help interop.

v2.23.0 | Report a Bug | By Email