Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-15.txt

Dave Crocker <dhc@dcrocker.net> Sun, 04 November 2018 14:17 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16BB512D4EC for <dnsop@ietfa.amsl.com>; Sun, 4 Nov 2018 06:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 v2u2lxa-bhXS for <dnsop@ietfa.amsl.com>; Sun, 4 Nov 2018 06:17:47 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 34008120072 for <dnsop@ietf.org>; Sun, 4 Nov 2018 06:17:47 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id wA4EIMkS006202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 4 Nov 2018 06:18:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1541341102; bh=2Ai4qcd4U+DBN3TGu63IbBAUXuJ/2GVx2+KkV0tyVM8=; h=Subject:To:References:Reply-To:From:Cc:Date:In-Reply-To:From; b=C+gfJOtU0TgOxogJJBnDQui65Z/G+fu3my6qeaw0ZR7t/mv0/pfAOPQmLq+yfTXS8 h21zFbriY4LxotCUXabzlV1PmaeteRs6JBj1lfvHEktHYTXucbtHrj2hdmtgApc7oV MuUlimprqKQsll2FEMUo2qTWbvO+rSCermCOuquE=
To: Warren Kumari <warren@kumari.net>
References: <154127656499.10164.10170177869879078794@ietfa.amsl.com> <CAHw9_iK8ZBvu=dox26RnHBW131T-frXBPpG6FuQ2u=_TN_rXsg@mail.gmail.com>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Cc: dnsop <dnsop@ietf.org>
Message-ID: <2979d2a4-11de-4aef-232b-41bf295e163f@dcrocker.net>
Date: Sun, 04 Nov 2018 06:17:39 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAHw9_iK8ZBvu=dox26RnHBW131T-frXBPpG6FuQ2u=_TN_rXsg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/93_rI3smb_XhWz-ic8H5eMQrpaU>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-15.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2018 14:17:49 -0000

On 11/3/2018 4:55 PM, Warren Kumari wrote:
> I'm also somewhat confused by the quoting in:
> "In the case of the "SRV" "RR" and "URI" "RR", distinguishing among 
> different types"  (and in "defining "RR"s that might" ) - I'm not sure 
> if it is intentional, but it doesn't align with much of the rest of the 
> formatting, and is (IMO) confusing around the first part.)

I used spanx too liberally, because it looked nice in the html version 
on my machine, and I didn't realize what it did for the text version. My 
use matched what I'm seeing in some bibxml entries, but you are right 
that it doesn't look right in some of the sequences here.

So I've removed most spanx occurrences in the source.


> Also nit (I think):
> Adam Roach, Petr &#352;pa&#269;ek, Ond&#345;ej Sury

This is a dilemma. The characters produce appropriate text in html, to 
show his actual name.  The xml2rfc text rendering engine produces this 
silliness and I'm inclined to class it as a bug in the engine.

If there is an established practice for working around that bug, to 
produce the proper characters in html and an 'acceptable' alternative in 
text, please let me know and I'll fix it.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net