A Framework for QoS Support in Mobile IP v6

Hemant Chaskar

Rajeev Koodli

draft-chaskar-mobileip-qos-00.txt

49th IETF, San Diego

December 15, 2000

Problem Statement

Mobile IP so far

Correct and efficient routing of packets

QoS support not addressed (yet)!

Re-programming forwarding treatment in intermediate

network domains subsequent to handover

Proposal

Perform QoS signaling along with Mobile IP signaling

Solution Overview

Introduction of QoS Object as an IPv6 extension header

option

Inclusion of QoS Object with Binding Messages

QoS Object Option (1/2)QoS Object Option (1/2)

Describes QoS requirement and traffic volume of MN's packet streams

A QoS Object corresponds to one unidirectional packet stream of MN

Composition of QoS Object

QoS Requirement (Traffic QoS Requirement (Traffic Class))Average Data Rate (32 Bit IEEE Flt. Pt.)Average Data Rate (32 Bit IEEE Flt. Pt.)

Token Bucket (32 Bit IEEE Flt. Pt.)Token Bucket (32 Bit IEEE Flt. Pt.)Peak Data Rate (32 Bit IEEE Flt. Pt.)Peak Data Rate (32 Bit IEEE Flt. Pt.)

Minimum Policed Unit (32 Bit Integer)Minimum Policed Unit (32 Bit Integer)Maximum Packet Size (32 Bit Integer)Maximum Packet Size (32 Bit Integer)

Packet Classification Parameters

Traffic Volume

Multi-Field (MF) Packet

Classifier

Inclusion of QoS Object with Binding MessagesInclusion of QoS Object with Binding Messages

QoS Object is included as Hop-by-Hop Option With BU for traffic from MN to CN With BA for traffic from CN to MN With BA for traffic from HA to MN

QoS Object is processed at the edges of QoS-enabled

network domains (DiffServ, MPLS, IntServ) and

transported transparently through the network domains

QoS Object Processing

MPLS Domain: Mapping to FEC, forward BU over LSP

DiffServ Domain: Program MF packet classifier, may consult bandwidth broker, core routers ignore QoS Object

IntServ Domain: Initiate RSVP within the network domain

Security Considerations

Denial of Service Attacks Caused by sending QoS Object too frequently Prevented by ignoring QoS Object if it arrives before a

fixed time interval

CoA Spoofing Demanding QoS by spoofing CoA AR should prevent CoA spoofing on the access link ERs should employ ingress filtering

No man-in-middle between two routers

Possible Optimizations

Micro-mobility

The proposed framework works seamlessly