IETF Logo Mail Archive

Re: [netmod] WG Last Call: draft-ietf-netmod-artwork-folding-02

Kent Watsen <kent@watsen.net> Tue, 28 May 2019 19:20 UTC

Return-Path: <0100016affe2af95-70f3b07d-93c4-4ee8-a72d-664900a10959-000000@amazonses.watsen.net>
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 85E881200BA; Tue, 28 May 2019 12:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.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 8xbNbZrSaPpp; Tue, 28 May 2019 12:20:09 -0700 (PDT)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7429120047; Tue, 28 May 2019 12:20:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1559071207; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=NxKRSf67j/LYBnREP6maOT6634yp2TAip4OM1q3iA9s=; b=jAIPwUJDw3JIBGXp4mMkGD9SZQ+mGOhOff/vW1pScRKCeLQ0Zati4UgcNycagwZT XMyAlBcJqgYEO5i6a+/B8lfJ+rYGhoHR22w4E5KQ3vo/KIutF1E/SYuYShgZxM3rVG5 IthrbNJBo6iPSMzr+IIE69YQPOY+uRtmCTUdmGNg=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016affe2af95-70f3b07d-93c4-4ee8-a72d-664900a10959-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_156816C9-C46F-40B1-B59C-AF4332598476"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 28 May 2019 19:20:07 +0000
In-Reply-To: <BYAPR11MB263188D9E6EAD9B54D915409B51E0@BYAPR11MB2631.namprd11.prod.outlook.com>
Cc: "netmod@ietf.org" <netmod@ietf.org>, "draft-ietf-netmod-artwork-folding@ietf.org" <draft-ietf-netmod-artwork-folding@ietf.org>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
References: <e6fc4541-891a-60cb-e956-86f238d09f14@labn.net> <BYAPR11MB263112EA231A41491AC4DF89B51E0@BYAPR11MB2631.namprd11.prod.outlook.com> <0100016aff1640f0-a301a70e-ecae-4754-84d1-12170d5b73fd-000000@email.amazonses.com> <BYAPR11MB263191E71A0E09CE1667AB45B51E0@BYAPR11MB2631.namprd11.prod.outlook.com> <0100016aff5c1a19-32fa804b-b9d4-4411-a350-0a5571256e10-000000@email.amazonses.com> <BYAPR11MB263188D9E6EAD9B54D915409B51E0@BYAPR11MB2631.namprd11.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.05.28-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/TAfmwTkDIgCQAEa3nJ0oDkP5qPs>
Subject: Re: [netmod] WG Last Call: draft-ietf-netmod-artwork-folding-02
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, 28 May 2019 19:20:10 -0000


> [RW] 
> Perhaps, less is more, e.g., 
>  
> “One strategy is based on the historical use of a single backslash ('\') character to indicate where line-folding has occurred.”?

Replaced.



> [RW]
> So, for example considering the current text, if it was a JSON input file, it would be more appropriate to change the indentation level to 2 spaces rather than 4 spaces to ensure that there are not unnecessary line wraps?  In theory, the only place in a JSON file that we would expect there to be a line breaks would be within a string because that is the only case that can’t be handled within JSON itself.
>  
> Is this your intended meaning?

Certainly one example, yes.



Kent // author

v2.23.0 | Report a Bug | By Email