Re: [Rats] Follow-up CoRIM: Horn clauses

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Fri, 22 March 2024 05:05 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 56511C14F705 for <rats@ietfa.amsl.com>; Thu, 21 Mar 2024 22:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.405
X-Spam-Level:
X-Spam-Status: No, score=-4.405 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_DNSWL_MED=-2.3, 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 KiUAi046YeeK for <rats@ietfa.amsl.com>; Thu, 21 Mar 2024 22:05:16 -0700 (PDT)
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 413F8C14F6BC for <rats@ietf.org>; Thu, 21 Mar 2024 22:05:15 -0700 (PDT)
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:CC:To:Subject: MIME-Version:Date:Message-ID:Content-Type:Sender:Reply-To: 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=9K1WTG//V9eAQgSVOyEIWUmM/bbPvz6CFj3NaLZ+Dp4=; b=bx6PIcWIG5SZ+xXesAZnRKwOgX pT37ap0xUUMFAA59QL+DnDFjanj5rf2uQj5/Bcqr5QQuQqWq5hLjJsGPl/NkTS4AcPtbpc5oG822E DGF+C20ieV8OX2o3PK1Da1lrG5eNFYCLTM45vby6q62qHar5T5C99FHD/GdLO67dQikQM7pNTiajH vCVmgRB4BXDu1aA220KYcsC/u/OfvyrXlWN5e2gPoNhqcrwWb/beJZDEAB879nc0vqE9nnNMmzGcC j3oSEuttMCGJjPwjNFA74C+o+X0LaqquW1/ZXvnTA84s4u8g+vnh+/55jiIDY2YNgw6k+BnIr1CSK vvEEB5WA==;
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 1rnX5Z-00ADoT-4Y; Fri, 22 Mar 2024 06:05:10 +0100
Received: from [192.168.1.2] (78.54.129.22) 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.37; Fri, 22 Mar 2024 06:05:04 +0100
Content-Type: multipart/alternative; boundary="------------0bZItY65i2ONQ3oxeOq4FweV"
Message-ID: <35ad3aea-0dfd-42fc-bb58-464f9eaf15da@tu-dresden.de>
Date: Fri, 22 Mar 2024 06:05:04 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "rats@ietf.org" <rats@ietf.org>
CC: Yogesh Deshpande <Yogesh.Deshpande@arm.com>
References: <1f4c5bad-857a-490c-b773-c8754d45489d@tu-dresden.de> <DB9PR08MB98518B5A64F79788CBD4600F8E2C2@DB9PR08MB9851.eurprd08.prod.outlook.com> <a28edcd7-6d82-4500-a42e-f76be30babf3@tu-dresden.de> <DB9PR08MB98510CF3E1274B44C28B34808E2C2@DB9PR08MB9851.eurprd08.prod.outlook.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <DB9PR08MB98510CF3E1274B44C28B34808E2C2@DB9PR08MB9851.eurprd08.prod.outlook.com>
X-ClientProxiedBy: msx-l318.msx.ad.zih.tu-dresden.de (172.26.34.118) 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/o5MAbX9rRDTeqW34mci-tPj6AxU>
Subject: Re: [Rats] Follow-up CoRIM: Horn clauses
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: Fri, 22 Mar 2024 05:05:20 -0000

None of the two issues pointed below mention Horn clauses. Also, the 
CoRIM meeting this week was cancelled. Some preliminary questions for 
better understanding:

  * How are "Horn clauses" relevant to the CoRIM draft? I don't fully
    understand the link of the CoRIM draft to Horn clauses.
  * How are the Horn clauses generated?
  * What are the assumptions/facts?
  * Which rule engine do you plan to use to analyze the Horn clauses?

We have some experience with Horn clauses, which will likely be helpful 
here, e.g., I have experience with ProVerif which is based on Horn 
clauses, and my colleagues have developed "Nemo" tool [1].

Since CoRIM is a WG document, could the editors and contributors please 
make a good-will effort to summarize the discussions on these meetings 
to the WG? Interested WG members would then get a chance to contribute 
and/or comment. This was already pointed out a couple of months ago [2], 
but I don't see any CoRIM update provided to the mailing list since 
then. I very much like the updates from PKIX attestation, e.g., [3].

[1] https://iccl.inf.tu-dresden.de/web/Inproceedings3354

[2] https://mailarchive.ietf.org/arch/msg/rats/OwTI-PfFpLXHKf3IhoNpayv3m10/

[3] https://mailarchive.ietf.org/arch/msg/rats/8X3N9e7-phCjDwGacWJrDoapeRE/

Thanks,

Usama

On 19.03.24 13:46, Yogesh Deshpande wrote:
> Hi Usama,
>
> Some of the linked github issues where the discussions happened is given below:
>
> https://github.com/ietf-rats-wg/draft-ietf-rats-corim/issues/197
>
> https://github.com/ietf-rats-wg/draft-ietf-rats-corim/issues/142
>
> Feel free to join CoRIM Meetings, I have forwarded you the invite.
>
> Regards,
> Yogesh
>
> -----Original Message-----
> From: Muhammad Usama Sardar<muhammad_usama.sardar@tu-dresden.de>
> Sent: Tuesday, March 19, 2024 12:05 PM
> To: Yogesh Deshpande<Yogesh.Deshpande@arm.com>
> Cc:rats@ietf.org
> Subject: Re: [Rats] Follow-up CoRIM: Horn clauses
>
> Hi Yogesh,
>
> Thanks. Could you point me to the recording and minutes of the relevant CoRIM team meeting where it was discussed?
>
> Usama
>
> On 19.03.24 12:53, Yogesh Deshpande wrote:
>> Hello Usama,
>>
>> This was only discussed recently in one of our CoRIM team meetings(has just been initiated), hence you do not find any update on the same in any of the IETF drafts.
>>
>> In the course of time, as part of CoRIM Verifier simplification
>> activity, concepts from this presentation will make its space into the draft.
>>
>> Regards,
>> Yogesh Deshpande
>>
>> -----Original Message-----
>> From: RATS<rats-bounces@ietf.org>  On Behalf Of Muhammad Usama Sardar
>> Sent: Tuesday, March 19, 2024 11:43 AM
>> To:rats@ietf.org
>> Subject: [Rats] Follow-up CoRIM: Horn clauses
>>
>> Dear Ned and CoRIM team,
>>
>> Horn clauses [1, slide 6] were mentioned yesterday in the meeting.
>> Surprisingly, I don't see any relevant discussion in any of the two relevant drafts [2,3]. Where can I find more details about how the Horn clauses are generated for any of these drafts? What are the assumptions/facts? etc.
>>
>> Thanks,
>>
>> Usama
>>
>> [1]
>> https://datatracker.ietf.org/meeting/119/materials/slides-119-rats-att
>> estation-verifier-theory-of-operation
>>
>> [2]https://datatracker.ietf.org/doc/draft-ietf-rats-corim/
>>
>> [3]
>> https://datatracker.ietf.org/doc/draft-cds-rats-intel-corim-profile/