[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
push & pull (Was: Re: comments on draft-adrangi-radius-bandwidth-capability-00.txt)
Hi Farid,
Ok. After a second read of the relevant parts in the document
I think I understand this. But it still seems that in order
for this functionality to be useful, the contents of the
advertisement must vary during the session, e.g., due to
other traffic through the AN. Otherwise it would be
sufficient for the HSN to rely on the initial advertisement, no?
Yes. However, There is no guarantee that the content of the
advertisement will be different from the initial one. This provides an
option for an HSN to receive a fresh advertisement (same as or different
from the initial one) before doing the Selection. So, are we in
agreement on this one?
I have not formed my opinion yet. Let me explore this a little
further: if we assume that due to other traffic load in the
access point, the advertisements vary. For instance, an initial
advertisement may have said that 50 Mbit/s is available, but
after getting some other sessions, the access point can now
offer just 5 Mbit/s for this session. This brings up two
interesting questions:
1. Is the home network's bandwidth decision based
on the advertisements? This seems natural, but
are you sure its not a "provide this if you can"
scenario? The only case where I'd see the advertisement
affecting a real decision would be if the user's
decision to buy some additional bandwidth would be
affected as well. For instance, the web page where
he can buy more bandwidth shows the available
bandwidth based on the advertisement. Is this what
we want?
(Otherwise accounting will take care of the actually
provided service and its cost.)
2. Are the Confirmed bandwidths binding? If they
are not, the available bandwidth may change
5 seconds after the reception of the COA, which
appears to make the advertisement pointless.
--Jari
--
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/>