Irish ipv6 task force
1 / 26

Irish IPv6 Task Force - PowerPoint PPT Presentation

  • Uploaded on

Irish IPv6 Task Force. IPv6 and Quality of Service. Irish IPv6 Task Force IPv6 Training Slide-sets. The Bigger Picture: Why is IPv6 so Important? Introduction to IPv6 Fundamentals (technical) IPv6 Deployment & Strategy (technical) The Business Case for IPv6 Mobile IPv6 (technical)

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Irish IPv6 Task Force' - marlie

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Irish ipv6 task force l.jpg

Irish IPv6 Task Force

IPv6 and Quality of Service

Irish IPv6 Task Force -

Irish ipv6 task force ipv6 training slide sets l.jpg
Irish IPv6 Task ForceIPv6 Training Slide-sets

  • The Bigger Picture: Why is IPv6 so Important?

  • Introduction to IPv6 Fundamentals (technical)

  • IPv6 Deployment & Strategy (technical)

  • The Business Case for IPv6

  • Mobile IPv6 (technical)

  • IPv6 Quality of Service (technical)<- This slide set is sixth in a series

  • IPv6 Security (technical)

Slide3 l.jpg

Presentation Structure

  • Introduction

  • What is QoS?

  • How is it used?

  • How is it implemented?

  • What is its current state in the Internet?

  • How does IPv6 fit into the QoS picture.

Slide4 l.jpg

IPv6 and QoS –


Introduction l.jpg

  • Quality of Service (QoS).

  • Sometimes said “Kwos”.

  • Many things to many people.

  • Basically: making network good enough for apps.

Qos what is the aim l.jpg
QoS: What is the aim?

  • Network needs to be good enough.

  • How do we measure good?

    • Enough bandwidth?

    • Enough buffering?

    • Short enough delay?

    • Consistent enough delay?

    • Enough packets arrive intact?

  • Often summarised as delay, loss, jitter, bw, …

Qos typical uses l.jpg
QoS: Typical Uses

  • Video/Voice traffic more sensitive than bulk data.

  • Safety critical traffic may be protected.

  • ISPs may prioritise premium customers.

  • Netadmins may protect control traffic (BGP, ssh, …)

  • Gamers don’t want to get fragged!

  • Preventing virtual links from interacting.

  • Interactive applications usually have some QoS needs.

    • Dialup and the World Wide Wait.

Qos how to achieve l.jpg
QoS: How to achieve?

  • If network is big and empty, QoS is easy.

    • Known as overprovisioning.

  • Otherwise identify traffic’s needs.

  • Treat traffic differently based on needs.

  • (Im)Possible to meet some/all needs?

Qos architecture l.jpg
QoS Architecture

  • We need to -

    • identify the traffic.

    • check that it is in spec.

    • decide how to queue it.

    • decide how to serve the queues.

    • manage, account and configure all this.

Intserv l.jpg

  • One of two standardised frameworks for IP QoS.

  • Hosts ask routers to treat particular flow specially.

  • They use the Reservation Protocol (RSVP).

  • It describes how to match packets and required QoS.

  • Each router has to track each flow.

  • Signalling and tracking makes scaling harder.

Diffserv l.jpg

  • Offer applications a short menu of QoS types.

  • Type required is written into small field in packet.

  • Menu items are called Per-Hop-Behaviours (PHB).

  • The field is called the Differentiated Services Code Point (DSCP) value.

  • Routers look at packets and decide how to queue.

  • Limited menu may not suit all apps.

  • No active negotiation, so need to police settings.

  • All traffic with same DSCP is treated in same way.

Manual ad hoc l.jpg
Manual/ad hoc

  • Manual configuration always an option.

  • May partially fit into some bigger scheme.

  • Examples:

    • 802.11 gives some control packets high priority.

    • A 3G operator might make Skype packets low priority.

    • A router might move BGP packets to head of queue.

Qos today l.jpg
QoS Today

  • Not widely deployed in public Internet.

  • Inter-network issues too great relative to demand?

    • Inter ISP policing, monitoring, charging, …

  • DiffServ and manual more widely deployed in ISPs and enterprise networks.

  • Most common solution is lots of bandwidth.

  • Becoming more common in home appliances with VoIP and video streaming.

  • Wireless an interesting case - overprovisioning much harder.

Ip v6 and qos l.jpg
IP(v6) and QoS

  • Any packet matching system must be able to deal with IPv4/IPv6 packets.

  • Often involves fields in TCP/IP headers, such as addresses, protocols and ports.

  • Need to extend to be able to deal with IPv6 addresses.

  • The DSCP value lives in the Type of Service (ToS) field in IPv4.

  • The DSCP value lives in the Traffic Class (TC) field in IPv6.

Ipv6 flow label l.jpg
IPv6 Flow Label

  • IPv6 has new flow label header.

  • 20 bits to identify flows.

  • Determined by end hosts.

  • Intended to facilitate QoS.

  • Could be used by IntServ to pick out flows.

  • Might help identify encrypted flows for QoS.

  • No final answer yet, but additional flexibility.

Ipv6 side effects l.jpg
IPv6 Side Effects

  • Less NAT means flows easier to identify

  • Better mobility -> better network path -> better QoS.

  • IPv6 extension headers may be applied to QoS in future.

  • IPv6 transition mechanisms can lead to poor performance if carelessly deployed!

  • E.g. Many tunnels in 6bone lead to scenic routing.

    • 6bone now retired and production routing is being refined.

  • QoS and IPv6 support are often considered advanced features, vendors sometimes unclear about their interactions.

  • Slide22 l.jpg


    • QoS allows traffic with special requirements to be treated specially.

    • DiffServ and manually configured QoS have some deployment.

    • As long as IPv6 packets can be classified, QoS in the IPv4 and IPv6 looks similar.

    • The IPv6 Flow Label is intended to facilitate QoS flow identification.

    Acknowledgements l.jpg

    This presentation includes some material from these other sources:

    • Name of person/people ???


    Contact l.jpg

    Mícheál Ó Foghlú

    Research Director

    Telecommunications Software & Systems Group

    Waterford Institute of Technology

    Cork Road



    +353 51 302963 (w) (Personal Blog)

    Further information l.jpg
    Further Information

    Web Sites:

    • National Irish IPv6 Centre

    • Irish IPv6 Task Force

    • IPv6 ePrints Server (Public Documents)

    • IPv6 Dissemination (Public Training)

      Individual Documents/Presentations:

    • (Iljitsch van Beijnum, 7th March 2007)

    • (Geoff Huston APNIC, 2006)

    • (IPv6 Forum Roadmap & Vision, 2006)

    • (Doug Montgomery NIST, 2005)

    Slide26 l.jpg

    Thank you!This presentation has been shared under the Creative Commons Attribution 2.0 UK: England & Wales Licence( the Irish IPv6 Task Force( acknowledge this source if you use it for free or for profit

    Irish IPv6 Task Force -