[Teas] Slice as a Service : Response of IETF Network slice coauthors to TEAS mailing list

[Adrian Farrel <[e-mail]>]

Thanks to the pen-holders for trying to progress this discussion.

 

I wonder whether we should separate the discussions into separate threads? As we discuss the different points it’ll get messy unless we do that.

 

I’ve changed the subject line for the issue I want to call out.

 

> IETF network slice as a Service

> The co-authors agree with the mailing list suggestion to treat the IETF network 

> slice as  a service. 

> In summary, an IETF Network Slice Service contains multiple endpoints (see

> discussion below for endpoint), multiple connections and multiple SLOs. 

> This is aligned with the mailing list. In consequence we propose to add

> “Service” to the text  in the draft defining what an IETF network slice is.

 

I don’t think this is an either/or. I think we have “a slice as perceived by the consumer/customer” and “a slice as operated by the operator of the underlay network”. This is very similar to how VPNs are discussed.

 

So, yes, lets have a description of a “network slice service”. But I think we have to start with a general description of a “network slice”. The former is how the consumer/customer perceives the slice. The latter is what is really going on: the resources and capabilities of the operator’s network are being selectively partitioned to provide the service.

 

Cheers,

Adrian