[OPSAWG] vpn-common scope (was RE: CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common)

mohamed.boucadair@orange.com Thu, 03 September 2020 13:42 UTC

From: mohamed.boucadair@orange.com
To: Italo Busi <Italo.Busi@huawei.com>, opsawg <opsawg@ietf.org>
Thread-Topic: vpn-common scope (was RE: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common)
Thread-Index: AdaB9/1MGBRzKT9ESgKCAXkkZXF1FQ==
Date: Thu, 03 Sep 2020 13:41:58 +0000
Message-ID: <1401_1599140519_5F50F2A7_1401_126_1_787AE7BB302AE849A7480A190F8B93303153A367@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/SCvr6kzo9ghoLPsmS5armrTXB8o>
Subject: [OPSAWG] vpn-common scope (was RE: CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common)
Precedence: list

Hi Italo, 

> Regarding the approach, my preference is to include in the common
> module all the types/groupings which are common.

I think that you are arguing to add to the common module even nodes that are only applicable to L3 or L2 such as nodes that are common between L3NM and L3SM or L2NM and L2NM. This is a fair comment. 

Unless there is an objection from the WG, we will update -01 to include items that are common between L3xMs or L2xMs. 

Thank you for raising the point. 

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>; 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.

[OPSAWG] vpn-common scope (was RE: CALL FOR ADOPT… mohamed.boucadair