From nobody Sun Jan 17 16:07:59 2021 Return-Path: X-Original-To: gendispatch@ietf.org Delivered-To: gendispatch@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8436F3A0A29; Sun, 17 Jan 2021 16:07:57 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: alissa@cooperw.in, francesca.palombini@ericsson.com, gendispatch-chairs@ietf.org, gendispatch@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.24.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <161092847743.29353.15415162214239008017@ietfa.amsl.com> Date: Sun, 17 Jan 2021 16:07:57 -0800 Archived-At: Subject: [Gendispatch] gendispatch - New Meeting Session Request for IETF 110 X-BeenThere: gendispatch@ietf.org X-Mailman-Version: 2.1.29 List-Id: General Area Dispatch List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 00:07:58 -0000 A new meeting session request has just been submitted by Francesca Palombini, a Chair of the gendispatch working group. --------------------------------------------------------- Working Group Name: General Area Dispatch Area Name: General Area Session Requester: Francesca Palombini Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 150 Conflicts to Avoid: Chair Conflict: artarea cbor ace core lake quic dprive anima opsawg spring tls wpack webtrans raw secdispatch emailcore Technology Overlap: genarea People who must be present: Pete Resnick Alissa Cooper Francesca Palombini Resources Requested: Special Requests: --------------------------------------------------------- From nobody Sun Jan 24 16:34:20 2021 Return-Path: X-Original-To: gendispatch@ietfa.amsl.com Delivered-To: gendispatch@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E90AB3A098C for ; Sun, 24 Jan 2021 16:34:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 yUr1F_mMx9Wv for ; Sun, 24 Jan 2021 16:34:16 -0800 (PST) Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DD193A0983 for ; Sun, 24 Jan 2021 16:34:16 -0800 (PST) Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from ) id 1l3ppe-0007IG-U0 for gendispatch@ietf.org; Sun, 24 Jan 2021 19:34:14 -0500 Date: Sun, 24 Jan 2021 19:34:08 -0500 From: John C Klensin To: gendispatch@ietf.org Message-ID: <7D714CFF4D97DD562B2C5639@PSB> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-SA-Exim-Connect-IP: 198.252.137.10 X-SA-Exim-Mail-From: john-ietf@jck.com X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false Archived-At: Subject: [Gendispatch] RFC 2028 X-BeenThere: gendispatch@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Area Dispatch List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2021 00:34:18 -0000 Hi. In conjunction with another effort, I've had occasion to review RFC 2028, "The Organizations Involved in the IETF Standards Process". With the passage of time, it is in really, seriously bad shape, having been, AFAICT, updated since October 1996 only for IPR-related issues and the IETF Administration LLC terminology change. It points (normatively in terms of use in the text) to a copy of documents as Work in Progress, neither of which has ever been published under that name. It still claims the IETF Chair is appointed by the IAB. While RFC 8717 (for which I'm the guilty party) made the Executive Director update, it points to 8711 for details that aren't really there and it is not clear to me whether we really intended the Secretariat, rather than the LLC to be "responsible for maintaining the formal public record of the Internet standards process". There are also many other errors due to the world changing and passing it by. Unlike the changes for the LLC, fixing 2028 is not going to be mostly a trivial substitution process. There are many things that just need to be corrected and hence should not be controversial but a few that will require decisions that may not easily get consensus. Anyway, while I don't think I want to volunteer to lead such an effort, I'd like to put "figure out how to revise, update, and likely replace RFC 2028" on the agenda because the document, in its current state, is periodically cited as a key process BCP and it rather badly represents the current IETF. john