Re: [Rats] CoTS and CoRIM

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Thu, 14 December 2023 14:08 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77572C14F60A for <rats@ietfa.amsl.com>; Thu, 14 Dec 2023 06:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tu-dresden.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g2Z_WH9zfcAm for <rats@ietfa.amsl.com>; Thu, 14 Dec 2023 06:08:20 -0800 (PST)
Received: from mailout4.zih.tu-dresden.de (mailout4.zih.tu-dresden.de [141.30.67.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A08CDC14EB19 for <rats@ietf.org>; Thu, 14 Dec 2023 06:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=In-Reply-To:From:References:To:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=0PKZIMHogTf/6m8gajYiotsIheMdSJDxgQ9faxTI+6Y=; b=h5BcZVzVJZTtphHyjnJgQZY8oY u4JNiRNjPYPkww24HUUElYg4msIucakgEpRkFbmZmLHd3vXUFLi7ymZuBr91b+JTiyGy0A3cB5Gu2 umtFjOvJ69lSmR8vks9VH3JwTG3jVCYn7E/lQlwkWdJEft6N65l7QpIiT4VDw6z83TUI+z+jigqva pj4QMbX9Gaxoc2wHUmz87kV/hSq7wXlb4v49CPzTHGYOBuvO/VfK1Q7lGGN700Gukg2WnJ+3ppMig AiHgpyyL5H/GYPZpXDRG0oOvW6HAmjzvTAKdtJxe+oa1VQhHYP1gQagAoi+TFCydlifsUOV+x1pCA Ube6Nqig==;
Received: from [172.26.35.114] (helo=msx.tu-dresden.de) by mailout4.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1rDmNs-00Gz64-N1; Thu, 14 Dec 2023 15:08:17 +0100
Received: from [10.70.3.25] (194.95.143.137) by MSX-T314.msx.ad.zih.tu-dresden.de (172.26.35.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.35; Thu, 14 Dec 2023 15:08:15 +0100
Content-Type: multipart/alternative; boundary="------------8KQlhX6f3YcvUpAx0ExmX6iJ"
Message-ID: <d88ac8d7-0566-4fbc-8164-3992d0d30faf@tu-dresden.de>
Date: Thu, 14 Dec 2023 15:08:15 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: hannes.tschofenig@gmx.net, 'Yogesh Deshpande' <Yogesh.Deshpande@arm.com>, rats@ietf.org
References: <005701da2e02$6acec900$406c5b00$@gmx.net> <84e6047b-b87b-4053-8e5a-fb2c8347defc@tu-dresden.de> <AM6PR08MB43257B9CB8ECD1BF6768D2138E8CA@AM6PR08MB4325.eurprd08.prod.outlook.com> <013001da2e8d$bf3c08a0$3db419e0$@gmx.net>
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <013001da2e8d$bf3c08a0$3db419e0$@gmx.net>
X-ClientProxiedBy: msx-l322.msx.ad.zih.tu-dresden.de (172.26.34.122) To MSX-T314.msx.ad.zih.tu-dresden.de (172.26.35.114)
X-TUD-Virus-Scanned: mailout4.zih.tu-dresden.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/0_hkAxgyfwpWUEOAqpD8ekek3wM>
Subject: Re: [Rats] CoTS and CoRIM
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Remote ATtestation procedureS <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2023 14:08:24 -0000

I support both points made by Hannes.

Cheers,

Usama

On 14.12.23 14:02, hannes.tschofenig@gmx.net wrote:
>
> Thanks for the quick response, Yogesh.
>
> Two points:
>
>   * The reason why I believe that the trust anchor functionality
>     should be part of CoRIM is that it is a core feature rather than
>     an extension. I understand that there is some history about how
>     these documents came into existence but this should not prevent us
>     from doing the “right” thing.
>
>   * Using trust anchors under the umbrella of endorsements makes sense
>     to me. This needs to be more clearly articulated in the documents
>     though.
>
> A word about the process: Decisions about the directions the document 
> take should be made on the mailing list rather than in private 
> meetings. The chairs should be more strict about this.
>
> Ciao
>
> Hannes
>
> *From:*RATS <rats-bounces@ietf.org> *On Behalf Of *Yogesh Deshpande
> *Sent:* Donnerstag, 14. Dezember 2023 12:31
> *To:* muhammad_usama.sardar <muhammad_usama.sardar@tu-dresden.de>; 
> rats@ietf.org
> *Subject:* Re: [Rats] CoTS and CoRIM
>
> Hi Hannes,
>
> To your question:
>
> /I am wondering why the two documents <draft-ietf-rats-corim> and 
> <draft-ietf-rats-concise-ta-stores> aren’t merged./
>
> //
>
> The work on Cots started at different point in time (by different 
> authors) and hence the CoRIM base document does refer Cots but is not 
> fully integrated.
>
> We will discuss the possibility and implications of such in our 
> regular CoRIM meetings.
>
> Regarding Trust Anchors as per RATS document (RFC 9334) to the best of 
> my knowledge it comes under the heading of Endorsements.
>
> https://datatracker.ietf.org/doc/html/rfc9334#name-endorsements
>
> RATS treats Trust Anchors as a type of Endorsements.
>
> Hope this information is helpful.
>
> Regards,
>
> Yogesh
>
> *From:*RATS <rats-bounces@ietf.org> *On Behalf Of *Muhammad Usama Sardar
> *Sent:* Thursday, December 14, 2023 8:21 AM
> *To:* rats@ietf.org
> *Subject:* Re: [Rats] CoTS and CoRIM
>
> Hi Hannes,
>
> On 13.12.23 21:24, hannes.tschofenig=40gmx.net@dmarc.ietf.org wrote:
>
>     I am wondering why the two documents <draft-ietf-rats-corim> and
>     <draft-ietf-rats-concise-ta-stores> aren’t merged. Reading through
>     the RATS drafts I often get the impression that trust anchors have
>     somehow been forgotten and were added later, as an afterthought.
>     The RATS architecture RFC does not list trust anchors as an item
>     in Figure 1. In some other document trust anchors are then
>     portrait as belonging to reference values – somehow. That does not
>     feel right to me either.
>
> I think it is completely wrong to consider trust anchors as Reference 
> Values. Can you name the document which presents this view?
>
>     Ciao
>
>     Hannes
>
> Cheers,
>
> Usama
>
> IMPORTANT NOTICE: The contents of this email and any attachments are 
> confidential and may also be privileged. If you are not the intended 
> recipient, please notify the sender immediately and do not disclose 
> the contents to any other person, use it for any purpose, or store or 
> copy the information in any medium. Thank you.
>