IETF Logo Mail Archive

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

mohamed.boucadair@orange.com Fri, 04 June 2021 09:34 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 C16593A30D1 for <opsawg@ietfa.amsl.com>; Fri, 4 Jun 2021 02:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.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 f6R2LyN--Pn2 for <opsawg@ietfa.amsl.com>; Fri, 4 Jun 2021 02:34:22 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 900243A30CC for <opsawg@ietf.org>; Fri, 4 Jun 2021 02:34:22 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 4FxHf435N2z2yll; Fri, 4 Jun 2021 11:34:20 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622799260; bh=z6sfJRFUF0sASNZbuKRky2/D4pJUoeSsuJgXliC2KfU=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=VzT00qvbvx2J69b9egzzU9GMeORLOaf9TQtNepoaahI4JpBfka40qNOwBskPYf/Be kkWc5e2d6nKzp/mEtsPcFdLl3wiZySfBQEIvI8RVBlxpHFh+4NPJ5Fci/jPfuTXOhz /cf/Atl7y7KHxz7hMopJWS45I97LjVwt5iP8padclZgPqa8eqbtAm5DLsR1lmX5qi1 4zRkoABqR6M9ZhklLueR1+ZiZeoo1PioRk+SW5djPUCg3SfPTZgytdE/NTozKoiiEj Kah0yZKoJZD32aaSdBYIVH8lZhpZiXWdUiKcfo6F6x+xmK+xQNPrWe86EriMqqV9G0 48VLHqsfEBh2A==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 4FxHf41x6Lz1xp9; Fri, 4 Jun 2021 11:34:20 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: Carsten Bormann <cabo@tzi.org>
CC: Michael Richardson <mcr@sandelman.ca>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] please see draft-lear-opsawg-ol on licensing
Thread-Index: AQHXUt+y++eYI4gOQU6/qboAEWBSIKr4kFxAgArmcPiAACm/QA==
Date: Fri, 04 Jun 2021 09:34:19 +0000
Message-ID: <8685_1622799260_60B9F39C_8685_106_16_787AE7BB302AE849A7480A190F8B933035398A6D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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> <31454.1622239977@localhost> <30792_1622448622_60B499EE_30792_414_1_787AE7BB302AE849A7480A190F8B933035394DFC@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <45505E41-664E-433F-940A-1F724561646D@tzi.org>
In-Reply-To: <45505E41-664E-433F-940A-1F724561646D@tzi.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/brzHONFj9bvRWcDIfMw2QJKeHak>
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, 04 Jun 2021 09:34:28 -0000

Hi Carsten, 

That's more a profiling thing than updating the base spec. 

Let's consider an example that you are very familiar with: RFC7252. The core WG published RFC8768 which says "New CoAP proxies MUST implement this option and have it enabled by default" without marking this as updating 7252. 

What I'm really concerned about is consistent use of the "update" header.

Cheers,
Med

> -----Message d'origine-----
> De : Carsten Bormann [mailto:cabo@tzi.org]
> Envoyé : vendredi 4 juin 2021 08:53
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
> Cc : Michael Richardson <mcr@sandelman.ca>; opsawg@ietf.org
> Objet : Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing
> 
> On 2021-05-31, at 10:10, mohamed.boucadair@orange.com wrote:
> >
> > If so, every extension (including modules with augment) would be
> tagged as updating their base RFC...while this is not the case.
> There are plenty examples out there.
> 
> This is not a syntactical issue (augment and all that), but a
> semantic one:
> RFC 8520 is updated with a "SHOULD use this".  That is the RFC 8520
> update, not the new module.
> 
> Grüße, Carsten


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

v2.23.0 | Report a Bug | By Email