IETF Logo Mail Archive

Re: [Teep] [Suit] Unique Identifier of TA_ID in TA_LIST for TEEP_QueryResponse

Benjamin Kaduk <kaduk@mit.edu> Mon, 18 May 2020 06:19 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 341BA3A086A; Sun, 17 May 2020 23:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_PASS=-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 K1QoSFdl4Olp; Sun, 17 May 2020 23:19:50 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5E383A085B; Sun, 17 May 2020 23:19:49 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 04I6JbWM006749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 18 May 2020 02:19:39 -0400
Date: Sun, 17 May 2020 23:19:37 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Akira Tsukamoto <akira.tsukamoto@aist.go.jp>
Cc: Mingliang Pei <mingliang.pei@broadcom.com>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>, teep <teep@ietf.org>, "suit@ietf.org" <suit@ietf.org>
Message-ID: <20200518061937.GH58497@kduck.mit.edu>
References: <7526678c-9ebc-e265-514c-435dce7595bc@aist.go.jp> <AM0PR08MB37161FA69D215123ACBC632FFABE0@AM0PR08MB3716.eurprd08.prod.outlook.com> <CABDGos5LfjqdK8LHijnqTiceu7E823SmA=4Vtyq144jH2Kx-Hw@mail.gmail.com> <00515b62-b2ae-405e-2c44-c533c6857873@aist.go.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <00515b62-b2ae-405e-2c44-c533c6857873@aist.go.jp>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/m42L08ecQ-yaC-njLMpvgwAaoSw>
Subject: Re: [Teep] [Suit] Unique Identifier of TA_ID in TA_LIST for TEEP_QueryResponse
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 May 2020 06:19:51 -0000

On Wed, May 13, 2020 at 08:17:39PM +0900, Akira Tsukamoto wrote:
> 
> We have to specify which sha256 or anything else to use.

Note that BCP 201 says you have to be able to support multiple algorithms.

-Ben

v2.23.0 | Report a Bug | By Email