Research Challenges in the Emerging Hybrid Network World Tom Lehman University of Southern California Information Sciences Institute (USC/ISI)

Hybrid Networking Defined Network architectures which provide IP routed service AND some form of: –service which provides access to dedicated, deterministic, and schedulable network resources "Deterministic" is the key concept here Users may not get exactly what they want, but they will know what they have, and can plan their application processes and workflows with confidence the network will deliver what has been promised

Hybrid Network Services Rationale and Objectives There is a class of users which require Deterministic Network Services These users do not want (or can they afford to) share fairly via the use of something like a TCP friendly congestion control Example users include expensive resource eScience communities, emergency response, mission or business critical functions, building (or traffic engineering) of the best effort IP network These users are the exception. They are not a large part of the total traffic from a flow perspective. They can be a large part from a bandwidth usage perspective. This service is not a replacement for the best effort IP network, but an additional network capability. The best effort IP network will still carry the majority of users.

Hybrid Networking - Data Planes Many Data Plane options to provide Hybrid Network Services: –Layer 3 for PSC with QoS (IP Routing) –Layer 2.5 for PSC with QoS (MPLS) –Layer 2 for L2SC (often Ethernet) –Layer 1.5 for TDM (often SONET/SDH) –Layer 1 for LSC (often WDM switch elements) From client hand-off perspective the "service" of choice is an Ethernet service –This is independent network technology layer –That is, all of the above Data Plane technologies can encapsulate Ethernet for the client service interface

Hybrid Networking - Architectures Many ways to architect the Data Plane Multi-Layer Parallel Combined Multi-Layer Multi-Service Hybrid Service

Hybrid Networking Deployments in U.S. Internet2 ION Service – –Layer 1.5 network Energy Sciences Network (ESnet) Science Data Network (SDN) – –Layer 3/2.5 network USLHCnet –lhcnet.caltech.edu –Layer 1.5/2 network Multiple Regional Networks –Layer 2 networks

Hybrid Networking What is the Service? Source Address Destination Address Bandwidth VLAN TAG (untagged | any | tagged | tunnel) User Identification (certificate) Schedule Client A Client B Circuit Request Ethernet Service (encapsulated in lower layer) Dynamically Provisioned Dedicated Resource Path (Circuit) Dynamic Service IDC InterDomain Controller api can run on the client, or in a separate machine, or from a web browser XML USER API Actual Network Path

Hybrid Networking Same Service for InterDomain Regional Hybrid Network Regional Hybrid Network Wide Area Hybrid Network 1. Client Service Request 2. Resource Scheduling 5. Service Instantiation (as a result of Signaling) A. Abstracted topology exchange A A USER API XML Multi-Domain Dynamically Provisioned Circuit client-to-network protocol network-to-network protocol

Hybrid Networking What is State of Control Plane? Current control plane implementations in U.S. are based on: –OSCARS –DRAGON dragon.east.isi.edu The client-to-network and network-to-network protocol definitions are based on: –DICE InterDomain Controller Protocol (IDCP)

DICE IDCP Web Service Definitions Originally developed in DICE –Dante, Internet2, CANARIE, ESNet –now includes other organizations as well wsdl - web service definition of message types and formats xsd – definition of schemas used for network topology descriptions and path definitions

DICE IDCP Conceptual View of the Messaging Four Primary Web Services Areas: Topology Exchange, Resource Scheduling, Signaling, User Request

Hybrid Network Services Footprint

