Download mobopts-2

Policy and Mobility
MOBOPTS RG, IETF #67, San Diego, Ca
Jouni Korhonen
Rajeev Koodli, Vijay Devarapalli, Gerardo
Giaretta
Motivation
• Work has been done @IETF on enabling fast
handovers at L3 and extensions to access
control protocols to enable fast handovers
• One aspect that has not been considered so far
are the policies that a user is subjected to when
accessing a subscribed network. These policies,
defined by the network operator, may have a
significant impact on the user's mobility
experience
Motivation cont’d
• The policies configured on a network may
govern:
– what kind of service the user is allowed
– which access network the user is allowed to
attach to
– enforce a particular quality of something (QoS)
– restrict the user to certain mobility protocols
Background
• In the last MOBOPTS @IETF#66 there
was a presentation about policies and
mobility in general
– ”Policies and how they affect IP Mobility”
• An action point was given:
– ”To document the problems encountered in
applying IP mobility due to policy
constraints…”
What Happened Since IETF #66
• A new I-D is actually under the process
– ”IP Mobility and Policy Control”
– Missed the -00 deadline though.. ;^)
Next steps
• The main purpose of the tbd I-D is to describe
the problems encountered when applying IP
Mobility protocols to networks where operator
defined policies and the resulting constraints
exist
• This could be useful to protocol designers who
can make better choices when designing IP
Mobility protocols and to network designers who
develop the policy architecture and configure the
policies.
Topics to be covered..
• Brief intro to ’current’ IP mobility @IETF
• Policies in operator controlled environment
– General taxonomy
– Firewalling & access restrictions
– Case study: 3GPP Policy & Charging Control
(PCC) architecture (as it seems to have gained
some momentum recently...)
• Identified issues in integrating IP Mobility
and policies
Locigal PCC Architecture (roaming)
Visited Domain
Home Domain
+--------------------------+
+--------------------------+
| +--------+
|
|
+--------------+ |
| | Proxy |--------------------------------------| OCS
| |
| | OCS
|
|
|
|
| |
| +--------+
|
| +----+ +--------------+ |
|
|
|
| | AF |
|
|
|
|
| +----+
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
+--------+ |
| +--------+ +-----+
|
|
|
| V-PCRF |----------------| H-PCRF |--| SPR |
|
|
|
+--------+ |
| +--------+ +-----+
|
|
|
|
|
|
|
|
|
|
|
|
|
| +----------------------+ |
|
|
| | V-PCEF & GW
| |
|
|
| +----------------------+ |
|
|
|
|
|
|
|
|
|
|
|
|
| +------+
+--------+ |
| +--------+
|
| | OFCS |------| BSyst |----------------| BSyst |
|
| +------+
+--------+ |
| +--------+
|
|
|
|
|
+--------------------------+
+--------------------------+
• PCC is not only
about access
policies
• Involves different
charging
systems...
• Policy databases
• Selected
applications affect
policies
• Access technology
agnostic
Questions & comments?