Follow up to consultation on restricting participant access to IETF systems

IETF Executive Director <exec-director@ietf.org> Thu, 25 August 2022 12:16 UTC

Return-Path: <exec-director@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C64BC1522C7 for <ietf-announce@ietfa.amsl.com>; Thu, 25 Aug 2022 05:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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
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 A4Mo7mjkOMXW for <ietf-announce@ietfa.amsl.com>; Thu, 25 Aug 2022 05:16:26 -0700 (PDT)
Received: from ietfx.amsl.com (ietfx.amsl.com [50.223.129.196]) (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 E2C44C14CE20 for <ietf-announce@ietf.org>; Thu, 25 Aug 2022 05:16:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ietfx.amsl.com (Postfix) with ESMTP id 8DFD640A6A6B for <ietf-announce@ietf.org>; Thu, 25 Aug 2022 05:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from ietfx.amsl.com ([50.223.129.196]) by localhost (ietfx.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26QFkOC3Fsil for <ietf-announce@ietf.org>; Thu, 25 Aug 2022 05:16:26 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net [92.27.125.209]) by ietfx.amsl.com (Postfix) with ESMTPSA id 24C6F40A6A63 for <ietf-announce@ietf.org>; Thu, 25 Aug 2022 05:16:25 -0700 (PDT)
From: IETF Executive Director <exec-director@ietf.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Follow up to consultation on restricting participant access to IETF systems
Message-Id: <B278EBB7-02C2-4197-BAF2-68CD1AF37BEF@ietf.org>
Date: Thu, 25 Aug 2022 13:16:23 +0100
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/_wXvXf0Datm4PFckr51_VXCJCvc>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2022 12:16:30 -0000

The IETF Administration LLC initiated a consultation on 29 June 2022 [1] on restricting participant access to IETF systems in specific circumstances in order to mitigate potentially serious legal consequences.  The responses to this consultation were mixed, with much of the focus on who is responsible for any such action and how the decisions are made [2].  The IESG and LLC have discussed the responses and agreed the the following:

1.  There will be a documented policy for restricting participant access to IETF systems covering the proposed set of circumstances
Some of the feedback was that a policy was not necessary, while some proposed limiting the applicable circumstances, but the IESG and LLC believe that one is needed to cover the identified circumstances for a number of reasons, including compliance with the DMCA safe harbour regime, transparency, and to set expectations.

2.  The IESG will be the owner and approver of the policy.  
Feedback on this point was mixed, but given the potential for an impact on the standards process the IESG believes it should assume responsibility for that by owning and approving the policy.  The LLC agrees and defers to the IESG.

3.  The policy will be written and maintained by the LLC for the iESG
While the IESG will be the owner and approver, which may include detailed decision making about the contents of the policy, the work of writing and maintaining it will be delegated to the LLC in order to ensure that any proposed text correctly addresses the legal responsibilities of the LLC.

The next steps are for the LLC to produce a draft policy for the IESG to consider, based on detailed feedback provided by the IESG.  Once a draft is ready for discussion, the IESG will decide what form any final policy should take and how to engage the community in that.


[1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/L8z1bBQ0ShDiJn2QHqEFXlAyQK0/ 
[2]  https://mailarchive.ietf.org/arch/browse/admin-discuss/?gbt=1&index=natSSnn6ULYWfQtMtEMnNjANsA8

Please feel free to contact me or the IESG if you have any questions.
-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org