1 / 18

Implementing the Integrated Services QoS model with IPv6 over ATM Networks

Implementing the Integrated Services QoS model with IPv6 over ATM Networks. D. Fernández 1 , D. Larrabeiti 2 , A.B. García 1 , A. Azcorra 2 , L. Bellido 1 , J. Berrocal 1 1 Dpto. Ingeniería de Sistemas Telemáticos Universidad Politécnica de Madrid, Spain

clive
Download Presentation

Implementing the Integrated Services QoS model with IPv6 over ATM 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. Implementing the Integrated Services QoS model with IPv6 over ATM Networks D. Fernández1, D. Larrabeiti2, A.B. García1, A. Azcorra2, L. Bellido1, J. Berrocal1 1 Dpto. Ingeniería de Sistemas Telemáticos Universidad Politécnica de Madrid, Spain 2 Area de Ingeniería Telemática Universidad Carlos III de Madrid, Spain E-mail: david@dit.upm.es, WWW: www.dit.upm.es/bti

  2. Contents • BTI Project Description • IntServ over ATM with IPv6 • BTI Applications & Scenarios • PATAM Integrated Protocol Stack • Conclusions

  3. Broadband Trial Integration (BTI) ACTS Project AC362 (1998-1999) Objectives: NETWORK: Development/Integration of IntServ QoS controlled broadband access network based on IPv6, RSVP, NHRP and ATM with multicast SVCs APPLICATION: Development/adaptation of tele-education applications enhancing them with QoS control TRIALS: Evaluate network and applications by means of international trials with real users in Cracow, Copenhagen and Aveiro. Verify design principles and implementation and make usability tests.

  4. IP and ATM Integración SVC Access ATM 25 Mbps SDH LT ONU Optical Distribution Network fibre Access Node NT Feeder OLM Network TE xDSL SDH ONU APON LT NT Content IP ATM LT Server router ATM 25 Mbps Qos App. Qos App. IP IP IP AAL5 AAL5 AAL5 AAL5 ATM ATM ATM ATM ATM ATM ATM ATM SDH SDH SDH SDH SDH PON PHY PON xDSL xDSL PHY SDH Protocol Architecture IP layer IPv6 / RSVP UNI 4.0 ATM layer UNI 4.0 Signalling and Control Plane BTI Network

  5. BTI Applications • Video on Demand (UKR-Cracovia) • Based on ORACLE video server • Videoconference (CCIR-Edimburgo) • Based on MBONE applications (VIC y RAT) • Cooperative applications (DIT-UPM) • Based on LEVERAGE ACTS project apps. • All of them were migrated to IPv6 and enhanced with QoS control capabilities

  6. Based on LEVERAGE ACTS Project applications Shared Workspace (DIT-UPM) • session desktop • chat tool • shared text editor • shared web browser • shared whiteboard

  7. RSVP reserv. dynamic membership m-point session(centralized ctrl) Video Retrieval Service (Cracow University ) • MPEG1 SIF • textual descriptions • search by category / keyword

  8. internet layer IPv4 IPv6 Neighbour Discovery convergence layer IPv4 over LAN IPv4 over ATM IPv6 over LAN IPv6 over ATM ARP ATMARP subnet layer LAN ATM LAN ATM IPv6 over ATM with IntServ QoS • IPv4 over ATM: • PVC: static routes and ATMARP tables • SVC: - ATMARP for address resolution - MARS for multicast • IPv6 over ATM with SVC: • Multicast must be supported by subnets • No need for ATMARP Router IP ATM • IntServ over ATM: • Best Effort traffic  UBR o ABR • RSVP reservations  multipoint CBR or VBR ATM circuits Hosts

  9. No QoS support MARS Server MARS Server ATM ATM MCS Hosts Hosts VC mesh Multicast Server IP multicast over ATM: MARS • MARS modes of operation:

  10. PATH P2P with MARS server ClusterControlVC Multicast BE RESV RESV Unicast BE Multicast CBR Example scenario (I): One source and two sinks Router + MARS server (Telebit) Client3 Client1 ATM Client2

  11. Example scenario (II): Three sources and three sinks Router + MARS server (Telebit) Client3 Client1 ATM P2P with MARS server ClusterControlVC Multicast BE Unicast BE (bidir) Multicast CBR Client2

  12. Contribution to BTI • Adaptation of Shared Workspace Applications developed in LEVERAGE ACTS project to BTI IPv6/ATM/IntServ network. • Development and integration of a protocol stack for Windows NT that supports: • IPv6 over ATM using SVCs • With IPv6 Multicast over dynamic multipoint ATM SVCs • RSVP over IPv6 • Traffic control over ATM interfaces

  13. IPAM TCM VCMM PFM MARS Client VCDB ATAM FORE ATM SP IPv6+RSVP+ATM Implementation BTI Applications Winsock2 API Conversion Module MSR IPv6 IPv6 IO Interface RSVP Daemon (ISI) IP over ATM Adap. Module PATAM Traffic Control

  14. IPv6 over ATM driver Architecture MSR IPv6 Stack PATAM IPv6 Access (IPAM) RSVP daemon Traffic Control Module Packet Forwarding Flows Database Classifier Receiver MARS Client Scheduler ATM Access Module (ATAM) ATM card drivers

  15. Lines of Code Module Original New Total MSR-IPv6 60.000 2.000 (kernel) 62.000 PATAM 7.000 14.500 21.500 RSVP 37.000 12.000 49.000 Test Apps. 0 4.000 4.000 104.000 32.000 136.000 Code Reused • IPv6 from Microsoft Research • RSVP daemon from ISI • MARS client of NIST • Proxy driver from Microsoft

  16. Conclusions (I) • Feasibility of implementing dynamically provided QoS using IPv6 and ATM. • The approach chosen provides a tight way of controlling network resources in an access network. • However: • Complex • Scalability is compromised: too many ATM circuits!! • Aggregation of flows (relaxing IntServ model) • Improvements to multicast signalling (MLD vs. MARS) • Enhance MCS mode with QoS support • Difficult development • Instability & Interoperability problems (ATM) • Lack of advanced APIs (e.g. to integrate IPv6 & RSVP)

  17. Conclusions (II) • From applications developers point of view: • Migration to IPv6 simple • QoS control: two API, data + QoS • Coordination made by applications • Can be cumbersome (ports, multiple IPv6 addresses: link-local, site-local, global, etc) • Integrated QoS API needed!! (e.g. GQOS) • Some applications required important modifications to adapt them to BTI network: • Cooperative applications  aggregation of all traffic to use a shared reservation

  18. Acknowledgements • This work has been partly supported by the EU Commission under the ACTS project 362 BTI. • We would like to thank all the partners involved in BTI for their positive collaboration and contribution to the project success. • PATAM Protocol Stack. Available at: http://www.dit.upm.es/bti (source code available upon request: david@dit.upm.es) Thanks for your attention

More Related