search

younglee-ietf / actn-cmi

IETF ACTN CMI Interface Repository
3 stars 2 forks source link

Can we allow VN model used to describe NNI connectivity between two endpoints or two PE? #3

Open sunseawq opened 5 years ago

sunseawq commented 5 years ago

In some cases, we need to use LxSM to describe SLA or service requirements on specific connectivity service, typical scenario is to describe bandwidth requirement, latency requirement on connectivity service between two sites. And then we can translate LxSM model into VN model and use VN model to describe connectivity service between any two VPN sites or any two endpoints. In addition, we can use VN model to provide lifecycle management of VN and provide service assurance and network visibility to the upper layer.

I want to see this case can be supported by VN model.

younglee-ietf commented 5 years ago

VN model is intended to be on CMI, but you'd want to use VN model to be used in MPI (which is NNI in your term). Currently VN model is used in collaboration with TE-topo Connectivity Matrix. Since VN model keeps the reference ID (via leafref) to connectivity matrix, the life cycle management can be maintained by the current VN model while making use of connectivity matrix module of TE-topology to achieve the same goal that you are describing. In case you don't want to make use of connectivity matrix for connectivity service between two sites, the VN model can be used over MPI, if you wish. I think this is an implementation issue. What do you think?