Re: [netmod] Alexey Melnikov's Discuss on draft-ietf-netmod-artwork-folding-08: (with DISCUSS)

Kent Watsen <kent+ietf@watsen.net> Thu, 29 August 2019 13:39 UTC

Return-Path: <0100016cdd99dcf3-5dcc1baf-bbcb-46ab-aa22-e2818c28dddc-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 CE67B120123; Thu, 29 Aug 2019 06:39:08 -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 evA_lFv8h412; Thu, 29 Aug 2019 06:39:06 -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 91D4912081C; Thu, 29 Aug 2019 06:39:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1567085944; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=8g2T+DrGANWeQCiPXPCV0BpM1yFZHy2pKpISxAIF9Os=; b=Zj045w5I+wuzcY7m0sjOG5d4JphpT5CoxYFRDwL1fy/Z2UskYmYf9pwdIxsM85Jg 6RG8NBMHS2P0J2XViCzH6u/8yEvporwpaLnYsGbiqLd0gD/R0I1iQYppk8b6H5UYWJ6 c6HlhnelXJgZFZl5aYPr/OepGQY9PqyOzASrMmok=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016cdd99dcf3-5dcc1baf-bbcb-46ab-aa22-e2818c28dddc-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AC973797-E66B-4429-A8A8-7490ACC92D79"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 29 Aug 2019 13:39:04 +0000
In-Reply-To: <CALaySJJRm0BHrRBaaUB+cmMa2uhtzLvN_AinRHSw0Co6TVWPDQ@mail.gmail.com>
Cc: Alexey Melnikov <aamelnikov@fastmail.fm>, "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, draft-ietf-netmod-artwork-folding@ietf.org, The IESG <iesg@ietf.org>, Lou Berger <lberger@labn.net>
To: Barry Leiba <barryleiba@computer.org>
References: <156701823840.1110.12340821702774896307.idtracker@ietfa.amsl.com> <0100016cda414a2b-9c5e2b3c-96c0-4a7e-99d0-54f227d5155c-000000@email.amazonses.com> <3A93201E-9027-4415-80B5-4DEF49190D10@fastmail.fm> <CALaySJJRm0BHrRBaaUB+cmMa2uhtzLvN_AinRHSw0Co6TVWPDQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.08.29-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/vrsSf3gcuXQpnWDgkSZEKeaVmfM>
Subject: Re: [netmod] Alexey Melnikov's Discuss on draft-ietf-netmod-artwork-folding-08: (with DISCUSS)
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: Thu, 29 Aug 2019 13:39:20 -0000

Correct and, to be even more clear, the location where the fold occurred was between the '\' and '\n' in the original input, thus producing the sequence: '\' + '\' + '\n' + '\n', where the first and last characters are from the input and the inner-two characters were introduced by the folding process.

Alexey, does this explanation clear your DISCUSS?

Kent // co-author




> On Aug 29, 2019, at 9:31 AM, Barry Leiba <barryleiba@computer.org> wrote:
> 
> The example is set up so that the source is in 9.4, 9.4.1 is the
> result of "\ folding" of 9.4, and 9.4.2 is the result of "\\ folding"
> of 9.4.
> 
> So the original source (in 9.4) was "This line ends with a backslash \".
> The result of "\ folding" gives "This line ends with a backslash \\",
> because the backslash had to be escaped.
> 
> Barry
> 
> On Thu, Aug 29, 2019 at 4:55 AM Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
>> 
>> Hi Kent,
>> 
>> On 28 Aug 2019, at 23:03, Kent Watsen <kent+ietf@watsen.net> wrote:
>> 
>> Hi Alexey,
>> 
>> Response at bottom.
>> 
>> Kent
>> 
>> 
>> On Aug 28, 2019, at 2:50 PM, Alexey Melnikov via Datatracker <noreply@ietf.org> wrote:
>> 
>> Alexey Melnikov has entered the following ballot position for
>> draft-ietf-netmod-artwork-folding-08: Discuss
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-netmod-artwork-folding/
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>> 
>> Thank you for your document.
>> 
>> It might be just me, but I think your examples in 9.4.1 with trailing \ don’t
>> seem to match the folding algorithm in section 7, as it doesn’t describe
>> special handling of trailing \.
>> 
>> 
>> Can you be more specific regarding what it is you think doesn't match?   Step (2) says, at the location where the fold is to occur, insert '\' followed by '\n'.  That appears to be what is shown in 9.4.1, yes?
>> 
>> 
>> In the HTML version (in datatracker) I am seeing:
>> 
>> “This line ends with a backslash \\”
>> 
>> followed by an empty line. So I see 2 trailing \ followed by end of line, instead of \, end of line, and then \.
>> 
>> 
>> FWIW, the text in Section 9.4.1 (as with all the examples in the draft) was dynamically-generated (at draft build time) by feeding the text in Section 9.4 into the script in the Appendix A.
>> 
>> Kent  // co-author
>> 
>>