PACE Workshop on New Uses of PCE Key Points Arising

1. PACE Workshop on New Uses of PCEKey Points Arising Notes from the PACE Workshop Vilanova i La Geltú 16 June 2014

2. Guang-Jie RenSmarter Cities and Open DataImplications for Path Computation Element • Clearly measurable results for the over-arching technology • Common threads running through all applications • Many data collection points (including crowd-source and automated) • Lots of data (real-time, historical, open) • 40 zaetabytes by 2020 • 2.5 quintillion bytes per day • Processing data offline or in applications (real-time analysis) • Access to data through APIs • Implications for PCE resulting from big data • Four Vs (volume, velocity, variety, veracity) • Security is a big issue • Social and sensor data quality becomes a networking problem at a non-physical (“social” level)

3. MohitChamaniaExperience with Use of PCE • Requirements • Low latency and processing overhead in devices • High scaling and security in NMS • Integration with multiple applications (e.g. SDN) • Different “standards” for TED representation • Flat network • Virtualization • Different views of the same TED • What information is in a TED? • Is a protocol interface of highest value • Is there a benefit in an API of some sort? • Security is complex to implement for application-based PCCs • Algorithms need to be pluggable

4. Oscar González de DiosIDEALIST--“Industry-Driven Elastic and Adaptive Lambda Infrastructure for Service and Transport Networks” • It’s an “SDN-like approach” to managing elastic optical networks • Application-based network operation • Not limited to specific device management • Challenges and Objectives • Optimise cost and power consumption • Innovate in data plane and control plane

5. RicardVilaltaSTRAUSS--“Scalable and efficient orchestration of Ethernet services using software-defined and flexible optical networks” • The development of efficient transport infrastructures for Ethernet services • Defining a “Common Orchestration Protocol” • This is a service request interface/protocol • The project is limited to Ethernet transport services

6. Giacomo BerniniLIGHTNESS--“Low latency and high throughput dynamic network infrastructures for high performance datacentre interconnects” • Addresses the scaling challenges of rapid growth in data centres • Hierarchical architecture • Focus on client-server interactions • Has a “Northbound API for custom DC applications” • Inter-DC scenario • Develop from intra-DC work • H-PCE • One child per DC • One child for inter-DC network • Maybe grandchildren for inter-DC networks

7. Adrian FarrelFuture Uses for PCEP • PCEP has already grown beyond its original intention • But PCEP was designed for extensibility • Already extended for many new scenarios • Already extended for stateful and active PCE • Where will we stop? • What things can we not use PCEP for? • Or will we roll back the function • Move some or all PCEP function into RESTconf?

8. Francesco PaolucciPCE - OAM Handler in ABNO: a use case of code adaptation in flex-grid networks • Working within the ABNO architecture • How to notify LSP degradation to ABNO • Who is the consumer? • PCE? • OAM Handler? • Is it an alarm? • Current prototype is using PCEP Notify messages • What information does PCE need? • Is it a modification to the TED? • Is it a report on an existing LSP? • Is it a request for a specific reoptimization?

9. RicardVilaltaThe role of PCE in Optical Network Virtualization • There will be many challenges in optical networks • Vendor proprietary islands is one of the biggest • PCE solves many of these issues • Virtual Optical Network is a ay to abstract the physical infrastructure and vendor-specifics • How to make network requests and how to manage the VON • PCEP does not seem like the right tool • Proposal is the “Resource Broker” • (Looks a lot like ABNO ;-) • PCE is a component • PCE as a virtualised function • Makes PCE a scalable cloud function

10. W.RamírezPCE position in IoT • A context-aware PCE • Demise of host-oriented communication models • Consider cloud • Connectivity is to a “thing” not to a location • Use service instance identifiers not IP addresses • A hierarchy of path computation based on Locator/identifier split to reach “cloud site” • Connectivity to a service (the interest/thing) from a host that may be moving

11. O. González de DiosPCE, the magic component of segment routing • Segment routing • Remove protocols from the network • Less complexity in operation • Less state in the routers • There is still a need for path computation • TE and load balancing • Use a PCE to compute and plan • PCE operations are remarkably similar to existing PCEP • Instantiation is “placing an identified label stack at an ingress node” • Classifying packets to

12. G. BerniniTopic: Inter-domain transport SDN with PCE • It’s SDN for a Transport Network • It needs to paths to be computed • PCE QED • There are service requests and there is network management and there is provisioning • ABNO QED • Inter-domain just adds some complexity • H-PCE QED

13. Summary of Questions • Where is PCE going? • “Poly-computation engine” • An engine that answers question on big data • Retain the “path” concept • Move out of pure computer networking problems • Compute connections and paths between things • How physical meets digital? • Security • For what environments and applications is security important? • Why are existing security mechanisms important? • Data models and representations • What is the “standard” TED representation? • What is a TED? • Can the question be partitioned into separate information sets? • Just one TED? • Different views of the TED in one PCE • Multiple PCEs in the same network use “the same TED”? • Who takes care of data modelling and algorithms in new problems space? • How to make an open API to a PCE? • Where does this fit with PCEP, REST, etc.? • How do you visualise the computed path? • What additional information is needed to make this question meaningful? • How do you request a service? • What is a “service”? • Is that a PCE question or an ABNO question? • Where do you draw the line in uses of PCEP • Should PCEP be extended for additional functions? • Should PCEP functions be moved to another protocol? • How do you dynamically deploy PCEs • Load-balancing • Discovery and advertisement • TED availability