Dear Adrian, Qin, Will and OPSAWG, First of all. I enjoyed reading RFC 8309. It is very helpful in context with RFC8199 and RFC 3444 to distinguish between "Customer Service Model" and "Service Delivery Model. The explanations make perfectly sense to me.
I have read the term "Service Delivery Model" in https://datatracker.ietf.org/doc/html/rfc8309#section-2 and understood its relations in Figure 3 in https://datatracker.ietf.org/doc/html/rfc8309#section-4 to BSS/OSS and its examples in https://datatracker.ietf.org/doc/html/rfc8309#section-6.2. I came to the conclusion that network assurance, monitoring and observability are not covered in the term "Service Delivery Model". It focuses solely on the fulfillment of the Network Service configuration if I am not mistaken and does not take closed loop operation into consideration. Within Network Service Models, there might be other categories such as "Network and VPN Service PM Models" as in Figure 1 in https://datatracker.ietf.org/doc/html/rfc9375#section-3. Taking figure 4 in https://datatracker.ietf.org/doc/html/draft-ietf-nmop-terminology-16#section-4, deriving the relevant state with its symptoms, how would you characterize the following YANG modules: https://datatracker.ietf.org/doc/html/draft-ietf-nmop-network-anomaly-lifecycle https://datatracker.ietf.org/doc/html/draft-ietf-nmop-network-anomaly-semantics https://datatracker.ietf.org/doc/html/rfc9418 My conclusion is that it is definitely in the category "Network Service Models", probably similar to RFC 9375, defining its own subcategory such as assurance or anomaly detection. Looking at https://datatracker.ietf.org/doc/html/draft-ietf-nmop-network-incident-yang, I would categorize it in "Customer Service Model". Probably in a sub category incident management. Does that make sense? Continue my search on easter eggs... Best wishes Thomas
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
