IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Fri, 28 May 2021 16:29 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 7C8C63A2DAB for <opsawg@ietfa.amsl.com>; Fri, 28 May 2021 09:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level:
X-Spam-Status: No, score=-0.89 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, RCVD_IN_DNSWL_BLOCKED=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 pZtMoPruqLZj for <opsawg@ietfa.amsl.com>; Fri, 28 May 2021 09:29:08 -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 602533A2DAC for <opsawg@ietf.org>; Fri, 28 May 2021 09:29:08 -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 14SGSvjg260128 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Fri, 28 May 2021 18:28:57 +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=1622219338; bh=HA++a24e76UYtGRO3wsCLNWuPqUjMKNkrOFK5hUlI8g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=QFpbt1KRkXOC7CSU9gKolCMjUYxV0kKR4PUtaGrn6oEdac/OU+NA9jBav/oHymouz zRcMkRrRd46it/6wKxuzwOrzxtO/TMIfwJ/TLX1DEkBD9B69iscjULzRaeiyVKCLh6 1/HwhJfvUy9YoKFo8o2UbPW5QmeHs9NCCKMddCns=
To: tom petch <ietfc@btconnect.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "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> <674c45ce-6b84-b50c-2d43-27839015123a@lear.ch> <5343_1622203174_60B0DB26_5343_176_1_787AE7BB302AE849A7480A190F8B933035393109@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <12487.1622212092@localhost> <21263_1622212875_60B1010B_21263_105_1_787AE7BB302AE849A7480A190F8B93303539447E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <AM7PR07MB6248FADA8D5D732E7327C556A0229@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: Eliot Lear <lear@lear.ch>
Message-ID: <f55e3bc8-707b-5db0-06e8-e3aca42be0f3@lear.ch>
Date: Fri, 28 May 2021 18:28:55 +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: <AM7PR07MB6248FADA8D5D732E7327C556A0229@AM7PR07MB6248.eurprd07.prod.outlook.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="tLNHdCst4xwipzJFq6sWJ2AVxTZQ6M3So"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/bkktYbXrwT5vwBkMltjsw3puz2w>
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 16:29:14 -0000

Hi Tom,

On 28.05.21 17:52, tom petch wrote:
>
> <tp>
> Well-formed I-D should explain how they update what they claim to update.  This one does, sort of, in the Introduction.  What is missing is text such as
> Section.x.y of RFC8520 is updated to include the following paragraph
> "Those generating MUD files SHOULD use the owner-license [RFCxxxx] extension unless ...2

What the draft says:

 > Those generating MUD files SHOULD use this extension, and thus this 
extension updates RFC 8520.

Regarding the words, "extends" or "updates", I have no horse in that race.

Eliot

v2.23.0 | Report a Bug | By Email