Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 18 September 2018 10:01 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C588D1292AD for <netmod@ietfa.amsl.com>; Tue, 18 Sep 2018 03:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level:
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_SORBS_WEB=1.5] autolearn=no autolearn_force=no
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 NtViMWr3IVAS for <netmod@ietfa.amsl.com>; Tue, 18 Sep 2018 03:01:34 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (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 4B44B130E93 for <netmod@ietf.org>; Tue, 18 Sep 2018 03:01:29 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id w8IA1JsL027977; Tue, 18 Sep 2018 11:01:22 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B56E522042; Tue, 18 Sep 2018 11:01:22 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs3.iomartmail.com (Postfix) with ESMTPS id A9C5722040; Tue, 18 Sep 2018 11:01:22 +0100 (BST)
Received: from 950129200 ([147.67.241.226]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id w8IA1LFE012009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Sep 2018 11:01:21 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'tom petch' <ietfc@btconnect.com>, 'Carsten Bormann' <cabo@tzi.org>, 'Robert Wilton' <rwilton=40cisco.com@dmarc.ietf.org>
Cc: netmod@ietf.org
References: <153617788181.19783.8030234113753073864.idtracker@ietfa.amsl.com> <5404BB62-C21E-4A70-AABC-6FEF1FC5C44F@juniper.net> <072a01d44771$0da216b0$28e64410$@olddog.co.uk> <8e62fa6d-b4a9-a6e3-b13f-145d2e50d208@cisco.com> <5ED5E487-E172-482B-ADB2-CD52A1EBCA14@bogus.com> <becad6b4-16f6-1d42-cdee-5fcf487b7d6e@cisco.com> <C0044BB4-1C2A-47AD-BE27-5A1697112B44@tzi.org> <041e01d44f35$77937340$4001a8c0@gateway.2wire.net>
In-Reply-To: <041e01d44f35$77937340$4001a8c0@gateway.2wire.net>
Date: Tue, 18 Sep 2018 11:01:20 +0100
Message-ID: <029001d44f36$8d3becd0$a7b3c670$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQNMbeAd7T+KwxeaeTKnNanmGQhT/wHtRokaArXGvDMBt+PrNwHPgdn9AQVO5SAA3ZTFvAIgbfo/oaQiEtA=
Content-Language: en-gb
X-Originating-IP: 147.67.241.226
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24102.006
X-TM-AS-Result: No--29.017-10.0-31-10
X-imss-scan-details: No--29.017-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24102.006
X-TMASE-Result: 10--29.016500-10.000000
X-TMASE-MatchedRID: 8+bhjh9TQnHxIbpQ8BhdbGiLf4SoVPzcmX+W7bzPOQH4JyR+b5tvoPTY LJi/AavYDsh9p6l8zpHgEe/gTiF1iWlm2w5uC3SGx7fVVD7rJEa36GGfwjLoZdp1biJhIyNRp7u eaEkDqTNe9N8X0ShXYCFyczyoJ0Rqkndp49uKhpOaVoAi2I40/fa/bRHEsPI32viB/Jr4D1Tr3n k7Nsq0gMz/SAq7gu2dBjJOMVCX9gquI2PD0uhaO8u00lnG8+PWu1b0t4ooa9swyfWtyopBqO94N WIGgiGMSW1GMAtQX7EpcDh3tjTU707YDfWPiC7Gqbg9uWhLYLf4qCLIu0mtIDyC5ddG2JcgOlt9 1MBw1ebnzlXMYw4XMAGLeSok4rrZU6baA36eiazEQdG7H66TyOk/y0w7JiZo
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/kiTiql-XEEwknoHNpSR7gTf6wLY>
Subject: Re: [netmod] New Version Notification for draft-kwatsen-netmod-artwork-folding-07.txt
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2018 10:01:40 -0000

Yeah :-Z

So my inclination is to say "tabs in artwork are evil" and move on.
Some folk like to use them when constructing text, but my suggestion is that they convert to spaces/LF before posting drafts.

If anyone wants to write another document tabs in json then, erm, knock yourselves out. But I would prefer to just exclude them from folding at this time.

Cheers,
Adrian

> -----Original Message-----
> From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of tom petch
> Sent: 18 September 2018 10:54
> To: Carsten Bormann; Robert Wilton
> Cc: netmod@ietf.org
> Subject: Re: [netmod] New Version Notification for draft-kwatsen-netmod-
> artwork-folding-07.txt
> 
> ----- Original Message -----
> From: "Carsten Bormann" <cabo@tzi.org>
> Sent: Friday, September 14, 2018 12:14 PM
> 
> > On Sep 14, 2018, at 13:05, Robert Wilton
> <rwilton=40cisco.com@dmarc.ietf.org> wrote:
> > >
> > > If all input files that we might ever want to fold and include in an
> RFC are guaranteed to never contain tabs then I agree with the position
> that they can just be rejected.
> >
> > Yep.
> >
> > > But if there is some future file format that we want to fold that
> might contain tabs, then I wonder whether it would not be more robust to
> look at whether they could be handled in some way.
> >
> > VT characters (colloquially tabs) should not be significant in any
> file format designed in the last couple of decades (i.e., they should be
> replaceable by spaces).  If they (or any other characters not
> representable in RFCs) are, or preserving byte wise identity is
> important, follow the lead of RFC 6716 and base64-encode.
> 
> This confuses me.  This I-D references RFC7991 which clearly defines tab
> as  9, which RFC20 labels H(orizontal) T(ab).  V(ertical) T(ab) is 11.
> 
> I would not expect VT to appear in any recent document but when it does,
> then replacing it by spaces would be wrong, IMHO.  HT I do see, far too
> much of, because there is no metadata saying what the Horizontal Tab
> settings should be and while a  value of five is common, there are RFC
> where replacing tab characters with five spaces yields rubbish.
> 
> Tom Petch
> 
> 
> 
> 
> 
> 
> >
> > Grüße, Carsten
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod