Dear OPSAWG colleagues,

                Let me remind that, after the IETF week, we retake the regular 
LxNM calls were we discuss the progress of the VPN network models. In case you 
don't have the invitation link, the opsawg invitation was sent out to the list, 
so it should be easy to find (if not , just ask our WG chairs).

                Also, let me remind that there is a single git repository for 
all the models https://github.com/IETF-OPSAWG-WG/l3nm When adding an issue you 
can tag it L2NM, L3NM and common.

In the agenda for tomorrow we have:


1)      L3NM

·         Issue #224: Proposal to extend the scope of the profiles. In the IETF 
published version, the Import/Export profiles are reusable. With the proposed 
scope, other fields can be reused too. Then, for VPN deployments that have do 
reuse a lot of fields, it avoids having to repeat many times the options. There 
is a proposal to cover the issue in 
https://github.com/IETF-OPSAWG-WG/l3nm/commit/1e711eac8c3ecfd9f9d45caa0e9dad4da8413536
 with a vpn-instance-profile.



2)      L2NM:



·         Review Issue #219 L2NM: multihoming: need fields for ESI, LACP System 
ID and LACP Administrative-key value

·         Review Issue #210  add EVPN variants from RFC 7432 to L2NM L2NM

·         Review Issue #207 Routing Directorate Review (L2NM) L2NM

·         Review Issue #205 EVPN support in L2NM: Diffserv Model type L2NM

·         Review Issue #204 EVPN support in L2NM: EVPN Flavors L2NM

·         Review Issue #203 EVPN Support in L2NM: Bridge Domain ID definition 
L2NM

·         Review issue #202 EVPN Support in L2NM: Split Horizon L2NM

·         Review issue #201 EVPN Suppport in L2NM: IP FRR L2NM


We would like to invite key authors from draft-www-opsawg-yang-vpn-service-pm 
to join the calls. The issues with vpn-service-pm could be dealt together.

Please feel free to request more items in the agenda and suggestions to the 
documents/models.

                Oscar


________________________________

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

Reply via email to