1. Rod LU (ZTE) Yunbo LI (CMCC) Yang ZHAO (CMCC) Yunbin XU (CATR)
TAPI 2.0 Gap Analysis
Rod LU (ZTE)
Yunbo LI (CMCC)
Yang ZHAO (CMCC)
Yunbin XU (CATR)

2. ONF Antitrust & Intellectual Policies and Specific Guidance
This is a reminder that all Open Networking Foundation activities are subject to strict compliance with the Open Networking Foundation's Antitrust Guidelines. Each individual participant and attendee at this meeting is responsible for knowing the contents of the Antitrust Guidelines, and for complying with the Antitrust Guidelines. Copies of the Antitrust Guidelines are available at: Participants also are expected to adhere to these Guidelines in any informal meetings or social gatherings in which they might participate in connection with the activities of the Corporation.
You are required to treat the contents, notes, artifacts, and all materials associated with this meeting (including recordings) as protected by the ONF Intellectual Property Rights (IPR) policy. Do not forward any of these contents to any non ONF members. For more information on the ONF IP policy, please consult

3. Single Domain Controller NBI Requirement
Network resource retrieval
Retrieval of Node, Ltp and Link
Including ETH, ODU, Och Info
Statistics of network resource utilization (For which I think we are running out of time)
Gap: Protection characteristic of Link, e.g. a ETH Link is supported by a ODUk Connection, the Protection characteristic of this Link will inherit the Protection Type of this Connection.
Path Computation
Support following Objective Function: Minimum Hop, Minimum Link Cost, Minimum Latency, Load Balance
Support following Topology Constraint: Include/exclude Node or Link, Optical Layer Constraint(Constraint of Wavelength and Optical Layer Performance, Considering OSNR, CD, PMD), Combination of above constraints
Diversity Policy for resilience (SRLG, Link/Node diversity)
Gap:
Minimum Hop, Minimum Latency, Load Balance, Optical Layer Constraint
Connection Management
Creation and Deletion of 10GE, STM-N, OTUk, EPL/EVPL/EP-LAN/EVP-LAN and Och Traffic
Modify Connection with: Capacity, Resilience Constraint
Support following Resilience Constraint: 1+1 Permanent Protection, 1+1 Protection Combine with Dynamic Restoration, Pre-compute Route Restoration, Dynamic Restoration
Gap: Resilience Constraint, Distinguish of virtual traffic (i.e. between EPL and EVPL, or between EPLAN and EVPLAN)

4. Multi-Domain Inter-operate Requirement
Network resource retrieval
Configuration of Inter-Domain Links (Auto-discovery is Optional)
The rest Same as Single-Domain.
Gap: Configuration of Inter-Domain Links
Path Computation
Topology Constraint for Inter-Domain Links
Connection Management
Resilience Constraint divided into two parts: Per-Domain(Segment) Resilience Constraint and End2End Resilience
Per-Domain(Segment) Resilience Constraint: Same as Single-Domain requirements
End2End Resilience: End to End ODUk 1+1 Protection, End to End Dynamic Restoration

5. Protection characteristic of Link
protectionType -> resilienceType, also the data type

6. Route Compute Policy
proposed to add OpticalRoutingStrategy to OTSi Module and augment the RouteComputePolicy Pac ; Relay to Regenerate?( to make sure )

7. Distinguish of virtual traffic
add description and examples of the isExclusieveService

8. Resilience Requirements

9. single-domain - 1+1 Permanent Protection
Once Route failed, restore this route

10. single-domain - 1+1 Protection Combine with Dynamic Restoration
Both Routes failed, then restore this service

11. single-domain - Pre-compute Route Restoration
Compute one Path for a Connectivity-Service but not reserve resources, when C-S failed, restore with this Path

12. single-domain - Dynamic Restoration
when C-S failed, compute a new route and restore

13. Per-Domain(Segment) Resilience Constraint
Same as Single-Domain requirements

14. End2End Resilience: End to End ODUk 1+1 Protection, End to End Dynamic Restoration

15. Resilience Constraint

16. THANK YOU!