Timestamps Sample Clauses

Timestamps. GlobalSign offers three types of timestamps: AATL, SEIKO, and QTSA. A DSS Product Pack includes timestamps equal in number to two times the Quantity of Signatures purchased in the Product Pack. Additional timestamps may be purchased with a DSS Product Pack or as a standalone Product Pack.
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
Timestamps. Perhaps the most common use of timestamps in cryptographic protocols is to counteract replay and interleaving attacks, and to provide uniqueness or timeliness guarantees. In this sense, timestamps are an alternative to challenge-response mechanisms using fresh random nonce and to message sequence numbers. The typical operation of a system relying on timestamps is the following. Before sending a message, a party obtains a time reading from its local clock, and cryptographically binds it to the message for transmission. The receiver of the message obtains the current time from its own local clock, and subtracts the value of the timestamp received. The message is immediately rejected if the timestamp difference is outside a fixed-size time interval, called an acceptance window, selected to account for the maximum message transit and processing time, plus clock skew between the two parties. Furthermore, the receiver keeps a list of all previously received messages whose timestamps are still within the acceptance window. The incoming message is also checked against this list, and it is rejected if it is found to be a replay. The fact that the receiver must keep local state to detect the replay of valid time stamped messages within the acceptance window may also be considered a disadvantage. For example, a solution based on a challenge response mechanism using a random nonce could be used for the same purpose and would only require the receiver to keep a small amount of short-term state (albeit per-connection). In comparison to challenge response mechanisms, protocols using timestamps will typically require one less message to complete and will not require parties to generate random numbers. On the downside, the receiver must keep a small amount of ephemeral local state to detect the replay of valid messages within an acceptance window. The amount of state that must be kept when using timestamps can also be seen as an advantage when compared, for example, with solutions using sequence numbers where the receiver must keep static long-term state for each possible peer. In other application scenarios, there is no real alternative to the use of timestamps. Examples of this are the implementation of time- limited privileges, such as those awarded by Kerberos tickets, or the legal validity of authenticated documents, such as
Sample 1
Timestamps. We share this information with Squarespace, our Website analytics provider, to learn about site traffic and activity. To learn more about Squarespace analytics click here.
Sample 1
Timestamps. When possible, ECOs shall cause to be applied Timestamps to individual CAD entries for the purposes of incident response data aggregation and review. Said Timestamps may include, but are not limited to:
Sample 1
Timestamps. The nature of OPC UA Historical Access requires that a single timestamp reference be used to relate the multiple data points or events, and clients may request which timestamp will be used as the reference. See [UA Part 4] for details on the TimestampsToReturn enumeration. An OPC UA Server supporting Historical Access will treat the various timestamp settings as described below. For HistoricalDataNodes: SOURCE Return the SourceTimestamp. SourceTimestamp is used to determine which historical data values are returned. SERVER Return the ServerTimestamp. ServerTimestamp is used to determine which historical data values are returned. BOTH Return both the SourceTimestamp and ServerTimestamp. SourceTimestamp is used to determine which historical data values are returned. NEITHER This is not a valid setting for any HistoryRead accessing HistoricalDataNodes. For HistoricalEventNodes: SOURCE Return the SourceTimestamp. SourceTimestamp is used to determine which historical events are returned. SERVER This is not valid setting for any HistoryRead accessing HistoricalEventNodes. BOTH This is not valid setting for any HistoryRead accessing HistoricalEventNodes. NEITHER This is not valid setting for any HistoryRead accessing HistoricalEventNodes. Any reference to Timestamps through out this specification will represent either ServerTimestamp or SourceTimestamp as dictated by the type requested in the ReadHistory service. Some servers may not support historizing both SourceTimestamp and ServerTimestamp, but it is expect that all servers will support historizing SourceTimestamp (see [UA Part 7] for details on Server Profiles).
Sample 1
Timestamps. <?xml version="1.0" encoding="UTF-8"?> <Logging_information> <Static_information> <User_Information> <user_ID>ID</user_ID> <legal_information> <name>Enter Name</name> <consent_form>Enter consent form</consent_form> <terms_and_conditions>Enter terms</terms_and_conditions> </legal_information> <pre_experimental_questionnaire> <gender>Male</gender> <age>24</age> </pre_experimental_questionnaire> <post_experimental_questionnaire> <subjective_quality>Enter values</subjective_quality> <qualitative_feedback>Enter feedback</qualitative_feedback> </post_experimental_questionnaire> </User_Information> <Setup_of_the_room> <condition>Enter condition</condition> <viewing_distance>Enter distance value</viewing_distance> </Setup_of_the_room> <Specifications_of_display_audio_devices_and_playback_software> <external_monitor> <display_size>Enter display size</display_size> <resolution>Enter resolution</resolution> <frame_rate>Enter frame rate</frame_rate> </external_monitor> <audio_device>Enter audio device type</audio_device> <immersive_display>Enter display type</immersive_display> <ambient_light_conditions> <Intensity>Enter Intensity</Intensity> <color_temperature>Enter temperature </color_temperature> </ambient_light_conditions> <software_version>Enter version</software_version> </Specifications_of_display_audio_devices_and_playback_software> <Content_identifiers_and_service_level_metadata> <codec_specifications>Enter specifications</codec_specifications> <channel_specifications> Enter specifications </channel_specifications> </Content_identifiers_and_service_level_metadata> </Static_information> <Dynamic_information> <Position_in_virtual_world>Enter position</Position_in_virtual_world> <Movement_acceleration>Enter acceleration</Movement_acceleration> <Viewport_field_of_view>Enter value</Viewport_field_of_view> <Audiovisual_monitoring> Enter position and action </Audiovisual_monitoring> <Frame_level_QoS_parameters> <instantaneous_bit_rate>Enter bit rate</instantaneous_bit_rate> <network_delay>Enter delay</network_delay> <packet_loss>Enter packet loss</packet_loss> <frame_rate>Enter frame rate</frame_rate> </Frame_level_QoS_parameters> <Timestamps>Enter Timestamps</Timestamps> </Dynamic_information> </Logging_information> Table 5: Example of an XML format of the logging information sent as input to the QoE module. The Implementation Plan of the QoE, depicted in Figure 15 involves four sub-modules as follows: INPUT DATA module, FEATURE EXTRACTION module, MODELING module a...
Sample 1

