Rod LU (ZTE) Yunbo LI (CMCC) Yang ZHAO (CMCC) Yunbin XU (CATR)

Slides:



Advertisements
Similar presentations
IETF 78, Maastricht, Netherlands, July 25-30, 2010Page - 1 Requirement and Framework for Multi Stages Multiplexing Configuration in G.709 network draft-fuxh-ccamp-multi-stage-multiplex-config-req-01.
Advertisements

G : DCM Signaling Mechanism Using GMPLS RSVP-TE ITU-T Workshop on IP-Optical, Chitose, Japan 7/11/2002 Dimitrios Pendarakis, Tellium, Inc. ITU-T.
Next-Generation ROADMs
Brocade VDX 6746 switch module for Hitachi Cb500
The data link layer Skills: none IT concepts: LAN, medium access, Ethernet and WiFi protocols, why standards win This work is licensed under a Creative.
Multiple constraints QoS Routing Given: - a (real time) connection request with specified QoS requirements (e.g., Bdw, Delay, Jitter, packet loss, path.
Delivery, Forwarding, and Routing
SMUCSE 8344 Constraint-Based Routing in MPLS. SMUCSE 8344 Constraint Based Routing (CBR) What is CBR –Each link a collection of attributes (performance,
1 Semester 2 Module 6 Routing and Routing Protocols YuDa college of business James Chen
EAIT, February 2006 A Pragmatic Approach towards the Improvement of Performance of Ad Hoc Routing ProtocolsOptimizations To Multipath Routing Protocols.
CS3502: Data and Computer Networks Local Area Networks - 4 Bridges / LAN internetworks.
Routers. What is a Router? A multi-port connectivity device Can connect different types of LANs as well as WANS Works at Layer 3 – Network Layer using.
SMUCSE 8344 Protection & Restoration of Optical Networks.
Load Balancing in Protection Switching of Optical Networks Hongkyu Jeong, Gyu-Myoung Lee Information and Communications Univ. (ICU) Student ID : ,
Optical Control Plane, Optical/IP integration Concepts and Issues Greg Bernstein Greg Bernstein
OIF NNI: The Roadmap to Non- Disruptive Control Plane Interoperability Dimitrios Pendarakis
Multi-layered Optical Network Security
1 Module 4: Implementing OSPF. 2 Lessons OSPF OSPF Areas and Hierarchical Routing OSPF Operation OSPF Routing Tables Designing an OSPF Network.
Data Communications and Networking Chapter 11 Routing in Switched Networks References: Book Chapters 12.1, 12.3 Data and Computer Communications, 8th edition.
Two-layer Restoration Scheme for IP over Optical Networks with MPLS Jia Ke, L. Mason, Q. Yang ICIS, School of EEE, Nanyang Technological University
Networking and internetworking devices. Repeater.
Reconfigurable Optical Mesh and Network Intelligence Nazar Neayem Alcatel-Lucent Internet 2 - Summer 2007 Joint Techs Workshop Fermilab - Batavia, IL July.
Resource Allocation in Network Virtualization Jie Wu Computer and Information Sciences Temple University.
1 Requirements for Very Fast Setup of GMPLS LSPs draft-malis-ccamp-fast-lsps-01 Andrew G. Malis Ronald A. Skoog Haim Kobrinski George Clapp John E. Drake.
CEN 5501C - Computer Networks - Spring UF/CISE - Newman1 Computer Networks Chapter 4 – Source Routing Bridges.
1 Revision to DOE proposal Resource Optimization in Hybrid Core Networks with 100G Links Original submission: April 30, 2009 Date: May 4, 2009 PI: Malathi.
Internet Traffic Engineering Motivation: –The Fish problem, congested links. –Two properties of IP routing Destination based Local optimization TE: optimizing.
Delivery and Forwarding Chapter 18 COMP 3270 Computer Networks Computing Science Thompson Rivers University.
Fall, 2001CS 6401 Switching and Routing Outline Routing overview Store-and-Forward switches Virtual circuits vs. Datagram switching.
Chapter 3: Packet Switching (overview)
Use Case for Distributed Data Center in SUPA
Kam LAM (Alcatel-Lucent) onf
Daniel King, Old Dog Consulting Adrian Farrel, Old Dog Consulting
Architecture and Algorithms for an IEEE 802
Matt Hornbrook James Beams
Zhenbin Li, Kai Lu Huawei Technologies IETF 98, Chicago, USA
Configuring and Troubleshooting DHCP
Planning and Troubleshooting Routing and Switching
3. Internetworking (part 1)
Packet Switching Outline Store-and-Forward Switches
Daniel King, Old Dog Consulting Adrian Farrel, Old Dog Consulting
Author: Daniel Guija Alcaraz
COMP 3270 Computer Networks
Reconfigurable Optical Mesh and Network Intelligence
Open Transport Config and Control Project Agenda and Notes
FRD Examples November 28, 2017 L. Ong.
ACTN Information Model
Use Case: Multi vendor domain OMS interworking
Multi-Layer Scenarios
ACTN Information Model
NTHU CS5421 Cloud Computing
DetNet Configuration YANG Model
Multi-Layer Scenarios
DetNet Information Model Consideration
ONF OTCC TAPI Contribution
Rapid Mobility via Type Indirection
SURVIVABILITY IN IP-OVER-WDM NETWORKS (2)
draft-ietf-teas-yang-te-topo-08
Optical communications & networking - an Overview
Proposed Extensible Approach for WLAN Mesh Standardization
Issues and solutions raised in CMCC lab test
Multi-Layer Scenarios
Task 62 Scope – Config / Operational State
CMCC Laboratory test of SOTN Northbound interface based on TAPI 2.0
TAPI Photonic Media Model
Multi-Layer Scenarios
TAPI Topology & Connectivity Concepts
Issue 1: Distinction between nominal and backup paths
Transport network requirements for TAPI considering NBI
YANG Model for ETH TE Topology CCAMP WG, IETF 105, Montreal, Canada draft-zheng-ccamp-client-topo-yang-06 Italo Busi, Haomian Zheng, Aihua Guo (Huawei)
Presentation transcript:

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)

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: https://www.opennetworking.org/about/onf-overview 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 https://www.opennetworking.org/images/stories/downloads/about/onf-operating-documents/organizational-documents/onf-ipr-policy.pdf

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)

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

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

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

Distinguish of virtual traffic add description and examples of the isExclusieveService

Resilience Requirements

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

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

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

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

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

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

Resilience Constraint

THANK YOU!