1 / 13

Routing Based on Outdated Information in MultiDomain MultiLayer Networks

János Szigeti János Tapolcai Tibor Cinkler. Routing Based on Outdated Information in MultiDomain MultiLayer Networks. High-Speed Networks Laboratory Dept. of Telecommunications and Media Informatics Budapest University of Technology and Economics. Outline. Motivations Standardization

aolani
Download Presentation

Routing Based on Outdated Information in MultiDomain MultiLayer Networks

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. János Szigeti János Tapolcai Tibor Cinkler Routing Based on Outdated Information in MultiDomain MultiLayer Networks High-Speed Networks Laboratory Dept. of Telecommunications and Media Informatics Budapest University of Technology and Economics

  2. Outline • Motivations • Standardization • Our approach • Gaps • Tests & Results • Conclusion

  3. Motivations • Optical • Multilayer • Fault tolerant • Scalable • Supports standards

  4. Standardization • Institutions: • ITU-T • IETF • OIF • ATM Forum • Covered Issues • Network planes (ASON/ASTN) • Source routing (GMPLS) • Interfaces (E-NNI)

  5. ASON Control Plane GMPLS data encapsulation levels: • fibre • wavelength • timeslot (grooming) • packet

  6. GMPLS Layers Data encapsulation levels: Fibre, Wavelength,Timeslot (grooming), packet

  7. OIF-UNI/E-NNI • Neighbor (topology) discovery • Service discovery • (Abstract) reachability information • (Abstract) signalling for connection Setup / Release

  8. Existing Inter-Domain Routing Approaches • OSPF+BGP4 • IP terminology • Hop-by-hop routing • traffic engineering is difficult when applying protection schemes • PNNI • very scalable solution • loss of important information (overaggregation)

  9. Our Solution • Topology aggregation supports • “Explicit” source routing • Sub-lambda connections • Resilience issues • Call control • Based on OIF specifications • Information • consistent • periodically flooded

  10. Topology discovery and RWA Problems: • Aggregated edges WL to WL (simple if ALL/NONE of the border nodes is WL converter) • Insufficient information about destination domain • Aggregation of other metrics

  11. Tests, Results • Hypotetical topology • Varied attributes: • traffic (Poisson(λ,ν)) • refresh intervals • maximal setup delay • Measured • Blocking ratio for inter-domain setups • Average setup delay

  12. Results Longer refresh periods cause higher blocking ratio Maximal setup delay time does not influence the blocking ratio significantly

  13. Conclusions • Topology aggregation in multilayer networks is not simple • Inter-domain routing based on stalled information: • Trade-off between flooding and accuracy • Information refresh period length has a roughly linear relation to the blocking ratio

More Related