Re: [OPSAWG] CALL FOR ADOPTION: draft-bgbw-opsawg-vpn-common

["Chang Liu(联通集团中国联通研究院-本部)" <[e-mail]>]

Hi All,

I support adoption, and I think the common module is useful.

Best Regrads

________________________________
Liu Chang
China Unicom
Email: [e-mail]<mailto:[e-mail]>
Phone: [phone]
Tel: [phone]



---Original---
De: OPSAWG <[e-mail]> en nombre de Joe Clarke (jclarke) <jclarke=[e-mail]>
Enviado: jueves, 13 de agosto de 2020 7:49
Para: opsawg <[e-mail]>
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

如果您错误接收了该邮件，请通过电子邮件立即通知我们。请回复邮件到 [e-mail]，即可以退订此邮件。我们将立即将您的信息从我们的发送目录中删除。 If you have received this email in error please notify us immediately by e-mail. Please reply to [e-mail] ,you can unsubscribe from this mail. We will immediately remove your information from send catalogue of our.