[Teas] What SLOs and SLEs should be in the Slicing Service Model?

[Adrian Farrel <[e-mail]>]

Hi,

Sorry for my audio being a mess in TEAS today.

I believe I heard the discussion between Kireeti and Reza correctly, and
there was some follow-up in the chat.

I agree that "Protection" is a realisation feature and so it qualifies as an
SLE, if at all.
But "Reliability" is clearly an SLO. Usually expressed as maximum down-time
per unit of time, or maximum lost traffic.

There was one thing that I *think* I heard. This was Reza saying that the
service YANG model was only including the SLOs and SLEs noted in the
framework. Maybe I misheard "only" because I think that might be a mistake.
The YANG model should certainly be interested in what the framework says,
but it is not a requirement that all SLOs and SLEs in the framework be in
the model if the authors find that there is no interest in implementing
them, and there should certainly be no limitation about including additional
SLOs or SLEs in the YANG model. Indeed, the SLOs and SLEs listed in the
framework are presented as examples.

Cheers,
Adrian