Return-Path: 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 425361206E1 for ; Mon, 17 Jun 2019 13:53:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham 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 bPTNJ57hcDEL for ; Mon, 17 Jun 2019 13:53:48 -0700 (PDT) Received: from mta8.iomartmail.com (mta8.iomartmail.com [62.128.193.158]) (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 32C751206DF for ; Mon, 17 Jun 2019 13:53:36 -0700 (PDT) Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta8.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5HKrYmM031757; Mon, 17 Jun 2019 21:53:34 +0100 Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 701772203B; Mon, 17 Jun 2019 21:53:34 +0100 (BST) Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs1.iomartmail.com (Postfix) with ESMTPS id 5AAE62203A; Mon, 17 Jun 2019 21:53:34 +0100 (BST) Received: from LAPTOPK7AS653V (25.129.51.84.dyn.plus.net [84.51.129.25] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5HKrWfO030355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 17 Jun 2019 21:53:33 +0100 Reply-To: From: "Adrian Farrel" To: "'Kent Watsen'" Cc: References: <155922665888.22158.34610875303939053@ietfa.amsl.com> <0100016b0930277d-e4cf4cc9-3be1-45c7-9ca1-505ccc8e59ea-000000@email.amazonses.com> <0100016b6685036e-0f341024-b692-42d1-aa0a-9d55cccc5402-000000@email.amazonses.com> <01f401d52538$ccb4e0a0$661ea1e0$@olddog.co.uk> <0100016b66c9568a-74256db2-9b9d-45da-99a9-ff4116293e2c-000000@email.amazonses.com> In-Reply-To: <0100016b66c9568a-74256db2-9b9d-45da-99a9-ff4116293e2c-000000@email.amazonses.com> Date: Mon, 17 Jun 2019 21:53:31 +0100 Organization: Old Dog Consulting Message-ID: <021101d5254e$b9802ec0$2c808c40$@olddog.co.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0212_01D52557.1B461D60" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQGfH+XDlDQC4lKNSSHBhCWukwulEwG0BD6bArRKtTgBRHTfeAIBEd5Hps7tPGA= Content-Language: en-gb X-Originating-IP: 84.51.129.25 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-24686.001 X-TM-AS-Result: No--19.299-10.0-31-10 X-imss-scan-details: No--19.299-10.0-31-10 X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24686.001 X-TMASE-Result: 10--19.299500-10.000000 X-TMASE-MatchedRID: Z/tjqhsgM6c7iuZ/mdYYtvPom+PRQD1/eVfJkJu97fTN25nZ2p7B7S4k rlw9EMr90WPjwvBymOUUmR8f4HPVzuv6L5uWBkxpJ2ZQ5u87lZl5bBiV7e/VjAKL4BUqBzvS3Is W8GtAmI9jBcCC3w+2IFqgyyHRhMBSAveunI5PTNi6Gxh0eXo7axGAou/AcMSIqsyhMt9RsWK4f9 3mHW3ZqqiySyvhc1tSutvHF25zoU8uAm3+nk3vKU9CJC/MWIZ4rZLAiMblSRGcoIHjPJYxCO//p rISz9EWCQK8suTMyGuYvybQm0otU2thGdTfum7agOlK2zN496mQgO5cTqSFVhsguN4Prv59BLvB 7dV9JZDpFBczyHpQrnCO70QAsBdCfglgnB0nDhORoQLwUmtov51ddxkSC3k368qNWtTEEnI+Jck 2RObbKmwxXIAB2+stTauf2PrRb1sHgh3sKJBzPyBwR3y4lKPEmwOHFxYq8mcweRiYo8gedbf6+/ 4c5hJ6GIOWW3Xs9vS9NsL2xEmLy0Yj0zDHPzJpu6qThyrnanPrmZEozMcOf0crGCwEg/izM65OD 4mt/+f/o+5l9ZSgvjKVTrGMDe/Db4EbH+L/ZAhsnR1RUJec9DCWp18HPoW89zhdFI0Bq7phX1Xn 5qIIOdwkpT7HHqpeTvKpZzlxUs/PFq5A6gp9a6ANamSpMq+hQbNTsIpfWx3p/p6JwbnRc9UNXIp K0p5G9ran5gMy09QHK0IhbYfex1TwUMN+zeHgzVgwP7ZMYf8+Zexv5dHAKi6lHYgBZ/STWkFwmQ DHvRoeWdHNBdxmTYicBKfMHlV8mHAp2UJ8+TxHQgtCTJ1arKPFjJEFr+ol6AvlZUR4Tsiypq0eC 3FVtj/cZn50ezHqi2QFaYS1v22rEHfaj14ZyavKuh6OVsUdZtW2q62OVqEqt8GbQcj8Kfx0xqK8 kWDTI9z8VwbJxkE= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 Archived-At: Subject: Re: [netmod] I-D Action: draft-ietf-netmod-artwork-folding-03.txt X-BeenThere: netmod@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: NETMOD WG list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2019 20:53:52 -0000 This is a multipart message in MIME format. ------=_NextPart_000_0212_01D52557.1B461D60 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable OK, we=E2=80=99re agreed on what we want to achieve, just not on the = wording to describe it =F0=9F=98=8A =20 How about=E2=80=A6 =20 1. Determine where the fold will occur. This location MUST be before or at the desired maximum column, and MUST NOT be chosen such that the character immediately after the fold is a space (' ') character. If no such location can be found, then exit (this text content cannot be folded) =20 Best, Adrian =20 From: Kent Watsen =20 Sent: 17 June 2019 19:53 To: Adrian Farrel Cc: netmod@ietf.org Subject: Re: [netmod] I-D Action: = draft-ietf-netmod-artwork-folding-03.txt =20 Hi Adrian, =20 Text suggestions welcomed. =20 =20 What needs to be expressed is that a space character cannot occupy the = column where the end-of-line '\' is to placed, as doing so would push = that space character to the beginning of the next line, which the = unfolding logic would subsequently delete, thinking that it was part of = a user-placed "indent". Makes sense? =20 Kent =20 On Jun 17, 2019, at 2:16 PM, Adrian Farrel > wrote: =20 Kent,=20 Thanks for the work. =20 I had a clear understanding of what =E2=80=9Cprecede a space=E2=80=9D = means. I struggle to understand what =E2=80=9Con top of=E2=80=9D means in a = stream of characters. I wondered whether you were referring to vertical = placement on the page (the text is talking about columns), but that = seems crazy! Do you mean that the fold must not be occupied by a space character? I think the question is whether it is easier to describe a fold = happening between characters or at a character slot. The original text used the =E2=80=9Cbetween characters=E2=80=9D = approach. If you prefer to say you fold at a column, that=E2=80=99s = fine, but probably =E2=80=9Con top of=E2=80=9D isn=E2=80=99t as clear as = =E2=80=9Cthe column at which we fold must not contain a space=E2=80=9D. =20 Best, Adrian =20 =20 From: netmod > = On Behalf Of Kent Watsen Sent: 17 June 2019 18:39 To: netmod@ietf.org =20 Subject: Re: [netmod] I-D Action: = draft-ietf-netmod-artwork-folding-03.txt =20 =20 I just posted an Editorial update that only touches the non-normative = script to add a -q (quiet) flag. Here's the diff: = = https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-artwork-folding-0= 4.txt. =20 Separately, it's been more than two weeks since the below message. = There has been no comments on #2 below, and so the chairs can more = forward with the publishing request now? =20 Kent // author (recused chair) =20 =20 On May 30, 2019, at 10:41 AM, Kent Watsen < = kent@watsen.net> wrote: =20 =20 This update reflects the changes discussed during the Last Call plus the = following additional changes: =20 1) s/see if any/ensure at least one/ (EDITORIAL: sounded too casual = before) 2) s/MUST NOT precede a space (' ') character/MUST NOT be on top of a = space (' ') character/ (TECHNICAL: see below) 3) wrapped the script with and (EDITORIAL, = per idnits) =20 Regarding #2, this change was made after I examined the algorithm more = carefully. It would be good for others to confirm this rather critical = change. =20 Thanks, Kent // contributor =20 =20 On May 30, 2019, at 10:30 AM, = internet-drafts@ietf.org wrote: =20 A New Internet-Draft is available from the on-line Internet-Drafts = directories. This draft is a work item of the Network Modeling WG of the IETF. Title : Handling Long Lines in Inclusions in = Internet-Drafts and RFCs Authors : Kent Watsen Adrian Farrel Qin Wu Filename : draft-ietf-netmod-artwork-folding-03.txt Pages : 25 Date : 2019-05-30 Abstract: This document defines two strategies for handling long lines in width-bounded text content. One strategy is based on the historic use of a single backslash ('\') character to indicate where line- folding has occurred, with the continuation occurring with the first non-space (' ') character on the next line. The second strategy extends the first strategy by adding a second backslash character to identify where the continuation begins and thereby able to handle cases not supported by the first strategy. Both strategies use a self-describing header enabling automated reconstitution of the original content. The IETF datatracker status page for this draft is: = https://datatracker.ietf.org/doc/draft-ietf-netmod-artwork-folding/ There are also htmlized versions available at: = https://tools.ietf.org/html/draft-ietf-netmod-artwork-folding-03 = = https://datatracker.ietf.org/doc/html/draft-ietf-netmod-artwork-folding-0= 3 A diff from the previous version is available at: = = https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netmod-artwork-folding-03 Please note that it may take a couple of minutes from the time of = submission until the htmlized version and diff are available at tools.ietf.org = . Internet-Drafts are also available by anonymous FTP at: = ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ netmod mailing list netmod@ietf.org = https://www.ietf.org/mailman/listinfo/netmod =20 _______________________________________________ netmod mailing list netmod@ietf.org = https://www.ietf.org/mailman/listinfo/netmod =20 ------=_NextPart_000_0212_01D52557.1B461D60 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

OK, we=E2=80=99re agreed on what we = want to achieve, just not on the wording to describe it 😊

 

How = about=E2=80=A6

 

=C2=A0=C2=A0 1.=C2=A0 Determine = where the fold will occur.=C2=A0 This location MUST = be

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= before or at the desired maximum column, and MUST NOT be = chosen

=C2=A0=C2=A0=C2=A0 = =C2=A0=C2=A0=C2=A0such that the character immediately after the fold is = a space

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= (' ') character.=C2=A0 If no such location can be found, then = exit

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= (this text content cannot be folded)

 

Best,

Adrian

 

From: Kent Watsen = <kent+ietf@watsen.net>
Sent: 17 June 2019 = 19:53
To: Adrian Farrel = <adrian@olddog.co.uk>
Cc: = netmod@ietf.org
Subject: Re: [netmod] I-D Action: = draft-ietf-netmod-artwork-folding-03.txt

 

Hi = Adrian,

 

Text suggestions welcomed. =   

 

What needs to be expressed is that a space character = cannot occupy the column where the end-of-line '\' is to placed, as = doing so would push that space character to the beginning of the next = line, which the unfolding logic would subsequently delete, thinking that = it was part of a user-placed "indent".  Makes = sense?

 

Kent

 



On Jun 17, 2019, at 2:16 PM, Adrian Farrel <adrian@olddog.co.uk> = wrote:

 

Kent, 

Thanks for the work.

 

I = had a clear understanding of what =E2=80=9Cprecede a space=E2=80=9D = means.

I struggle to = understand what =E2=80=9Con top of=E2=80=9D means in a stream of = characters. I wondered whether you were referring to vertical placement = on the page (the text is talking about columns), but that seems = crazy!

Do you mean that = the fold must not be occupied by a space = character?

I think the = question is whether it is easier to describe a fold happening between = characters or at a character slot.

The original text used the =E2=80=9Cbetween = characters=E2=80=9D approach. If you prefer to say you fold at a column, = that=E2=80=99s fine, but probably =E2=80=9Con top of=E2=80=9D = isn=E2=80=99t as clear as =E2=80=9Cthe column at which we fold must not = contain a space=E2=80=9D.

 

Best,

Adrian

 

 

From: netmod <netmod-bounces@ietf.org> On Behalf Of Kent = Watsen
Sent: 17 June 2019 = 18:39
To: netmod@ietf.org
Subject: Re: [netmod] I-D Action: = draft-ietf-netmod-artwork-folding-03.txt

 

 

I just posted an Editorial update that only touches = the non-normative script to add a -q (quiet) flag.  Here's the = diff: https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-n= etmod-artwork-folding-04.txt.

<= div>

 

Separately, it's been more than two weeks since the = below message.   There has been no comments on #2 below, and so the = chairs can more forward with the publishing request = now?

 

Kent // author (recused = chair)

 

 




On May 30, 2019, at 10:41 AM, Kent Watsen <kent@watsen.net> = wrote:

 

 

This update reflects the changes discussed during the = Last Call plus the following additional = changes:

 

  1) s/see if any/ensure at least one/ =  (EDITORIAL: sounded too casual = before)

  = 2) s/MUST NOT precede a space (' ') character/MUST = NOT be on top of a space (' ') character/  (TECHNICAL: = see below)

  3) wrapped the script with <CODE BEGINS> = and <CODE ENDS> (EDITORIAL, per = idnits)

 

