Chargeable-User Sample Clauses

Chargeable-User. Identity Chargeable-User-Identity (CUI), as defined in [RFC4372], was designed primarily for accounting support. In eduroam, its main use is to provide a persistent User ID support. The main concepts and use cases are described in RadSec Standardisation and Definition of eduroam Extensions [DJ3.1.1]. This document presents the details of actual implementations. The general concepts were developed during work on the FreeRADIUS implementation, which has served both as a proof-of-concept and testing ground for new ideas. The main goals of the implementations are as follows: • The final RADIUS packet of a successful authentication (Access-Accept) should carry a CUI RADIUS attribute, containing an identifier which can be used by the visited eduroam site to recognise the user on return. • CUI values, while being persistent, should not be traceable to a particular person without cooperation from the user's home institution. • CUI values should be different for every visited institution, so it is not possible to create behavioural profiles of users. • CUI support should include RADIUS-Accounting. Upon receipt of an Accounting-Request packet from a Network Access Server, the server can supplement it with a proper value of a CUI, making accounting much more meaningful. CUI support clearly differentiates between both co-operating parties, the visited institution (acting as SP) and the authenticating institution (acting as IdP). The SP is interested in being able to merge various user sessions and requests the IdP to supply CUI values. The IdP responds to these queries, generating CUI responses. In spite of the fact that most eduroam institutions are at the same time both and SP and IdP, it makes sense to clearly separate these roles in software implementation. Note one particular case: when an institution uses eduroam as its local network and authenticates its own users. This is conceptually different from eduroam used for guest access for two reasons: no packet proxying appears in this process and, more importantly, the institution is able to recognise its own users, since it is responsible for authentication (and does not require CUI for that). However, the functionality brought by CUI can be a very welcome addition for local administrators. One use of the attribute is in local RADIUS accounting support, which will become more valuable because the accounting packets are then immediately linked to the actual user. Another use is in local blacklisting of users. Even ...
Sample 1
AutoNDA by SimpleDocs

Related to Chargeable-User

  • Direct Charges To the extent Cash-based Expenses are incurred by the Contractor, the Contractor shall be reimbursed for reasonable and necessary actual direct costs incurred (e.g., equipment, supplies, travel and other costs directly associated with the performance of the Agreement) to the extent required in the performance of the Work and to the extent such costs are anticipated in the Budget. Travel, lodging, meals and incidental expenses shall be reimbursed for reasonable and necessary costs incurred. Costs shall not exceed the daily per diem rates published in the Federal Travel Regulations. Reimbursement for the use of personal vehicles shall be limited to the Internal Revenue Service business standard mileage rate in effect at the time the expense was incurred.

  • Transportation Charges The cost of transporting Employees and Material necessary for the Mining Operations.

  • Goods and Services Tax You shall be responsible for all goods and services tax and all other taxes imposed on or payable in respect of any amount required to be paid under this Agreement. We may debit the amount of such tax to your Card Account.

  • CONTRACT CHARGES The Contract Charges for the Services shall be structured using any of the following pricing mechanisms (as may be agreed by the Parties and set out in an SOW); Capped Time and Materials; Price per Story; Time and Materials; Fixed Price (to be used only for Services that are ancillary to software development services); or using such other pricing mechanism or combination of pricing mechanism thereof as may be agreed by the Parties. In consideration of the Supplier’s performance of its obligations under this Contract and in consideration of the specific services that are set out in an applicable SOW, the Customer shall pay the undisputed Contract Charges in accordance with the relevant SOW for the Release and the payment provisions set out at Clause 14 (Payment and VAT). The Customer shall, in addition to the Contract Charges and following delivery by the Supplier of an Invoice, pay the Supplier a sum equal to the VAT chargeable on the value of the Services supplied in accordance with this Contract. If at any time during this Contract Period the Supplier reduces its framework Prices for any Services which are provided under the framework Agreement (whether or not such Services are offered in a catalogue (if any) which is provided under the framework Agreement) in accordance with the terms of the framework Agreement, the Supplier shall immediately reduce the Contract Charges for such Services under this Contract by the same amount. The Supplier shall in any event ensure that the Contract Charges are at all times compliant and consistent with the charging structure set out in framework Schedule 8 (Charging Structure) and do not exceed the prices set out therein. Contract Charges:

  • Service Charges No service charge shall be made for any exchange or registration of transfer of Warrants.

  • Charges and Billing The amount payable for the Cloud Service is specified in an Order Document.

  • Goods and Services Tax (GST (a) For the purposes of clause 9:

  • Rates and Charges 6.3.1 Wholesale discounts for resold Telecommunications Services offerings are provided in Exhibit A. The Telecommunications Services offerings available for resale but excluded from the wholesale pricing arrangement in the Agreement are available at the retail Tariff, price list, catalog, or other retail Telecommunications Services offering rates. Telecommunications Services available for resale with or without a wholesale discount are subject to Commission-approved change, and any such changes shall apply from the effective date of such change on a going-forward basis only.

  • VAT (a) All amounts expressed to be payable under a Finance Document by any Party to a Finance Party which (in whole or in part) constitute the consideration for any supply for VAT purposes are deemed to be exclusive of any VAT which is chargeable on that supply, and accordingly, subject to paragraph (b) below, if VAT is or becomes chargeable on any supply made by any Finance Party to any Party under a Finance Document and such Finance Party is required to account to the relevant tax authority for the VAT, that Party must pay to such Finance Party (in addition to and at the same time as paying any other consideration for such supply) an amount equal to the amount of the VAT (and such Finance Party must promptly provide an appropriate VAT invoice to that Party).

  • Ancillary and Travel Expenses A. Except as otherwise provided in the Grant Agreement, no ancillary expenses incurred by the Grantee in connection with its provision of the services or deliverables will be reimbursed by the System Agency. Ancillary expenses include, but are not limited to, costs associated with transportation, delivery, and insurance for each deliverable.

Time is Money Join Law Insider Premium to draft better contracts faster.