Description of Algorithms Sample Clauses

Description of Algorithms. In this subsection, we present three interval-based dis- tributed rekeying algorithms. They are the Rebuild algo- rithm, the Batch algorithm and the Queue-batch algorithm. The use of interval-based rekeying aims to maintain good rekeying performance independent of the dynamics of joins and leaves. The three distributed algorithms are developed based on the following assumptions: The key tree of TGDH is used as a foundation of all the algorithms. The rekeying operations are carried out at the begin- ning of every rekey interval. There exists a virtual queue holding all join and leave requests till the be- ginning of the next rekey interval. When a new member sends a join request, it should also include its individual blinded key. For simplicity, all clients know the existing key tree structure and they also know all the blinded keys within the tree. The group members would elect sponsors to be respon- sible for computing and broadcasting blinded keys. To obtain the blinded keys of the renewed nodes (a node is said to be renewed if it is a non-leaf node and its as- clients contribute to the composition of the group key. The pseudo code of the Batch algorithm is given as: sociated keys are updated), the key paths of the spon- sors should contain those renewed nodes. Since the interval-based rekeying operations involve nodes lying on more than one key paths, more than one sponsors may be elected. Also, a renewed node may be rekeyed by more than one sponsor. In this case, we assume that the sponsors can coordinate with one another such that the blinded keys of all the renewed nodes are broadcast once only. We adopt the following notations for the three distributed algorithms. Let denote the existing key tree. Assume that existing members = wish to leave, and new members = wish to join the communication group within a rekey interval.
AutoNDA by SimpleDocs
Description of Algorithms. In this subsection, we present three interval-based dis- tributed rekeying algorithms. They are the Rebuild algo- rithm, the Batch algorithm and the Queue-batch algorithm. The use of interval-based rekeying aims to maintain good rekeying performance independent of the dynamics of joins and leaves. The three distributed algorithms are developed based on the following assumptions: The rekeying operations are carried out at the begin- ning of every rekey interval. There exists a virtual queue holding all join and leave requests till the be- ginning of the next rekey interval. obtain the blinded keys of the renewed nodes (a node is said to be renewed if it is a non-leaf node and its as- clients contribute to the composition of the group key. The pseudo code of the Batch algorithm is given as: sociated keys are updated), the key paths of the spon- sors should contain those renewed nodes. Since the interval-based rekeying operations involve nodes lying on more than one key paths, more than one sponsors may be elected. Also, a renewed node may be rekeyed by more than one sponsor. In this case, we assume that the sponsors can coordinate with one another such that the blinded keys of all the renewed nodes are broadcast once only. We adopt the following notations for the three distributed algorithms. Let T denote the existing key tree. Assume that L 0 existing members M l = hM l; ;M l i wish to Xxxxx (T , M j , J , M l, L) 1. if (L == 0) f /* pure join case */
Description of Algorithms public function construct(Point g); The constructor serves only to populate the generator point for ECDH. public function getPublicPoint(); When called, this method generates a pseudo-random number ”secret” between 0 and the order of the generator point. Upon successful generation it returns the public point secret*Generator. public function setPublicPoint(Point q); This method is used to set a public point that was received from the person wishing to establish secure communication through an untrusted channel. public function calculateKey(); The calculateKey method’s purpose is to finally establish the shared secret. When both parties call this method, they both arrive at the same key. Find the explanation of cor- rectness behind ECDH in Section 3. public function encrypt(string); public function decrypt(string); public function encryptFile(path); public function decryptFile(path); The methods above are demonstrations of how a dual-key encryption scheme may be used with the ECDH shared key agreement protocol. The first pair of methods may be used for arbitrary strings. For hashing the x value of the generated shared secret, the implemen- tations use SHA256. This hash is then fed into the 256 bit EAS encryption function in CBC mode. The methods which operate on files are identical to the previous two, but are designed to read in a file as the message to be communicated between Xxxxx and Xxx.

