From nobody Thu Oct 7 17:43:27 2021 Return-Path: X-Original-To: admin-discuss@ietf.org Delivered-To: admin-discuss@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0983A00D6 for ; Thu, 7 Oct 2021 17:43:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Administration LLC Board of Directors Chair To: X-Test-IDTracker: no X-IETF-IDTracker: 7.38.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: admin-discuss@ietf.org Message-ID: <163365380434.27962.7303825958312943478@ietfa.amsl.com> Date: Thu, 07 Oct 2021 17:43:26 -0700 Archived-At: Subject: [admin-discuss] LLC Board Meeting Details - 14 October 2021 X-BeenThere: admin-discuss@ietf.org X-Mailman-Version: 2.1.29 List-Id: Discussion list for IETF LLC administrative issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Oct 2021 00:43:26 -0000 IETF LLC Board of Directors meetings are conducted via web/teleconference. Members of the community are welcome to attend certain portions of these meetings as observers. Regular meetings are divided into four sections: 1. Open (to Observers) 2. Board + Support Staff Only 3. Board + Executive Director Only 4. Executive Session (Board-Only) The next meeting will be held on Thursday, 14 October 2021 at 12:00 PT (19:00 UTC). WebEx and Dial-in information is at the bottom of this message and also at . The agenda for the meeting can be found at . A calendar of upcoming public meetings can be downloaded or subscribed to at: https://calendar.google.com/calendar/ical/ietf.org_vmffrv4hq14aqpedenuv5v42hs%40group.calendar.google.com/public/basic.ics ------------------------------------------------------- JOIN WEBEX MEETING https://ietf.webex.com/ietf/j.php?MTID=m5481867e37f4c98327c151d9a6a7cd78 Meeting number (access code): 178 797 1273 Meeting password: meetings JOIN BY PHONE 1-650-479-3208 Call-in toll number (US/Canada) Access code: 178 797 1273 IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. From nobody Mon Oct 25 14:49:13 2021 Return-Path: X-Original-To: admin-discuss@ietfa.amsl.com Delivered-To: admin-discuss@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA1DD3A0FBF; Mon, 25 Oct 2021 14:49:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.917 X-Spam-Level: X-Spam-Status: No, score=-0.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PDS_RDNS_DYNAMIC_FP=0.001, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NiLUh81NlR2N; Mon, 25 Oct 2021 14:49:00 -0700 (PDT) Received: from sobco.sobco.com (173-166-5-71-newengland.hfc.comcastbusiness.net [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id C2F463A1057; Mon, 25 Oct 2021 14:48:43 -0700 (PDT) Received: from [192.168.50.224] (173-166-5-67-newengland.hfc.comcastbusiness.net [173.166.5.67]) by sobco.sobco.com (Postfix) with ESMTPSA id BBC22C27D4E; Mon, 25 Oct 2021 17:48:42 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\)) From: "Scott O. Bradner" In-Reply-To: <163519459469.589.12754966153448508018@ietfa.amsl.com> Date: Mon, 25 Oct 2021 17:48:41 -0400 Cc: IETF Announcement List Content-Transfer-Encoding: quoted-printable Message-Id: <19FCE016-231E-49CD-9A61-6459325B309F@sobco.com> References: <163519459469.589.12754966153448508018@ietfa.amsl.com> To: admin-discuss@ietf.org, IETF Chair X-Mailer: Apple Mail (2.3445.9.7) Archived-At: Subject: Re: [admin-discuss] Information about error in the IPR disclosure form X-BeenThere: admin-discuss@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion list for IETF LLC administrative issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Oct 2021 21:49:12 -0000 seems like the right set of things to do Scott > On Oct 25, 2021, at 4:43 PM, IETF Chair wrote: >=20 > We recently became aware of an error on the IETF IPR disclosure form: = text on the form appears to suggest that disclosures and any stated = licensing commitments apply only to "standards-track" documents (the = form states: "Above licensing declaration is limited solely to = standards-track IETF documents"). However, IETF participants routinely = file disclosures and make licensing commitments on non-standards-track = documents, such as Experimental or Informational RFCs or Internet-Drafts = intending to be published as such. The error has led to some odd = dissonance, such as where a disclosing party has explicitly committed to = license implementations of non-standards-track RFCs cited in their = disclosure form, via a form that appears to undermine the stated = commitment. =20 >=20 > Some non-standards-track RFCs are widely implemented, and implementers = expect that the express licensing commitments made in connection with = these RFCs are binding. >=20 > We traced the error back to a change to the disclosure form made in = late December of 2014. Prior to 2012, IPR disclosures were made to the = secretariat by e-mail using the form described in RFC 3905. In 2012, a = web form was created that used more-or-less the same format. = Unfortunately, the data from the checkbox indicating that the licensing = declaration "is limited solely to standards-track RFCs" was accidentally = not saved for those disclosures, meaning if anyone checked them, we = don't have a record of it. For this reason, a decision was made in 2014 = to eliminate this checkbox option, but an error was made in implementing = this decision, resulting in the checkbox itself being eliminated, but = the associated text remaining on the form, introducing an unintended = suggestion that the limitation applied to all disclosures.=20 >=20 > Uncovering the fact that the checkbox data from 2012-14 was not saved = raised an additional concern. During that period a party may have made a = disclosure on a non-standards-track document and affirmatively checked = this box. This combination would lead to the same dissonance identified = above=E2=80=94a party would have made an explicit license commitment = related to a non-standards-track document that would appear to be = undermined by a contrary statement=E2=80=94but the intent of the = discloser in this case would be a degree murkier. We simply don=E2=80=99t = know if this ever happened. =20 >=20 > Precise details of the 2014 decision to eliminate the checkbox appear = to have been lost to history, but the logic seems clear: if a party = chooses to file a disclosure and make an associated express license = commitment on technology embodied in a non-standards-track IETF = document, nobody's interest is served by introducing ambiguity into the = equation. Promising to license but then checking a box that undermined = this promise wouldn't make sense, so removing this checkbox option was = logical, particularly given that parties that specifically desired to = exclude these types of specifications from their licensing commitment = could always state this in the text of their declaration. Unfortunately, = the implementation error that removed the checkbox but kept the text = introduced its own ambiguity, which we are now striving to resolve. = Further, we want to address any potential uncertainties caused by the = missing 2012-2014 checkbox data. >=20 > We are taking three actions to resolve these errors: >=20 > 1. We are correctly implementing the 2014 decision, by removing the = text from the IPR disclosure form that says "Above licensing declaration = is limited solely to standards-track IETF documents." Licensing = declarations apply to whatever documents the disclosing party cites in = their form, whether they are published or intended to be published as = standards-track documents or non-standards-track documents. >=20 > 2. We are sending emails to each of the 54 parties that filed an IPR = disclosure form between 21-DEC-2014 and now that explicitly references a = document that was, or became, a non-standards-track RFC, bringing their = attention to this announcement and stating our understanding that any = express commitment they made to license implementations of a = non-standards-track IETF document control over the erroneous statement = in the form. We believe this is the only reasonable interpretation of = the ambiguity introduced by the erroneous text, but if a party that = previously made a licensing commitment disagrees they might choose to = update their disclosure to clarify their position. They can find their = disclosure at https://datatracker.ietf.org/ipr/about/. >=20 > 3. We are sending emails to each of the 50 parties that filed an IPR = disclosure form between 25-FEB-2012 and 21-DEC-2014 that explicitly = references a document that was, or became, a non-standards-track RFC, = bringing their attention to this announcement and stating that our = understanding is that parties that made an explicit license commitment = in connection with a non-standards-track document intended to be bound = by that commitment, and that we will assume that disclosing parties did = not check the box that would have appeared to undermine their explicit = commitment. Parties will be free to update their disclosure if they wish = to communicate anything different. They can find their disclosure at = https://datatracker.ietf.org/ipr/about/. >=20 > Please let me know if you have any questions about this matter. >=20 > Lars Eggert > IETF Chair >=20 > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce