[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: QoS attributes
- To: <email@example.com>
- Subject: RE: QoS attributes
- From: "Joel M. Halpern" <firstname.lastname@example.org>
- Date: Tue, 23 Dec 2003 15:17:13 -0500
- In-reply-to: <A675D99D53706742B50619249A8EBF04832D08@MAANDMBX2.ets.enter asys.com>
This presume a very simple consortium model. At the very least I would
expect hot spot operators to be planning to participate in multiple
consortia, so as to offer service to the widest range of customers. Those
distinct consortia are not likely to have the same collections of QoS sets.
Joel M. Halpern
At 03:02 PM 12/23/2003 -0500, Nelson, David wrote:
If the partners in a roaming consortium can't agree on a few, simple
classes of service for QoS that will be comprehensible to the customer
as he/she roams, and will be amenable to straightforward billing and
reconciliation at the end of the month, then the business model is
profoundly broken, and no protocol in the world is going to fix it. At
least that's my view of the situation. Sometimes too much flexibility
is a severe impediment to scalability, especially across multiple
organizations. I think maybe the KISS model applies here.
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.