Hi Oscar, > - This text > > To avoid the issues discussed above, this document defines a common > YANG module that is meant to be reused by various VPN-related modules > such as Layer 3 VPN Service Model (L3SM) [RFC8299], Layer 2 VPN > Service Model (L2SM) [RFC8466], Layer 3 VPN Network Model (L3NM) > [I-D.ietf-opsawg-l3sm-l3nm], and Layer 2 VPN Network Model (L2NM) > [I-D.ietf-opsawg-l2nm]: "ietf-vpn-common" (Section 4). > > While it is clear how this common model can be used by work-in-progress L3NM > and L2NM models, I am not sure about the published service model. Maybe you > want to suggest that a future update of these service models MAY use this > common model? If yes, better to be explicit. > > > Oscar>> The common model can also be used with the already published L3SM and > L2SM models. Should the IETF community decide to proceed that way, an updated > version could be produced importing from the common module. However, in the > short term the focus is on the published drafts.
[Dhruv]: My suggestion is to update the quoted text to differentiate between the LxNM and LxSM models. Once the LxNM models are updated to use the common model, we can clearly state that fact and then include a statement that a future update to LxSM models MAY choose to reuse the common model as well. > - I was hoping to find L3NM and L2NM models using this common model either in > the draft or Github. Maybe the plan to update only after successful adoption > by the WG? > > > Oscar>> Once the WG has made the decision of the path to take, we will modify > the draft accordingly. The version in github is to facilitate people seeing > how the L3NM module would look like with the common module proposal. > I was looking at the wrong place. I found it now - https://github.com/IETF-OPSAWG-WG/l3nm/blob/master/yang/IETF-04/ietf-l3vpn-ntw.yang Thanks! Dhruv > Thanks! > Dhruv > > Oscar>> Thanks for the comments! > > On Thu, Aug 13, 2020 at 6:19 PM Joe Clarke (jclarke) > <[email protected]> wrote: > > > > Hello, WG members. On the IETF 108 virtual meeting, Oscar presented the > > status of the L3NM, L2NM, and the VPN common work. While this VPN common > > YANG module started as an individual document (per the chairs’ request), > > the L2NM and L3NM modules need to choose a direction for how to handle > > common typedefs and groupings between them. > > > > On the virtual meeting we did a hum which indicated “Pianissimo” support. > > Again, the hum system had some interesting rules, so this is not > > conclusive, but seems to favor that this common module work should exist as > > its own, standalone document that both L2NM and L3NM will consume. In this > > manner, one would not need to import either L2NM or L3NM to make use > > of/extend these common attributes. > > > > To that end, the chairs would like a call for adoption of > > draft-bgbw-opsawg-vpn-common. Additionally, comments on the approach and > > the choice of common attributes are welcome, especially from those that > > were unable to attend the IETF 108 virtual meeting. > > > > This serves as a two week call for adoption ending on August 27, 2020. > > > > Thanks. > > > > Joe > > _______________________________________________ > > OPSAWG mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/opsawg > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg > > ________________________________ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el destinatario > indicado, queda notificado de que la lectura, utilización, divulgación y/o > copia sin autorización puede estar prohibida en virtud de la legislación > vigente. Si ha recibido este mensaje por error, le rogamos que nos lo > comunique inmediatamente por esta misma vía y proceda a su destrucción. > > The information contained in this transmission is privileged and confidential > information intended only for the use of the individual or entity named > above. If the reader of this message is not the intended recipient, you are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this transmission > in error, do not read it. Please immediately reply to the sender that you > have received this communication in error and then delete it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, > pode conter informação privilegiada ou confidencial e é para uso exclusivo da > pessoa ou entidade de destino. Se não é vossa senhoria o destinatário > indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia > sem autorização pode estar proibida em virtude da legislação vigente. Se > recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente > por esta mesma via e proceda a sua destruição _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
