IETF Logo Mail Archive

Re: [OPSAWG] WG adoption call for draft-aguado-opsawg-l3sm-l3nm-02

<mohamed.boucadair@orange.com> Mon, 30 September 2019 14:25 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 B20631200B3 for <opsawg@ietfa.amsl.com>; Mon, 30 Sep 2019 07:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
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 4N3PRrUYs9-h for <opsawg@ietfa.amsl.com>; Mon, 30 Sep 2019 07:25:34 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07D25120058 for <opsawg@ietf.org>; Mon, 30 Sep 2019 07:25:34 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 46hl701Cskz7tNB; Mon, 30 Sep 2019 16:25:32 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.73]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 46hl700Pw7zBrMR; Mon, 30 Sep 2019 16:25:32 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM23.corporate.adroot.infra.ftgroup ([fe80::9108:27dc:3496:8db3%21]) with mapi id 14.03.0468.000; Mon, 30 Sep 2019 16:25:31 +0200
From: mohamed.boucadair@orange.com
To: Tianran Zhou <zhoutianran@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: WG adoption call for draft-aguado-opsawg-l3sm-l3nm-02
Thread-Index: AdV2jv6zHsr5DVFJRS+jC2+KXIwbmgBCzS7Q
Date: Mon, 30 Sep 2019 14:25:31 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93303132826B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <BBA82579FD347748BEADC4C445EA0F21BEFF7F8F@NKGEML515-MBX.china.huawei.com>
In-Reply-To: <BBA82579FD347748BEADC4C445EA0F21BEFF7F8F@NKGEML515-MBX.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/6kcCyBt9sCi8VjOsr-qroc_Dry4>
Subject: Re: [OPSAWG] WG adoption call for draft-aguado-opsawg-l3sm-l3nm-02
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: Mon, 30 Sep 2019 14:25:36 -0000

Hi all,

I support. 

It would be useful if the document discusses (1) how the L3SM data can fed L3NM (with same examples) and (2) why the module is not defined as a normal "augment" of L3SM.

Cheers,
Med

> -----Message d'origine-----
> De : OPSAWG [mailto:opsawg-bounces@ietf.org] De la part de Tianran Zhou
> Envoyé : dimanche 29 septembre 2019 08:29
> À : opsawg@ietf.org
> Objet : [OPSAWG] WG adoption call for draft-aguado-opsawg-l3sm-l3nm-02
> 
> Hi WG,
> 
> This email starts a 2 weeks working group adoption call for draft-aguado-
> opsawg-l3sm-l3nm-02.
> https://datatracker.ietf.org/doc/draft-aguado-opsawg-l3sm-l3nm/
> 
> This document proposes a L3VPN Network Yang Model (L3NM) to facilitate
> communication between a service orchestrator and a network
> controller/orchestrator.
> 
> If you support adopting this document please say so, and please give an
> indication of why you think it is important. Also please say if you will
> be willing to review and help the draft.
> If you do not support adopting this document as a starting point for work
> on this topic, please say why.
> This poll will run until Oct 14.
> 
> Thanks,
> Tianran and Joe
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

v2.23.0 | Report a Bug | By Email