IETF Logo Mail Archive

Re: [Rfced-future] Welcome to the RFC Editor Future Development Program

"John R. Levine" <johnl@iecc.com> Fri, 03 April 2020 20:46 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A36D13A0ADE for <rfced-future@ietfa.amsl.com>; Fri, 3 Apr 2020 13:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com
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 Hj4XQ--1u2PX for <rfced-future@ietfa.amsl.com>; Fri, 3 Apr 2020 13:46:19 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E2C93A0A98 for <rfced-future@iab.org>; Fri, 3 Apr 2020 13:46:19 -0700 (PDT)
Received: (qmail 83042 invoked from network); 3 Apr 2020 20:46:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14460.5e87a099.k2004; i=johnl-iecc.com@submit.iecc.com; bh=+m0X/GL6xtcjQRuf/bKAaZ7CPFLKpvcsa+rdxhvVtiM=; b=D35nYHzt0AYJNkjBw7tsmZHDOKyeuzpLNfy/vjXCO62+OBzujDPF/cW8g6JSNCHAbDq2mHAClvIlDHSvxuoJ6LUSrXDDPEokSKv/+iqKmEJKV6973R8Ra6mqbZTE1qYBYliMuI9W0/tBvkdTBNnNhpNySx4C3Agq7040knNnZjDwaJAUkI46pnHNDn4LlRnlfoiy2V/jb6eZgP6c7hWKSeu5aWswAO10/qgkv88TgalEyvq9IDAelQ8b/WQ1MUhc
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 03 Apr 2020 20:46:17 -0000
Date: Fri, 03 Apr 2020 16:46:17 -0400
Message-ID: <alpine.OSX.2.22.407.2004031644350.42355@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Julian Reschke <julian.reschke@gmx.de>
Cc: rfced-future@iab.org
In-Reply-To: <46ebaffc-9c69-f5ce-8155-bd7dda3cde7c@gmail.com>
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy> <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com> <009601d60964$2648e7a0$72dab6e0$@acm.org> <alpine.OSX.2.22.407.2004022303110.37555@ary.qy> <1533669f-6891-e50a-be08-b5293fc5cbbf@gmx.de> <DF6A09DD-C7D4-4542-B83F-C687861F5492@tzi.org> <3b1df23c-d1e4-46f9-d7d4-6fac978be8d3@gmx.de> <46ebaffc-9c69-f5ce-8155-bd7dda3cde7c@gmail.com>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/87p8cDCIdPdpOMoFPiYbeasFSos>
Subject: Re: [Rfced-future] Welcome to the RFC Editor Future Development Program
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Apr 2020 20:46:25 -0000

>> The (canonical, published) XML never ever should be adjusted to work
>> around a bug. Is this happening?

I sure hope not.  The RPC now has a document state TI that means that a 
document is waiting for tools to be fixed.  That's happened a few times 
but so far the fixes have been simple enough that Henrik has been able to 
do them without unduly delaying the documents.

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email