Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?

Robert Sparks <rjsparks@nostrum.com> Mon, 02 November 2020 18:02 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5993A00D2; Mon, 2 Nov 2020 10:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.247, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 2j3RrNxa4wcg; Mon, 2 Nov 2020 10:02:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E4DB3A0061; Mon, 2 Nov 2020 10:02:37 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F3D9DF406F7; Mon, 2 Nov 2020 10:02:16 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id DC770F406F7 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 10:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCInyk1fnPHu for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 10:02:14 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by rfc-editor.org (Postfix) with ESMTPS id 7EE79F406F6 for <rfc-interest@rfc-editor.org>; Mon, 2 Nov 2020 10:02:14 -0800 (PST)
Received: from unescapeable.local ([47.186.30.41]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0A2I2Ki9093221 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 2 Nov 2020 12:02:20 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1604340141; bh=AUqlZ/JeSqN8P5q7SUdj4s3NbwmRjAf4suyAqN5F3/Q=; h=To:References:From:Subject:Date:In-Reply-To; b=mKaRexlDTqwaspbJtTufZikYWHXzdOvpjY5ykgp2fbZsqCPn/G2d1ceU8JMivF+sA vRC6kh+q1EBAE/OJvxZRNAQbuN0O5sLGT7Np1jcriPz6J9dZPjNB2X7uOAu7re1urE kmFB9zzAVFTpRRyrRNTthRQHptE11toJLPdwOBGg=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.30.41] claimed to be unescapeable.local
To: Julian Reschke <julian.reschke@gmx.de>, tom petch <daedulus@btconnect.com>, rfc-interest@rfc-editor.org
References: <20201026181442.GA2438@faui48f.informatik.uni-erlangen.de> <263C265C19B24BA97AF48934@PSB> <225062D7-C061-4543-8665-53A4F4831510@isc.org> <20201029005519.GT39170@kduck.mit.edu> <A05242FC-C38C-474F-A2AC-412329CA5C52@isc.org> <CAKq15ve-kAFZWH_f7=1XXC5PfxvO-sAzppB1fVTyqUufLftkVg@mail.gmail.com> <D2DB703DBF2A44A19B8F80DD@PSB> <CAKq15vdFVkG6_grNtqUqq-yDwj9QQcHJFZB5+RB-8fdxQXhFSw@mail.gmail.com> <fa36e919-b1a0-5b3c-9b42-54c6fdaadfb@iecc.com> <e8554ea2-1849-279f-733d-5798de8817b9@gmail.com> <26d1ff54-777f-884b-e35-d91e9fe59662@iecc.com> <00a1fc15-7559-96c6-7cd7-3ae5afd62237@gmail.com> <a34f219b-7c76-4b48-4844-5af3cd4f344@iecc.com> <be8dce95-2b4c-52c8-7eda-8a9b127a6dd4@gmail.com> <cdc14c1-54c9-5273-584c-ddb656912952@iecc.com> <5F9FDB7E.1080805@btconnect.com> <ae44e31b-964a-7901-4883-72abb0dbb8d3@gmx.de> <5F9FF8EA.9020809@btconnect.com> <bfa63584-1f49-1370-65d0-a217dcc4dbc5@gmx.de> <e530ccdc-6587-13dd-df51-29fc0c0b2fcd@nostrum.com> <752c6c5d-eab0-966f-141f-a7d402fdf4fe@gmx.de>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <61673811-f47f-7122-2260-527bdec591d6@nostrum.com>
Date: Mon, 02 Nov 2020 12:02:20 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <752c6c5d-eab0-966f-141f-a7d402fdf4fe@gmx.de>
Content-Language: en-US
Subject: Re: [rfc-i] [Rsoc] RFCs with page numbers (pretty please) ?
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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Re-adding the context you dropped:

> I do understand that both would interfere with extraction code that has
> been written for plain text, but that should not be needed/used anymore
> in the v3 xml world anyway. 
zooming in to the particular specific you are asking for:

> that should not be needed/used anymore
> in the v3 xml world anyway. 
and again returning context:

> For the v3 transition, I'm still more on the fence that it's too soon 
> to break people's toolchains just because we can. At some point, when 
> there's not such a mix of historic text files that have to be 
> processed along with the new things (which may or may not be in v3 
> format while they are internet drafts), then sure - we can say "Get 
> with the times". But I don't think those times are here yet. 
I'm puzzled that you didn't find the exact point of disagreement in 
that, but I'll try to restate it:

Some people have repeatedly held the position it's ok to disrupt 
existing toolchains because what we're creating is so much better and 
breakage will make people use the new thing. Others think that a longer 
period of transition allowing older toolchains to continue working is 
important.



On 11/2/20 11:49 AM, Julian Reschke wrote:
> Am 02.11.2020 um 17:17 schrieb Robert Sparks:
>> It's worth noting that this has been a fundamental point of disagreement
>> between people involved in the v3 effort (and is often so in any world
>> where you are adding big new things).
>> ...
>
> Which point exactly?
>
> Best regards, Julian

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest