Re: [OPSAWG] svc-common (RE: CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common

Italo Busi <Italo.Busi@huawei.com> Wed, 23 September 2020 09:44 UTC

Return-Path: <Italo.Busi@huawei.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 86A6F3A0EF6 for <opsawg@ietfa.amsl.com>; Wed, 23 Sep 2020 02:44:08 -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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SSl2F3rzs4lt for <opsawg@ietfa.amsl.com>; Wed, 23 Sep 2020 02:44:06 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 B78CA3A0EF1 for <opsawg@ietf.org>; Wed, 23 Sep 2020 02:44:06 -0700 (PDT)
Received: from lhreml750-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 6EF172B5571F9A934800; Wed, 23 Sep 2020 10:44:05 +0100 (IST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by lhreml750-chm.china.huawei.com (10.201.108.200) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 23 Sep 2020 10:44:05 +0100
Received: from fraeml715-chm.china.huawei.com (10.206.15.34) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 23 Sep 2020 11:44:04 +0200
Received: from fraeml715-chm.china.huawei.com ([10.206.15.34]) by fraeml715-chm.china.huawei.com ([10.206.15.34]) with mapi id 15.01.1913.007; Wed, 23 Sep 2020 11:44:04 +0200
From: Italo Busi <Italo.Busi@huawei.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, opsawg <opsawg@ietf.org>
Thread-Topic: svc-common (RE: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
Thread-Index: AdaBwCxEHb86eyBIRz68QNAiiG5eNgPzVdVA
Date: Wed, 23 Sep 2020 09:44:03 +0000
Message-ID: <1455e2bcc55344658af9166b28a2f9a5@huawei.com>
References: <1214_1599116546_5F509502_1214_79_6_787AE7BB302AE849A7480A190F8B933031537EE4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <1214_1599116546_5F509502_1214_79_6_787AE7BB302AE849A7480A190F8B933031537EE4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.94.9]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/0X9iQAZ-NXyTadwlDbLKFTfh0a4>
Subject: Re: [OPSAWG] svc-common (RE: CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
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: Wed, 23 Sep 2020 09:44:09 -0000

Hi Med,

When I look at the L2SM/L2NM, I can see some groupings/identities/types which are not really specific for L2VPN but have a broader applicability to other solutions/implementations of Ethernet services.

I therefore see some benefits in extending the potential scope of this module even if we can keep the scope of its initial revision limited/focused to what it is needed.

My 2 cents

Thanks, Italo

> -----Original Message-----
> From: mohamed.boucadair@orange.com
> [mailto:mohamed.boucadair@orange.com]
> Sent: giovedì 3 settembre 2020 09:02
> To: Italo Busi <Italo.Busi@huawei.com>om>; opsawg <opsawg@ietf.org>
> Subject: svc-common (RE: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-
> opsawg-vpn-common
> 
> Hi Italo,
> 
> I'm afraid that "svc-common" is too generic and does not reflect what we are
> planning to do in this draft: L2/L3 VPNs. I suggest we maintain the initial scope
> and name.
> 
> Thank you.
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : OPSAWG [mailto:opsawg-bounces@ietf.org] De la part de Italo Busi
> > Envoyé : lundi 24 août 2020 11:57 À : Joe Clarke (jclarke)
> > <jclarke@cisco.com>om>; opsawg <opsawg@ietf.org> Objet : Re: [OPSAWG]
> > CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common
> >
> > I support the adoption of this draft as WG document
> >
> > I think the scope of the draft/model can also be extended to be
> > applicable to any service-type module and not being limited to only
> > L2VPN and L3VPN. For example we can call it svc-common rather than
> > vpn-common.
> >
> > Regarding the approach, my preference is to include in the common
> > module all the types/groupings which are common.
> >
> > In order not to delay the progress of L3NM, it is possible to follow
> > the same approach that has been followed in CCAMP WG with layer0-
> > types: once L3NM is ready for WG LC, it is possible to move forward
> > for WG LC only the common types/groupings which are needed by L3NM (as
> > first revision of the common YANG module) and to move the
> > types/groupings needed by other on-going work (e.g., L2NM) into a new
> > draft which is intended to become a second revision of the common YANG
> > module.
> >
> > My 2 cents
> >
> > Italo
> >
> 
> 
> ________________________________________________________________
> _________________________________________________________
> 
> 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.