-----Original Message-----
From: Avi Lior [mailto:avi at bridgewatersystems.com]
Sent: Tuesday, May 30, 2006 4:55 PM
To: Hannes Tschofenig
Cc: isalekul at hotmail.com; dime at ietf.org; Tschofenig,Hannes
Subject: RE: [Dime] Policy based Applications and QoS Application
Hi Hannes,
The discussion on MIPv6 bootstrapping is different. We know
that it is an Application we were just debating whether or
not we need to create a new Application ID.
QoS may be an application and it may also be an attribute
that is used by various applications.
While it may be difficult for the IETF to come up with a QoS
application that would work across many SDOs, it may be good
enough for DIME to define a standerdized QoS blob and have
SDOs pick it up as they work on SDO specific applications.
For vendors like us, providing products across SDOs, having a
standerdized QoS blob is adventageous. QoS Blob is
relatively complex, and requires a complex GUI for
provisioning it and also complex API.
Avi
-----Original Message-----
From: Hannes Tschofenig [mailto:Hannes.Tschofenig at gmx.net]
Sent: Monday, May 29, 2006 4:52 PM
To: Avi Lior
Cc: dime at ietf.org; isalekul at hotmail.com; Tschofenig, Hannes
Subject: Re: [Dime] Policy based Applications and QoS Application
Hi Avi,
thanks for raising this topic. Please find my response below;
Avi Lior wrote:
Hi All,
This email prompts me to start a discussion on Policy and
QoS Application.
As some of you are aware IMS Rel 7.0 has an entity called
PCRF. This
PCRF is supposed to broker per flow based policy actions
between the
IMS infrastructure and the Network. Initially this policy
was QoS and
in release 7.0 it also brokers Charging Policy. In the
future it will
probably broker other per flow policy. For example, it may
instruct
the network to apply security policies to a flow or group
of flows.
The QoS Application that is being developed by the IETF (IMO) was
targeting the Policy entity in its IMS Rel 6.0 form when it
was called
the PDF instead of PCRF and when it was only serving QoS
policies.
Now in rel 7.0 the Diameter application being developed
is serving
both QoS and Charging information and is based on the
Diameter Credit
Control function.
Also QoS policies are also delivered as part of
Authentication. So
EAP Application may be used to deliver initial QoS
policies to the
User session being authenticated and authorized.
I agree with you.
So I am raising the following questions:
1) Is there any reason to create a QoS Application in Diameter?
I guess your question is 'Does it need to be an application'
and thereby referring to question 3. In some sense we also
discussed
this question in context of MIPv6 Bootstrapping as well.
Are you concerned about the additional messaging or more about the
degree of flexbility.
2) Should we work on a Diameter Flow-based Policy
Application that is
able to deliver QoS/Charging and in the future other flow
based application?
-Should this work be done in the IETF? Do we get folks in
3GPP/3GPP2
and WiMAX to agree to work on this within the IETF. Or
perhaps we can
agree to work on this together outside the IETF?
>
3) Perhaps we should just define QoS based attributes that can be
pulled into various future Diameter Applications.
The last two approaches sound like interesting approaches we should
investigate.
Ciao
Hannes
Comments are welcome!!!
--------------------------------------------------------------
----------
*From:* Tschofenig, Hannes
[mailto:hannes.tschofenig at siemens.com]
*Sent:* Monday, May 08, 2006 4:23 AM
*To:* john.loughney at nokia.com; dime at ietf.org
*Cc:* isalekul at hotmail.com
*Subject:* AW: [Dime] FW: [AAA-WG]: Policy
representation for AAA server
Hi Salekul,
could you formulate your question in more detail?
What type of policies are you talking about? E.g.,
policies that
represent the business logic at a AAA server or
policies that are
conveyed from the AAA server to the AAA client? Are you
looking for
a language to express these policies or rather for the
content of
these policies? Do you have a specific application in
mind (e.g.,
policies regarding charging, QoS, location information)
Ciao
Hannes
--------------------------------------------------------------
----------
*Von:* john.loughney at nokia.com
[mailto:john.loughney at nokia.com]
*Gesendet:* Montag, 8. Mai 2006 10:10
*An:* dime at ietf.org
*Cc:* isalekul at hotmail.com
*Betreff:* [Dime] FW: [AAA-WG]: Policy
representation for AAA server
Forward to the DiME WG, in case any one has
opinions for Diameter.
John
--------------------------------------------------------------
----------
*From:* owner-aaa-wg at merit.edu
[mailto:owner-aaa-wg at merit.edu] *On Behalf Of
*ext Salekul Islam
*Sent:* 30 April, 2006 08:55
*To:* aaa-wg at merit.edu
*Cc:* Salekul Islam
*Subject:* [AAA-WG]: Policy representation for
AAA server
Hi,
I am interested in policy representation or
policy server in
Diameter architecture. Is there any Internet
Draft or paper
addressing the issues related to policy
representation for
AAA server? Is there any specific direction or
goal of the
WG regarding this issue?
Any sort of information will be very helpful for me.
regards,
Salekul Islam
PhD candidate, Concordia University
Montreal, Canada
--------------------------------------------------------------
----------
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime
_______________________________________________
DiME mailing list
DiME at ietf.org
https://www1.ietf.org/mailman/listinfo/dime
