Re: [OPSAWG] Timeline to decide to go with the common module in L3NM/L2NM, upload and present current version?

tom petch <ietfc@btconnect.com> Fri, 10 July 2020 10:28 UTC

Return-Path: <ietfc@btconnect.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 8647F3A0847 for <opsawg@ietfa.amsl.com>; Fri, 10 Jul 2020 03:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.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 N3L6phJyYell for <opsawg@ietfa.amsl.com>; Fri, 10 Jul 2020 03:28:01 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150094.outbound.protection.outlook.com [40.107.15.94]) (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 CB72C3A0846 for <opsawg@ietf.org>; Fri, 10 Jul 2020 03:28:00 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OxZnnoKU9wLaPtunbaCGBfvwFNjAjZnkwugrJ/1Q4s+T9XozCBnXRnoUeEmSRSuUjOL6l1c7/of9iPTljYHya6UMtbOFYZwyeRhd85c1H1vzy9oCSQyY/R8LEmQ1QJtd6BZWVrI1C09wY8+j6L0k7CcNH4L/1cJtCwUHcZWra2rEn6EQMkULBF9TmphX2kOTGmVYA+cAHtVZj309BE2w3fJ4UuWqQcnnEHNqBJgLbhl0M3HnhpykBmZbt07Hf25PbcG3htONqJPCvKbctjeXNmiRFkMG3l16JvmJNwoQg0obpFc/eTHTqQY5TUj9T+iLrBC0UC+8uqjBkGHmK15X5A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=gew2GhbYirigiwzOVTLkTHcVhQPkez8GDteslemyfaw=; b=UN2A++bs2GcrlMA/xpHcJJ67Ddg2efftCrH2asPrn9tHDo57wpwJ1Ga7MflHghMMH12tjxmiPTRKf9Wfnfgo0V+6CMHaW5kDSdv2LutyxI2ZthPFtOtVgZprpQw6a0RdQPwbdABIMYMwTwBVGDYMwYS8DR/2n/S2tHBJXP8I4gBaCKvd++q1jexKaBpBsS1WWzMWJh8S5O5s/H4t7Ge9a0hvOXMcPcZJI11TqS156mJCsMFoQNfCpKwOONexsbkBvd7Y4zayEcyJorVOmKgyWTUWTv7vqZckteq9oSUHH4NgjpE7q0SWOvnARJkmqZRlW8DNM1qZWR7gTnNWT8wz6A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=gew2GhbYirigiwzOVTLkTHcVhQPkez8GDteslemyfaw=; b=oQMN+DQ8BXPZQeFArPp6SXDlLXOeEMsPkBgDpzlicUqgMJc7+HhAOAt8/f/l2FkFyEIg14PmE449e8hIH43uIJATYvTsad7PM9n3pE53MiNljKJU0iGs5OIBMvKbJgB85Vv1JTwDoTNwFAw5UMpxHABJzFZtLp0loEGpIDvoLiY=
Received: from DBAPR07MB7016.eurprd07.prod.outlook.com (2603:10a6:10:198::14) by DB6PR0701MB2917.eurprd07.prod.outlook.com (2603:10a6:4:6f::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.16; Fri, 10 Jul 2020 10:27:58 +0000
Received: from DBAPR07MB7016.eurprd07.prod.outlook.com ([fe80::b09b:5a3b:9735:bf26]) by DBAPR07MB7016.eurprd07.prod.outlook.com ([fe80::b09b:5a3b:9735:bf26%5]) with mapi id 15.20.3174.020; Fri, 10 Jul 2020 10:27:58 +0000
From: tom petch <ietfc@btconnect.com>
To: Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>, opsawg <opsawg@ietf.org>
Thread-Topic: Timeline to decide to go with the common module in L3NM/L2NM, upload and present current version?
Thread-Index: AdZV5OZR7cROT8S4R5Wrwo4ONv0cZQAv1u7b
Date: Fri, 10 Jul 2020 10:27:58 +0000
Message-ID: <DBAPR07MB7016CCBB0D6F2C0ABACEAF2BA0650@DBAPR07MB7016.eurprd07.prod.outlook.com>
References: <AM6PR06MB5653B93FAE70DA06FB538397FD640@AM6PR06MB5653.eurprd06.prod.outlook.com>
In-Reply-To: <AM6PR06MB5653B93FAE70DA06FB538397FD640@AM6PR06MB5653.eurprd06.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: telefonica.com; dkim=none (message not signed) header.d=none;telefonica.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [81.131.229.35]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f08bcc88-b1ef-49a3-0097-08d824bbea60
x-ms-traffictypediagnostic: DB6PR0701MB2917:
x-microsoft-antispam-prvs: <DB6PR0701MB2917E35B7C1EEF7194DAAE61A0650@DB6PR0701MB2917.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kI31bMQ+O+kMLQQI96KiXLkmGvddEr/SFnGJoKTQ8DMbhvDHcmC/omsfrCj6/sWJoLCnTIyWD/xy0GqO6dK7VKMu7wm2lwW02879ltAhGWopBUwve+pjUEiqFUhQbB7phJ0h07qUOKhzGgE5KkkmuwaWag/jsUR3UlPOnt8Z2pJwVDRTqA60dYTn5JYvZr33Ag8/ebBonceuBZACr/+xSyFeABOZQOOE1bU3ziIQdTNwN2s5SSyktVxHhz0RWVcSTGuBPRLSU/koc+/BKMnNecBR1GFJ1HB6/nZsitpL2eqBLfMhIsyimBTaihzTQUPf+xmNcsSrSJY+lFfbpSyyq2RaOjPzO8kp1Io8CsBeelfoGbikQPN8eIfHgGxkZuAq
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DBAPR07MB7016.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(136003)(39860400002)(366004)(396003)(376002)(346002)(64756008)(66476007)(66556008)(66446008)(71200400001)(7696005)(86362001)(83380400001)(9686003)(66574015)(33656002)(52536014)(76116006)(91956017)(478600001)(6506007)(296002)(316002)(5660300002)(2906002)(8676002)(66946007)(110136005)(26005)(186003)(8936002)(55016002)(32563001); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: VhDuDnmkmNJfY0w09ZMvlRoUVtpYaQ+1jTX3IDO9rmu78KADdOO8dg88o7IgxIoo+EIlxtNU9KQS79gZ+knbMS1DqkCaZY834kwa5rla3VlzFt9gr0bXN9E1Wui7Qz6dU0Jogj9VgW+jGmXj2R7AS7MjHMIZqeZyCiva2rd0FBeYCnPcR6QH5rY0PGmmra8/gvUqdJU7whcGJIBSG+eEw0B0KQnoZG8tFPdeUXesHN+YKwWzMxAywUfkVC7qP3UMW8cPsBnbZAukSUl8d3eLFyv+mZiaBWhR3HtA9+saobH65Gm4OhLYfHJOd1z68zH1UAHi5CFTHitLavI2cdkMJXZGfs5j3HoYVXK0og/ykevIbJRwkfsMylpVapRPbFvq8aNZSGskiQTGVlxCVV9ndDbYRgVcvjox8k5ySE9Zq7EIB1prlIJU+4shwecKAEDUyrBp+2S8zNwAqAABK14aGGIfPaav8PdsbTIjVFcRGlY=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DBAPR07MB7016.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f08bcc88-b1ef-49a3-0097-08d824bbea60
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2020 10:27:58.2141 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: aesuof2cFizRfJCXFSB3PAEn+Gy76zN9qZ2n5foUZ1MOi8UDi7TnJ8YlVyqjCrPpr7AqXDJBhOoorbU1OsbXwg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2917
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/zkmdjDN4KD6IxKWcUyVtUnR5W2M>
Subject: Re: [OPSAWG] Timeline to decide to go with the common module in L3NM/L2NM, upload and present current version?
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, 10 Jul 2020 10:28:03 -0000

From: OPSAWG <opsawg-bounces@ietf.org> on behalf of Oscar González de Dios <oscar.gonzalezdedios@telefonica.com>
Sent: 09 July 2020 12:34

Hi Joe, Tianran,

During las weeks we’ve been working in the common module proposal. There have been many interactions with cross-reviews of each proposal (more than 50 pull requests in the last weeks) It has been already shared with the list. We have also ready a new version of the draft including the proposed change.

This version using the common module also solves several issues raised in the Yang doctor review and reviews in the mailing list.

As the deadline to submit the new drafts is approaching (13th July), we would like to agree with you on how to proceed. Do we upload the draft with the common module proposal, ask formally for review, present it in next IETF meeting and send it to Yang doctor, as his comments were addressed?

<tp>
For myself, I prefer plain text I-D and see that as part of the IETF's successes, making information available in a standard, but simple, format.  So another alternative is to publish an individual I-D which can be adopted by the WG, copied into an all-embracing I-D, binned, .....

Tom Petch

                If you have some time, we can have a short call on how to proceed,

                Best Regards,


                               Oscar



________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição