IETF Logo Mail Archive

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

"John R. Levine" <johnl@iecc.com> Thu, 02 April 2020 21:09 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 721A53A19DA for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 14:09:44 -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 8VWXtWfVHZz2 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 14:09:43 -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 B7A253A19D9 for <rfced-future@iab.org>; Thu, 2 Apr 2020 14:09:42 -0700 (PDT)
Received: (qmail 30170 invoked from network); 2 Apr 2020 21:09:40 -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=75d8.5e865494.k2004; i=johnl-iecc.com@submit.iecc.com; bh=XcQwGl/BMafb3BmPCGgZ2MWJRK51o5Ch0UtUDqMUKls=; b=gb00f2YrmD+bIDuO3VexOMwGUED4FAWKD10Bu6k/0Zh2EAgNZ/tjr5hAzf6a/KwoeoAHLt5TvplwkLvCfm0tRFt9PhVqCmy7b7MkGZ0K3/sxJffAhTX0O4wMHpXeNhlBZw/f6WaADoWfQFp7N2dUpSm2UkoCKpTh/Iqxjoc7G61RjdHMXvo5aOBk9LiMP1KlUcg9mWJkmPG9/jGtTMQmPAPE/QUTEFAZ/9lD0kE1XDnFk2X1CWL0hqdiIteW4l2e
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; 02 Apr 2020 21:09:39 -0000
Date: Thu, 02 Apr 2020 17:09:39 -0400
Message-ID: <alpine.OSX.2.22.407.2004021706460.35478@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Cc: rfced-future@iab.org, LMM@acm.org
In-Reply-To: <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.gmail.com>
References: <0ac801d6089c$c36031b0$4a209510$@acm.org> <20200402195947.D569E16EE8CE@ary.qy> <CAA=duU2Zyr9gju4J+smtfeWy4iTiJCRQCeGozkbnaHtA66z7PA@mail.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/1LNJiMJVLNgi2fIjRx3nL2Ee_BU>
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: Thu, 02 Apr 2020 21:09:45 -0000

> But following this process, I'm fairly certain that "the to-be-published 
> RFC, in all its published formats, reflects the intent of the author and 
> the body that approved it."  So I'm curious why you feel that's not 
> possible.

Usually it will, but sometimes no matter how careful everyone is, 
sometimes they'll miss something.  I'm certainly not saying that we 
shouldn't try to make the quality as good as possible, but I am saying 
that as good as possible is not perfect and our processes have to be able 
to deal with that reality.

Sometimes it slips through all the way to the published RFC, which is why 
we have errata.  We have a lot of them, not infrequently for documents 
published many years ago.

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