IETF Logo Mail Archive

Re: [Rats] IPR check for draft-ietf-rats-architecture

Eliot Lear <lear@lear.ch> Wed, 21 September 2022 06:28 UTC

Return-Path: <lear@lear.ch>
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 2927AC1522A8 for <rats@ietfa.amsl.com>; Tue, 20 Sep 2022 23:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.899
X-Spam-Level:
X-Spam-Status: No, score=-0.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 rTZBIb0HTp1z for <rats@ietfa.amsl.com>; Tue, 20 Sep 2022 23:28:35 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ECE6C14CE44 for <rats@ietf.org>; Tue, 20 Sep 2022 23:28:34 -0700 (PDT)
Received: from [IPV6:2001:420:c0f8:1002::144] ([IPv6:2001:420:c0f8:1002:0:0:0:144]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 28L6SOiQ1872366 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 21 Sep 2022 08:28:25 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1663741706; bh=Sh4T52VhTEDu7QKVMHFA/XKKGbujc+lTueTePYeqeIU=; h=Date:Subject:To:References:From:In-Reply-To:From; b=aVTUaDny1z8P079EZ89h0pxCS5rD29U8U3fUSmdYNQ1J5fGjSwT0nkpY3DgaQkauE Nk2nRl5cZEK6JtKbxIA0tTlcuwkrvG5TlNethex+OtbtoBN8Y0++O1FIZyn7DLQqTp wigNyTtkDPXVF6I8sFIXqLgtOaAmr51vpcm3PL7A=
Message-ID: <be7f6b26-4bd5-1f77-ae1d-e5a98c9f70ff@lear.ch>
Date: Wed, 21 Sep 2022 08:28:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.13.0
Content-Language: en-US
To: Roman Danyliw <rdd@cert.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "rats@ietf.org" <rats@ietf.org>
References: <BN2P110MB110700AC2C8A6C5DB916DDFDDC4C9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM> <1394812.1663695639@dooku> <BN2P110MB1107D9FFBF8E79DDB958A053DC4C9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <BN2P110MB1107D9FFBF8E79DDB958A053DC4C9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------G6CQFKsRpUl5z0UjSqmRwCqg"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/MicF-mWv6EjB9p4rrgFkhe5MYYk>
Subject: Re: [Rats] IPR check for draft-ietf-rats-architecture
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: Wed, 21 Sep 2022 06:28:40 -0000

Hi Roman,

On 20.09.22 23:43, Roman Danyliw wrote:
> As a process check, in this call as in the one during WGLC (https://mailarchive.ietf.org/arch/msg/rats/3nCTOkNYW8ydEo0zHZlQoY8F92A/), we want to chart a path for how to proceed with the document, not evaluate the merits of the IPR claim.

That's hard to do without understanding what the claims are.

Eliot

v2.23.0 | Report a Bug | By Email