Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing

Eliot Lear <lear@lear.ch> Fri, 28 May 2021 11:43 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 CD6AC3A25D2 for <opsawg@ietfa.amsl.com>; Fri, 28 May 2021 04:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level:
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 TIjq4imEeUOW for <opsawg@ietfa.amsl.com>; Fri, 28 May 2021 04:43:06 -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 0C9F93A25D4 for <opsawg@ietf.org>; Fri, 28 May 2021 04:43:05 -0700 (PDT)
Received: from [IPv6:2001:420:c0c0:1011::7] ([IPv6:2001:420:c0c0:1011:0:0:0:7]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 14SBh2wr252659 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 28 May 2021 13:43:03 +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=1622202183; bh=d7nyX8Gmaooq7rG5tVi1jvVU34vbsbWmbbcCeZ5le2E=; h=To:References:From:Subject:Date:In-Reply-To:From; b=fk28unU0cr1hq7wm+rdeSo/mdioRFP1AL4EbKGu55Uh0IqFvOUavUZ1ooSk2G/kZT V57DoyJHWMSEL5SQaVO0zcVRchNWXH5G/XOaXJiyf/rCgUF/ZdqEXdaFAH/BxHLYly F/1C7ACYz0uRJHAQ9XtwmdmIDMZ1UoM/wyuAlPlM=
To: mohamed.boucadair@orange.com, "opsawg@ietf.org" <opsawg@ietf.org>
References: <340b29f4-e867-6a5d-b45c-8c8b9e45eb47@lear.ch> <13971_1622193488_60B0B550_13971_295_1_787AE7BB302AE849A7480A190F8B93303539075F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: Eliot Lear <lear@lear.ch>
Message-ID: <674c45ce-6b84-b50c-2d43-27839015123a@lear.ch>
Date: Fri, 28 May 2021 13:43:00 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <13971_1622193488_60B0B550_13971_295_1_787AE7BB302AE849A7480A190F8B93303539075F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="iJoFErYDkN5TKiBw1kfbAXnTKEAwpZTp8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/QBYwv5EP16gRcW7s892DQ3zllIk>
Subject: Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing
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: Fri, 28 May 2021 11:43:12 -0000

Hi Med,

Thanks for your comments.  Please see below.

On 28.05.21 11:18, mohamed.boucadair@orange.com wrote:
> Hi Eliot, all,
>
> This extension makes sense to me. I support it to be adopted in opsawg (where 8520 was developed).
>
> That's said, this draft does not update 8520. I suggest to remove "Updates: 8520 (if approved)"
>
> Please find below some other comments, fwiw.
>
> (1)
>
> OLD:
>
>       import ietf-inet-types {
>         prefix inet;
>       }
>
> NEW
>       import ietf-inet-types {
>         prefix inet;
>         reference
>           "RFC 6991: Common YANG Data Types, Section 4";
>       }


Sure, thanks.


> (2) Use the prefix as defined in 8520:
>
> OLD:
>
>       import ietf-mud {
>         prefix mud;
>       }
>
> NEW:
>
>       import ietf-mud {
>         prefix ietf-mud;
>         reference
>           "RFC 8520: Manufacturer Usage Description Specification";
>       }
>

Right.


> (3)
>
> You may remove the note about normative language in the description of the module given that you don't use it.

I think we need to discuss this more, because we SHOULD be applying a 
SHOULD on this document to 8520 so that there is no IPR confusion.  And 
that implies an update.

>
> (4)
>
> OLD:
>         reference
>           "RFC XXXX: Extension for ownership and licensing";
> NEW:
>         reference
>           "RFC XXXX: Ownership and licensing statements in YANG";


Corrected, thanks.

>
> (5)
>
> Rather than using "leaf-list owners", I would define this as a list keyed by owners and which may include a leaf-list of licenses. Rather than defining license as a choice, I would use a "union".
We're still discussing the substance of this.
> (6)
>
> OLD:
>
>         "ol": {
>           "owners": [
>             "Copyright (c) FrobMaster 2021. All Rights Reserved"
>           ],
>           "spdx-tag": "0BSD"
>         },
>
> NEW:
>         "ietf-ol:ol": {
>           "owners": [
>             "Copyright (c) FrobMaster 2021. All Rights Reserved"
>           ],
>           "spdx-tag": "0BSD"
>         },
Still working on this.
> (7) Please update the IANA section as follows:
>
> OLD:
>     The IANA is requested to add "ol" to the MUD extensions registry as
>     follows:
>
>       Extension Name: ol
>       Standard reference: This document
>
> NEW:
>     The IANA is requested the following entry to the MUD extensions registry
>     available at: https://www.iana.org/assignments/mud/mud.xhtml#mud-extensions
>
>       Extension Name: ol
>       Reference: This document
Done.  Thanks.
> (8) Please update the IANA section with the following:
>
> NEW
>
>     This document requests IANA to register the following URI in the "ns"
>     subregistry within the "IETF XML Registry" [RFC3688]:
>
>           URI: urn:ietf:params:xml:ns:yang:ietf-ol
>           Registrant Contact: The IESG.
>           XML: N/A; the requested URI is an XML namespace.
>
>     This document requests IANA to register the following YANG module in
>     the "YANG Module Names" subregistry [RFC6020] within the "YANG
>     Parameters" registry.
>
>           name: ietf-ol
>           namespace: urn:ietf:params:xml:ns:yang:ietf-ol
>           maintained by IANA: N
>           prefix: ol
>           reference: RFC XXXX
What does "maintained by IANA" mean in this context?

Thanks again for the update.

Eliot