1 / 21

Research Challenges in the Emerging Hybrid Network World

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:

carver
Download Presentation

Research Challenges in the Emerging Hybrid Network World

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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

  3. Hybrid Network ServicesRationale 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.

  4. 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

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

  6. Hybrid NetworkingDeployments in U.S. • Internet2 ION Service • www.internet2.edu/ion/ • Layer 1.5 network • Energy Sciences Network (ESnet) Science Data Network (SDN) • www.es.net • Layer 3/2.5 network • USLHCnet • lhcnet.caltech.edu • Layer 1.5/2 network • Multiple Regional Networks • Layer 2 networks

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

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

  9. Hybrid NetworkingWhat is State of Control Plane? • Current control plane implementations in U.S. are based on: • OSCARS • www.es.net/oscars • DRAGON • dragon.east.isi.edu • The client-to-network and network-to-network protocol definitions are based on: • DICE InterDomain Controller Protocol (IDCP) • www.controlplane.net

  10. 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 • www.controlplane.net

  11. DICE IDCPConceptual View of the Messaging • Four Primary Web Services Areas: • Topology Exchange, Resource Scheduling, Signaling, User Request

  12. Hybrid Network Services Footprint

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

  14. 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)

  15. 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

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

  17. Intelligent Resource Computation Ask PCE Give me an IP overlay triangle topology with 500Mbps per link. hybrid network • 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 Site B Can I have a slice of 1 GigE VLAN with customer tag 300? Site A Site C I prefer paths with least jitter. What is available 8:00-10:00AM every Friday? Application Specific Topology

  18. Service Interface Definition 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 Parameters by Categories Value-Added Services Path TE Parameters (source, destination IDs, bandwidth, link switching type, etc) QoS Parameters (bandwidth guarantees, latency, jitter, packet loss etc.) Layer-Specific Params (MTU, VLAN Tags, SONET VC type, WDM wavelengths etc.) Basic Operations request for single path Batch Operations request for a group of paths as atomic operations Routing Profile (explicit routes, link inclusion and exclusion lists etc.) Scheduling Params (start and end times, ranges of acceptable time windows, priorities) Execution Method (‘hard’,‘soft reservation’, ‘query only’, ‘schedule only’, ‘preemptible‘ etc) Conditional Operations operations with conditional logic to support workflows Management Info. (auxiliary information for service monitoring and trouble shooting) Protection Capability (‘non-protection’, ‘1:1’, ‘1+1’, ‘shared mesh protection’ etc.) AAA Information (parameters for user authentication and policy enforcement) Topology Services request for custom topology views and information 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.”

  19. Monitoring and Debugging 1. Circuit Request 2. Circuit Setup 3. Notification 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 6 Management Agent 6 Management Agent Web Browser USER API 4 7 7 5 3 1 2 looking for help from PerfSonar on this

  20. Hybrid Network ResearchSponsor 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

  21. Thank You! Questions/Comments?

More Related