Subject: [Actn] ACTN BoF summary and meeting minutes

From: Leeyoung <[email-masked]>
Date: Mon, 4 Aug 2014 17:27:57 +0000

Dear All,

Attached please find a draft ACTN BoF meeting minutes. We thank Andy Malis for taking the minutes. Please feel free to comment on that. Below is an executive summary for those who do not have time to read the minutes. This information will also be upload to ACTN wiki: https://sites.google.com/site/actnbof/.

Thanks for your interest in ACTN work and we look forward to see more discussion on the mailing list.

Best regards,
Dan & Young

------------------------------------------------------------------------------------------------------------

Abstraction and Control of Transport Networks (ACTN) Summary
THURSDAY, July 24, 2014

1. Introduction

-          Good attendance (over 110 signed) http://goo.gl/NKmRfw and support for network operators both who presented (KDDI, Microsoft, KT, Telefonica, China Mobile & SKT) and those who participated at the mic (British Telecom and Deutsch Telecom).

-          Session intended as a non-WG forming BoF

-          Opportunity to hear operators' pain points in operating dynamic connectivity in current multi-domain transport networks

-          Discuss if there is enough interest and agreement to pursue further.

2. Use Cases from Operators

-          Multi-Tenant Virtual Network Operation
http://tools.ietf.org/html/draft-kumaki-actn-multitenant-vno

-          Data Center Operator: Multi-domain Data Center Interconnect

https://datatracker.ietf.org/doc/draft-fang-actn-multidomain-dci/

-          Transport Network Operators: On-demand E2E Connectivity Services in Multiple Vendor Domain Transport Networks/Virtual Network Operation for Multiple Domain in a Single Operator Network

https://datatracker.ietf.org/doc/draft-klee-actn-connectivity-multi-vendor-domains/

https://datatracker.ietf.org/doc/draft-lopez-actn-vno-multidomains/

-          Mobile Network Operators: Mobile Backhaul Packet Transport Networks/Mobile Virtual Network Operation for Multiple Domains in a Single Operator Network

https://datatracker.ietf.org/doc/draft-cheng-actn-ptn-requirements/

https://datatracker.ietf.org/doc/draft-shin-actn-mvno-multi-domain/

-          ACTN is multi-dimensional problem: administrative domain, switching technology and time (to-deploy or resize or reconfigure topologies of existing services).

-          Operator use case objectives include requirements for more efficient use of transport network resources, fast deployment of new services, and control of the core transport network by the service network operator (network programmability), virtualization of network resources for centralized control and packet-optical integration for multi-layer integration.

-          Observation that the control plane should be simpler, and if we expend more time on the control plane, we create more complexity. Data Plane interoperability is out of scope.

3. Research Use Case

-          Towards Ultimate Convergence of All Networks (TOUCAN)

-          TOUCAN - UK EPSRC Project<http://www.ietf.org/proceedings/90/slides/slides-90-actn-5.ppt>

4. Open Discussion

-          Open discussion reiterated the operator requirements for greater control of network interconnectivity (between administrative and technology domains), abstraction of underlay resources and ability to slice and present resources.

-          Suggestion that other SDOs have also researched aspects of the problem space, including ITU-T (Y.1311, Y.1312, and Y.1313), ONF (Architecture group), and TMF (network modeling).

-          Requirement to clarify differences between inter-technology, inter-region, and inter-domain, suggestion to do this on the list.

-          Vendor suggestion that protocol work exists, and would need to be clearly identified. PCE also suggested a technology solution, as part of larger platform towards solving ACTN use cases.

-          Proposed that a common abstraction model would help with simplifying network operations and providing network abstraction.

-          Highlighted that abstraction (data plane) is hard to model due to the breadth and complexity of transport technologies.

-          Investigation of existing work (including YANG) would be required.

5. Summary and Next Steps

-          AD highlighted the common threads, and agreement that solving ACTN will require interoperable technologies, however it would be extremely premature to be talking about solutions.

-          Agreement that the next steps should include further polishing of the use cases and drawing out common requirements, development of a problem statement and a clear scope and architecture document would also facilitate discussion.

-          AD polled the room to see who would be willing to write text to scope the problem and frame solutions, approximately 20 people put their hands up.

-          Request by the AD and Chairs for people to participate on the list, and contribute both the use cases and additional documents.

6. Links to session slides

-          Administrivia, Agenda Bashing, Introduction<http://www.ietf.org/proceedings/90/slides/slides-90-actn-0.pptx>

-          Multi-Tenant VNO Use Case<http://www.ietf.org/proceedings/90/slides/slides-90-actn-1.pptx>

-          Multi-domain Data Center Interconnect Use Case<http://www.ietf.org/proceedings/90/slides/slides-90-actn-2.pptx>

-          On-demand E2E Connectivity/Virtual Network Operation in Multiple Vendor Domains Use Case<http://www.ietf.org/proceedings/90/slides/slides-90-actn-3.pptx>

-          Mobile Operator Packet Transport Network/Mobile Virtual Network Operation Use Case<http://www.ietf.org/proceedings/90/slides/slides-90-actn-4.pptx>

-          TOUCAN - UK EPSRC Project<http://www.ietf.org/proceedings/90/slides/slides-90-actn-5.ppt>