Hello, Tom/ WG just to clarify. I was referring to "facilitate" the implementations mainly because of the high number of dependencies that now exits between the service and network models. A common module would allow to independently implement one model or the other, avoiding undesired cross-references.
In the current Service models RFCs, remarkable service-related definitions are written twice (in one model and the other), thus, a module containing these definitions would avoid the information duplication. Regards, Samier Barguil Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte | Móvil +57 3017026430 Móvil +34 665416074 E-mail samier.barguilgiraldo....@telefonica.com E-mail samier.barg...@wipro.com ________________________________ De: tom petch <ie...@btconnect.com> Enviado: viernes, 14 de agosto de 2020 11:19 Para: SAMIER BARGUIL GIRALDO <samier.barguilgiraldo....@telefonica.com>; Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org>; opsawg <opsawg@ietf.org> Asunto: Re: CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common From: OPSAWG <opsawg-boun...@ietf.org> on behalf of SAMIER BARGUIL GIRALDO <samier.barguilgiraldo....@telefonica.com> Sent: 14 August 2020 08:41 Hello WG, I Support the adoption of this draft using the "Forte" approach. It is necessary to decouple the modules in order to facilitate their future implementations. <tp> M mmm I find the reason somewhat strange. Creating a common module, that is imported into several others, binds those others together and so couples them, not decouples. If you want to decouple, then each of those several modules would have its own e.g. vpn-services definitions. The common module does have benefits, of consistent definitions where the objects are wanted in more than one module, decoupling is not one of them. What you could say is that the designers of a module saw something that they wanted to use in another module and so imported that other module lock, stock and barrel when 90% of it was not wanted and created an unnecessarily complicated combination, but that is really a comment on the inadequacies of YANG, of the inability to import only the bits you wanted, something that SMI did not suffer from:-) Tom Petch Regards, Samier Barguil Transport & IP Networks | GCTIO - Technology | CIT Centro Integrado de Transporte | Móvil +57 3017026430 Móvil +34 665416074 E-mail samier.barguilgiraldo....@telefonica.com E-mail samier.barg...@wipro.com ________________________________ De: OPSAWG <opsawg-boun...@ietf.org> en nombre de Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org> Enviado: jueves, 13 de agosto de 2020 7:49 Para: opsawg <opsawg@ietf.org> Asunto: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common 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 OPSAWG@ietf.org 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 ________________________________ 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 OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
