Re: [netmod] reference statement examples in draft-ietf-netmod-rfc6087bis-18

Benoit Claise <bclaise@cisco.com> Mon, 26 February 2018 20:44 UTC

Return-Path: <bclaise@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 B5D2512D864 for <netmod@ietfa.amsl.com>; Mon, 26 Feb 2018 12:44:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 dyxkub9rt5wm for <netmod@ietfa.amsl.com>; Mon, 26 Feb 2018 12:44:12 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60A33127601 for <netmod@ietf.org>; Mon, 26 Feb 2018 12:44:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=546; q=dns/txt; s=iport; t=1519677852; x=1520887452; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=F0rtjFiP2qpYIrjrC0ovxRaoyxdZpS3v5McnRXpd4c8=; b=hvuyORi3f1f4pFgQyHziOPHjIUiW7YEr7RSLCFDH90VUOHXchilFz3uG EcqSkt4dHdTZ2o6FdNJKcKDMnDoTcfQN5IMQKoUvZwYjVy84yVsaPfSnd cT2J9MZcAVogNPsh7U/QfL9Cq2icc8YtZE48EoftsRkULWcDP52VdkVLL I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByAQD0cJRa/xbLJq1eGQEBAQEBAQEBAQEBAQcBAQEBAYUlg3yLFo5agUiYGwqFMwKDHBUBAgEBAQEBAQJrKIUkBiMPAQVRCxoCJgICVxMIAQGFDKw5gieEdIN8ghQBAQEHAgElgQ+ICoIPgwSFbYJBgmUBBKFhCZQggXKJOYc1jlGHJIEvNCKBUTMaCBsVGYJlhFo/jQ0BAQE
X-IronPort-AV: E=Sophos;i="5.47,397,1515456000"; d="scan'208";a="2303700"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Feb 2018 20:44:10 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w1QKiAHK026932 for <netmod@ietf.org>; Mon, 26 Feb 2018 20:44:10 GMT
To: netmod@ietf.org
References: <20180223071204.wio22cwopgajy7hb@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <8fe72d11-c992-cf73-3fd0-72c86e718fe8@cisco.com>
Date: Mon, 26 Feb 2018 21:44:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <20180223071204.wio22cwopgajy7hb@elstar.local>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5p40_6BmCi7R06f7wwAbqziwgnQ>
Subject: Re: [netmod] reference statement examples in draft-ietf-netmod-rfc6087bis-18
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: Mon, 26 Feb 2018 20:44:13 -0000

Jürgen,

It makes sense.
This comment should be considered as an IETF LC comment.

Regards, B.
> Hi,
>
> I think it was common practice to write
>
>    reference "RFC 6991: Common YANG Data Types";
>
> instead of just
>
>    reference "RFC 6991";
>
> that is to include the RFC title (this can be especially useful with
> longer lists of references and less commonly known RFC numbers). It
> seems that draft-ietf-netmod-rfc6087bis-18 kind of suggests to only
> use the RFC number (section 3.2 and section 4.7).
>
> /js
>