Regarding #2, this change was made after I examined = the algorithm more carefully.  It would be good for others to = confirm this rather critical = change.

 

Thanks,

Kent // = contributor

 

 




On May 30, 2019, at 10:30 AM, internet-drafts@ietf.org wrote:

 


A New Internet-Draft is available from the on-line = Internet-Drafts directories.
This draft is a work item of the Network = Modeling WG of the = IETF.

       Title =           : Handling = Long Lines in Inclusions in Internet-Drafts and = RFCs
       Authors =         : Kent = Watsen
          &nb= sp;           &nbs= p;  Adrian = Farrel
          &nb= sp;           &nbs= p;  Qin Wu
   Filename =        : = draft-ietf-netmod-artwork-folding-03.txt
       Pages =           : = 25
       Date =            : = 2019-05-30

Abstract:
  This document defines two = strategies for handling long lines in
  width-bounded text = content.  One strategy is based on the historic
  use = of a single backslash ('\') character to indicate where = line-
  folding has occurred, with the continuation = occurring with the first
  non-space (' ') character on the = next line.  The second strategy
  extends the first = strategy by adding a second backslash character = to
  identify where the continuation begins and thereby = able to handle
  cases not supported by the first strategy. =  Both strategies use a
  self-describing header = enabling automated reconstitution of the
  original = content.


The IETF datatracker status page for this draft = is:
https://datatracker.ietf.org/doc/draft-ietf-netmod= -artwork-folding/

There are also htmlized versions = available at:
https://tools.ietf.org/html/draft-ietf-netmod-artw= ork-folding-03
https://datatracker.ietf.org/doc/html/draft-ietf-n= etmod-artwork-folding-03

A diff from the previous = version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-net= mod-artwork-folding-03


Please note that it may = take a couple of minutes from the time of submission
until the = htmlized version and diff are available at tools.ietf.org.

Internet-Drafts= are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
=
_______________________________________________
netmod mailing = list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

 

_______________________________________________
netm= od mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

 

------=_NextPart_000_0212_01D52557.1B461D60--