[netmod] Comments on draft-lhotka-netmod-yang-markup-00

Robert Wilton <rwilton@cisco.com> Fri, 17 March 2017 12:30 UTC

Return-Path: <rwilton@cisco.com>
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 CB05E129329 for <netmod@ietfa.amsl.com>; Fri, 17 Mar 2017 05:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 0WLnI5d5eocm for <netmod@ietfa.amsl.com>; Fri, 17 Mar 2017 05:30:07 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C192127735 for <netmod@ietf.org>; Fri, 17 Mar 2017 05:30:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1662; q=dns/txt; s=iport; t=1489753807; x=1490963407; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=31ME5KdOPZaJeWrs40eJStRYiDzPtDLYEIKLVa6wE+o=; b=gXnWkXGBCezzuUXmtNfmO0rgX6JclhEvrdEAaVJZSttj/+uFWqUIPDL9 lpDG8bJUTe955i7EgX9g78XQYyBfv6CjUW/zkTgxWj2y2OZ+lEN1lCqy2 SrA3iXYdACkEkuNGsnQanYnXiH5MQXwLsfmUhnQlhLNSQ56t2kIbNZyHx Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DSBwD91ctY/xbLJq1dGwEBAQMBAQEJAQEBgyeBNYRCiwKQRpdviWUVAQIBAQEBAQEBayiFPxV2AiYCXwEMCAEBiXyxd4ImilMBAQEBBgIBJYELhUOCBQiEHoYegl8FnEmBU5BvgXuIWyOGMotCiBE1IoEEIxYIFxWFJYFzQIoMAQEB
X-IronPort-AV: E=Sophos;i="5.36,176,1486425600"; d="scan'208";a="650495094"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Mar 2017 12:30:05 +0000
Received: from [10.63.23.115] (dhcp-ensft1-uk-vla370-10-63-23-115.cisco.com [10.63.23.115]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v2HCU5xL011394; Fri, 17 Mar 2017 12:30:05 GMT
To: "netmod@ietf.org" <netmod@ietf.org>, Ladislav Lhotka <lhotka@nic.cz>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <e17f7458-1192-b0d7-d72d-4f56e4b18386@cisco.com>
Date: Fri, 17 Mar 2017 12:30:04 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/_UhW0pG481itovuzPTHs-dAFV1M>
Subject: [netmod] Comments on draft-lhotka-netmod-yang-markup-00
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Mar 2017 12:30:09 -0000

Hi Lada,

I've had a quick scan of your YANG markup extension draft and I have a 
few comments:

Allowing description, and similar descriptive statements, to use 
something other than text seems like it could be useful in some cases.

I'm not sure that allowing the statements to use any text-like media 
type is a good idea, this could increase the burden on tool makers if 
each module author chooses their own preferred format.

Instead, I think that it might be better to restrict it to a very small 
set of media types, that could be extended in future.  I would think 
that initially just allowing plain text and one particular flavour of 
markdown would be a reasonable starting point.

I think that the only formats that should be allowed are those that are 
still readily readable as plain text, so that tools that don't want to 
parse the formatted text can still sensibly display the descriptive 
statements.  I.e. I don't think that it would be helpful to allow things 
like text/xml since it isn't easy to read.

Allowing this extension on particular descriptive statements may also be 
helpful.  It seems plausible that the vast majority of these statements 
in a module might just be written in plain text with just a few of them 
using more advanced formatting like markdown.

Finally, I have a concern that if more structured formatting in the 
comments is used then would that encourage model writers to produce more 
verbose comments, and if so that might possibly reduce the readability 
of the modules.  Although, I guess ultimately one has to trust the model 
writers to do the right thing.

Thanks,
Rob