NOTE:

R5 EI Alto will be a "maintenance/ technical debt" release. It will be  shortened (3-month cycle) and focused on internal (tech) debt and defect backlogs.

All the  feature enhancements will be pushed to R6 release.

How to join CCVPN's mailing List

• You can set your subscription settings here: https://lists.onap.org/g/onap-ccvpn/editsub. You can opt to receive: all messages in individual emails, collections of messages in a digest, a daily summary, or only special notices.
• If you do not wish to belong to this group, you may unsubscribe by sending an email to: onap-ccvpn+unsubscribe@lists.onap.org
• To see and modify all of your groups, go to https://lists.onap.org
• The email address for this group is: onap-ccvpn@lists.onap.org. Because our system allows for participants to post via web or email, you can use this email to post new topics.
• But most importantly, please add this email address to your safe sender list in your email client’s contacts.

CCVPN  Upcoming Call

 Continual discussion with E2E Network slicing every week in March 

URL:  https://zoom.us/j/3122290279

Duration: 1h

Schedule:

the First Call:  Mar 6th, 2020,  10:30am Beijing Time /  Mar 5th, 2020 9:30pm EST Time

First Introduction on IETF Transport slicing proposal. (Any other proposals are also welcomed! )

the Second call: Mar 13th, 2020, 9:30 am Beijing time/ Mar 12th, 2020, 8:30 pm CST Time (change it to an hour earlier)

Continue the discussion on the IETF Model, have a basic concensus on the model. (if you have any questions, you can send it out via email in advance so that Henry can acknowledge and solicit the questions and have a more efficient discussion during the call )

the Third call: Mar 20th, 2020, 9:30 am Beijing time/ Mar 19th, 2020, 8:30 pm CST Time 

Discussion about functional impact in ONAP modules, have a basic concensus on the functional impacts.

If you’re willing to contribute this solution (code commitment in related modules and do the integration test), you can contact me and let me know after this call.

the Forth call: Mar 27th, 2020, 9:30 am Beijing time/ Mar 26th, 2020, 8:30 pm CST Time （Cancel this week ）

Optional to join.  Commitment companies are mandatory to join.

BUSINESS DRIVER

This section describes Business Drivers needs.

Executive Summary - This is the first attempt by using ONAP to realize cross carrier communication. In this use case, we provide an end to end cross operators international VPN service which includes features like cross operator, cross domain(different OTN domains) and cross layer(Layer 2 and Layer 3) by taking advantage of the strong orchestration ability of ONAP.

Business Impact - This use case meets the demands of the following aspects:

• Real-time resource update.
• OTN equipment operation and scheduling for different vendors.
• Multi-constrained end-to-end route computation.
• Multi-domain end-to-end service providing.
• Multi-domain network end-to-end survivability.
• Supply SMB companies with VPN service on demand, instantly, flexibly
• Deploy VPN service by overlay mode , untouch carrier network
• “One-click open”and “One-stop”, automatically deploy enterprise VPN service
• Self-service order for client-side CPE, self-delivery client-side CPE
• Provide various value-added service on client-side SD-CPE and cloud side

Business Markets - For  enterprise customers who want to set up VPNs among multiple sites. Specifically for Enterprise having branches overseas.

Funding/Financial Impacts -

• Large time saving and labor saving by providing automatic service scheduling and resource maintenance.
• Provide cross carrier connection. Service provisioning is not restrict within one ONAP any more.

Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider. 

Planning for Frankfurt Release

Recap for What Has Been Done

Supporting Files