1 / 10

A Framework for Internetworking Heterogeneous High-Performance Networks via GMPLS and Web Services

niran
Download Presentation

A Framework for Internetworking Heterogeneous High-Performance Networks via GMPLS and Web Services

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. A Framework for Internetworking Heterogeneous High-Performance Networks via GMPLS and Web Services Xi Yang, Tom Lehman Information Sciences Institute (ISI) University of Southern California (USC)

    2. High-performance internetworking GMPLS based control plane (GMPLS-CP) and the DRAGON solution Heterogeneous high-performance internetworking framework Web services based control plane (WS-CP) Conclusions

    3. Why Multi-layer: Existing technologies IP is not enough Applications at different layers ? Pricing, scale, performance … app. characteristics (raw aggregate capacity, per flow QoS, fast recovery, low latency, low jitter, legacy equipment …) Future vision: Internet ? An evolution strategy Not because the multi-layer architecture design methodology… Multi-region … The Internet is not a result of perfect design from the beginning. It evolves by allowing multiple experimental technologies coexisting in the real networks. This philosophy has been proven a good one. Why Multi-layer: Existing technologies IP is not enough Applications at different layers ? Pricing, scale, performance … app. characteristics (raw aggregate capacity, per flow QoS, fast recovery, low latency, low jitter, legacy equipment …) Future vision: Internet ? An evolution strategy Not because the multi-layer architecture design methodology… Multi-region … The Internet is not a result of perfect design from the beginning. It evolves by allowing multiple experimental technologies coexisting in the real networks. This philosophy has been proven a good one.

    8. OK That’s about the DRAGON solution. We have been focused on GMPLS technologies. Here I want to present some thoughts beyond DRAOGN and beyond GMPLS. In our recent research paper, we proposed a framework … The main point is that … GMPLS is good and probably the only true … However, we should not be limited tight coupling ? Leak topology information, allow external signaling to directly control internal equipment loose coupling vs. GMPLS ? Web services Web services security architecture OK That’s about the DRAGON solution. We have been focused on GMPLS technologies. Here I want to present some thoughts beyond DRAOGN and beyond GMPLS. In our recent research paper, we proposed a framework … The main point is that … GMPLS is good and probably the only true … However, we should not be limited tight coupling ? Leak topology information, allow external signaling to directly control internal equipment loose coupling vs. GMPLS ? Web services Web services security architecture

    10. The actual definitions are much more complicated. But this should give a taste of what the WS-CP will be like … Implementation Strategies Networks have three control-plane options: GMPLS-CP, WS-CP and Hybrid (WS routing and GMPLS signaling) Web services Security (WSS) architecture and service discovery mechanism, e.g., UDDI, provide solid foundation Sufficient know-how, standardization, toolkits, engineers and user adoption for Web services related development Performance Considerations Web services processing overhead and latency, bulky XML metadata ? Can be improved by well-structured topology/ resource description language based on WS-RDF Web services are normally ‘pull’ style, lacking the mechanisms of flooding and notification. ? Can be improved by WS-Notificaiton and WS-Eventing (specifications, the work in progress) The actual definitions are much more complicated. But this should give a taste of what the WS-CP will be like … Implementation Strategies Networks have three control-plane options: GMPLS-CP, WS-CP and Hybrid (WS routing and GMPLS signaling) Web services Security (WSS) architecture and service discovery mechanism, e.g., UDDI, provide solid foundation Sufficient know-how, standardization, toolkits, engineers and user adoption for Web services related development Performance Considerations Web services processing overhead and latency, bulky XML metadata ? Can be improved by well-structured topology/ resource description language based on WS-RDF Web services are normally ‘pull’ style, lacking the mechanisms of flooding and notification. ? Can be improved by WS-Notificaiton and WS-Eventing (specifications, the work in progress)

More Related