Re: [OPSAWG] Externalize some data nodes for better flexibilty (RE: [Last-Call] Yangdoctors last call review of draft-ietf-opsawg-l2nm-07)

mohamed.boucadair@orange.com Tue, 05 October 2021 14:59 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 6F1D63A03FC; Tue, 5 Oct 2021 07:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_MSPIKE_H2=-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 v7ZQj1pj1XgO; Tue, 5 Oct 2021 07:59:29 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (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 8AE3C3A03F7; Tue, 5 Oct 2021 07:59:28 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4HP12Q5SxXzCrmT; Tue, 5 Oct 2021 16:59:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1633445966; bh=Ot0xgtiLrpj8m5iQ0mBj2Y+fyUbeiQQkUcAE3eW0uO4=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=MMubt6g2GN8QmIQCSCVDJ3TtX4aLSus0LoNyHN4CWjN1DXJnAgTLg82oAN7KiCKTn SS6bFNaXPfcdNozc4/UzsMkPK4Ld1ro+cZfW3J1SAaY2m5YpmuagYO0PFN/Ext3if8 uBueFVkVnqSu5v1MhWzaKAyB8W7PnYJkVzCSCOwKME+YfWcMlCFIPLP0L+pTxVOUi+ 2NNVufbBdqUKI+qUzp8gHbUmuTRCB5qy6PHza8CRf2tGO+8fcOl0WWe4wXv3Ubftg2 2ZA1NafqUYqHoyTta1xUI8hdM1u1c1PWweRQ6gtCS7WreVrMDFOsHdbb0kBq8DF7X8 drrxKsohty52Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr00.francetelecom.fr (ESMTP service) with ESMTPS id 4HP12Q4ZkRzDqBV; Tue, 5 Oct 2021 16:59:26 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: Moti Morgenstern <Moti.Morgenstern@rbbn.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>
CC: "draft-ietf-opsawg-l2nm.all@ietf.org" <draft-ietf-opsawg-l2nm.all@ietf.org>
Thread-Topic: [OPSAWG] Externalize some data nodes for better flexibilty (RE: [Last-Call] Yangdoctors last call review of draft-ietf-opsawg-l2nm-07)
Thread-Index: Ade56uH4sv3PBI2aTeiPXotnL+zrOg==
Content-Class:
Date: Tue, 05 Oct 2021 14:59:25 +0000
Message-ID: <3524_1633445966_615C684E_3524_415_13_787AE7BB302AE849A7480A190F8B933035413BF0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-10-05T13:14:30Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=2982107d-34e6-433d-aa2e-d3aaad1ab592; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/Pde5qfs-XDtAai9quh255GLePms>
Subject: Re: [OPSAWG] Externalize some data nodes for better flexibilty (RE: [Last-Call] Yangdoctors last call review of draft-ietf-opsawg-l2nm-07)
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: Tue, 05 Oct 2021 14:59:35 -0000

Re-,

Thanks, Moti. 

If this proposal is adopted, I suggest we add this text to the ACK section:

NEW:

Acknowledgements

  ...

   A YANG module for Ethernet Segments was first defined in the context
   of the EVPN device module [I-D.ietf-bess-evpn-yang].

Cheers,
Med

> -----Message d'origine-----
> De : Moti Morgenstern <Moti.Morgenstern@rbbn.com>
> Envoyé : mardi 5 octobre 2021 14:43
> À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>;
> opsawg@ietf.org; adrian@olddog.co.uk
> Cc : draft-ietf-opsawg-l2nm.all@ietf.org
> Objet : RE: [EXTERNAL] [OPSAWG] Externalize some data nodes for better
> flexibilty (RE: [Last-Call] Yangdoctors last call review of draft-ietf-
> opsawg-l2nm-07)
> 
> Hi,
> 
> I think it's OK to manage the ES object via a separate module.
> It is very same approach as in
> https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-yang-07 (which
> expired two years ago).
> 
> Regards,
> Moti
> 
> -----Original Message-----
> From: OPSAWG <opsawg-bounces@ietf.org> On Behalf Of
> mohamed.boucadair@orange.com
> Sent: Tuesday, October 5, 2021 3:22 PM
> To: opsawg@ietf.org; adrian@olddog.co.uk
> Cc: draft-ietf-opsawg-l2nm.all@ietf.org
> Subject: [EXTERNAL] [OPSAWG] Externalize some data nodes for better
> flexibilty (RE: [Last-Call] Yangdoctors last call review of draft-ietf-
> opsawg-l2nm-07)
> 
> Hi all,
> 
> Lada made a comment about the flexibility of the module (see below). A
> proposal to address the comment is to move the ethernet segment part into
> a separate module as suggested in the following PR:
> https://clicktime.symantec.com/3QU3R71WM87hLHH56QkYggD6H2?u=https%3A%2F%2F
> github.com%2FIETF-OPSAWG-WG%2Flxnm%2Fpull%2F349%2Ffiles. The change is
> straightforward and has the merit to preserve the same global structure
> for both L2NM and L3NM.
> 
> Please review the PR and share your thoughts.
> 
> Of course, do no change is still an option.
> 
> Cheers,
> Med
> 
> > >> -----Message d'origine-----
> > >> De : Ladislav Lhotka via Datatracker <noreply@ietf.org> Envoyé :
> > >> mardi 5 octobre 2021 10:04 À : yang-doctors@ietf.org Cc :
> > >> draft-ietf-opsawg-l2nm.all@ietf.org; last-call@ietf.org;
> > >> opsawg@ietf.org Objet : Yangdoctors last call review of
> > >> draft-ietf-opsawg-l2nm-07
> > >>
> > >> Reviewer: Ladislav Lhotka
> > >> Review result: Ready with Issues
> > >>
> > >> **** General comments
> > >>
> > >> The ietf-l2vpn-ntw module with about 400 data nodes represents an
> > >> impressive amount of work. Its size, however, raises some concerns
> > >> in terms of manageability. For example, if the ITU-T Y-1731
> > >> recommendation ever gets updated (I don't know how likely this is),
> > >> the module will have to be updated.
> > >> I would therefore suggest to consider factoring out such parts into
> > >> separate modules.
> > >
> > > [Med] We have already made an effort to factorize many items in:
> > > * I-D.ietf-vpn-common
> > > * two separate IANA-maintained modules
> > >
> > > One candidate "externalization" that I think would work to address
> > > your
> > concern is to move ethernet-segments (and esi types) into a separate
> > module.
> > >
> > > I have a preference to work in that direction vs. touching the OAM
> part.
> > >
> > > Would that solve your concern? Thank you.
> >
> > I think it is up to the authors and WG to consider what to do, maybe
> > nothing. I am not an expert in this domain, so I have no strong
> > opinion, but it is certainly better to think twice because the module
> > structure cannot be easily changed afterwards.
> 
> 
> 
> __________________________________________________________________________
> _______________________________________________
> 
> 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 mailing list
> OPSAWG@ietf.org
> https://clicktime.symantec.com/3Ur78Ht4sGyPAUod8ApTUTZ6H2?u=https%3A%2F%2F
> www.ietf.org%2Fmailman%2Flistinfo%2Fopsawg
> 
> Notice: This e-mail together with any attachments may contain information
> of Ribbon Communications Inc. and its Affiliates that is confidential
> and/or proprietary for the sole use of the intended recipient. Any review,
> disclosure, reliance or distribution by others or forwarding without
> express permission is strictly prohibited. If you are not the intended
> recipient, please notify the sender immediately and then delete all
> copies, including any attachments.
> 
> Notice: This e-mail together with any attachments may contain information
> of Ribbon Communications Inc. and its Affiliates that is confidential
> and/or proprietary for the sole use of the intended recipient. Any review,
> disclosure, reliance or distribution by others or forwarding without
> express permission is strictly prohibited. If you are not the intended
> recipient, please notify the sender immediately and then delete all
> copies, including any attachments.

_________________________________________________________________________________________________________________________

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.