Re: [Tools-discuss] Tool request: datatracker link(s) to RFC-extracted YANG module(s)

worley@ariadne.com (Dale R. Worley) Fri, 10 March 2017 21:58 UTC

Return-Path: <worley@alum.mit.edu>
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 475911294F4 for <tools-discuss@ietfa.amsl.com>; Fri, 10 Mar 2017 13:58:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 21YsJqRS3bm4 for <tools-discuss@ietfa.amsl.com>; Fri, 10 Mar 2017 13:58:25 -0800 (PST)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 316A8129452 for <tools-discuss@ietf.org>; Fri, 10 Mar 2017 13:58:25 -0800 (PST)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-11v.sys.comcast.net with SMTP id mSXncuZ0pEyOCmSYKcECJ8; Fri, 10 Mar 2017 21:58:24 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-08v.sys.comcast.net with SMTP id mSYJcNph24ebhmSYJcEFzc; Fri, 10 Mar 2017 21:58:24 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v2ALwMcg024035; Fri, 10 Mar 2017 16:58:22 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v2ALwMQB024032; Fri, 10 Mar 2017 16:58:22 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Benoit Claise <bclaise@cisco.com>
In-Reply-To: <9b8a826f-9e15-727b-efd9-cc609085222e@cisco.com> (bclaise@cisco.com)
Sender: worley@ariadne.com
Date: Fri, 10 Mar 2017 16:58:22 -0500
Message-ID: <87poho6bgh.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfIoJqpB9e3pJw8WXdCAGEuqa55pEPHrKnpkaf3DyhTb8Mt9wmLZfky1fQqJ1aDevmKZdgS2q7UrNYVhf6zf74BiJuwQTBsu967x54Sppcie2go4UBzME sdwBUkhCt9K7Q6Hpqf9aqzHbTZJggeKokxpnqg8KkzEpVFl+VP/cfiaUykzRPYE9LMzTjFWYajs1WmAeG+u2IL7lcYJCJh8toJk=
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/ScU0z9SIOmqGNpeWIzS6pYDz3aY>
Cc: iesg@ietf.org, tools-discuss@ietf.org
Subject: Re: [Tools-discuss] Tool request: datatracker link(s) to RFC-extracted YANG module(s)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 10 Mar 2017 21:58:26 -0000

Benoit Claise <bclaise@cisco.com> writes:
> If you are familiar with github, all YANG modules are at 
> https://github.com/YangModels/yang/tree/master/standard/ietf/RFC
>      See the latest pull request so that it's up to date: 
> https://github.com/YangModels/yang/pull/121
>
> In the end, we should observe that a YANG module (or a MIB module, or 
> code ...) embedded in a RFC is not easily accessible to the wider audience.
> Sure there is CODE BEGINS/CODE ENDS as delimiters. Even those is a pain: 
> I spent one hour this morning sending email to authors, explaining how 
> to use them correctly.

Perhaps better would be an IANA registry mapping

    RFC-number
    module-name
    module-description
    pointer-to-clean-copy

each RFC could mention it in "IANA Considerations", and if the clean
copies have to be moved, the registry could be bulk-updated by AD
request or something simple.

Dale