Hi all, I have read rev-05 of the draft and I think this document is ready to progress. The draft defines a flexible service assurance architecture and provides some concrete examples to illustrate how to use it.
Just a few suggestions to improve readability: 1 The definition of 'service' seems not clear to me, e.g. Introduction refers the service module definition in RFC 8199, but Section 3.7<https://datatracker.ietf.org/doc/html/draft-ietf-opsawg-service-assurance-architecture#section-3.7>. Flexible Functional Architecture says the definition of service is very generic, and this is true that in the example the IS-IS, device and interface could also be service. I noticed Med also raised some questions on this. I hope this has been solved. 2 'metric engine' is defined in Terminology. It is not clear to me where is this function belonged to, is it part of SAIN agent? Thanks, Bo From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Tianran Zhou Sent: Wednesday, June 8, 2022 6:00 PM To: opsawg@ietf.org Subject: [OPSAWG] WGLC for draft-ietf-opsawg-service-assurance-architecture-03 Hi WG, This mail we start a two weeks working group last call for draft-ietf-opsawg-service-assurance-architecture-03. https://datatracker.ietf.org/doc/draft-ietf-opsawg-service-assurance-architecture/ Please send over your comments before June 22. Please also indicate if you think this document is ready to progress. Cheers, Tianran, on behalf of chairs
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
