2020-03-06

Attendees

@LIN MENG (CMCC)

@Henry Yu (Huawei)

@Dave Allabaugh (Fujitsu)

@Chuanyu Chen (Huawei)

@Former user (Deleted)  (Fujitsu)

@Hesam Rahimi (Fujitsu)

 

@Raghavan Subramanian  (Fujitsu)

@Rishi (Verizon)

@Seshu Kumar Mudiganti (Huawei)

@Shankaranarayanan Puzhavakath Narayanan (AT&T)

@Swaminathan Seetharaman (Wipro)

@Takuya Miyashita (Fujitsu)

Agenda

  1. Lin Introduce the background of this joint call

  2. Attendee  self introduction

  3. Henry present the tranport slicing proposal

Notes and Actions

1, Current design is based on IETF transport slicing model. Also, it is aligned with ETSI ZSM003 network slicing solution.
MEF didn't touch the implementation model, they are focusing on customer facing model or the subsriber type model.

2, Transport have several segments,the model is an abstraction of one segment: the front haul, the mid haul,the end haul, but it can be used to describe any above segment. In other words, the "transport slicing network"described in the infomration model, is actually a mutiple instances belonging to a single "transport slice connectivity".

3, To fully implement ONAP as an NSSMF, the unified northbound interface should be provided in EXT-API.

4. weekly separate discussion about  transport slicing in March, in April to discuss on E2E network slicing weekly call. Change the time one hour earlier.

NO.

Action

Responsible

Status

NO.

Action

Responsible

Status

20200305_1

Set the separate discussion like this in March (the next three weeks), In April start discussion in E2E Network Slicing weekly call.  Change the time one hour earlier.

Lin Meng

(to send out the invitation)

open

20200305_2

Henry to solicit the inputs, continue the discussion in next week

Henry

open

 

 

 

 

Recording