Harmonizing with draft-ietf-teas-applicability-actn-slicing

[aguoietf]

draft-ietf-teas-applicability-actn-slicing currently defines the mapping between IETF NSC and ACTN as:

          +--------------------------------------+   |    +-----+
          |    Consumer orchestration system     | =====> | CNC |
          +--------------------------------------+   |    +-----+
                            ^                                ^
                            | NSC NBI                |       | CMI
                            v                                v
          +-------------------------------------+    |    +------+
          | IETF Network Slice Controller (NSC) |  =====> | MDSC |
          +-------------------------------------+    |    +------+
                            ^                                ^
                            | NSC SBI                |       | MPI
                            v                                v
          +-------------------------------------+    |    +-----+
          |         Network Controller          |  =====> | PNC |
          +-------------------------------------+    |    +-----+
     Figure 1: Mapping Between IETF Network Slice and ACTN Components

According to the discussion, this mapping may need to be updated to reflect the fact that,

• There is a difference in understanding what a "customer" is between IETF NSC and ACTN CNC
• MDSC contains service related functions and network related functions which can be split/combined on different systems. Action item is to work out a revised mapping between IETF-NSC and MDSC.

OTN-SC NBI is another service function of the MDSC(-H) interface

[aguoietf]

Add text to the ACTN applicability document to reflect the use case for OTN slicing.

[aguoietf]

Text update is depending on the update draft-ietf-teas-applicability-actn-slicing. May be postponed to after IETF 113.

[italobusi]

@danielkinguk , @dancecca , @sergiobelotti and me have had a call to review the figures in draft-ietf-teas-applicability-actn-slicing

These are the proposed new figures:

actn-slicing-figures-01.txt

[sergiobelotti]

About this issue we are locked until we do not receive any answers from TEAS as required in https://mailarchive.ietf.org/arch/msg/teas/s2xFbLfeUs2vD6ka3eMKjDEn8kI/ The last feedback is coming from Daniele Ceccarelli, replying to Daniel King mail on August 29: "Hi Dan,

I think it is needed, but is this the right document to do so? I mean, I still believe this new xMI is needed to "fix" the leftovers of the CMI or better to complement it when the consumer is not the paying customer but any other application/department of the operator. However, I'm not sure this is related to slicing and an applicability to network slicing is the document I would look for if searching for the definition of such interface.

What other document would be the right place? Maybe a standalone document called "ACTN xMI interface" ?

Cheers Daniele " Personally, I would agree on Daniele's suggestion.

[aguoietf]

CCAMP mailing list discussion Hi All (copying in draft-ietf-ccamp-yang-otn-slicing Authors too),

I think have reached a conclusion after talking to various authors from both yang-otn-slicing and applicability-actn-slicing, along with the comments from Sergio and Danielle, below.

We will close the draft-ietf-teas-applicability-actn-slicing in its current form and continue the discussion on the xMI requirement in the yang-otn-slicing I-Ds which will then allow us to create an entirely new ACTN xMI interface I-D.

If you have any further thoughts or comments, please let me know. Otherwise, I think my actions are:

• Propose actn xmi requiment text and figure for yang-otn-slicing I-D
• Propose actn xmi interface I-D

I will set up a conference call to review the text contribution and new I-D.

BR, Dan.