Objects architecture Sample Clauses

Objects architecture. The basic object in the library is the MikeyMessage. It is inherited by key agreement type specific objects (MikeyMessagePSK, MikeyMessageDH, MikeyMessagePK). These objects are shown in the upper part of figure 9.1. A MikeyMessage contains a list of MikeyPayload objects. A MikeyPayload may be a MikeyPayloadHDR, MikeyPayloadT, etc. The MikeyMessage::MikeyMessage() builds the initiation message. MikeyMessage::build response() creates a response message from the received message, and MikeyMessage::parse response() processes this re- sponse. An additional class, KeyAgreement, was created to handle the key agree- ment parameters and to store the result of the key exchange. It should be (as much as possible) independent from the MIKEY protocol. The KeyAgreement class will contain the TEK Generation Key (TGK) and salt negotiated during the key agreement. The KeyAgreementDH, KeyAgreementPSK, and KeyAgreementPK subclasses add the key agreement type specific inputs (the group and secret key for Xxxxxx-Xxxxxxx, the pre-shared key, or the peer’s public key). Some general classes are used both by the MIKEY and SRTP implemen- tations, such as an AES in counter-mode encryption function. The Xxxxxx- Xxxxxxx exchange also require some certificate handling functions, for which we use the OpenSSL [35] libraries.
Sample 1
AutoNDA by SimpleDocs

Related to Objects architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Layout a. Estimate and quantity sheet

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • Design At no cost to SCE, Seller shall be responsible for:

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

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