[rfc-i] Managing the v3 XML and Style Guide change requests

Sarah Banks <sbanks@encrypted.net> Wed, 14 October 2020 16:14 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 322353A097A; Wed, 14 Oct 2020 09:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id sCWIx0MpN_2p; Wed, 14 Oct 2020 09:14:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E22C23A0972; Wed, 14 Oct 2020 09:14:23 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6EA37F4071C; Wed, 14 Oct 2020 09:14:04 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost []) by rfc-editor.org (Postfix) with ESMTP id 9E6D1F4071C for <rfc-interest@rfc-editor.org>; Wed, 14 Oct 2020 09:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([]) by localhost (rfcpa.amsl.com []) (amavisd-new, port 10024) with ESMTP id bBbmNwW84A3n for <rfc-interest@rfc-editor.org>; Wed, 14 Oct 2020 09:14:02 -0700 (PDT)
Received: from aws.hosed.org (aws.hosed.org []) by rfc-editor.org (Postfix) with ESMTPS id 40EC9F4071B for <rfc-interest@rfc-editor.org>; Wed, 14 Oct 2020 09:14:01 -0700 (PDT)
Received: from localhost (localhost []) by aws.hosed.org (Postfix) with ESMTP id EF98BE02E5; Wed, 14 Oct 2020 12:14:19 -0400 (EDT)
Received: from aws.hosed.org ([]) by localhost (aws.hosed.org []) (amavisd-new, port 10024) with ESMTP id 6jmjb5I3nYRs; Wed, 14 Oct 2020 12:14:19 -0400 (EDT)
Received: from [] (c-73-71-250-98.hsd1.ca.comcast.net []) by aws.hosed.org (Postfix) with ESMTPSA id 82632E02E1; Wed, 14 Oct 2020 12:14:19 -0400 (EDT)
From: Sarah Banks <sbanks@encrypted.net>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Message-Id: <E35A80B8-C9A7-42C2-BA5E-B911303E5217@encrypted.net>
Date: Wed, 14 Oct 2020 09:14:18 -0700
To: RFC Interest <rfc-interest@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.104.14)
Subject: [rfc-i] Managing the v3 XML and Style Guide change requests
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RSOC <rsoc@iab.org>, Internet Architecture Board <iab@iab.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>


	A key role of the RFC Series Editor (RSE) has been to support the RFC Production Center (RPC) and the xml2rfc developer, Henrik Levkowetz, in triaging incoming change requests for the v3 XML and the RFC Style Guide and deciding how those are addressed.  This could mean saying 'no', or any combination of changing the XML of an I-D, changing the v3 XML schema, and changing the Style Guide.

	The role of the Temporary RFC Series Project Manager (TRFCSPM), John Levine, doesn’t include this responsibility and that has left a gap with no clear management of these decisions.  Consequently, the RSOC has formed an "RFC XML and Style Guide change management team" to fill this gap as a temporary measure while the IAB process to determine the future role of an RSE progresses.  This team is made up of Henrik Levkowetz as the developer, John Levine as the TRFCSPM, Robert Sparks as the Tools Team PM and Peter Saint-Andre as an RSOC representative. The role of the team will be to discuss and approve all changes to the RFC XML and Style Guide.

	It is expected that providing this formalization around change management will lead to the v3 XML schema stabilizing quickly, which in turn will enable a new SLA to be established and so ensure that RFC processing times meet community expectations.

Sarah Banks
On behalf of the RSOC

rfc-interest mailing list