Thanks, Joe Sure!
With regards to the L* modules split issue, given the feedback we received as a follow-up to the minutes sent to the list back in May https://mailarchive.ietf.org/arch/msg/opsawg/FQ5gJ1gN8aHWVpUQea6Of0_0elw/, we worked on a common VPN module proposal. The rationale for creating the common module is documented in the candidate -04 (https://github.com/IETF-OPSAWG-WG/l3nm/blob/master/I-D-L3NM/draft-ietf-opsawg-l3sm-l3nm-04.txt): The "ietf-vpn-common" module includes a set of identities, types, and groupings that are meant to be reused by other VPN-related YANG modules independently of the layer (e.g., Layer 2, Layer 3) and the type of the module (e.g., network model, service model) including future revisions of existing models (e.g., [RFC8299] or [RFC8466]). The approach that was followed for building this common module is to first extract nodes that are common for both L3NM and L3SM; these nodes are then filtered out against Layer 2 modules. All the common grouping are called in the L3NM module defined in this document. In order to avoid data duplication and optionally to ease passing data between layers (service layer to network layer and vice versa), early versions of the L3NM reused many of the data nodes that are defined in [RFC8299]. Nevertheless, that approach was abandoned in favor of the "ietf-vpn-common" module because that design was interpreted as if the deployment of L3NM depends on L3SM, while this is not the case. For example, a Service Provider may decide to use the L3NM to build its L3VPN services without exposing the L3SM. The candidate Common Module, which we consider can be reviewed by the WG, is available in: https://github.com/IETF-OPSAWG-WG/l3nm/blob/master/yang/IETF-04/ietf-vpn-common.yang Please, WG, look at the common yang proposal and let us know if this is the good direction and we can move forward in the direction of the ietf-vpn-common yang split. Thank you and Best Regards, Oscar -----Mensaje original----- De: Joe Clarke (jclarke) <[email protected]> Enviado el: jueves, 2 de julio de 2020 16:47 Para: Oscar González de Dios <[email protected]> CC: opsawg <[email protected]> Asunto: Re: [OPSAWG] CALL FOR ADOPTION: draft-barguil-opsawg-l2sm-l2nm > On Jul 2, 2020, at 07:23, Oscar González de Dios > <[email protected]> wrote: > > Hi Joe, > > The document draft-ietf-opsawg-l2nm has been uploaded changing only the name > and date and replacing draft-barguil-opsawg-l2sm-l2nm. Thanks, Oscar. Now that this is a WG document, please make sure you bring your GH/side meeting work to the list to get consensus and comments from the entire WG. Tom’s concern over the common module break down is valid, and the WG needs to be able to weigh in on how that is shaping up. Joe ________________________________ 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
