Re: [Rats] CoTS and CoRIM

hannes.tschofenig@gmx.net Thu, 14 December 2023 15:06 UTC

Return-Path: <hannes.tschofenig@gmx.net>
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 B858CC14F681 for <rats@ietfa.amsl.com>; Thu, 14 Dec 2023 07:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level:
X-Spam-Status: No, score=-2.102 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=gmx.net
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 UaVGKsV0gmWh for <rats@ietfa.amsl.com>; Thu, 14 Dec 2023 07:06:11 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 350E1C14F5E2 for <rats@ietf.org>; Thu, 14 Dec 2023 07:06:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=s31663417; t=1702566367; x=1703171167; i=hannes.tschofenig@gmx.net; bh=e7uJamF7MPYHo6T/7JrWAC4Ko72peqyhVNB3CBFdMdQ=; h=X-UI-Sender-Class:From:To:References:In-Reply-To:Subject:Date; b=OuYW3OnNaC/nwG7bMeBoyrnADLeqFIbn7nIrTGEyOaQuuFWr/kNpULZn2nM87I8G mgG64Vjb0iTn06oz2X9g0BYLEjVLMSTXZd79DLg0mp3BTDMPY7F6Gwhphw2/xcWTj zsq4qgEII5jQ1l1dcsVjEKXTEGFieYMslnk/C0xSgh/wDfw8KsGP6sM60WGe4NCoY m8aTLehM2rt6nwL6nsTxnyYV+N7wp2VagDogdvbUrn9GzmDbiRK+i9LCsqqEhosJO qxRmmiZUQBrh7NyA98ySdbCnZ56usiCfaryHsTG1P7vvgMLce30dUtdqxxwbGLozD verkVrk4yxWq8ImhIA==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from Surface ([185.104.138.31]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N17YY-1rK4pt42na-012aCD; Thu, 14 Dec 2023 16:06:07 +0100
From: hannes.tschofenig@gmx.net
To: 'Yogesh Deshpande' <Yogesh.Deshpande@arm.com>, "'muhammad_usama.sardar'" <muhammad_usama.sardar@tu-dresden.de>, 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> <AM6PR08MB43255B8E2ECC1FE657AF325E8E8CA@AM6PR08MB4325.eurprd08.prod.outlook.com>
In-Reply-To: <AM6PR08MB43255B8E2ECC1FE657AF325E8E8CA@AM6PR08MB4325.eurprd08.prod.outlook.com>
Date: Thu, 14 Dec 2023 16:05:59 +0100
Message-ID: <01c601da2e9f$0f402230$2dc06690$@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01C7_01DA2EA7.7106FB30"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIypL3ao4eyVP6NJJEK319/7y0r6wE/ZkIpAqYEAjkCuBQfkgIxouv/r7F6y4A=
Content-Language: de-at
X-Provags-ID: V03:K1:89Kv+MZtFdaj5B8CTvOEjHkA4Ry0smP0BaZdHpYClGmTT3RYHAk W9mKHqJsLhKkgE/ktZjdTU4rPPTnqonusBeQdjTEfJFbocjewHRjAPln6KCpWgKbTw1jgA4 G7u8s6Y1FwsGnqLHtA3vp4o4ld7jVshhglH5zRPm3Ag6b1AGr2+PW9igD3PdCTZU0ZCmJNl OvXPntCj/qp+G/wk2oVsw==
UI-OutboundReport: notjunk:1;M01:P0:8UEZfeYXHI4=;4EqO7Y7aWYFTb7Z9Z1dGXlr+RqL wt0QpBszZSeeH2Iw20vvTQ+J9Bj5P/LGP1wLP6SWx8/1t+lM16blGwMXfgFzxNFKcS3gfIpj7 5d7qasrhNVlDXnzdT/nW6/75jorgEmQvLn4PVC1j9K04Dvg5yYLtbYRRKti0U9NKbGOLrw2Ki KHcbmxc2mjC2y+jMoqifcAv6aYjd7BS4LrtOU3GvjA+6zExdzRJ9IVUeBnZuBib2LZnUzz2Z8 wObrDiB7jiznfSAv88/wo+VCSTxVQhi/9XI7c6NvDZjPwLQxxNQBgPkGIoLgRSq1qYtw8gnSe t2O8IpFORTT/+pmbzStEXaoejazg0T9VB4XXPuE1Uycx3GdH5f/kv1UQq1Ryucook6frOfLYt sFZG7KgUG+5Ct6idWbb/sJysqF+P8zzyGLYarqSdauUTMpTbOYi8Jm2aRh5e4TtpC8Y/K3toU 4xS1MngbLDZMKa+uF7flhk2HwkHX5v1T3w9MAHGxMT5zOtw67rhLz3EDi4wn+041OyiZwYbxa 22ifYTjzkK6jnR/y9LnwCoeR2KChgWVTcMdKEuoe2yldlWmUYVbmaaDq5jjh7O6uuSBlSUz7a woD7m6QJek2PSx4p2/22a6b/QsBak9/vhshedt5vJLaNoSrqCr7YZnzfHDnkbC7sw3QeIv/Xg HeAoMOx/vVWdZGmhSdqU0A9KNX/hTmqxEFLdxJdXiXLujYwvCS6bK0xeg1LI8sE7KMV3cZy+/ ghdYeH8DNQxesp9UCRgP2DiVNfbXdOjq29W4PD002NWh1NU7duoAbbH2cwBzNx3CWT1BQtbix AylxMhAeV5Xg4/Ds3YUKY7CE4TmjsgiliERsL8ZI3vCNeL+VWJ+yB5nvtrUI5r1FZr94tKca4 kF6UDFSrNtBVjbZdWN3xadnnDFJ7UMQ0PEFPDfaG1yKbjZkqD/R6N5Se39v+J6/qhw/h/yBTh eXgz4oS93cdMkD5/OA6u0QNU/Eo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/DEjOa7kry4Olo6x3Ix3XajKkRA0>
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 15:06:15 -0000

Hi Yogesh,

 

Here this for guidance for these types of meetings:

https://www.ietf.org/about/groups/iesg/statements/interim-meetings-guidance/

 

Under this definition, your meeting is private even if you announce it in the public.

 

Ciao
Hannes

 

From: RATS <rats-bounces@ietf.org> On Behalf Of Yogesh Deshpande
Sent: Donnerstag, 14. Dezember 2023 14:10
To: hannes.tschofenig@gmx.net; muhammad_usama.sardar <muhammad_usama.sardar@tu-dresden.de>; rats@ietf.org
Subject: Re: [Rats] CoTS and CoRIM

 

Hi Hannes,

 

To your comment: 

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. 

 

Please note: CoRIM Meetings are NOT private meetings.

 

We advertise the details of CoRIM Weekly Meeting periodically and everyone following RATS are Welcome to join and participate in the discussions.

 

Regards,

Yogesh

 

From: hannes.tschofenig@gmx.net <mailto:hannes.tschofenig@gmx.net>  <hannes.tschofenig@gmx.net <mailto:hannes.tschofenig@gmx.net> > 
Sent: Thursday, December 14, 2023 1:02 PM
To: Yogesh Deshpande <Yogesh.Deshpande@arm.com <mailto:Yogesh.Deshpande@arm.com> >; muhammad_usama.sardar <muhammad_usama.sardar@tu-dresden.de <mailto:muhammad_usama.sardar@tu-dresden.de> >; rats@ietf.org <mailto:rats@ietf.org> 
Subject: RE: [Rats] CoTS and CoRIM

 

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 <mailto: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 <mailto:muhammad_usama.sardar@tu-dresden.de> >; rats@ietf.org <mailto: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 <mailto:rats-bounces@ietf.org> > On Behalf Of Muhammad Usama Sardar
Sent: Thursday, December 14, 2023 8:21 AM
To: rats@ietf.org <mailto:rats@ietf.org> 
Subject: Re: [Rats] CoTS and CoRIM

 

Hi Hannes,

On 13.12.23 21:24, hannes.tschofenig=40gmx.net@dmarc.ietf.org <mailto: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. 

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.