Re: [Teas] FW: The word "transport"

[Adrian Farrel <[e-mail]>]

> I don’t understand “we (IETF) do not deal with network slice”.

 

Please refer to Figure 4 of the draft.

In summary, an E2E network slice is the logical network from End user X to End use Y and comprises of:

*	One or more Transport slices (TS)
*	One or more Other Slices (OS)

 

Well yes. I can read the drafts. That’s why I don’t understand your comment that the IETF does not deal with network slice.

 

Referring  this Figure, it is clear that IETF deals with Transport slice which is part of an E2E network slice and “Other slices” are outside scope of IETF.

 

You mean that you are saying that the scope of the IETF is limited to a subset of network slices that you call transport slices. But that is to say that the IETF works on some network slices, so I think we’re clear that the IETF does deal with network slices.

 

Please make a clear distinction between Transport Slices and e2e network slices. They are different.

 

I have read the 3GPP work. Yes, they are different. Although, I think it is a terrible shame to limit ourselves to this use case. Slicing is an abstract function and we should be able to use it to support many different types of service. And I think it is important that it should be a recursive concept. So, when a transport slice is enabled by slicing a lower layer network, you (presumably) call the slice of the lower layer network a transport slice, and the transport slice that is enabled by the transport slice is called a transport slice. Not confusing at all 😊

 

IMHO, any reference to “Network Slice” in IETF drafts means “Transport slice” . 

 

Wow, well, maybe you need to check that with the authors of those drafts and (of course) set it in the context of the definition of “transport”.

 

>  Why do we have a “TEAS Network Slicing Design Team”?

Good question. The correct name can be “TEAS Transport Slicing Design Team”

 

Well, here I am going to be a little snarky, I fear.

No!

The name of the DT and it’s charter were clearly set out. It is what it is, and it’s work scope is clear. 

 

Enjoy,

Adrian