Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] New xml2rfc release: v3.0.0

Jay Daley <> Wed, 02 September 2020 20:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5D28D3A0EC9; Wed, 2 Sep 2020 13:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Gc_mpTMGXvBs; Wed, 2 Sep 2020 13:36:44 -0700 (PDT)
Received: from jays-mbp.localdomain (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4F4933A0EB8; Wed, 2 Sep 2020 13:36:30 -0700 (PDT)
From: Jay Daley <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_65B8F290-8601-4DE2-946B-65C18F7C91F5"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Thu, 3 Sep 2020 08:36:28 +1200
In-Reply-To: <>
Cc:, XML2RFC Interest Group <>, XML Developer List <>, Henrik Levkowetz <>
To: Carsten Bormann <>
References: <> <> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] New xml2rfc release: v3.0.0
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 02 Sep 2020 20:36:46 -0000

>> You mention a “schema change board”, can you tell us more about the
>> coordinates of that?
> It's currently John Levine, Peter Saint-Andre, Robert Sparks and myself.
> It was set up in order to have some way of moving forward (or decide to
> not move forward) with various changes, whether registered as tickets,
> requested by the RPC or through the RPC by document authors, or otherwise
> brought up.

Just to provide some more context.  When we had an RSE they were responsible for helping the RPC and the developer (Henrik) triage incoming change requests and decide how those were addressed, which included: saying ’no’; changing the XML; changing the schema; and changing xml2rfc.

John’s role as Temporary RFC Series Project Manager (TRFCSPM) doesn’t include this responsibility, which left a gap that Henrik has being trying to fill while doing everything else.  Consequently, a small group has been formed to fill this gap as a temporary measure while the IAB process to determine the future role of an RSE progresses.  That group is made up of Henrik as the developer, John as the TRFCSPM, Robert as the Tools Team PM and Peter as an RSOC rep. 

’Schema Change Board’ is a label I’ve not heard before for this small group and sounds more established and authoritative than this group is meant to be.  


> Best regards,
> 	Henrik
> _______________________________________________
> xml2rfc mailing list

Jay Daley
IETF Executive Director