Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft

Adam Roach <adam@nostrum.com> Wed, 06 November 2019 02:33 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19ECE12002E for <tools-discuss@ietfa.amsl.com>; Tue, 5 Nov 2019 18:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.28
X-Spam-Level:
X-Spam-Status: No, score=-1.28 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.399, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=no 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 d5T3wXj34Xp9 for <tools-discuss@ietfa.amsl.com>; Tue, 5 Nov 2019 18:33:24 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4D0A12003E for <tools-discuss@ietf.org>; Tue, 5 Nov 2019 18:33:21 -0800 (PST)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id xA62XJPh067560 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 5 Nov 2019 20:33:20 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1573007601; bh=UmXvSB55slZJIVEhNX+kaRl0tgfL5qz+c+fS50XlPbs=; h=Subject:To:References:From:Date:In-Reply-To; b=dOWjxKmpI83cMYqqw/6FgauPhkTkxDvusiDg2gUUiozgix1tS6poBpWfCiOvWtfAK aseJSlb68NpJX1HCQfMy509SJHkJThj/pFmJUGDDdOG1waT6PogSyZSWPZa5nuQSf8 56rdbjLqvM1QAA978HgBqAthBrUfCZUcVWyVWMqw=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Tom Pusateri <pusateri=40bangj.com@dmarc.ietf.org>, tools-discuss <tools-discuss@ietf.org>
References: <157288484424.16663.3995065379449438987.idtracker@ietfa.amsl.com> <E2A5257F-8926-4570-81E1-288DDDC6DA34@bangj.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <eca7be6d-dabe-21b1-725f-36c897940382@nostrum.com>
Date: Tue, 5 Nov 2019 20:33:13 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <E2A5257F-8926-4570-81E1-288DDDC6DA34@bangj.com>
Content-Type: multipart/alternative; boundary="------------F31D3C60CA804A51AB2855FD"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/Eqyfnkf7K2e1JirszHsartqyexY>
Subject: Re: [Tools-discuss] UTF-8 box characters with wavy lines in XML2RFC v3 draft
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Nov 2019 02:33:26 -0000

While v3 allows Unicode characters, it's not a free-for-all 
anything-goes permission. RFC 7997 outlines the nine very narrowly 
scoped ways that Unicode can be used in v3 documents. I can't find one 
that covers the use in your draft. Which one do you think applies?

/a

On 11/5/19 7:21 PM, Tom Pusateri wrote:
> Hi,
> As a follow up to DKG’s comments about v3 submissions and UTF-8 box 
> characters, we recently submitted this draft.
>
> We did get the new v3 HTML version referenced in the document 
> datatracker if you click the “status” link below, you will see the 
> first HTML link is the new version.
> We also got the old HTML version using the htmlized link in the 
> document datatracker. This seems unnecessary to me.
>
> But below, you see two htmlized links in the outgoing email and 
> neither of these refer to the new v3 HTML version.
>
> I would like to see both of these links removed and replaced with a 
> link to the v3 HTML version in the announcement email.
>
> Also, note how the box characters in the v3 HTML version end up are 
> unaligned? There is probably something going wrong here in the CSS or 
> maybe our source but I’m not sure what. Maybe we’re not using the 
> correct vertical bar? Any help on that would be appreciated so we 
> don’t get wavy lines.
>
> Thanks,
> Tom
>
>> Begin forwarded message:
>>
>> *From: *internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>> *Subject: **New Version Notification for 
>> draft-pusateri-dnsop-update-timeout-04.txt*
>> *Date: *November 4, 2019 at 11:27:24 AM EST
>> *To: *"Tim Wattenberg" <mail@timwattenberg.de 
>> <mailto:mail@timwattenberg.de>>, "Tom Pusateri" <pusateri@bangj.com 
>> <mailto:pusateri@bangj.com>>
>>
>>
>> A new version of I-D, draft-pusateri-dnsop-update-timeout-04.txt
>> has been successfully submitted by Tim Wattenberg and posted to the
>> IETF repository.
>>
>> Name:draft-pusateri-dnsop-update-timeout
>> Revision:04
>> Title:DNS TIMEOUT Resource Record
>> Document date:2019-11-04
>> Group:Individual Submission
>> Pages:17
>> URL: 
>> https://www.ietf.org/internet-drafts/draft-pusateri-dnsop-update-timeout-04.txt
>> Status: 
>> https://datatracker.ietf.org/doc/draft-pusateri-dnsop-update-timeout/
>> Htmlized: 
>> https://tools.ietf.org/html/draft-pusateri-dnsop-update-timeout-04
>> Htmlized: 
>> https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout
>> Diff: 
>> https://www.ietf.org/rfcdiff?url2=draft-pusateri-dnsop-update-timeout-04
>>
>> Abstract:
>>   This specification defines a new DNS TIMEOUT resource record (RR)
>>   that associates a lifetime with one or more zone resource records.
>>   It is intended to be used to transfer resource record lifetime state
>>   between a zone's primary and secondary servers and to store lifetime
>>   state during server software restarts.
>>
>>
>>
>>
>> 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 
>> <http://tools.ietf.org>;.
>>
>> The IETF Secretariat
>>
>
>
> ___________________________________________________________
> Tools-discuss mailing list
> Tools-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-discuss
>
> Please report datatracker.ietf.org and mailarchive.ietf.org
> bugs at http://tools.ietf.org/tools/ietfdb
> or send email to datatracker-project@ietf.org
>
> Please report tools.ietf.org bugs at
> http://tools.ietf.org/tools/issues
> or send email to webmaster@tools.ietf.org