Re: [netmod] Adam Roach's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)

Martin Bjorklund <mbj@tail-f.com> Thu, 08 March 2018 14:31 UTC

Return-Path: <mbj@tail-f.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 893EE126DFB; Thu, 8 Mar 2018 06:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 15OC4lXcWH1K; Thu, 8 Mar 2018 06:31:43 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 07E121241F8; Thu, 8 Mar 2018 06:31:43 -0800 (PST)
Received: from localhost (unknown [173.38.220.45]) by mail.tail-f.com (Postfix) with ESMTPSA id 6E2591AE048A; Thu, 8 Mar 2018 15:31:41 +0100 (CET)
Date: Thu, 08 Mar 2018 15:31:40 +0100 (CET)
Message-Id: <20180308.153140.634508796793182947.mbj@tail-f.com>
To: bclaise@cisco.com
Cc: adam@nostrum.com, iesg@ietf.org, netmod-chairs@ietf.org, netmod@ietf.org, sginoza@amsl.com, draft-ietf-netmod-rfc6087bis@ietf.org, michelle.cotton@iana.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <c6f95654-9665-0b1d-eac8-7a0e05201aef@cisco.com>
References: <6ac9d4d5-d725-ad5a-d275-888afbc827cc@cisco.com> <20180308141508.mgah4poryqqs5weu@elstar.local> <c6f95654-9665-0b1d-eac8-7a0e05201aef@cisco.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/YjLa8thUmZEeuP8nkT0hSXjCFqA>
Subject: Re: [netmod] Adam Roach's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)
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: Thu, 08 Mar 2018 14:31:45 -0000

Benoit Claise <bclaise@cisco.com>; wrote:
> On 3/8/2018 3:15 PM, Juergen Schoenwaelder wrote:
> > On Thu, Mar 08, 2018 at 02:21:01PM +0100, Benoit Claise wrote:
> >> I see two solutions from here.
> >> 1. we mention "pyang -f yang --yang-canonical --keep-comments FILE" in
> >> RFC6087bis, with a warning such as: "As the tool matures, a human
> >> might need
> >> to polish the results"
> >> 2. we don't mention "pyang -f yang --yang-canonical --keep-comments
> >> FILE" in
> >> RFC6087bis, but we ask the YANG doctors to run the tests.
> > I am not sure it is a good idea to hard code command line options of
> > specific tools in a BCP document. We should require that things are
> > consistently indented and stay away from the advice of the day how
> > to achieve that.
> RFC 6087 mentions "pyang --ietf"  and
> draft-ietf-netmod-yang-tree-diagrams mentions "pyang -f tree
> --tree-line-length 50"

Maybe we can say that "for example, a tool like pyang can be used ..."

> If not in RFC6087bis, where would we document this?
> As a rhetorical question: How many of the YANG doctors were aware of
> and are enforcing this command?
> 
> Background Info.
> Typical question I've been receiving lately (in this case from IANA):
> When requesting the final files from the RFC-Editor, the file they
> extracted using their tool and the yang modules appear to have a lot
> of blank space in them. Is this OK?

The extraction tools often produce additional blank lines b/c it is
tricky to know how many blank lines were in the original module when
all you have is the RFC in ascii.


/martin