Web Portal If you elect to link to and use the web interface provided by us (the “Web Portal”), you agree that the Web Portal is for the sole purpose of enabling Recipients to update and add their contact information. If you elect to use the Web Portal, we grant for the period of the Term (as defined below) to you a limited non-exclusive, worldwide, royalty-free license to place a digital image of the applicable sign-up Logo, which will be presented to you (the “Image”), on an appropriate page of your Internet site, with a hyperlink to our Web Portal site (the “Link”) currently at xxxxx://xxxxxx.xxxxxxxxxxxxxxxxxxx.xxx/. You may not use any other trademark or service xxxx in connection with the Image without our prior written approval. The Link may not be used in any manner to provide an Authorized User with access to the Web Portal via any framing, layering or other techniques now known or hereafter developed that permit display of the Web Portal with any materials posted by you or anyone other than us. You may not allow the Image to be linked to any other web site. You may not use the Image in any manner not permitted hereunder, modify the Image, or copy, or create a derivative work from, the “look and feel” of the Image. We will have the right to review all uses of the Image for quality control purposes and proper compliance. We reserve the right to modify permission to use the Image and/or the Link at any time.
Conversion of Wholesale Services to Network Elements or Network Elements to Wholesale Services Upon request, BellSouth shall convert a wholesale service, or group of wholesale services, to the equivalent Network Element or Combination that is available to Global Dialtone pursuant to Section 251 of the Act and under this Agreement or convert a Network Element or Combination that is available to Global Dialtone pursuant to Section 251 of the Act and under this Agreement to an equivalent wholesale service or group of wholesale services offered by BellSouth (collectively “Conversion”). BellSouth shall charge the applicable nonrecurring switch-as-is rates for Conversions to specific Network Elements or Combinations found in Exhibit A. BellSouth shall also charge the same nonrecurring switch-as-is rates when converting from Network Elements or Combinations. Any rate change resulting from the Conversion will be effective as of the next billing cycle following BellSouth’s receipt of a complete and accurate Conversion request from Global Dialtone. A Conversion shall be considered termination for purposes of any volume and/or term commitments and/or grandfathered status between Global Dialtone and BellSouth. Any change from a wholesale service/group of wholesale services to a Network Element/Combination, or from a Network Element/Combination to a wholesale service/group of wholesale services, that requires a physical rearrangement will not be considered to be a Conversion for purposes of this Agreement. BellSouth will not require physical rearrangements if the Conversion can be completed through record changes only. Orders for Conversions will be handled in accordance with the guidelines set forth in the Ordering Guidelines and Processes and CLEC Information Packages as referenced in Sections 1.13.1 and 1.13.2 below.
Portal-to-Portal All employees shall receive portal to portal mileage reimbursement when on a call back.
Competent Authorities and Contact Points 1. Each Party shall provide each other Party with a description of its competent authorities and their division of responsibilities.
Internet Connectivity School must provide sufficient hardline internet connectivity and the required network configurations (provided in Exhibit A) for each Pixellot System to allow live broadcasts. PlayOn will provide the point-to-point wireless internet base station (“Point to Point”) when needed to deliver hardline internet connectivity to Pixellot Systems installed in outdoor venues; provided that PlayOn is able to select the make and model of the Point to Point system. In the event that School requests, or requires, a specific Point to Point system that is different from what is provided by PlayOn, then School must provide and install the Point to Point system at its own expense.
Verizon’s Provision of Network Elements Subject to the conditions set forth in Section 1, in accordance with, but only to the extent required by, Applicable Law, Verizon shall provide PCS access to the following:
Nyiso and Connecting Transmission Owner Authority General. NYISO or Connecting Transmission Owner may take whatever actions with regard to the New York State Transmission System or the Connecting Transmission Owner’s Attachment Facilities it deems necessary during an Emergency State in order to (i) preserve public health and safety, (ii) preserve the reliability of the New York State Transmission System or the Connecting Transmission Owner’s Attachment Facilities, (iii) limit or prevent damage, and (iv) expedite restoration of service. NYISO and Connecting Transmission Owner shall use Reasonable Efforts to minimize the effect of such actions or inactions on the Large Generating Facility or the Developer’s Attachment Facilities. NYISO or Connecting Transmission Owner may, on the basis of technical considerations, require the Large Generating Facility to mitigate an Emergency State by taking actions necessary and limited in scope to remedy the Emergency State, including, but not limited to, directing Developer to shut-down, start-up, increase or decrease the real or reactive power output of the Large Generating Facility; implementing a reduction or disconnection pursuant to Article 13.4.2; directing the Developer to assist with blackstart (if available) or restoration efforts; or altering the outage schedules of the Large Generating Facility and the Developer’s Attachment Facilities. Developer shall comply with all of the NYISO and Connecting Transmission Owner’s operating instructions concerning Large Generating Facility real power and reactive power output within the manufacturer’s design limitations of the Large Generating Facility’s equipment that is in service and physically available for operation at the time, in compliance with Applicable Laws and Regulations.
Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting the HUB Program at 000-000-0000 or toll-free in Texas at 0-000-000-0000.
Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES
Local Number Portability Database 10.6.1 The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. BellSouth agrees to provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.