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

Benoit Claise <> Wed, 07 March 2018 16:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3F4AD129C56; Wed, 7 Mar 2018 08:02:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 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, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 70qPjecdRIQX; Wed, 7 Mar 2018 08:02:45 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7A13A129C70; Wed, 7 Mar 2018 08:02:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=2585; q=dns/txt; s=iport; t=1520438565; x=1521648165; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=PqCQRwi+KVaTwZsdRKLP8NFEdPkAT/CqrH98aYTjQ6k=; b=aF/yDieWG5UVUbINHAGyEMOVHkbvAsq82agj2ZNWpq4q3xIE9VWGdNYk Siwhhtq6Zpx0sNgiUTCjHSWvKcTQWfep/TmEvy6n49upHdHQuSL++aeLQ LWPkVbmgQHllbB0uWZdudoMsz42UyenDoCprUAUSoEIlikMRPam/igevT 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B4AQDxC6Ba/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQ2cCiDVIsYjmKBPZQ0FIIBChgLhD5PAoMrNhYBAgEBAQEBAQJ?= =?us-ascii?q?rJ4UkAgQBASEVNgsQCw4MAiYCAicwBgEMBgIBAYUXEKhhgieEcoNyghwFgQ+EI?= =?us-ascii?q?oQFgWYpDIJ4gy4BAQECAYE6ARIBgyqCYgSGCIIbkkQJhlSGM4NxB4FnhDeCeIV?= =?us-ascii?q?kiX6BTIYNgS4kATFhWBEIMxoIGxU6gkOCY4FmPzcBiU6COgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.47,436,1515456000"; d="scan'208";a="2437972"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Mar 2018 16:02:42 +0000
Received: from [] ( []) by (8.14.5/8.14.5) with ESMTP id w27G2gxd017727; Wed, 7 Mar 2018 16:02:42 GMT
To: Alvaro Retana <>, The IESG <>
References: <>
From: Benoit Claise <>
Message-ID: <>
Date: Wed, 7 Mar 2018 17:02:42 +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: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <>
Subject: Re: [netmod] Alvaro Retana's No Objection on draft-ietf-netmod-rfc6087bis-18: (with COMMENT)
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 07 Mar 2018 16:02:48 -0000

Hi Alvaro,
> Alvaro Retana has entered the following ballot position for
> draft-ietf-netmod-rfc6087bis-18: No Objection
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> Please refer to
> for more information about IESG DISCUSS and COMMENT positions.
> The document, along with other ballot positions, can be found here:
> ----------------------------------------------------------------------
> ----------------------------------------------------------------------
> (1) This sentence in the Introduction caught my attention: "This document
> defines a set of usage guidelines for Standards Track documents containing
> models."    The Abstract extends to say that "Applicable portions
> may be used as a basis for reviews of other YANG data model documents."
> I don't remember a non-Standards Track document off the top of my head [*], but
> I'm sure the guidelines apply to any IETF document containing a module.  Is
> that true?
In my mind, yes. I don't see why we would make a distinction.
I believe the text should be improved.

As history, this sentence is a cut/paste from RFC6087.
> I see, for example, that in 4.1 (Module Naming Conventions) it is clear how
> modules published by the IETF should be named...and a note is included about
> what other SDOs might do.  Are there cases where the guidelines are only
> applicable to Standards Track documents, but would not apply to other IETF
> documents?
I don't think so.

Regards, B.
> This may be a nit, but I think it is good to close this door before the
> justification for non-compliance starts being the Status of a document.
> [*] I do remember the IESG talking about whether a document with a module for
> an Experimental protocol should be in the Standards Track or not.  IMHO, what
> matters is for the module to be used (i.e. correct, implementable, implemented,
> etc.) and not the status of the document it is in.
> (2) The second paragraph in 2.1. (Requirements Notation) is not needed: "RFC
> 2119 if it were describing best current practices."  This
> document is now a BCP.
> _______________________________________________
> netmod mailing list
> .