[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: QoS attributes

I have been watching this exchange, and I am somewhat puzzled.
We all seem to agree that the interesting case is roaming.
There then seem to be a set of unstate assumptions about what the business relationships are between the roaming and home operators, and their relationship to the promises made to the customer.

I can imagine a model in which sending platinum / gold / silver / tin / copper is meaningful. But that is a specific model where the customer has been told "you will get the negotiated corresponding service level from roaming partners", and part of the business negotiation is to define what the correspondences are.

THis is a defensible model.  It can even be extended to consortia, etc.
But it seems unlikely to be the only model.

One could easily imagine a model where the business relationship says "as a roaming operator we will support whatever QoS you would like to give your customers, and here is the price list." Without a lot of work this does not map to a colored service model, since the relationship does not require picking levels in the business relationship, and the services to different roaming partners may well be chosen differently by those partners.

I suppose that we could assert that the interpretation of the QoS colors by the roamer is to be influenced by the domain of the subscriber. But that seems to be asking an awful lot of other parts of the system.

Am I misunderstanding the discussion?

Joel M. Halpern

At 10:06 PM 12/22/2003 +0200, Jari Arkko wrote:
Nakhjiri Madjid-MNAKHJI1 wrote:

My issue still is (without getting into specifics of QoS or WLAN parameters) how can bundle the parameters in a way that not every
single parameter has to be listed in a RADIUS RFC?

Oh that's easy -- we can just put it in some opaque string, vendor specific attribute, or design some OID hierarchy around the parameters.

But the question is do we want to? The hard issue is how all this works
without buying the whole network from one vendor. Or how a home server
can control parameters in a roaming situation when it has never even
heard of the link technology that the foreign network uses. Essentially,
there would have to standardization of the parameters. Whether or not
that happens inside a particular IETF RFC is another question.

Maybe the best we can do at the moment is this Gold-Silver-Etc
service level classification. Or perhaps we could do that, and
the specific, more detailed parameters for a popular link layer,
such as 802.11 wireless LANs.


-- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>

to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>