Searchable Whois Clause Samples

POPULAR SAMPLE Copied 2 times
Searchable Whois. Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must make available the services only to authenticated users after they logged in by supplying proper credentials (i.e., user name and password). Registry Operator must issue such credentials exclusively to eligible users and institutions that supply sufficient proof of their legitimate interest in this feature (e.g., law enforcement agencies).
View SourceView Similar (788)
Searchable Whois. Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must implement at least one of the following mechanisms in order to prevent abuse of the searchable Whois service: • Username and password based authentication. • Certificate based authentication. • CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) with rate-­‐limiting mechanism to prevent repetitive invocation of the service.
View SourceView Similar (176)
Searchable Whois. Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator shall use rate-­‐limiting to prevent abuse of the searchable Whois service.
View SourceView Similar (36)
Searchable Whois. Notwithstanding anything else in this Agreement, Registry Operator must offer a searchable Whois service compliant with the requirements described in Section 1.10 of Specification 4 of this Agreement. Registry Operator must make available the services only to authenticated users after they logged in by supplying proper credentials (e.g., user name and password). Registry Operator must issue such credentials exclusively to eligible users and institutions that supply sufficient proof of their legitimate interest in this feature (e.g., law enforcement agencies). Registry Operator shall use rate-­‐limiting to prevent abuse of the searchable Whois service. SPECIFICATION 1 CONSENSUS POLICIES AND TEMPORARY POLICIES SPECIFICATION
View Source

Related to Searchable Whois

  • Searchability Offering searchability capabilities on the Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.10.1 Registry Operator will offer searchability on the web-­‐based Directory Service. 1.10.2 Registry Operator will offer partial match capabilities, at least, on the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-­‐fields described in EPP (e.g., street, city, state or province, etc.). 1.10.3 Registry Operator will offer exact-­‐match capabilities, at least, on the following fields: registrar id, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.10.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.10.5 Search results will include domain names matching the search criteria. 1.10.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws or policies.

  • Help Desk A help desk for Product support issues (the “Help Desk”) will be available to Customer. Unless specified in an Order, Customer should contact ▇▇▇.▇▇▇.▇▇▇▇ to receive a telephone number for the applicable supporting Solutions & Support Center. Customer will appoint one Product administrator and one backup administrator to serve as the primary point of contact regarding maintenance services.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Wire Unbundled DS1 Digital Loop This is a designed 4-wire Loop that is provisioned according to industry standards for DS1 or Primary Rate ISDN services and will come standard with a test point, OC, and a DLR. A DS1 Loop may be provisioned over a variety of loop transmission technologies including copper, HDSL-based technology or fiber optic transport systems. It will include a 4-Wire DS1 Network Interface at the End User’s location.

  • Extra Trips All trips other than regular runs or supplemental runs shall be awarded to drivers according to the following procedures: 9.7.1 All extra trips shall be assigned in compliance with the following section of this Agreement; provided, however, that no driver shall be eligible to work more than forty (40) hours in any workweek, exclusive of hours worked on Saturday or Sunday, when another eligible driver is available and would not be put into overtime. 9.7.2 Assignment of extra trips shall be made on the basis of a “Trip Board.” The most senior driver who signs up for the extra trip shall be awarded the trip. No driver may give up any extra trip or supplemental run or regular run previously awarded in order to take an extra trip, if Section 9.7.1 above would be violated. There shall be no pre-empting of regular runs by drivers who wish to take extra trips. 9.7.3 Trips are to be dated as they are received by the Transportation Office. All extra trips shall be awarded to the most senior appropriate driver signing the “Trip Board.” If the extra trip is posted before a driver’s regular run clock-out time, the driver has until the driver’s next regular run clock-in time to reply. If there is no reply, the dispatcher shall assign the extra trip to the next senior driver on the sign-up sheet. 9.7.4 Drivers shall not be eligible for extra trips during periods of absence due to illness. Drivers absent for personal illness on the last working day before a Saturday, Sunday, or holiday trip shall not be eligible to drive such trip and will lose his/her turn on the list until the process begins anew. Drivers absent for other reasons will be able to drive such trips provided they contact the Transportation Office by 3:30 p.m. on the last working day prior to the scheduled trip to verify their availability and confirm the start time of the trip. 9.7.5 The dispatch book shall be made available for driver viewing by the Transportation Office.