Verity Voting System
Verity Voting System Sample Clauses
Related to Verity Voting System
Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.
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 a 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.
Unbundled Voice Loops (UVL) may be provisioned using any type of facility that will support voice grade services. This may include loaded copper, non-loaded copper, digital loop carrier systems, fiber/copper combination (hybrid loop) or a combination of any of these facilities. BellSouth, in the normal course of maintaining, repairing, and configuring its network, may also change the facilities that are used to provide any given voice grade circuit. This change may occur at any time. In these situations, BellSouth will only ensure that the newly provided facility will support voice grade services. BellSouth will not guarantee that Southern Telecom will be able to continue to provide any advanced services over the new facility. BellSouth will offer UVL in two different service levels - Service Level One (SL1) and Service Level Two (SL2).
Shareholder Internet Services The Transfer Agent shall provide internet access to the Fund’s shareholders through a designated web site (“Shareholder Internet Services”), which will be accessed by the Fund’s shareholders via a link on the Fund’s web site. The Shareholder Internet Services will be provided pursuant to established procedures and will allow shareholders to view their account information and perform certain on-line transaction request capabilities. The Shareholder Internet Services shall be provided at no additional charge, other than the transaction fees currently being charged for the different transactions as described on the Fee Schedule. The Transfer Agent reserves the right to charge a fee for this service in the future.
Unbundled Network Element Combinations 5.1. Unbundled Network Element Combinations shall include: 1) Enhanced Extended Links (EELs); 2) UNE Loops/Special Access Combinations; 3) Loop/Port Combinations; and 4)
CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.
Other Directory Services 73.10.1 Both parties acknowledge that CenturyLink’s directory publisher is not a party to this Agreement and that the provisions contained in this Agreement are not binding upon CenturyLink’s directory publisher. 73.10.2 CenturyLink agrees to include critical contact information pertaining to CLEC in the “Information Pages” of those of its White Pages directories containing information pages, if CLEC meets criteria established by its directory publisher. Critical contact information includes CLEC’s business office number, repair number, billing information number, and any other information required to comply with applicable regulations, but not advertising or purely promotional material. CLEC will not be charged for inclusion of its critical contact information. The format, content and appearance of CLEC’s critical contact information must conform to applicable directory publisher’s guidelines and will be consistent with the format, content and appearance of critical contact information pertaining to all CLECs in a directory. 73.10.3 The directory publisher shall maintain full authority as publisher over its publishing policies, standards and practices, including decisions regarding directory coverage area, directory issue period, compilation, headings, covers, design, content or format of directories, and directory advertising sales.
Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.
Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-‐based Directory Service at <whois.nic.TLD> providing free public query-‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.
EPP query-‐command RTT Refers to the RTT of the sequence of packets that includes the sending of a query command plus the reception of the EPP response for only one EPP query command. It does not include packets needed for the start or close of either the EPP or the TCP session. EPP query commands are those described in section 2.9.2 of EPP RFC 5730. If the RTT is 5-‐times or more the corresponding SLR, the RTT will be considered undefined.
