Performance monitoring for IP domains

[italobusi]

I think the scope of the draft will be both performance monitoring for IP and OP domains. In my opinion we shouldn't restrict to Optical only.

_Originally posted by @jbouqui153 in https://github.com/italobusi/draft-poidt-teas-actn-poi-assurance/pull/2#discussion_r1132439486_

[italobusi]

2023-05-23 ACTN POI Call

Jeff: our preference is that even for multi-layer services, the MDSC can be able to do performance monitoring of L2/L3 VPN services throught the O-PNC and P-PNC so it would be good if the draft can describe which mechanisms can be used to report this information to the MDSC from the P-PNC

We may need input from packet experts to address this analysis

• [ ] @jbouqui153 review the ToC of the I-D and propose new sections to address this issue

[jbouqui153]

I think for assurance we need to cover an E2E L2/L3VPN service with a given SLA (Bandwidth, packet loss, latency etc.) which is decomposed then into two segments: (L2/L3VPN segment1, SLA1) managed by P-PNC1 and (L2/L3VPN segment2, SLA2) managed by P-PNC2. MDSC is responsible for the E2E L2/L3VPN service PM monitoring considering also the inter-domain links which are under its scope but not directly seen by each P-PNC. So MDSC should support TCA settings for (L2/L3VPN segment1, SLA1) towards P-PNC1 and for (L2/L3VPN segment2, SLA2) towards P-PNC2. P-PNC1 and P-PNC2 only report to MDSC when either SLA1 in domain 1 or SLA2 in domain 2 cannot be fulfilled anymore (e.g. after a network failure ni domain 1 the rerouting that happened in the IP network doesn't meet the latency constraint part of SLA1). We need also to have the possibility for troubleshooting to set OAM service management (creation/deletion of MEPs, MIPs, MEG) through P-PNCs so that they can report, through RESTCONF/YANG the key OAM values between the end points configured (e.g. packet loss, jitter, delay). If we assume two separated optical domains as in draft POI then it is not applicable for optical but if we consider interconnected optical domain with multi-domain OTN services, then we should have same Performance management at MDSC level as for IP described above. Support as well of TCAs when provisioning each segment with its respective SLA in each optical domain, support of OAM management with TCMs in each segment from MDSC through the O-PNCs with capabilities from the O-PNCs to then report the service OAM KPIs back to MDSC who is in charge of the end-to-end OTN service. We need to discuss how to address these points in the ToC. All the TCA settings and OAM management between MDSC and P-PNCs/O-PNCs would need to be investigated. For IP there is a YANG model "draft-ietf-opsawg-yang-vpn-service-pm" (RFC9375) but its applicability seems more focused on single domain. To be further investigated and discussed.

[italobusi]

2023-07-04 ACTN POI Call

Need further discussion to understand what is in the scope of the POI assurance document and what is out of scope