IPR disclosure bug and IESG response

IETF Executive Director <exec-director@ietf.org> Fri, 18 August 2023 14:12 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81ACFC14CF13 for <ipr-wg@ietfa.amsl.com>; Fri, 18 Aug 2023 07:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20221208.gappssmtp.com
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 KiOe_hazX1CR for <ipr-wg@ietfa.amsl.com>; Fri, 18 Aug 2023 07:12:00 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 D313AC15109B for <ipr-wg@ietf.org>; Fri, 18 Aug 2023 07:12:00 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-522dd6b6438so1185400a12.0 for <ipr-wg@ietf.org>; Fri, 18 Aug 2023 07:12:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20221208.gappssmtp.com; s=20221208; t=1692367919; x=1692972719; h=to:cc:message-id:date:subject:mime-version:reply-to :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=jnZQr70vsCgcvKi9LL9zFFYCP6/n+0rq4fsNpq1PB/g=; b=nblGXLkCEqz4/BM1JXYWbziu6HK1TGG/e133JojSswNNXaHMGUrz8xQBj6fwD9zVGn Aa8bV4pW5NWRuAhGCiDOCgVGK43khMwQGo1iIZj2dxLmbWlv1HZs/khFdZgM3DM7EOVp PAjpgw3mgm4eYClDkZnqFofBWyxoACvFqPNorvP04ugLivTi5HZM1jJ6TRfGIgl4325c T8hm9tCPB+YkwmH/4AeLr0DfWkN4yZYLizB5EbzJeeIiqJNvg+fXjdsG0sE1PVLhNaEU SSLOYMajov5mYweRwc07JErInKnjV4y+ZeThy/CZJDfr0OmyWlQ4eFlqg5rkRoKXgpHC szDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692367919; x=1692972719; h=to:cc:message-id:date:subject:mime-version:reply-to :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jnZQr70vsCgcvKi9LL9zFFYCP6/n+0rq4fsNpq1PB/g=; b=F6WJRSHpsrkP1EQJlMtjfVQxn8q3K+gLSuSqNvhklEKBh5dn7JNKA3hZOm8/46dA5q Qecmt+2JIDPdw1stCh2rb4VYGsJXwxyELAqQvN5BMHkoWIp3KXXJPZLZtpSNbQtzGPN/ LH9nk5RGnzyOoGD93gzuoIaX6uI4B1vtIW5I540I6vMuDmGMC6bDRGQezWcoC22eL+Oj aZ2iRNdWaZNL9sr5W5CrGvi2PIg8iezOabH3QpTZ2egvtQZ5rK8j+aMBtPmS7SEQJ26h rpWFAWdieyP8dX2PrQmsB0vqhYamXoyXcixb2yc5pdplBGBisdLRvumy9a2lcDzHrux1 y/1w==
X-Gm-Message-State: AOJu0YxvTgAjrkD1EWi/OmFt3ofwFG6v5wdAPeBFNrDuF9OlPRA7f749 4UClBiE3758oihEO6myLf5YeKgvNrJqf8nyi7jlI6C+G
X-Google-Smtp-Source: AGHT+IFTzR19HWJuDfaneEVbup/GTGlRvpa4Om72B+M/W8XwdWq5TE/ncQzI5ElFN5zzdHW9c3ivTA==
X-Received: by 2002:a17:906:74d7:b0:99d:f7f3:5218 with SMTP id z23-20020a17090674d700b0099df7f35218mr1945175ejl.25.1692367918905; Fri, 18 Aug 2023 07:11:58 -0700 (PDT)
Received: from smtpclient.apple ([92.27.125.209]) by smtp.gmail.com with ESMTPSA id q15-20020a1709060f8f00b0099ba3438554sm1235726ejj.191.2023.08.18.07.11.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Aug 2023 07:11:58 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Reply-To: The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Subject: IPR disclosure bug and IESG response
Date: Fri, 18 Aug 2023 15:11:47 +0100
Message-Id: <6FBD043B-2758-45B0-AF05-11475A0A47B5@ietf.org>
Cc: ipr-announce@ietf.org, ipr-wg@ietf.org
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipr-wg/lzqL9OzJMHSiJxapS_c6eBYZhf4>
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipr-wg/>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2023 14:12:04 -0000

In June 2023, the IESG was alerted [1] to a bug in the IPR disclosure system that has been present since 2014, which meant that IPR disclosures were not linked to a specific Internet-Draft (I-D) version, as required by the relevant RFCs [2].

Going forward, this bug will be fixed so that any IPR disclosure must specify the I-D version. 

The IESG has discussed in depth, with the assistance of counsel and the Tools Team, what to do with the ~3,500 IPR disclosures that were posted while this bug existed.  It has concluded that the only time where the relevant version can be accurately deduced is when there was only a -00 version of the I-D at the time of the disclosure, because for all other disclosures, the intended I-D version may have been a previous version.   

The IESG also considered if a standard warning message could be applied to all of these disclosures but there are too many different circumstances that such a warning would need to account for.

The IESG has therefore asked the Tools Team to add relevant on-screen notices that warn readers about the applicability of these IPR disclosures along with a recommendation on who to contact if they have any questions about which version the disclosure applies to.  There will be multiple versions of this notice, depending on multiple factors including who made the disclosure and what versions existed when it was made.

The changes to the IPR disclosure system are scheduled to be deployed within a week.

Please send any feedback or questions to the IESG at iesg@ietf.org

[1]  https://mailarchive.ietf.org/arch/msg/ipr-wg/h2VHiw8slrZsoUvEtdGzuX98kgw/
[2]  RFC 3668 (from February 2004), RFC 4879 (from March 2005), RFC 8179 (from March 2017).

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org