Dear OPSAWG, The notes of the last desing meeting:
LXNM Desing Team Meeting ________________________________ <https://codimd.ietf.org/#Date>Date: 08-04-2021 <https://codimd.ietf.org/#Assistants>Assistants * Roque Gagliano * Raul Arco * Mohamed Boucadair * Luis Angel Muñoz * Victor Lopez * Oscar Gonzalez de dios * Samier Barrguil <https://codimd.ietf.org/#Agenda>Agenda * Review the implementation section. * Review of the open issues. <https://codimd.ietf.org/#Discussion>Discussion * Roque ask about the possibility to add cisco as part of the implementation section in the L3NM and the L2NM. * In this moment the draft has pointers to the implementation<https://github.com/IETF-OPSAWG-WG/lxnm/tree/master/Implementattion> support of each vendor. * VPN common has been submited this morning. * Review the comments done by Druvh in the issue<https://github.com/IETF-OPSAWG-WG/lxnm/issues/263> <https://codimd.ietf.org/#Action-Points>Action Points * Check the status of the implementation sections. @Oscar * Check the new issues and It’s solutions opened by Roque. @Med and @Samier * Check the status of the document for the last-call review. @all 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: SAMIER BARGUIL GIRALDO Enviado: jueves, 25 de marzo de 2021 19:57 Para: opsawg@ietf.org <opsawg@ietf.org> Cc: Oscar González de Dios <oscar.gonzalezded...@telefonica.com> Asunto: LxNM Desing Team -- Minutes LXNM Desing Team Meeting Date: 25-03-2021 <https://codimd.ietf.org/#Assistants0>Assistants * Bo Wu * Qin Wu * Luis Muñoz * Raul Arco * Oscar Gonzalez de dios * Samier Barrguil <https://codimd.ietf.org/#Agenda0>Agenda * Review of the open issues owned and opened by Qin Wu. * Review the ESI issue <https://codimd.ietf.org/#Discussion0>Discussion * Issue 201<https://github.com/IETF-OPSAWG-WG/lxnm/issues/224>. Fast re-route i the L2NM. * There are two scenarios sing and dual homing. * Both requires the configuration of FRR in the PEs. * Enable FRR for MAC routes between the local and remote end. * Option #1: In both cases the global configuration of FRR applies. * Option #2: Configure the FRR as part of the Far-End Configuration. * How it is done today at device level Cisco: By default, no backup next hop address is set for FRR. Huawei: Sample configuration delivered by Qin. Huawei: EVPN VPWS configuration Example（Interface+EVPL instance+EVPN instance） Nokia: Raul is going to check if this is something supported in Nokia at service level or control plane. <https://codimd.ietf.org/#Action-Points>Action Points * Add samples on the text how the Single Active and Active/Active scenarios are covered by the model. @RaulArco * Move the Ethernet Segment Identifier at VPN Network Access level. @Samier * Add new issues to the GitHub based on expert review @Qin Wu<mailto:bill...@huawei.com> 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 ________________________________ 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