Hybrid Networking What about Application Interfaces? The below applications have adapted their existing systems to communicate via the user request side of the IDCP –LambdaStation ( –TeraPaths ( –Phoebus (e2epi.internet2.edu/phoebus.html) –DETER (isi.deterlab.net) (development underway)

What are the Research Challenges? Path Computation Integration with Application Domain Workflows –Application Specific Topologies Robust Service Interface Definition –client-to-network piece Scalable Authentication, Authorization, Accounting (AAA)

What are the Research Challenges? Hybrid Service Monitoring and Debugging –Multi-Domain complicates this greatly Topology Distribution/Routing Signaling (mainly speed issues) How to use these services to make the IP routed infrastructure better? –Traffic Engineering of the IP routed network

Topology Hybrid Networking Path Computation Layer 3 Tuesday, 2pm Operational View Friday, 3am Maintenance View IP View Virtual Organization Specific View User Specified Multiple Views What paths are possible between A and B, between time i and ii, with specific service interface request parameters? A B Path Computation Time Domain AAA Management (SNMP) Data Administrator Requirements Layer 2 Layer 1 PCE to PCE Coordination Domain Boundary Time Domain AAA Management (SNMP) Data Administrator Requirements Layer 3 Layer 2 Layer 1 Topology

Intelligent Resource Computation Path Computation will have handle multi-dimensional information and constraints that are typically not considered in current networks PCE Computing both paths and topologies for multi-layer networks hybridnetworkhybridnetwork Give me an IP overlay triangle topology with 500Mbps per link. Can I have a slice of 1 GigE VLAN with customer tag 300? I prefer paths with least jitter. What is available 8:00-10:00AM every Friday? Site B Site C Site A Ask PCE Application Specific Topology

Service Interface Definition Path TE Parameters (source, destination IDs, bandwidth, link switching type, etc) Path TE Parameters (source, destination IDs, bandwidth, link switching type, etc) Layer-Specific Params (MTU, VLAN Tags, SONET VC type, WDM wavelengths etc.) Layer-Specific Params (MTU, VLAN Tags, SONET VC type, WDM wavelengths etc.) Scheduling Params (start and end times, ranges of acceptable time windows, priorities) Scheduling Params (start and end times, ranges of acceptable time windows, priorities) QoS Parameters (bandwidth guarantees, latency, jitter, packet loss etc.) QoS Parameters (bandwidth guarantees, latency, jitter, packet loss etc.) Routing Profile (explicit routes, link inclusion and exclusion lists etc.) Routing Profile (explicit routes, link inclusion and exclusion lists etc.) Execution Method (hard,soft reservation, query only, schedule only, preemptible etc) Execution Method (hard,soft reservation, query only, schedule only, preemptible etc) Protection Capability (non-protection, 1:1, 1+1, shared mesh protection etc.) Protection Capability (non-protection, 1:1, 1+1, shared mesh protection etc.) Management Info. (auxiliary information for service monitoring and trouble shooting) Management Info. (auxiliary information for service monitoring and trouble shooting) AAA Information (parameters for user authentication and policy enforcement) AAA Information (parameters for user authentication and policy enforcement) Parameters by Categories The Service Interface framework defines hybrid network services. This definition should focus on service parameters, as opposed to network technology details. Network should be responsible for selection specific network provisioning operations based on service requests/requirements A service is defined by elements containing some of the above parameters. These services can be flexibly integrated into virtualization workflows and be discovered and invoked via standard mechanisms, such as Web Services. Value-Added Services Basic Operations request for single path Basic Operations request for single path Batch Operations request for a group of paths as atomic operations Batch Operations request for a group of paths as atomic operations Conditional Operations operations with conditional logic to support workflows Conditional Operations operations with conditional logic to support workflows Topology Services request for custom topology views and information Topology Services request for custom topology views and information

Monitoring and Debugging 1 USER API Web Browser 2 Management Agent 1. Circuit Request 2. Circuit Setup 3. Notification 4 4. User Indicates a problem in data plane 5. Additional (lower level) queries in local domain 6. Management Agent to Management Agent InterDomain Interactions 7. Remote domain local status checks Management Agent Management Agent looking for help from PerfSonar on this

Hybrid Network Research Sponsor Acknowledgement Multi-Layer Hybrid Networks –Funded by United States Department of Energy (DOE) –hybrid.east.isi.edu DRAGON (Dynamic Resource Allocation via GMPLS Optical Networks) –Funded by National Science Foundation (NSF) –dragon.east.isi.edu

Thank You! Questions/Comments?