1 / 14

Resource Reservation over IP and ATM networks

Resource Reservation over IP and ATM networks. Silvia Giordano EPFL ICA March, 1998. 1. QoS Today. Applications are TCP/IP based to provide QoS: IP with more than best effort end-to-end ATM negotiation (renegotiation) native ATM or Arequipa. 2. IP with more than best effort. RSVP

sven
Download Presentation

Resource Reservation over IP and 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. Resource Reservation over IP and ATM networks Silvia Giordano EPFL ICA March, 1998 1

  2. QoS Today • Applications are TCP/IP based • to provide QoS: • IP with more than best effort • end-to-end ATM • negotiation (renegotiation) • native ATM or Arequipa 2

  3. IP with more than best effort • RSVP • precise and efficient reservation • soft state • scalability • Differentiated Service and SRP • scalability for large number of flows • traffic aggregation

  4. End-to-end ATM Today • negotiation and renegotiation • negotiation of connection parameters before establishing the connection (negotiate bw - UNI 3.x 4.0) • modification of connection parameters while the connection is active (renegotiate bw - ITU Q.2963.1) • native ATM or Arequipa 3

  5. Renegotiation • Connection remains active during modification: • applications still send data at the original PCR • original PCR is used if modification fails • shorter latency and less processing: • modification messages are small • ATM Network performs not addressing, routing (only CAC) 4

  6. Arequipa • Application driven shortcuts • no changes in the networks • uses 2 networks in parallel: ATM and Internet • completely integrated in TCP/IP 6

  7. VIC: videoconference MBone tool • make QoS visible to the users • user chooses a simple PCR only 7

  8. BW Renegotiation: Arequipa for VIC 24 Oct. 1997 8

  9. BW Renegotiation: Arequipa for VIC 9

  10. Implementation: • ATM Forum UNI 4.0 and renegotiation (ITU Q.2963.1) for: • ATMLight Ring - ASCOM • ATM on Linux 10

  11. Conclusion (1) • Resource Reservation is simple to use on the end-to-end system side • IP is the only end-to-end solution • end-to-end ATM should use something like Arequipa to preserve TCP/IP environment 12

  12. Conclusion (2) • end-to-end ATM is only for niche applications, otherwise IP • majority of applications will require priority IP service (RSVP, differential service, SRP) 13

  13. Who • Arequipa: W. Almesberger, J-Y. Le Boudec, Ph. Oechslin • Demo97: ASCOM, ASPA, EPFL, SWISSCOM, TIK • cookbook & paper 97: W.Almesberger, L. Chandran, S. Giordano, J-Y. Le Boudec, R. Schmid • SRP: W. Almesberger, T. Ferrari, J-Y. Le Boudec 14

  14. References • Arequipa: http://lrcwww.epfl.ch/arequipa/ • Demo97: http://lrcwww.epfl.ch/WebOverATM/vic.html • cookbook: http://lrcwww.epfl.ch/WebOverATM/ • paper 97: http://lrcwww.epfl.ch /~giordano/vpf2.ps • SRP: ftp://lrcftp.epfl.ch/pub/people/almesber/pub/srri.ps.gz • full paper: http://lrcwww.epfl.ch/~giordano/Heid.ps 15

More Related