OIF Interoperability Demonstration show that Transport SDN is becoming real. ONF T-API Specification is published, implemented and tested. Next is T-API 2.0
Nathan Tracy, OIF Technical Committee Chair and TE Connectivity was invited to speak at ECOC's Market Focus on OIF Interoperability – The Key to Unlocking the Benefits of SDN
OIF - The Path to Open, Interoperable Optical Networking "Interoperability Te...Leah Wilkinson
The document summarizes an interoperability testing event for SDN Transport APIs. Participants from OIF, ONF, and MEF tested implementations of transport APIs across multiple vendors. Key findings included the need for further alignment of APIs with standards, support for additional use cases, and performance improvements. The document also discussed plans for an OIF T-API certification program to facilitate long-term interoperability testing.
Transport SDN & NFV - What does it mean for Optical Networking?Deborah Porchivina
The document discusses transport SDN and NFV and their implications for optical networking. It summarizes the goals of the Optical Internetworking Forum (OIF) which include accelerating adoption of new technologies through standards development. The key points discussed are:
- Transport network virtualization allows dynamic allocation of network resources and logical centralization of control.
- The OIF is developing a transport SDN toolkit to enable transport SDN deployment for both greenfield and brownfield networks. This includes APIs, services, and architecture.
- Interoperable common APIs are needed, and work is ongoing to define standard information models and verify API functionality through prototypes and demonstrations.
The Path to Open, Interoperable Optical NetworkingLeah Wilkinson
OFC 2019 Session:
The goal of SDN is to enable flexible, automated and programmable networks that reduce Opex and accelerate service delivery. Realizing open, interoperable multi-vendor optical networking is one key to achieving this goal. A panel of industry experts will discuss the drivers, needs, and challenges in the evolution to widescale adoption of open, interoperable optical networks:
- Definition and specific requirements
- Risks, trade-offs and benefits
- Disaggregation, open line systems, and APIs
- Use cases, interop testing, trials and deployment scenarios
- Implementation agreements, interoperability demonstrations and certification testing
Moderator: Dave Brown, Director of Communications, OIF, Product Marketing Senior Manager, Optical Networking, Nokia, USA
Speakers
Victor López , Technology Expert at Systems and Network Global Direction, Telefónica gCTIO, Spain
Lyndon Ong, Market Awareness & Education Committee Co-chair - Networking, OIF and Ciena, USA
Jonathan Sadler, Network Interoperability Working Group Chair OIF and Infinera, USA
OIF presentation at 21st European Conference on Networks and Optical Communications (NOC). Service Providers want programmable network control, Lower costs, New Services, Differentiation. SDN APIs in a Component Architecture
enable programmability. Components may be added in parallel, upgraded. Rich APIs required - Connection Management, Path Computation, Topology.
Jonathan Sadler, of Coriant and Vice Chair OIF Technical Committee spoke at
Globecom 2015 on the OIF's 2014 Global Transport SDN Demonstration results.
Introducing Application Engineered Routing Powered by Segment RoutingCisco Service Provider
Application-Engineered Routing
Application programs the Segment Routing network to deliver end-to-end per-flow policy from DC through WAN to end-user
Adding value at your own pace
– Leveraging the existing MPLS dataplane without any change. SW upgrade only.
– Simplification, Automated 50msec FRR, per-domain and then end-to-end policies
Economic gains
– Improved service richness and velocity
– Optimized CAPEX and OPEX thanks to the simplicity of the SR architecture
Segment Routing deployments in CY15 in all the markets – WEB, SP, Entreprise
Strong partnership with lead operator group Commitment to standardization and multi-vendor support

