Re: [netmod] upcoming adoptions

Robert Wilton <rwilton@cisco.com> Fri, 08 September 2017 12:19 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 92D7F132715; Fri, 8 Sep 2017 05:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 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, 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 UWIl0eVij_V2; Fri, 8 Sep 2017 05:19:08 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C07DE1321B6; Fri, 8 Sep 2017 05:19:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1283; q=dns/txt; s=iport; t=1504873148; x=1506082748; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=0/Gfsl+31mtdxYF1M3bnCgh5xa7oE7CPuRyHFprGg7Y=; b=HwwpLmjog5uVQjJTdgaWCqSpy9AS+ZQP2Jsffl1Gje8evjtvUyo8lzR+ 3QT/UtQZ4wu2ck2cR3broWdXlgyI9I/srnxNxvXxypvyGldfI027OyTxU 9I95T4DBHYsKZzAex3CCki7T7tBy4euZD7nLUHfurfjWd48PhbZ5/ovrv s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DmBAAmirJZ/xbLJq1cGgEBAQECAQEBAQgBAQEBhSyEHosVkHMrmDoKhT4ChE4UAQIBAQEBAQEBayiFGQEFIw8BBVELGAICJgICVwYBDAgBAYotq2eCJ4s5AQEBAQEBBAEBAQEBI4ENgh2DUIFjK4FwgQ2ICIJhBaB0lFGLVIcdjVeHVIE5NiGBDTIhCBwVSYccP4pUAQEB
X-IronPort-AV: E=Sophos;i="5.42,361,1500940800"; d="scan'208";a="655500580"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Sep 2017 12:19:03 +0000
Received: from [10.63.23.66] (dhcp-ensft1-uk-vla370-10-63-23-66.cisco.com [10.63.23.66]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v88CJ37F020266; Fri, 8 Sep 2017 12:19:03 GMT
To: Andy Bierman <andy@yumaworks.com>, Martin Bjorklund <mbj@tail-f.com>, NETCONF Working Group <netconf-chairs@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
References: <20170908105648.ur5ihv3gvypd7d7f@elstar.local>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <c5a6cbed-34d7-a49f-127c-82f0c20f0061@cisco.com>
Date: Fri, 08 Sep 2017 13:19:03 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <20170908105648.ur5ihv3gvypd7d7f@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/asbNMlktrpSnYwf7P1ZIBuiZvgE>
Subject: Re: [netmod] upcoming adoptions
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, 08 Sep 2017 12:19:09 -0000


On 08/09/2017 11:56, Juergen Schoenwaelder wrote:
> On Fri, Sep 08, 2017 at 11:17:10AM +0100, Robert Wilton wrote:
>>
>> On 07/09/2017 22:23, Juergen Schoenwaelder wrote:
>>> On Thu, Sep 07, 2017 at 10:51:54AM -0700, Andy Bierman wrote:
>>>> I suggested the naming guideline because the NMDA design team decided to
>>>> add semantics to certain naming patterns, so authors have to be warned.
>>>>
>>>> But this is a really bad idea (and slippery slope).
>>> I agree.
>> I think that there are really a few aspects to this:
>>
> [...]
>
> CLRs are always created with the best intention but then they become
> over time a problem. There is quite some experience with this.
In the same vane, I think that you could regard RFC 6087 and 6087bis as 
one long list of CLRs ...

But giving people sensible advice on how to use to produce good YANG 
models generally seems helpful to me.  But with the understanding that 
it is just advice, is not set in stone, and it could reasonably change 
over time.

I actually think that this sort of information (e.g. perhaps the bulk of 
6087 content) may be better on wiki pages, where it is less formal and 
can change in a more fluid way.  Oops! I've just created another CLR ;-)

Thanks,
Rob


>
> /js
>