Taskforce Mobility Mailarchive
|
Subject |
Re: CUI reloaded |
|
From |
Tomasz Wolniewicz <twoln@xxxxxx> |
|
Date |
Thu, 31 Jul 2008 11:54:46 +0200 |
Hi Stefan,
stefan.winter@xxxxxxxxxx wrote:
Well no, I would prefer to tell them to turn off accounting, regardless
of the fact if they want to use CUI or not. What business do you have
as the IdP administrator to know how many bytes your roaming users are
transferring and at which places? These bytes do not belong to you,
they belong to the SP. The SP is not charging IdP for these bytes, so
this information should not be made available in the name of protecting
user's privacy.
Well, that's a valid argument for most of Europe, yes, but there are
other regions without "flatrate" outbound connectivity, for whom it
actually is important to know how much traffic their users generated.
This situation led in Australia to the VPN-only solution, so that
users will generate outbound traffic originating in their home
institution. AFAIK, in AU it is being looked into replacing this with
sending accounting information for backoffice cross-inst compensation.
So, I would feel very bad dismissing Accounting completely.
Again, I would like to argue that, unless you are telling me that if a
user from our University is going to use eduroam in Australia than I am
going to receive a bill.
Are Australian universities charging each other form roaming? If not,
then I ask once again: what business do I have in knowing how many bytes
my user pushed while visiting Australia?
Concerning the FR support for doing the right thing in accounting -
sounds good. Even if accounting records are not proxied but stored
locally, this would be useful anyway.
Tomasz
--
Tomasz Wolniewicz
twoln@xxxxxx http://www.home.umk.pl/~twoln
Uczelniane Centrum Informatyczne Information&Communication Technology Centre
Uniwersytet Mikolaja Kopernika Nicolaus Copernicus University,
pl. Rapackiego 1, Torun pl. Rapackiego 1, Torun, Poland
tel: +48-56-611-2750 fax: +48-56-622-1850 tel kom.: +48-693-032-576