Related to Description of Algorithms

  • Description of Funding Techniques 6.2.1 The following are terms under which standard funding techniques shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. Funding Technique Name Description Actual Clearance, ZBA - Same Day Payment The State shall request funds the same day it pays out funds, in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. A Federal agency will deposit funds in a State account the same day as requested. The amount of the request shall be for the amount of funds that clear the State's account that day. This funding technique is interest neutral. Composite Clearance The State shall request funds such that they are deposited on the dollar-weighted average number of days required for funds to be paid out for a series of disbursements, in accordance with the clearance pattern specified in Exhibit II. The request shall be made in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. The amount of the request shall be the sum of the payments issued in the series of disbursements. This funding technique is interest neutral. Pre-Issuance The State shall request funds such that they are deposited in a State account not more than three business days prior to the day the State makes a disbursement. The request shall be made in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. The amount of the request shall be the amount the State expects to disburse. This funding technique is not interest neutral. 6.2.2 The following are terms under which funding techniques for administrative costs shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. Funding Technique Name Description Actual Costs - Estimated Allocation - Monthly The State shall request funds once a month, such that they are deposited on the median day of the month, to fund the activity of the prior month. The request shall be made in accordance with the appropriate Federal agency cut-off time specified in Exhibit I. The amount of the request shall be an estimate based on the actual costs of the month distributed to the program according to the allocation of costs for the preceding six months. This funding technique is interest neutral. 6.2.3 The following are terms under which miscellaneous funding techniques shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. There are currently no funding techniques listed in Section 6.2.3. 6.2.4 The following are terms under which State unique funding techniques shall be implemented for all transfers of funds to which the funding technique is applied in section 6.3.2 of this Agreement. There are currently no programs listed for Section 6.2.4.

  • Description of Services A description of Google Workspace for Education Service provided by Google is set forth in the Services Summary located at xxxxx://xxxxxxxxx.xxxxxx.xxx/terms/user_features.html.

  • Descriptions All descriptions referred to in this Agreement are expressly incorporated herein by reference as if set forth in full, whether or not attached hereto.

  • Description of Work that has been omitted or

  • Processes Any employer, employee, trade union or employer’s association may at any point in time apply for an exemption from any of the provisions of this Collective Agreement. The applicant is required to complete and submit in writing with the relevant office of the Council, a fully and properly completed prescribed application for exemption form, accompanied by all relevant supporting documentation.

  • Description of Appropriate Unit For purposes of this Agreement, the appropriate unit shall mean all Education Assistant/LPN/ARN employees employed by the School District excluding the following: confidential employees, supervisory employees, essential employees, part-time employees whose services do not exceed 14 hours per week or 35% of normal work week, employees who hold positions of a temporary or seasonal character for a period not in excess of 67 working days in any calendar year, and emergency employees.

  • Techniques Framework agreement: Information about the dynamic purchasing system: No dynamic purchase system

  • Description of Service 2.9.1.1 BellSouth shall make available to <<customer_short_name>> LMU information with respect to Loops that are required to be unbundled under this Agreement so that <<customer_short_name>> can make an independent judgment about whether the Loop is capable of supporting the advanced services equipment <<customer_short_name>> intends to install and the services <<customer_short_name>> wishes to provide. LMU is a preordering transaction, distinct from <<customer_short_name>> ordering any other service(s). Loop Makeup Service Inquiries (LMUSI) and mechanized LMU queries for preordering LMU are likewise unique from other preordering functions with associated SIs as described in this Agreement. 2.9.1.2 BellSouth will provide <<customer_short_name>> LMU information consisting of the composition of the Loop material (copper/fiber); the existence, location and type of equipment on the Loop, including but not limited to digital loop carrier or other remote concentration devices, feeder/distribution interfaces, bridged taps, load coils, pair-gain devices; the Loop length; the wire gauge and electrical parameters. 2.9.1.3 BellSouth’s LMU information is provided to <<customer_short_name>> as it exists either in BellSouth's databases or in its hard copy facility records. BellSouth does not guarantee accuracy or reliability of the LMU information provided. 2.9.1.4 BellSouth’s provisioning of LMU information to the requesting CLEC for facilities is contingent upon either BellSouth or the requesting CLEC controlling the Loop(s) that serve the service location for which LMU information has been requested by the CLEC. The requesting CLEC is not authorized to receive LMU information on a facility used or controlled by another CLEC unless BellSouth receives a LOA from the voice CLEC (owner) or its authorized agent on the LMUSI submitted by the requesting CLEC. 2.9.1.5 <<customer_short_name>> may choose to use equipment that it deems will enable it to provide a certain type and level of service over a particular BellSouth Loop as long as that equipment does not disrupt other services on the BellSouth network. The determination shall be made solely by <<customer_short_name>> and BellSouth shall not be liable in any way for the performance of the advanced data services provisioned over said Loop. The specific Loop type (e.g., ADSL, HDSL, or otherwise) ordered on the LSR must match the LMU of the Loop reserved taking into consideration any requisite line conditioning. The LMU data is provided for informational purposes only and does not guarantee <<customer_short_name>>’s ability to provide advanced data services over the ordered Loop type. Furthermore, the LMU information for Loops other than copper-only Loops (e.g., ADSL, UCL-ND, etc.) that support xDSL services, is subject to change at any time due to modifications and/or upgrades to BellSouth’s network. Except as set forth in Section 2.9.1.6, copper-only Loops will not be subject to change due to modification and/or upgrades to BellSouth’s network and will remain on copper facilities until the Loop is disconnected by <<customer_short_name>> or the End User, or until BellSouth retires the copper facilities via the FCC’s and any applicable Commission’s requirements. <<customer_short_name>> is fully responsible for any of its service configurations that may differ from BellSouth’s technical standard for the Loop type ordered. 2.9.1.6 If BellSouth retires its copper facilities using 47 C.F.R § 52.325(a) requirements; or is required by a governmental agency or regulatory body to move or replace copper facilities as a maintenance procedure, BellSouth will notify <<customer_short_name>>, according to the applicable network disclosure requirements. It will be <<customer_short_name>>’s responsibility to move any service it may provide over such facilities to alternative facilities. If <<customer_short_name>> fails to move the service to alternative facilities by the date in the network disclosure notice, BellSouth may terminate the service to complete the network change.

  • Description of Projects Services a. Project/Services to be performed by A-E shall consist of the work as specified herein and as required in Attachment A. If in the event Attachment A shall be in conflict with any provision of this Contract, the wording as set forth in Attachment A shall prevail. b. A-E shall be responsible for submitting all Projects/Services to County in a form which has been thoroughly reviewed and checked for completeness, accuracy and consistency by the registered professional named in Section 1.1.2 herein; and, any Projects/Services not meeting this requirement will be returned to A-E prior to review by County.

  • Service Descriptions Credit Card processing services: Global Direct’s actions to the appropriate card associations and/or issuers (e.g., Visa, MasterCard, Diners, Discover); settlement; dispute resolution with cardholders’ banks; and transaction-related reporting, statements and products. Debit/ATM Processing Services: Global Direct has connected to the following debit card networks (“Networks”): Accel, AFFN, Interlink, MAC, Maestro, NYCE, Pulse, Star, and Tyme. Global Direct will provide Merchant with the ability to access the Networks that Global Direct has connected to for the purpose of authorizing debit card transactions at the point of sale from cards issued by the members of the respective Networks. Global Direct will provide connection to such Networks, terminal applications, settlement and reporting activities. EBT Transaction Processing Services: Global Direct offers electronic interfaces to Electronic Benefits Transfer (“EBT”) networks for the processing of cash payments or credits to or for the benefit of benefit recipients (“Recipients”). Global Direct will provide settlement and switching services for various Point of Sale transactions initiated through Merchant for the authorization of the issuance of the United States Department of Agriculture, Food and Nutrition Services (“FNS”) food stamp benefits (“FS Benefits”) and/or government delivered cash assistance benefits (“Cash Benefits, ”with FS Benefits, “Benefits”) to Recipients through the use of a state-issued card (“EBT Card”). With respect to Visa and MasterCard products, Merchant agrees to pay and Merchant's account(s) will be charged pursuant to Section 5 of this Agreement for any additional fees incurred as a result of Merchant's subsequent acceptance of transactions with any Visa or MasterCard product that it has not elected to accept.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!