Re: [Teas] ACTN update

[Daniele Ceccarelli <[e-mail]>]

The entity that creates the tunnels is the MDSC. The MDSC is a functionality and it can be included into the service orchestrator or the network orchestrator.

If the service is between nodes belonging to the same domain it is obviously possible to do it directly via the domain controller or (if the operator wants to have only the Service/Network Orchestator as unique point to control the network) via the Service/Network Orchestrator that in this case would speak just with one PNC.

Regarding the layers in the slide I only considered one layer (MPLS) because the service is done at one layer. I have added a slide with a packet-otpical scenario but I think it is irrelevant wrt the service to tunnel binding.

Critiques to the slides are more than welcome but also proposals on how to improve them would be highly useful.

Daniele


From: Scharf, Michael (Nokia - DE) [mailto:[e-mail]]
Sent: venerdì 18 novembre 2016 11:57
To: Daniele Ceccarelli <[e-mail]>; Igor Bryskin <[e-mail]>; TEAS WG ([e-mail]) <[e-mail]>
Subject: RE: ACTN update

In case of L3VPNs and L2VPNs, a "service orchestrator" may not have to create tunnels (or pseudowires etc.). This can be a function of a "network orchestrator" or a "domain controller" (or however we call them(), or it can be a standalone function outside any "orchestrator".

I agree with Igor that the picture does not cover well the case of having different IP and optical controllers - simply because it only shows one layer.

Michael


From: Teas [mailto:[e-mail]] On Behalf Of Daniele Ceccarelli
Sent: Friday, November 18, 2016 12:32 AM
To: Igor Bryskin; TEAS WG ([e-mail]<mailto:[e-mail]>)
Subject: Re: [Teas] ACTN update

Hi Igor,

Some more thoughts in line in red.

Cheers
Daniele

From: Igor Bryskin [mailto:[e-mail]]
Sent: venerdì 18 novembre 2016 03:14
To: Daniele Ceccarelli <[e-mail]<mailto:[e-mail]>>; TEAS WG ([e-mail]<mailto:[e-mail]>) <[e-mail]<mailto:[e-mail]>>
Subject: RE: ACTN update

Hi Daniele,

Please, see in-line.

Igor

From: Daniele Ceccarelli [mailto:[e-mail]]
Sent: Thursday, November 17, 2016 12:29 PM
To: Igor Bryskin; TEAS WG ([e-mail]<mailto:[e-mail]>)
Subject: RE: ACTN update

Hi Igor,

I've used the L3SM example because it is the customer facing model and it is what we have on top of the MDSC and the orchestrator and, being on top of the MDSC, means that the sigle-multi/domain aspects are hidden (on top of the MDSC you don't care and you don't know if between CE1 and CE2 or between AP1 and AP2 there is one, two or N domains.

In the context of L3SM multi-domain service coordination is NOT mandatory. The L3SM can be used on top of the MDSC in case of multiple domains  and in case of single domain it can be used either on top of the MDSC or on top of the PNC, this is a deployment choice and I just used an example.

IB>> I agree with you, except that L3 service controller does not seat on top of MDSC as a direct client. The L3SM<=>MDSC relationship is indirect and much more complex. Also from your slide below it is hard to interpret that L3SM nulti0domain coordination is not mandatory (IMHO by the way it is simply not needed)
DC: I get your point. The picture seems to mandate a multi-domain coordination between the "service" boxes, which is not the case, that's correct. The message that it wants to convey are the following:

1.       Coordination between the MDSC and the Service function in the Service Orchestrator is needed (in order to be able to map a service against a tunnel or a VN). It applies to single or multi domain and it doesn't care if it is single or multiple domains

2.       The MDSC does not the service

3.       The service can be created also at Controller level (within its own domain) and it is not the PNC that is doing that.

Hence a Service function box is needed in all the boxes, but this does not mean that they coordinate among them.

[cid:image001.png@01D241C7.455BFF00]

The interaction between the overlay network (i.e. the services) and the underlay/infrastruscture (i.e. the VN, tunnels etc) is mandatory if you want to map a service against a given tunnel or set of tunnel.

IB>> It is not clear what do you mean by tunnels. Normally L3 service (e.g. L3 VPN) PEs are connected via a mesh of IP/MPLS layer  RSVP-TE tunnels and L3 service specific LSPs are nested inside them. In any case, the TE part does not go deeper than IP/MPLS layer, and said RSVP-TE tunnels are not re-configured necessarily with every addition of a new L3 service. So, direct interaction between L3 service and transport service controllers is not mandatory (especially if the two are owned by separate organizations and implemented by separate vendors).
DC: I don't disagree with that. It must be possible to do the service to tunnel binding (i.e. I want L3VPN X to use tunnel Y) or in the classic way with not such a binding (i.e. I want an L3VPN between A and B and I don't care which tunnel will be used).
The binding does not mandate to create a new tunnel for each service obviously. Existing ones can and must be reusable.

If you don't want to do so you don't need ACTN or SDN in the network and you can simply operate the network as you did yesterday, with the tunnels created by LDP and the unawareness of which service uses which tunnel...it is simply enough to kwno that a packet goes from a source to a destination and you don't care about the path, the constraints related to the service, and the capability to know which services are used by which tunnel.

IB>> The point is that L3 service SDN controller and transport service (T-SDN) controller are both needed, but the two do not have to be integrated into one solution. It should be possible for an operator to cherry pick the controllers (e.g. L3 service controller provided by JNPR and T-SDN controller provided by Huawei).
DC: again agree, what in the figure makes you think that this is not the case?

Cheers
Daniele

From: Igor Bryskin [mailto:[e-mail]]
Sent: venerdì 18 novembre 2016 01:08
To: Daniele Ceccarelli <[e-mail]<mailto:[e-mail]>>; TEAS WG ([e-mail]<mailto:[e-mail]>) <[e-mail]<mailto:[e-mail]>>
Subject: RE: ACTN update

Danielle,

Why in your opinion L3SM should know or care whether the provider looks after a single- or multi-domain network? There is a strong case for multi-vendor multi-domain transport network, but this is not necessarily true for a network providing L3 services, which (in contrast to, say.  L0/L1 transport network) could be a multi-vendor single domain network. In other words, why in the context of L3SM multi-domain service coordination is necessary?
Another question: when and how L3 service controller interacts with a transport controller (providing transport services)?

These clarifications I think would be useful.

Cheers,
Igor

From: Teas [mailto:[e-mail]] On Behalf Of Daniele Ceccarelli
Sent: Wednesday, November 16, 2016 9:32 PM
To: TEAS WG ([e-mail]<mailto:[e-mail]>)
Subject: [Teas] ACTN update

Dear WG and ACTNers,

Please find attached some slides trying to clarify terminology, roles and functionalities in ACTN (in line with the discussion we had at the mic during the TEAS session). It provides an architectural explanation and a possible workflow description trying to see if it fits with the architecture.

My proposal is to:

1.       Add a section in the framework document to explain the relationship and the split of roles between PNC, MDSC and existing components like orchestrator and domain controller.

2.       Add a section to the "Applicability of YANG models for ACTN" to explain how this impacts the definition of the MPI and what is missing (i.e. TE-Service model). This will have impacts also on the PCEP applicability.

3.    Write a new document defining service mapping model that provides mappings across LxSM and TE-service model and that can be extend to support different service models (L3VPN/L2VPN/L1VPN, VTS, Transport Connectivity service, etc). Dhruv, Young and I are already working on this.


Opinions? Thoughts?

BR
Daniele