The document discusses the transition to a new "All-IT Network" architecture for 5G networks based on principles of open source software and hardware, virtualization, and network softwarization. Key aspects of this new architecture include software-defined infrastructure, network functions virtualization, network slicing, open interfaces, and moving from a CAPEX to OPEX business model. The architecture aims to make networks more scalable, automated, lean, and optimized through composable, open solutions like SK Telecom's ATSCALE and COSMOS platforms.
Vishnu Shukla of Verizon USA and the OIF Carrier Working Group Chair spoke at Globecom 2015 about the Verizon perspective towards SDN and how the OIF was working to support carrier needs to improve transport control through SDN.
Disaggregated Networking - The Drivers, the Software & The High AvailabilityOpen Networking Summit
Dis-agregration is real… This trend started with SDN and the separation of Data plane and Control plane. The scope has expanded to include separate of hardware and software and created a whole new industry of white boxes, general purpose X86 commodity hardware. All three markets - Cloud, Enterprise and Carriers are now engaged in various solutions inside the Data Center. The disaggregation is impacted all parts of the network including Access and Edge layers.
Segment routing is a technology that is gaining popularity as a way to simplify MPLS networks. It has the benefits of interfacing with software-defined networks and allows for source-based routing. It does this without keeping state in the core of the network and needless to use LDP and RSVP-TE.
Accelerating the Deployment of Practical, Programmable Transport NetworksDeborah Porchivina
The OIF and Carrier SDN: Accelerating the Deployment of Practical, Programmable Transport Networks
Speaker: Dave Brown, Alcatel-Lucent, OIF VP of Marketing
Lyndon Ong, of Ciena and the OIF Marketing Committee Co-Chair spoke at Globecom 2015. Focus on work in OIF Transport SDN Framework and joint work between OIF and ONF on Transport APIs
- Transport SDN is being driven by business needs like improved service availability and network automation, as well as trends like virtualization and separation of hardware and software.
- The OIF brings together industry groups to foster interoperable optical networking products and services. It aims to provide guidance on Transport SDN through documents outlining use cases, requirements, and a framework.
- A joint OIF/ONF demonstration in 2014 showed cloud bursting over optical networks using an SDN controller to dynamically create OTN connections according to application needs, highlighting the potential for Transport SDN.
This session will discuss MEF's Lifecycle Service Orchestration (LSO) requirements from ordering through service activation, including supporting APIs. We will also discuss how MEF is working with open source communities including OPNFV and Open Daylight to make LSO a reality.
This document summarizes Guru Parulkar's presentation at the 2017 Open Networking Summit. The presentation discusses the journey of SDN/NFV from disaggregation and open source software to production deployment. It notes that while network operators want to adopt open solutions, they lack development resources and investment. Vendors and system integrators also see opportunities but lack expertise and investment. To succeed in taking disaggregation and open source to production requires aligning incentives to drive sufficient investments.
The document discusses how segment routing can help networks support new services by providing simplified, automated, and scalable IP transport. Segment routing uses source routing techniques and standard routing protocols to enable network slicing, which allows for the efficient sharing of network resources across different services. The key capabilities of segment routing include simplification of network protocols, improved scalability, simplified traffic engineering, and universal forwarding across access and data center networks.
In networks built from proprietary and specialized equipment and software, can we really achieve the touted benefits of applying open source? One year has passed since the experiment called OPNFV was launched as act of faith by a brave few who wanted to accelerate true interoperability, by developing an open and flexible development reference platform to address NFV. In this year we have wrestled with many issues on both the development and business front, as we balance CSP expectations vs CSP realities, cooperation vs differentiation, and try to harness the chaotic open source development model to deliver useful software in a timely manner. This talk will provide an overview of the challenges we faced, our learnings and achievements.
Software Innovations and Control Plane Evolution in the new SDN Transport Arc...Cisco Canada
Loukas Paraschis, Technology Solution Architecture at Cisco presents software innovation and control plane evolution in the new SDN transport at Cisco Connect Toronto 2015.
The Optical Internetworking Forum (OIF) and the Open Networking Foundation (ONF) conducted three global events to share the results from the joint Transport Software Defined Networking (SDN) prototype demonstration with the industry. The results were shared with OFC 2015 attendees.
Oif at iir_next_genopticalnetworking_nice_22june15_jmcdonoughDeborah Porchivina
This document summarizes the OIF's work on software-defined networking (SDN) for transport networks. It discusses why transport networks need SDN to simplify management and enable rapid service provisioning. It also outlines challenges to SDN deployment and the OIF's efforts to address these challenges through a reference architecture, requirements documentation, demonstrations, and implementation agreements. The overall goal is to accelerate SDN adoption through multi-vendor interoperability testing and guidance for applying SDN concepts across multiple network domains.
Junjie Li represented OIF at the OptinetChina event this week. Junjie discussed how OIF's work on SDN transport APIs and packet-optical SDN use cases is helping operators unlock the benefits of SDN for their optical networks.
Enabling Key Applications for Transport SDN - Optinet China 2020Leah Wilkinson
Dr Hu Qian presents OIF Enabling Key Applications for Transport SDN at the Optinet China 2020 event. From Transport SDN to Integrated Packet Optical SDN: IP SDN and transport SDN is ready; Integrated packet optical SDN on the way.
The document summarizes plans for the Falcon and Goldeneye releases of the ONOS project. For the Falcon release in February 2016, goals include reviewing community plans, connecting people with shared interests, planning for dependencies, and providing sprint planning context. Various contributors outline proposed deliverables for their projects focusing on areas like core, northbound, southbound, virtualization, and test infrastructure improvements. The Goldeneye release in May 2016 aims to build upon work from Falcon with additional features, integrations, and enhancements across many areas.
The document summarizes a 2014 global transport SDN demonstration conducted jointly by the OIF and ONF. It describes the goals of demonstrating the current state of SDN in the transport industry using REST APIs and OpenFlow. It provides an agenda that includes an overview of tests, deep dives into OpenFlow CDPI and CVNI tests, and a summary. The demonstration involved participation from 17 companies across 5 carriers and 9 vendors.
Presentation : Business Process Management with mobile routesCharif Mahmoudi
The 11th ACS/IEEE International Conference on Computer Systems and Applications (AICCSA'2014)
November 10-13, 2014 at InterContinental, West Bay, Doha, Qatar
O-RAN is an open architecture for radio access networks that defines interfaces between network functions and promotes interoperability. The document discusses:
- The O-RAN logical architecture including the SMO, non-RT RIC, near-RT RIC, and interfaces like A1, E2, and open fronthaul.
- Implementation options for O-RAN like centralized/distributed near-RT RIC and shared cell deployment modes.
- The work groups developing O-RAN specifications for areas like architecture, interfaces, cloudification, and hardware.
- Details of the O-RAN fronthaul protocol stack supporting control, user, and synchronization planes over Ethernet.
- The reference
The document summarizes a session on gearing up for transport SDN deployment. It discusses how recent proofs-of-concept have shown progress towards commercial SDN deployment in transport networks. It outlines that network providers and vendors are collaborating through standards bodies and laboratories to address technical and business challenges inhibiting adoption. The OIF panelists will review findings from a global transport SDN prototype demo and steps to clear roadblocks to wide-scale deployment. They will discuss transport SDN drivers, needs, challenges and review the demo. It aims to accelerate adoption through providing guidance on use cases, requirements, frameworks and demonstrations.
1. The document discusses disaggregated transport networks and the use of open APIs to enable interoperability between multi-vendor components.
2. It proposes using open and standard APIs like TAPI and OpenConfig that provide abstraction layers and mandate interaction between software and hardware.
3. The goal is to allow mix-and-matching of components from different vendors and automate provisioning of end-to-end connectivity services across packet and optical domains.
Software Defined Optical Networks - Mayur ChannegowdaCPqD
This document discusses software defined optical networks using SDN. Key points include:
- SDN and OpenFlow can decouple the data and control planes in optical networks for automated provisioning and unified control.
- There are challenges in applying SDN to optical networks including switching constraints, physical impairments, multi-domain/multi-technology operation, and network virtualization.
- OpenFlow extensions are needed to abstract optical network elements and account for characteristics like flexible grid networks, impairment awareness, and multi-dimensional resource allocation.
- Proof-of-concept demonstrations have shown the potential for media-aware SDN, packet and optical convergence, and virtualization across multiple domains.
Software Defined Optical Networks - Mayur ChannegowdaCPqD
This document discusses software defined optical networks using SDN. Key points include:
- SDN and OpenFlow can decouple the data and control planes in optical networks for automated provisioning and unified control.
- There are challenges in applying SDN to optical networks including switching constraints, physical impairments, multi-domain/multi-technology operation, and network virtualization.
- OpenFlow extensions are needed to abstract optical network elements and account for characteristics like flexible grid networks, impairment awareness, and multi-dimensional resource allocation.
- Proof-of-concept demonstrations have shown the potential for media-aware SDN, packet and optical convergence, and virtualization across multiple domains.
Automation, Agility and NFV
The document discusses automation, agility, and network functions virtualization (NFV) in responding to over-the-top providers. It covers automation opportunities across the service lifecycle including order fulfillment, configuration, security, and analytics. Agility requires a DevOps approach using modeling languages and tools. NFV enables new services but faces challenges around integration and standards. Open source projects are important for NFV management and orchestration. Web giants like Facebook and Amazon use custom hardware and management tools rather than just commodity solutions.
Summit 16: The Hitchhiker/Hacker's Guide to NFV BenchmarkingOPNFV
The document summarizes benchmarking methodologies and tools for network function virtualization (NFV). It discusses standards from groups like ETSI and IETF, as well as open source projects from OPNFV. Traditional approaches to benchmarking physical network devices need to evolve to address virtual network functions (VNFs) and their supporting infrastructure. New methods are needed to test virtual switches, controllers, and other infrastructure components in NFV environments.
Similar to SDN Transport API Interoperability Demo with OIF and ONF (20)
This document discusses the development of 112Gbps electrical interfaces. It begins with an overview of the OIF's CEI specifications for various data rates ranging from 1.6Gbps to 112Gbps. It then examines potential modulation schemes for 112Gbps, including PAM-4, PAM-8, duo-binary and DMT. The document evaluates the feasibility of a 112Gbps very short reach channel based on existing 56Gbps channel models. It finds that channel improvements would be needed to support 112Gbps. Finally, it considers approaches to developing improved 112Gbps channels, such as reducing channel length, using lower loss materials, and integrating cable connectors.
The OIF represents over 100 member companies working to accelerate the adoption of new optical networking technologies. It develops implementation agreements (IAs) for electrical, protocol, and optical interfaces to address current industry needs. Recent work includes the CEI IA for electrical chip-to-chip interfaces up to 56Gbps and new CFP8-ACO and flexible coherent transmission frameworks. Interoperability demonstrations have validated OIF solutions work across member products. The OIF aims to fill gaps in optical networking standards through open collaboration.
The document discusses the OIF CEI-56G projects which are optimizing signal integrity for different interconnect applications. Five projects are underway for chip-to-chip reaches: LR for backplanes up to 100cm, MR for midplanes up to 50cm, VSR for chip-to-module up to 10cm, XSR for chip-to-nearby optics up to 5cm, and USR for 2.5D/3D die-to-die up to 1cm. Modulation variants like NRZ and ENRZ are being considered to meet power and latency requirements for applications like HPC that cannot tolerate forward error correction. Simulation results show ENRZ can achieve sufficient eye opening for long-reach
This document discusses testing considerations for 56G PAM-4 signaling, which introduces new impairments compared to previous NRZ signaling. It outlines how the CEI-56G Implementation Agreements are defining new transmitter output and receiver input stress tests to ensure data link integrity. Examples of new tests mentioned include linearity tests on receiver inputs. It also provides an overview of upgraded measurement tools needed for characterizing and testing PAM-4, such as oscilloscopes, pattern generators, and error detectors.
The OIF has developed several new 56Gbps implementation agreements to address higher data rates beyond 28Gbps. These agreements consider signal modulations like NRZ and PAM4, and different transmission reaches from chip-to-chip to backplane implementations. Throughout this work, signal integrity has been the primary focus while also considering power consumption and complexity. The agreements are aimed at applications in storage, computing, networking and telecommunications. Multiple modulation and implementation options will be needed to satisfy the varying requirements of latency, power, cost, density and transmission reach across different applications operating at 56Gbps.
OIF's Carrier Working Group Chair, Vishnu Shukla, Verizon shares network virtualization and SDN controls to enable transport network as a service to OFC2016 attendees.
The Optical Internetworking Forum (OIF) will host a public workshop on March 24, 2016 in Anaheim, California to address the latest developments in 100G Serial technology. The workshop will feature presentations from subject matter experts at companies like Cisco, Microsoft, Brocade, MACOM, TE Connectivity, and Kandou Bus. It will include two working sessions on 100G Serial application requirements and 100G Serial electrical technology. The deadline to register for the workshop is March 17, 2016.
Clearing a Path to Wide-Scale Transport SDN DeploymentDeborah Porchivina
The document summarizes an agenda for a session reviewing progress towards wide-scale adoption of SDN in transport networks. It will include a presentation on a global transport SDN prototype demo by OIF, a discussion of the OIF's SDN framework and APIs by Ciena, and a presentation on virtual transport network services by Verizon. The session aims to identify technical and business challenges preventing broader SDN adoption and provide components of a toolkit to help clear the path towards widespread deployment of SDN in transport networks.
The document discusses OIF's CEI-56G interface projects which are key building blocks for 400G data center optics. It summarizes OIF's CEI-56G projects addressing various link reaches using NRZ, PAM-4, and ENRZ modulation. It describes how the 56G VSR chip-to-module interface and IEEE 400G 802.3bs electrical and optical specifications leverage OIF's work. The document concludes that CEI-56G PAM4 interfaces will enable next generation 200G/400G client optics and OIF has additional projects addressing data center needs.
The document discusses the promise of SDN for transport networks. It notes changing business and usage models are driving the need for more elastic, on-demand networks. SDN can help by providing programmable control of optical networks through standardized interfaces. The OIF and ONF conducted a global demo of transport SDN using an application for cloud bursting over optical networks. This identified gaps around multi-domain control and relationships between controllers and network management. Wider SDN deployment faces challenges around operational simplicity, scalability, security and continuous availability. Multiple SDOs are working on related standards but alignment is still needed.
Quantum Communications Q&A with Gemini LLM. These are based on Shannon's Noisy channel Theorem and offers how the classical theory applies to the quantum world.
Sustainability requires ingenuity and stewardship. Did you know Pigging Solutions pigging systems help you achieve your sustainable manufacturing goals AND provide rapid return on investment.
How? Our systems recover over 99% of product in transfer piping. Recovering trapped product from transfer lines that would otherwise become flush-waste, means you can increase batch yields and eliminate flush waste. From raw materials to finished product, if you can pump it, we can pig it.
7 Most Powerful Solar Storms in the History of Earth.pdfEnterprise Wired
Solar Storms (Geo Magnetic Storms) are the motion of accelerated charged particles in the solar environment with high velocities due to the coronal mass ejection (CME).
Quality Patents: Patents That Stand the Test of TimeAurora Consulting
Is your patent a vanity piece of paper for your office wall? Or is it a reliable, defendable, assertable, property right? The difference is often quality.
Is your patent simply a transactional cost and a large pile of legal bills for your startup? Or is it a leverageable asset worthy of attracting precious investment dollars, worth its cost in multiples of valuation? The difference is often quality.
Is your patent application only good enough to get through the examination process? Or has it been crafted to stand the tests of time and varied audiences if you later need to assert that document against an infringer, find yourself litigating with it in an Article 3 Court at the hands of a judge and jury, God forbid, end up having to defend its validity at the PTAB, or even needing to use it to block pirated imports at the International Trade Commission? The difference is often quality.
Quality will be our focus for a good chunk of the remainder of this season. What goes into a quality patent, and where possible, how do you get it without breaking the bank?
** Episode Overview **
In this first episode of our quality series, Kristen Hansen and the panel discuss:
⦿ What do we mean when we say patent quality?
⦿ Why is patent quality important?
⦿ How to balance quality and budget
⦿ The importance of searching, continuations, and draftsperson domain expertise
⦿ Very practical tips, tricks, examples, and Kristen’s Musts for drafting quality applications
https://www.aurorapatents.com/patently-strategic-podcast.html
Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Em...Erasmo Purificato
Slide of the tutorial entitled "Paradigm Shifts in User Modeling: A Journey from Historical Foundations to Emerging Trends" held at UMAP'24: 32nd ACM Conference on User Modeling, Adaptation and Personalization (July 1, 2024 | Cagliari, Italy)
Transcript: Details of description part II: Describing images in practice - T...BookNet Canada
This presentation explores the practical application of image description techniques. Familiar guidelines will be demonstrated in practice, and descriptions will be developed “live”! If you have learned a lot about the theory of image description techniques but want to feel more confident putting them into practice, this is the presentation for you. There will be useful, actionable information for everyone, whether you are working with authors, colleagues, alone, or leveraging AI as a collaborator.
Link to presentation recording and slides: https://bnctechforum.ca/sessions/details-of-description-part-ii-describing-images-in-practice/
Presented by BookNet Canada on June 25, 2024, with support from the Department of Canadian Heritage.
RPA In Healthcare Benefits, Use Case, Trend And Challenges 2024.pptxSynapseIndia
Your comprehensive guide to RPA in healthcare for 2024. Explore the benefits, use cases, and emerging trends of robotic process automation. Understand the challenges and prepare for the future of healthcare automation
The DealBook is our annual overview of the Ukrainian tech investment industry. This edition comprehensively covers the full year 2023 and the first deals of 2024.
Implementations of Fused Deposition Modeling in real worldEmerging Tech
The presentation showcases the diverse real-world applications of Fused Deposition Modeling (FDM) across multiple industries:
1. **Manufacturing**: FDM is utilized in manufacturing for rapid prototyping, creating custom tools and fixtures, and producing functional end-use parts. Companies leverage its cost-effectiveness and flexibility to streamline production processes.
2. **Medical**: In the medical field, FDM is used to create patient-specific anatomical models, surgical guides, and prosthetics. Its ability to produce precise and biocompatible parts supports advancements in personalized healthcare solutions.
3. **Education**: FDM plays a crucial role in education by enabling students to learn about design and engineering through hands-on 3D printing projects. It promotes innovation and practical skill development in STEM disciplines.
4. **Science**: Researchers use FDM to prototype equipment for scientific experiments, build custom laboratory tools, and create models for visualization and testing purposes. It facilitates rapid iteration and customization in scientific endeavors.
5. **Automotive**: Automotive manufacturers employ FDM for prototyping vehicle components, tooling for assembly lines, and customized parts. It speeds up the design validation process and enhances efficiency in automotive engineering.
6. **Consumer Electronics**: FDM is utilized in consumer electronics for designing and prototyping product enclosures, casings, and internal components. It enables rapid iteration and customization to meet evolving consumer demands.
7. **Robotics**: Robotics engineers leverage FDM to prototype robot parts, create lightweight and durable components, and customize robot designs for specific applications. It supports innovation and optimization in robotic systems.
8. **Aerospace**: In aerospace, FDM is used to manufacture lightweight parts, complex geometries, and prototypes of aircraft components. It contributes to cost reduction, faster production cycles, and weight savings in aerospace engineering.
9. **Architecture**: Architects utilize FDM for creating detailed architectural models, prototypes of building components, and intricate designs. It aids in visualizing concepts, testing structural integrity, and communicating design ideas effectively.
Each industry example demonstrates how FDM enhances innovation, accelerates product development, and addresses specific challenges through advanced manufacturing capabilities.
An invited talk given by Mark Billinghurst on Research Directions for Cross Reality Interfaces. This was given on July 2nd 2024 as part of the 2024 Summer School on Cross Reality in Hagenberg, Austria (July 1st - 7th)
Best Programming Language for Civil EngineersAwais Yaseen
The integration of programming into civil engineering is transforming the industry. We can design complex infrastructure projects and analyse large datasets. Imagine revolutionizing the way we build our cities and infrastructure, all by the power of coding. Programming skills are no longer just a bonus—they’re a game changer in this era.
Technology is revolutionizing civil engineering by integrating advanced tools and techniques. Programming allows for the automation of repetitive tasks, enhancing the accuracy of designs, simulations, and analyses. With the advent of artificial intelligence and machine learning, engineers can now predict structural behaviors under various conditions, optimize material usage, and improve project planning.
Support en anglais diffusé lors de l'événement 100% IA organisé dans les locaux parisiens d'Iguane Solutions, le mardi 2 juillet 2024 :
- Présentation de notre plateforme IA plug and play : ses fonctionnalités avancées, telles que son interface utilisateur intuitive, son copilot puissant et des outils de monitoring performants.
- REX client : Cyril Janssens, CTO d’ easybourse, partage son expérience d’utilisation de notre plateforme IA plug & play.
The Rise of Supernetwork Data Intensive ComputingLarry Smarr
Invited Remote Lecture to SC21
The International Conference for High Performance Computing, Networking, Storage, and Analysis
St. Louis, Missouri
November 18, 2021
SDN Transport API Interoperability Demo with OIF and ONF
1. 2016 SDN Transport API
Interoperability Demonstration
Jonathan Sadler (Coriant)
Interop Working Group Chair
OIF Technical Committee
Open
Networking
Foundation
3. SDN improves Transport Control
Eliminate “One-size-fits-all” solutions
• NE-behaviors may not match
carrier requirements
• Example
• Combined Reroute and Protection
Programmability enables carrier requirements to be met
400% Capacity use
50ms protection all the time
300% Capacity use
50ms protection switch first fault
~300ms switch second and subsequent
2
4. Open APIs between SDN Components
How can programmability be provided?
3
Control
Components
Service Management
Connection
Management Routing Control
Path Query Topology
Signaling Proto Dataplane Config
Link Management
Discovery Routing Proto
Directory
Service Requests
Dataplane
http://www.oiforum.com/documents/framework-for-transport-sdn-components-and-apis
5. Evaluate current state of SDN in Transport industry
• Validate APIs in SDN Framework
• Useful:
• Do the defined API solve a business problem?
• Is the API consistent with business structural boundaries?
• Perform well:
• Would a different API improve performance?
• Can be implemented
2016 SDN Transport API Interoperability Demonstration
4
6. Joint activity of OIF and ONF
• OIF
• API Framework
• Prototype API experience – 2014 Interop Test event
• ONF – Standards Organization for SDN
• SDN Architecture
• Transport API Project
2016 SDN Transport API Interoperability Demonstration
5
7. OIF SDN Framework
6
Control
Components
Service Management
Connection
Management Routing Control
Path Query Topology
Signaling Proto Dataplane Config
Link Management
Discovery Routing Proto
Directory
Service Requests
Dataplane
http://www.oiforum.com/documents/framework-for-transport-sdn-components-and-apis
8. Participants from both OIF and ONF
• OIF: ADVA, China Telecom, Ciena, Coriant, FiberHome, Huawei,
Juniper, NEC, Orange, Telus, Verizon, ZTE
• ONF: ADVA, CATR, China Telecom, Ciena, FiberHome, Huawei, Juniper,
NEC, Sedona, SK Telecom, SMOptics, Telefonica, Verizon, ZTE
• Interested 3rd Party: China Unicom
• OIF: ADVA, China Telecom, Ciena, Coriant, FiberHome, Huawei,
Juniper, NEC, Orange, Telus, Verizon, ZTE
• ONF: ADVA, CATR, China Telecom, Ciena, FiberHome, Huawei, Juniper,
NEC, Sedona, SK Telecom, SMOptics, Telefonica, Verizon, ZTE
• Interested 3rd Party: China Unicom
2016 SDN Transport API Interoperability Demonstration
7
9. Timeline
8
Test end
May Jun
2016
ONF Workday
Contract/NDA
Jul Aug
BCE
MarSep Oct Nov Dec Jan Feb
ECOC
2016
3Q OIF 4Q OIF
L123 SDN
Test start Readouts
OECC
2Q16 OIF
ETSI NFV
MWC
2017
1Q OIF OFC
2017
ONF Interim
Tech Spec Start
11. Intra-lab Pairings
Carrier A
• Orchestrators: Ca, Ra
• Dataplane: Vd, Ve, Vf
Carrier B
• Orchestrators: Cb
• Dataplane: Ve, Vf
Carrier C
• Orchestrators: Cc, Va
• Datraplane: Va, Vg
Carrier D
• Orchestrators: Vb, Vc
• Dataplane: Vh, Vi, Vk, Va, Vg, Vb
Carrier E
• Orchestrators: Vb
• Dataplane: Vh, Vj, Vb
6 pairings
4 pairings
4 pairings
10 pairings
3 pairings
27 Pairs
10
12. Inter-lab Pairings
Carrier A – Carrier C
• Orchestrators: Ra
• Dataplane: Va, Vg
Carrier C – Carrier E
• Orchestrators: Ra
• Dataplane: Vh
Carrier A – Carrier E
• Orchestrators: Vb
• Dataplane: Vd, Ve, Vf
Carrier C – Carrier D
• Orchestrators: Cc
• Dataplane: Vb, Vi
Carrier D – Carrier E
• Orchestrators: Vb, Sedona
• Dataplane: Vh, Vj, Vb
Carrier C – Carrier E
• Orchestrators: Vb
• Dataplane: Va, Vg
2 pairings
3 pairings
2 pairings
2 pairings
1 pairing
6 pairings
16 Pairs
11
14. Use Case: MultiDomain Orchestration
Service provider equipment is in different domains
• Different Geographies
• Different Vendors
• Different Technologies
Services cross domain boundaries
• Orchestration across domains is necessary
13
15. NFV POC
Multi-domain Orchestration is
necessary in NFV deployments
involving the transport layer
• Best technology for carrying service
• Support multiple provider networks
T-API provides interface required
by WAN Infrastructure Manager
• Integrates Transport into MANO
14
17. Topology API Capture
HTTP/1.1 201 Created
Server: Apache-Coyote/1.1
Content-Type: application/json
Date: Tue, 12 Dec 2016 4:41:37 GMT
Connection: close
{
"itemlist": [
"/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_link/55c7c8b9-3b87-4822-9c9b-
3392f0109065/",
"/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_link/e7eb128a-82a5-4fa1-b030-
e386ec93c30f/",
"/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_link/76fd27f4-e4f0-42a8-8b1a-
909302b426ce/"
]
}
NE
NE
NE
GET /restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_link/ HTTP/1.1
User-Agent: Faraday v0.9.0
Content-Type: application/json
Accept: application/json
Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
Connection: close
Host: 10.131.22.2:8081
Content-Length: 183
16
18. Topology API Capture
NE
NE
NE
GET /restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_link/55c7c8b9-
3b87-4822-9c9b-3392f0109065/ HTTP/1.1
User-Agent: Faraday v0.9.0
Content-Type: application/json
Accept: application/json
Accept-Encoding: gzip;q=1.0,deflate;q=0.6,identity;q=0.3
Connection: close
Host: 10.131.22.2:8081
Content-Length: 183
17
19. Topology API CaptureHTTP/1.1 201 Created
Content-Type: application/json
Server: Werkzeug/0.11.11 Python/2.7.5
Date: Tue, 12 Dec 2016 4:41:37 GMT
{
"_linkPort": [
{
"_nodeEdgePoint": "/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_node/07d7ad4c-
4214-4d98-8be8-4e6826cece43/_ownedNodeEdgePoint/37a03a6b-3e95-48bb-a253-fd5b3d2f597b/",
"direction": "BIDIRECTIONAL",
"localId": "lp13",
"role": "SYMMETRIC"
}, {
"_nodeEdgePoint": "/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_node/019ac632-
20d6-4750-b77c-80852ee60ed6/_ownedNodeEdgePoint/a4b58599-58af-4c38-862b-6c4a46ca9ec7/",
"direction": "BIDIRECTIONAL",
"localId": "lp31",
"role": "SYMMETRIC"
}
],
"_node": [
"/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_node/07d7ad4c-4214-4d98-8be8-
4e6826cece43/",
"/restconf/config/Context/_topology/7a360591-5561-421f-abf2-4c48c4ab9d3e/_node/019ac632-20d6-4750-b77c-
80852ee60ed6/"
],
"_state": {
"administrativeState": "UNLOCKED",
"lifecycleState": "INSTALLED",
"operationalState": "ENABLED"
},
NE
NE
NE
Response continued on the next page
18
24. Topology API Capture
GET /restconf/config/Context/_topology/TOP
Content-Type: application/json; charset=utf-8
Host: 10.141.6.5:8080
NE
NE
NENE
NE
NE
23
25. Topology API CaptureHTTP/1.1 200 OK
Content-Type: application/json
Date: Tue, 20 Dec 2016 10:58:06 GMT
{
"_extensions": [ ],
"label": [ ],
"uuid": "TOP",
"name": [ {
"value": "TOP",
"valueName": "name"
} ],
"_node": [ {
"_extensions": [ {
"extensionsSpecTarget": [ "sm" ],
"extensionsSpecification": "vendor"
}, {
"extensionsSpecTarget": [ "SM/00000031-0000-0000-0031-000000736d6f/" ],
"extensionsSpecification": "domainId"
} ],
"label": [ ],
"uuid": "tsdn:sm:script",
"name": [ {
"value": "tsdn:sm:script",
"valueName": "name"
} ],
"_encapTopology": null,
"_state": {
"administrativeState": "UNLOCKED",
"operationalState": "ENABLED",
"lifecycleState": "INSTALLED"
},
"_transferTiming": null,
NE
NE
NENE
NE
NE
Response continued on the next page
24
NE NENE
26. Topology API Capture"_ownedNodeEdgePoint": [ {
"_extensions": [ ],
"label": [ ],
"uuid": "tsdn:sm:script::1",
"name": [ { "valueName": "name", "value": "OGBE10-1-3-6" } ],
"_state": {
"administrativeState": "UNLOCKED",
"operationalState": "ENABLED",
"lifecycleState": "INSTALLED"
},
"direction": "BIDIRECTIONAL",
"_layerProtocol": [ ],
"_clientNodeEdgePoint": [ ],
"_mappedServiceEndPoint": [ "/restconf/config/Context/_serviceEndPoint/tsdn:sm:script::1/" ]
}, {
"_extensions": [ ],
"label": [ ],
"uuid": "tsdn:sm:script::2",
"name": [ { "valueName": "name", "value": "OGBE10-1-3-5" } ],
"_state": {
"administrativeState": "UNLOCKED",
"operationalState": "ENABLED",
"lifecycleState": "INSTALLED"
},
"direction": "BIDIRECTIONAL",
"_layerProtocol": [ ],
"_clientNodeEdgePoint": [ ],
"_mappedServiceEndPoint": [ "/restconf/config/Context/_serviceEndPoint/tsdn:sm:script::2/" ]
},
NE
NE
NENE
NE
NE
Response continued on the next page
25
NE NE
27. Topology API Capture{
"_extensions": [ ],
"label": [ ],
"uuid": "tsdn:sm:script::3",
"name": [ { "valueName": "name", "value": "OGBE10-1-3-5" } ],
"_state": {
"administrativeState": "UNLOCKED",
"operationalState": "ENABLED",
"lifecycleState": "INSTALLED"
},
"direction": "BIDIRECTIONAL",
"_layerProtocol": [ ],
"_clientNodeEdgePoint": [ ],
"_mappedServiceEndPoint": [ ]
}, {
"_extensions": [ ],
"label": [ ],
"uuid": "tsdn:sm:script::4",
"name": [ { "valueName": "name", "value": "OGBE10-1-3-5",} ],
"_state": {
"administrativeState": "UNLOCKED",
"operationalState": "ENABLED",
"lifecycleState": "INSTALLED"
},
"direction": "BIDIRECTIONAL",
"_layerProtocol": [ ],
"_clientNodeEdgePoint": [ ],
"_mappedServiceEndPoint": [ ]
} ],
"layerProtocolName": [ "OCH" ],
"_transferCapacity": null,
"_transferCost": null,
"_aggregatedNodeEdgePoint": [ ],
"_transferIntegrity": null
},
NE
NE
NENE
NE
NE
Response continued on the next page
26
NE NE
45. Findings
ONF’s T-API provides functions necessary for multi-domain orchestration
• Topology view
• Connection establishment
• Topology abstraction
ONF’s T-API localizes interoperability to Orchestrator/Controller interface
• GMPLS requires NEs in a sequence to have a consistent behavior in order to
achieve interoperability
ONF’s T-API supports multiple technologies
• Ethernet
• OTN
• DWDM44
46. Findings
Controllers abstract the network in different ways
• E.g. Unidirectional vs Bidirectional links
Controllers provide/report different capabilities
• E.g. Connectivity restrictions
Division of responsibility between controllers unclear
• E.g. Multi-domain Path Computation
Maintaining RPC and REST styles is confusing
• Not all implementations supported both styles
45
47. Findings
T-API needs to be validated for additional use cases
• Use of topology interface for Path Computation
• Service Management interface
T-API evolution is needed to meet current Transport Network uses
• Protected Services
• Generalized Notification Service
Based on demo feedback, ONF will align T-API with YANG Best Practices
• Object ID format and lifecycle
• Separation of Configuration, Operational Data
46
48. Summary
Demonstration shows:
• Cooperation between 17 companies
• 7 Carriers (5 Host, 2 Consulting)
• 10 Vendors
• 2 Research Institutions
• Transport SDN is becoming real
• ONF T-API Specification published, implemented and tested
• Testing is a success
• Identified strengths and areas for further activity
Next step:
• T-API 2.0
47
49. 2016 SDN Transport API Interoperability Demonstration
Accelerating Momentum on the Road to Next-Generation Architectures
www.opennetworking.org www.oiforum.com
Open
Networking
Foundation