IETF Logo Mail Archive

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

mohamed.boucadair@orange.com Fri, 04 June 2021 11:50 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 4E0EF3A0DCD for <opsawg@ietfa.amsl.com>; Fri, 4 Jun 2021 04:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, 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 5EqYFYcztsOF for <opsawg@ietfa.amsl.com>; Fri, 4 Jun 2021 04:50:29 -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 312363A0DCA for <opsawg@ietf.org>; Fri, 4 Jun 2021 04:50:29 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 4FxLg70M4fz8tt2; Fri, 4 Jun 2021 13:50:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622807427; bh=UfxVimHT3IMYMKO9KnXITEZgs/rNnTp01asZwiEuJzg=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=Pw6J7rd+K6u1tsyFFXZZNBLBoryumEYK9uulQCYXLeQViUfhDwX1xlc+0bf3Z74Us 8A7qIGAp8jny7XwWkVXCLc6dLpCGmEaWIXyh5YN39emmW9DdiWGndXgtFuOjb1wytG nU1k3aIvX42IkY2WgSok14BxOEGVNL4nycFPpcFRZBX+AG6t/nTHX3XbBnIY38WbkN ktRw10uY2B0C6sg8pfGe2NMk8dJhE4WtKAoW7o3yBn6fxfKLoIMBYsthWmxQHzBFV+ 97mF7/7/UVA4sy19sjVum38WMWBX0QXMgjC/kAYrsHYug3TsLR5RgvXOXf+RKb6utN /TTr23cvsEn0g==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.76]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 4FxLg66V13z3wbN; Fri, 4 Jun 2021 13:50:26 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: Carsten Bormann <cabo@tzi.org>
CC: "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: [OPSAWG] please see draft-lear-opsawg-ol on licensing
Thread-Index: AQHXUt+y++eYI4gOQU6/qboAEWBSIKr4kFxAgAseQiiAABk8cA==
Date: Fri, 04 Jun 2021 11:50:26 +0000
Message-ID: <10327_1622807426_60BA1382_10327_206_13_787AE7BB302AE849A7480A190F8B933035398B57@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> <8685_1622799260_60B9F39C_8685_106_16_787AE7BB302AE849A7480A190F8B933035398A6D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <71E78BA5-8B70-4827-9809-11DF0C118F4D@tzi.org>
In-Reply-To: <71E78BA5-8B70-4827-9809-11DF0C118F4D@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: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933035398B57OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/WPLASOVescUZ4orNM_7grzgb0P8>
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 11:50:34 -0000

Re-,

It is also ours as participants, Carsten.

If you really want to make sure that extension is considered by a MUD implementer (and this is really about the augment thing), you can consider defining version 2 of the mud module in the ol I-D. This is a much more clean design to convey the message you want.

Cheers,
Med

De : Carsten Bormann [mailto:cabo@tzi.org]
Envoyé : vendredi 4 juin 2021 12:13
À : 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 4. Jun 2021, at 11:34, <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:

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

That’s the IESG’s job — above my paygrade :-)

What I’m concerned is that 8520 readers find a pointer to the new document.
An “updated by” on the (metadata rich versions of) 8520 raises the likelihood substantially.
Which is more important than any concept of consistency (which we won’t really have until the IESG is done with Mirja’s proposals).

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