[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: QoS attributes
thanks for raising this problem with cops. theoretically it also provides
roaming with the same concepts. however, from a deployment point of view it
was only used within a local domain. most operators don't want to setup the
same infrastructure (cops and radius/diameter) for inter-domain
communication only to support authorization for qos requests.
this is one of the problems we discovered when we looked at how rsvp
provides authorization for qos requests (there are other issues which are
described in the 'rsvp security properties' draft).
hence, we started working on the draft <draft-alfano-aaa-qosreq-01.txt>
which john mentioned.
john might have some additional comments beyond my description of the
history behind this draft.
> -----Ursprüngliche Nachricht-----
> Von: Jari Arkko [mailto:email@example.com]
> Gesendet: Freitag, 19. Dezember 2003 19:24
> An: 'firstname.lastname@example.org'
> Cc: Avi Lior; email@example.com
> Betreff: Re: QoS attributes
> Avi wrote:
> > ... COPS ... RADIUS/Diameter
> John, perhaps you can educate me a little bit regarding the use
> of COPS in these environments. How does roaming work? That is,
> if my home operator is in Finland but I'm in California and use
> a local ISP's QoS and COPS-based services -- does COPS have a
> concept similar to AAA proxies and multiple parties that take
> part in the "transaction"?
> to unsubscribe send a message to firstname.lastname@example.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 email@example.com with
the word 'unsubscribe' in a single line as the message text body.