Re: RFC 20 status change last call: References to appendices

Julian Reschke <> Fri, 02 January 2015 15:27 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 47A131A87C7 for <>; Fri, 2 Jan 2015 07:27:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cRTvl-wiMUtk for <>; Fri, 2 Jan 2015 07:27:52 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AEE4E1A879E for <>; Fri, 2 Jan 2015 07:27:51 -0800 (PST)
Received: from [] ([]) by (mrgmx103) with ESMTPSA (Nemesis) id 0LjJCt-1XYYP41Qbv-00dXYR; Fri, 02 Jan 2015 16:27:49 +0100
Message-ID: <>
Date: Fri, 02 Jan 2015 16:27:42 +0100
From: Julian Reschke <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Carsten Bormann <>
Subject: Re: RFC 20 status change last call: References to appendices
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:RNzi1Sc2MnUL7w0+nibiKeITxHxn2XvSY9rvC7ko1Ma05+ytuiL Kq+UPgDKqCX1Q4jPHtcMQTIpV1cqSgWjXakL6rcFBBlc/ot/LapM4ftdujaCIEaacNWGPE9 /edAGfLnRwCXCRCFR+Vs4hyzZKjLdPplQAH+m/b5VuDPGI15rktSWzhqpUg7Ak/Gcxz1WKZ ziAtIFy27UrnX+HhYrJZg==
X-UI-Out-Filterresults: notjunk:1;
Cc: IETF Discussion List <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 02 Jan 2015 15:27:53 -0000

On 2015-01-02 16:13, Carsten Bormann wrote:
> On 02 Jan 2015, at 14:20, Julian Reschke <> wrote:
>> rfc20bis
> The original intention was to have a low-effort procedure to recognize RFC 20 for its standards status.
> I continue to believe this is the right thing to do.
> I do believe it would be a worthwhile effort to think about the place that ASCII has in Internet protocols in 2015, but if there is a result from that, that would be a quite different document.
> The current discussion is to a large extent about the way the original RFC was turned into the online version.
> AFAIK, we haven’t had this discussion at all for any of the reconstructed RFCs.
> And I’m not sure that the rules for new RFCs fit with the reconstructed ones.
> The original RFC has been issued on paper, and that is what shouldn’t change, not necessarily the (always less than perfect) rendition as plaintext.  But there is a cost to giving up the translation of the “RFCs never change” mantra into “RFC files never change”, even for the reconstructed files, and I’m not sure this can of worms needs to be opened.
> ...


So if this exercise is supposed to make sense, we'll first have to find 
out whether the rfc 20 text file we're looking at actually is a useful 
conversion of the original RFC 20. If it's not, there's no point in 
having a discussion about re-classification until we all can read the 
same document.

Best regards, Julian