Related to Timestamps

  • Timesheets 5.1. At the end of each week of an Assignment (or at the end of the Assignment where it is for a period of 1 week or less or is completed before the end of a week) the Agency Worker shall deliver to the Employment Business a timesheet duly completed to indicate the number of hours worked during the preceding week (or such lesser period) and signed by an authorised representative of the Hirer.

  • Pledge, Mortgage or Charge as Collateral for a Loan You may pledge, mortgage or charge your escrow securities to a financial institution as collateral for a loan, provided that no escrow securities or any share certificates or other evidence of escrow securities will be transferred or delivered by the Escrow Agent to the financial institution for this purpose. The loan agreement must provide that the escrow securities will remain in escrow if the lender realizes on the escrow securities to satisfy the loan.

  • E-Verification If applicable, Contractor represents and warrants that it will ensure its compliance with the Mississippi Employment Protection Act of 2008, and will register and participate in the status verification system for all newly hired employees. Mississippi Code Annotated §§ 71-11-1 et seq. The term “employee” as used herein means any person that is hired to perform work within the State of Mississippi. As used herein, “status verification system” means the Illegal Immigration Reform and Immigration Responsibility Act of 1996 that is operated by the United States Department of Homeland Security, also known as the E-Verify Program, or any other successor electronic verification system replacing the E-Verify Program. Contractor agrees to maintain records of such compliance. Upon request of the State and after approval of the Social Security Administration or Department of Homeland Security when required, Contractor agrees to provide a copy of each such verification. Contractor further represents and warrants that any person assigned to perform services hereafter meets the employment eligibility requirements of all immigration laws. The breach of this agreement may subject Contractor to the following:

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

  • Monthly Billing Statements The Engineer shall request reimbursement of costs incurred by submitting the original and one copy of an itemized billing statement in a form acceptable to the State. The Engineer is authorized to submit requests for reimbursement no more frequently than monthly and no later than ninety (90) days after costs are incurred.

  • RECORDAL 2.1. The SCC is the Fund’s standard terms and conditions of contract and constitutes part of the Service Provider Agreement between the Fund and the Service Provider, or in lieu of a Service Provider Agreement, constitutes part of the Purchase Order issued by the Fund to the Service Provider (whichever is applicable)

  • Bills Upon receipt of proper instructions, to pay or cause to be paid, insofar as funds are available for the purpose, bills, statements, or other obligations of the Fund.

  • Account Verification Whether or not a Default or Event of Default exists, Agent shall have the right at any time, in the name of Agent, any designee of Agent or any Borrower, to verify the validity, amount or any other matter relating to any Accounts of Borrowers by mail, telephone or otherwise. Borrowers shall cooperate fully with Agent in an effort to facilitate and promptly conclude any such verification process.

  • Transfert A. Le Logiciel Apple obtenu via le Mac App Store n’est pas transmissible. Si vous vendez votre matériel de marque Apple à un tiers, vous êtes tenu de supprimer le Logiciel Apple dudit matériel avant de le remettre à l’acheteur.

  • Recording Either Lessor or Lessee shall, upon request of the other, execute, acknowledge and deliver to the other a short form memorandum of this Lease for recording purposes. The Party requesting recordation shall be responsible for payment of any fees or taxes applicable thereto.

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