Ok!
We put the decission of creating the module with the types on hold. Looking
forward for more feedback on the issue.
Oscar
De: Joe Clarke (jclarke) <[email protected]>
Enviado el: jueves, 21 de mayo de 2020 16:44
Para: Oscar González de Dios <[email protected]>
CC: opsawg <[email protected]>
Asunto: Re: [OPSAWG] Minutes of L3NM/L2NM module discussions
2. L3NM
Revision of the three main issues:
Implementation Report by Cisco. It has two main issues
(https://github.com/IETF-OPSAWG-WG/l3nm/issues/110)
- Common module to have all the L3NM specific requirements. Type-like module.
[Anton]: It makes implementation simpler. Does not generate unnecessary
dependencies
[Adrian]: It depends on if we need module for specific types, to avoid
unnecessary imports. Also don't you only need to import types, not the entire
module?
[Qin]: With L3SM we did not take an augmentation approach. If there are common
types defined in both models, then we may need to find the common components.
We should decouple of L3SM.
[Sriram]: Prefer to have a separate type-file for the specific parameters.
[Oscar]: Define a common type-file for the service models.
[Qin]: Is it possible to manage it as an independent draft?
[Oscar in github issues]: After the discussions, it seems reasonable to have a
separate Yang module to contain the types. The suggestion is to write the
module to cover the four service models (client service models, l3sm, l2sm and
Network service models, l2nm, l3nm). It seems reasonable to include this module
in l3nm draft instead of creating a new one to avoid dependencies.
Samier, Dan and Anton to collaborate for a first version of the split
As chair, I want to call this out since it sounds like the authors made a
decision here, and I want to make sure the whole WG has a chance to weigh in..
In reading these minutes and issue #110, I can see the value of a types module
to avoid what may be confusing imports, but I want to know if anyone on the WG
has a different opinion.
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
