Re-, Great. Thanks.
The change is now implemented in the draft as you can see in this diff: https://www.ietf.org/rfcdiff?url1=draft-ietf-opsawg-l3sm-l3nm-12&url2=draft-ietf-opsawg-l3sm-l3nm-13 Cheers, Med > -----Message d'origine----- > De : Julian Lucek [mailto:jlu...@juniper.net] > Envoyé : lundi 27 septembre 2021 15:55 > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; > opsawg@ietf.org > Objet : Re: [OPSAWG] Last Call: <draft-ietf-opsawg-l3sm-l3nm-10.txt> (A > Layer 3 VPN Network YANG Model) to Proposed Standard > > Hi Mohamed > > Yes, that would be perfect > > Cheers > > Julian > > On 27/09/2021, 14:16, "mohamed.boucad...@orange.com" > <mohamed.boucad...@orange.com> wrote: > > [External Email. Be cautious of content] > > > Hi Julian, > > Following-up on the LAG point. > > The current model supports managing the LAG outside of the L3NM (as > other interface management). In this approach, a pointer to a LAG > interface can be provided under interface-id of vpn-network-access. > > However, I understand that you would like one step further and > control directly the creation of a LAG interface in the L3NM itself in > same way that we control the creation of loopbacks. Would adding these > data nodes under connection address your need? > > | +--rw lag-interface > | {vpn-common:lag-interface}? > | +--rw lag-interface-id? string > | +--rw member-link-list > | | +--rw member-link* [name] > | | +--rw name string > > Thank you. > > Cheers, > Med > > > -----Message d'origine----- > > De : last-call [mailto:last-call-boun...@ietf.org] De la part de > > mohamed.boucad...@orange.com > > Envoyé : mardi 7 septembre 2021 14:35 > > À : 'Julian Lucek' <jlucek=40juniper....@dmarc.ietf.org>; last- > > c...@ietf.org; opsawg@ietf.org > > Objet : Re: [Last-Call] [OPSAWG] Last Call: <draft-ietf-opsawg- > l3sm- > > l3nm-10.txt> (A Layer 3 VPN Network YANG Model) to Proposed > Standard > > > > Hi Julian, > > > > Thanks for the comments. > > > > Please see inline. > > > > Cheers, > > Med > > > > > -----Message d'origine----- > > > De : last-call [mailto:last-call-boun...@ietf.org] De la part de > > > Julian Lucek Envoyé : vendredi 6 août 2021 16:06 À : > > > last-c...@ietf.org; opsawg@ietf.org Objet : [Last-Call] [OPSAWG] > Last > > > Call: <draft-ietf-opsawg-l3sm- l3nm-10.txt> (A Layer 3 VPN > Network > > > YANG Model) to Proposed Standard > > > > ... > > > > > 2/ vpn-network-access is missing the ability to invoke a lag- > > > interface, including listing which are the member-links. > (However the > > > L2-NM model has this feature, this could be reused in the L3-NM) > > > > [Med] We do actually have a discussion as part of the L2NM whether > LAG > > matters (link members, in particular) should be defined > independently of > > the service (and thus removed from the model or at least moved up > in the > > structure). Will need to think further about this one. > > > > > > ________________________________________________________________________ > _________________________________________________ > > 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. > > > > Juniper Business Use Only _________________________________________________________________________________________________________________________ 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://www.ietf.org/mailman/listinfo/opsawg
