1 / 22

Quality of IPv6 Service : To be considered

Quality of IPv6 Service : To be considered. Hyun-Kook Kahng Korea University kahng@korea.ac.kr. Contents. QoS in IP network IPv6 QoS QoS Signaling Protocols Conclusions. QoS. QoS means providing consistent, predictable data delivery service, satisfying end-user requirements.

gafna
Download Presentation

Quality of IPv6 Service : To be considered

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. Quality of IPv6 Service : To be considered Hyun-Kook Kahng Korea University kahng@korea.ac.kr

  2. Contents • QoS in IP network • IPv6 QoS • QoS Signaling Protocols • Conclusions

  3. QoS • QoS means providing consistent, predictable data delivery service, satisfying end-user requirements. • The problematic • Standardization • QoS will only be guaranteed under an End to End basis • Migration from IPv4 to IPv6 • This process will affect to the QoS through the adequateuse of the IPv6 fields • Backbone dimensioning • As users begin to demand QoS features, thedimensioning of the internal infrastructure, will have to be upgraded. • Adequate interplay among the different QoS enabling technologies • Especially by specifying coherence along the different protocol layers that avoidcounterworking among the solutions proposed.

  4. General QoS Principles • Integration Challenge ! • Separation Challenge !! • Transparency • Multiple Time scale • Performance • Simplicity • Scalability

  5. E-mail, FTP, Web TCP/UDP/RTP IPv4 (MIPv4) Ethernet Protocol Stacks E-mail, FTP, Web, AV conferencing, etc Signaling Application NSIS SP RSVP, DiffServ Signaling TP TCP/UDP/RTP IPv6, MIPv6 IEEE 802.11, MPLS, etc

  6. E-mail, FTP, Web, AV conferencing, etc Congestion Control Congestion Avoidance Flow Control Error Control Authentication Admission Control Resource Management Policing Flow labeling, Queue management, Traffic Shaping, Security, Mobility Labeling, Mobility, Security Mechanisms for supporting QoS requirements

  7. QoS Enabling Technologies QoS Enabling Technologies • Metrics • Availability • Throughput • Bandwidth • Packet Loss • Delay/Latency • Jitter • Security • Mechanisms • Packet Classification • Queuing & Scheduling • Mapping • Traffic Conditioning • Rate Limiting & Shaping • Optimization, Tuning(e.g., TCP) • - Congestion Control • - Flow Control • Traffic & Network • Management • Performance measurement • Traffic monitoring • Traffic engineering

  8. QoS requirements for certain types of service [source 1 ]

  9. Interactive Real Time Non-Interactive Real Time Non- Real Time Premium Delay 150ms 300ms 200 ms Jitter 3 ms 50 ms best effort Loss 1% 1% 2% Guarantee 99% 99% 98% Basic Delay 400ms 600ms 500ms Jitter 3 ms 100 ms best effort Loss 4% 5% 5% Guarantee 95% 95% 92% QoS User Requirements [source 2 : EURESCOM ProjectP906]

  10. Removed IPv4 vs IPv6 bit 0 bit 0 8 16 24 31 4 12 16 24 31 Version Class Flow Label IHL Service Type Total Length Version Identifier Flags Fragment Offset Next Header Payload Length Hop Limit Time to Live Protocol Header Checksum 32 bit Source Address 128 bit Source Address 32 bit Destination Address Options and Padding IPv4 Header 20 octets, 12 fields, including 3 flag bits + fixed max number of options 128 bit Destination Address Changed IPv6 Header 40 octets, 8 fields + Unlimited Chained Extension (options) Header

  11. IPv6-only QoS • Originally Best-Effort service through FCFS by a single packet Queue • Daisy chain of “Headers” • Flow-Label • Redefinitions Flow Label • Hybrid • Modified Hop-by-Hop Extension Header

  12. Redefinition of IPv6 Flow Labels (1) • DS with PHB Id • Following format can be used for the Flow Label: • DS with multi field classifier • The Flow Label classifier is basically a 3-element tuple • Port number and H-to-H protocol • The algorithmic mapping of the port numbers and protocol into the Flow Label. [Source 3 : draft-conta-ipv6-flow-label-02.txt]

  13. Redefinition of IPv6 Flow Labels (2) • TCP & UDP port • Using TCP server port number • Using UDP server port number • IPv6 headers length [source 3 :draft-conta-ipv6-flow-label-02.txt]

  14. Redefinition of IPv6 Flow Labels (3) • Hybrid • 000 Default • 001 Random number • 010 Hop-by-Hop extension header • 011 MFC • 100 Port # and TCP/UDP • 101 New definition [source 4 : draft-banerjee-flowlabel-ipv6-qos-03.txt]

  15. QoS Signaling Protocols • Bandwidth Management Algorithms/Schemes

  16. RSVP & DiffServ (1) • RSVP • More than expected [source 5 ] • Policy and Shaping increase the data path latencies [source 6,7] • DiffServ • Queuing Algorithm • Priority Queuing • WFQ • (W)RED • PHB • EF & AF for UDP traffic • AF not optional for TCP traffic

  17. RSVP & DiffServ (2) • Interoperation of RSVP & DiffServ • RSVP + DiffServ with Priority Queuing • RSVP + Best-Effort • Bandwidth Broker • DiffServ Admission Control • Aggregated Flow demand based AC • Measurement based AC • Congestion information • Probe packet

  18. Boomerang - A simple RSVP • Simple Implementation • Small Processing Load in Routers • Fast Reservation Setup • Low Protocol Overhead • No requirements on the Far-end Node [source 8: http://www.cs.inf.ethz.ch/37-235/studentprojects/farkas.pdf ]

  19. YESSIR - YEt another Sender Session Internet Reservations • Sender-initiated reservation • Robustness and soft-state • Allow partial reservations • Provide different reservation styles • Individual / Share • Low protocol and processing overhead • Interoperable with RTP and IntServ model • Provide link resource advertising functions [source 9]

  20. INSIGNIA • Very simple signaling mechanism for supporting QoS in mobile ad-hoc networks • Adaptive Services for continuous Media Flow and Micro-Flow support • Separation of Routing, Signaling and Forwarding • In-Band Signaling • Soft-State Management [source 10]

  21. E-mail, FTP, Web, AV conferencing, etc TCPng / UDP+ RSVP, DiffServ, RSVP-Lite, DiffServ+ IPv6 with “careful implementation” IEEE 802.11, MPLS, 3G/4G, etc Conclusions • All protocols and mechanisms should be revisited for QoS. • ITU-T X.641 QoS Framework, X.642 QoS Methods and Mechanisms

  22. reference • [source 1] B.Koch(AQUILA), D.Goderis(TEQUILA), R.Philips(TOREENT), Cisco, NGN-I Briefing Paper on QoS for IP Networks • [source 2] EURESCOM ProjectP906 • [source 3] IETF, draft-conta-ipv6-flow-label-02.txt • [source 4] IETF, draft-banerjee-flowlabel-ipv6-qos-03.txt • [source 5] Martin karsten, Jens Schmitt, and Ralf Steinmetz. Implementation and Evaulation of the KOM RSVP Engine. In Proceedings of the 20th Annual Joint Conference of the IEEE Computer and Communications Societies(INFOCOM'2001), April 2001, pp1290-1299 • [source 6] Tsipora Barizilai, Dilip Kandlur, Debanjan Saha, Ashish Mehra, Steve Wise; Design and Implementation of an RSVP-based Quality of Service Architecture for Integrated Computing Systems (ICDCS'97) • [source 7] Roberto Canonico, Simon Pietro Romano, Mauro Selitto, and Giorgio Ventre A Scheme for Time-Depedent Resource Reservation in QoS-Enabled IP Networks, Springer LNCS 1815, pp.81 • [source 8] http://www.cs.inf.ethz.ch/37-235/studentprojects/farkas.pdf • [source 9] [PaSc98] Ping Pan, Henning Schulzrinne, "YESSIR: A Simple Reservation Mechanism for the Internet". In the Proceedings of NOSSDAV, Cambridge, UK, July 1998. • [source 10] http://comet.ctr.columbia.edu/insignia/

More Related