A few comments on -03. Section 4.1
Overall, this section seems like it could use more grounding to this work. It is a generic example of VPN layering. What would be a nice addition is to markup points where performance monitoring would be helpful to illustrate how this work comes into play. In the YANG module, I'm curious about two things: First, why are inbound-discards a counter32 whereas outbound-discard a counter64? I think both should be 64-bit, yes? Second, the description on inbound-nunicast is different than outbound-nunicast with the latter being more descriptive. Can you do a pass to make sure these two sets of descriptions (inbound and outbond) align respective to their direction? Thanks. Joe On 2/28/22 18:06, Joe Clarke (jclarke) wrote: Ahead of IETF 113, we'd like to get working group consensus on https://datatracker.ietf.org/doc/draft-ietf-opsawg-yang-vpn-service-pm/. We are therefore conducting a two-week WG LC on this work. I have also requested reviews from Yang Docs, Ops, and Routing DIRs. Please share you comments and reviews on list. WG LC will end on March 14, 2022. Thanks. Joe _______________________________________________ OPSAWG mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/opsawg
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
