IETF Logo Mail Archive

Re: [OPSAWG] Review of draft-lear-opsawg-ol

Eliot Lear <lear@lear.ch> Wed, 04 August 2021 18:05 UTC

Return-Path: <lear@lear.ch>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 436183A0E9C for <opsawg@ietfa.amsl.com>; Wed, 4 Aug 2021 11:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.891
X-Spam-Level:
X-Spam-Status: No, score=-0.891 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 6Q3RdgiiHHjH for <opsawg@ietfa.amsl.com>; Wed, 4 Aug 2021 11:05:24 -0700 (PDT)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (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 221DD3A0E90 for <opsawg@ietf.org>; Wed, 4 Aug 2021 11:05:23 -0700 (PDT)
Received: from [IPv6:2a02:aa15:4101:2a80:9587:3ee9:8a1:632e] ([IPv6:2a02:aa15:4101:2a80:9587:3ee9:8a1:632e]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 174I5HKZ191932 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Wed, 4 Aug 2021 20:05:17 +0200
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1628100317; bh=lu0Dmfk3/5EvEXve8sdPfCFMhHWY0vTamdvHUNma3cQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=SIg1V1IwwvKL+M+dKtCDs7kIFYlBh3+la2Y2S16tq0hu/KG4ACtqnSeXNGp9tVwXS TzZcqKjmtv52LFW9gxCOHTJpKOr/c9CYpd7mfO8yudE748toNec/MkjvSa5RdlUtiW zULAO6IfdifCMdVsQkV7xA1WI77xNIDqrMrk+VqI=
To: "Joe Clarke (jclarke)" <jclarke=40cisco.com@dmarc.ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
Cc: Balazs Lengyel <balazs.lengyel@ericsson.com>
References: <BN9PR11MB5371EA70E28B271C5728FDB0B8F19@BN9PR11MB5371.namprd11.prod.outlook.com>
From: Eliot Lear <lear@lear.ch>
Message-ID: <bc82e399-4c35-2c5a-bfdc-4f125ac4de0f@lear.ch>
Date: Wed, 04 Aug 2021 20:05:15 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <BN9PR11MB5371EA70E28B271C5728FDB0B8F19@BN9PR11MB5371.namprd11.prod.outlook.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="knStI7XewrElDzcVVIm96v57CyGMm4Wb9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/6-8IpJboGen0gDstNMC1o6OfUTY>
Subject: Re: [OPSAWG] Review of draft-lear-opsawg-ol
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2021 18:05:29 -0000

Hi Joe,

I could totally turn ol inside out and make it a standalone module that 
the MUD augmentation just includes.  Is that something people would prefer?

Eliot

On 04.08.21 16:56, Joe Clarke (jclarke) wrote:
> I had a read through draft-lear-opsawg-ol.  I find the concept of adding
> owner and license metadata to YANG artifacts useful.  Eliot mentioned a
> desire to make this MUD-agnostic at the mic during 111, but that seems
> to only extend as far as the title.  The contents still very much rely
> on MUD.
>
> In reading through this, I feel there is a nice tie-in to
> draft-ietf-netmod-yang-instance-file-format (so copying Balazs and
> Benoit) as, while they have contact and org metadata for instance data,
> they don't have an owner or license per se.  I think having ol augment
> the instance data file module would be beneficial.
>
> On the ol work itself, I think the SPDX URL should fit into a reference
> under its leaf, and I wonder if there is a well-defined pattern for SPDX
> that can further refine the string type?
>
> Joe
>
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
>

v2.23.0 | Report a Bug | By Email