Registrar Data 1.6.1 Query format: whois “registrar Example Registrar, Inc.”
1.6.2 Response format: Registrar Name: Example Registrar, Inc. Street: 0000 Xxxxxxxxx Xxx City: Marina del Rey State/Province: CA Postal Code: 90292 Country: US Phone Number: +1.0000000000 Fax Number: +1.3105551213 Email: xxxxxxxxx@xxxxxxx.xxx WHOIS Server: whois.example-‐registrar.tld Referral URL: xxxx://xxx.xxxxxxx-‐registrar.tld Admin Contact: Xxx Registrar Phone Number: +1.3105551213 Fax Number: +1.3105551213 Email: joeregistrar@example-‐registrar.tld Admin Contact: Xxxx Registrar Phone Number: +1.3105551214 Fax Number: +1.3105551213 Email: janeregistrar@example-‐registrar.tld Technical Contact: Xxxx Geek Phone Number: +1.3105551215 Fax Number: +1.3105551216 Email: johngeek@example-‐registrar.tld >>> Last update of WHOIS database: 2009-‐05-‐29T20:15:00Z <<<
Publication of Registration Data Registry Operator shall provide public access to registration data in accordance with Specification 4 attached hereto (“Specification 4”).
Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.
(b) With respect to renewal of domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying, Qualified Marketing Programs or other programs which had the effect of reducing the price charged to registrars) of no less than one hundred eighty (180) calendar days. Notwithstanding the foregoing sentence, with respect to renewal of domain name registrations: (i) Registry Operator need only provide thirty (30) calendar days notice of any price increase if the resulting price is less than or equal to (A) for the period beginning on the Effective Date and ending twelve (12) months following the Effective Date, the initial price charged for registrations in the TLD, or (B) for subsequent periods, a price for which Registry Operator provided a notice pursuant to the first sentence of this Section 2.10(b) within the twelve (12) month period preceding the effective date of the proposed price increase; and (ii) Registry Operator need not provide notice of any price increase for the imposition of the Variable Registry-‐Level Fee set forth in Section 6.3. Registry Operator shall offer registrars the option to obtain domain name registration renewals at the current price (i.e., the price in place prior to any noticed increase) for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.
(c) In addition, Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal. The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Registry Operator with documentation that demonstrates that the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domain name following clear and conspicuous disclosure of such Renewal Pricing to such registrant, and (ii) discounted Renewal Pricing pursuant to a Qualified Marketing Program (as defined below). The parties acknowledge that the purpose of this Section 2.10(c) is to prohibit abusive and/or discriminatory Renewal Pricing practices imposed by Registry Operator without the written consent of the applicable registrant at the time of the initial registration of the domain and this Section 2.10(c) will be interpreted broadly to prohibit such practices. For purposes of this Section 2.10(c), a “Qualified Marketing Program” is a marketing program pursuant to which Registry Operator offers discounted Renewal Pricing, provided that each of the following criteria is satisfied: (i) the program and related discounts are offered for a period of time not to exceed one hundred eighty (180) calendar days (with consecutive substantially similar programs aggregated for purposes of determining the number of calendar days of the program), (ii) all ICANN accredited registrars are provided the same opportunity to qualify for such discounted Renewal Pricing; and (iii) the intent or effect of the program is not to exclude any particular class(es) of registrations (e.g., registrations held by large corporations) or increase the renewal price of any particular class(es) of registrations. Nothing in this Section 2.10(c) shall limit Registry Operator’s obligations pursuant to Section 2.10(b).
(d) Registry Operator shall provide public query-‐based DNS lookup service for the TLD (that is, operate the Registry TLD zone servers) at its sole expense.
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
DELIVERY: FOB DESTINATION, INSIDE DELIVERY, FREIGHT PAID Whenever possible, contractors should give the ordering entities 3 working days prior notice of any deliveries and/or installations. Furniture contractors will not be responsible for the removal/moving of existing furnishings unless requested by the ordering entity. Contractors should verify site readiness prior to delivery. All deliveries will be made during normal working hours unless otherwise arranged with the ordering entity. Contractor will communicate any scheduling delays and/or changes immediately. Agencies will not be responsible for any freight damage, concealed or otherwise.
Costs of updating of registration statement If provided for in the Prospectus for a Trust, the Trustee shall pay, or reimburse to the Depositor, the expenses related to the updating of the Trust's registration statement, to the extent of legal fees, typesetting fees, electronic filing expenses and regulatory filing fees. Such expenses shall be paid from the Income Account, or to the extent funds are not available in such Account, from the Capital Account, against an invoice or invoices therefor presented to the Trustee by the Depositor. By presenting such invoice or invoices, the Depositor shall be deemed to certify, upon which certification the Trustee is authorized conclusively to rely, that the amounts claimed therein are properly payable pursuant to this paragraph. The Depositor shall provide the Trustee, from time to time as requested, an estimate of the amount of such expenses, which the Trustee shall use for the purpose of estimating the accrual of Trust expenses. The amount paid by the Trust pursuant to this paragraph in each year shall be separately identified in the annual statement provided to Unit holders. The Depositor shall assure that the Prospectus for the Trust contains such disclosure as shall be necessary to permit payment by the Trust of the expenses contemplated by this paragraph under applicable laws and regulations. The provisions of this paragraph shall not limit the authority of the Trustee to pay, or reimburse to the Depositor or others, such other or additional expenses as may be determined to be payable from the Trust as provided in this Section 6.02.
Notice of Registration If at any time or from time to time the Company shall determine to register any of its securities, either for its own account or the account of a security holder or holders, other than (i) a registration relating solely to employee benefit plans, or (ii) a registration relating solely to a Commission Rule 145 transaction, the Company will:
(i) promptly give to each Holder written notice thereof; and
(ii) include in such registration (and any related qualification under blue sky laws or other compliance), and in any underwriting involved therein, all the Registrable Securities specified in a written request or requests, made within twenty (20) days after receipt of such written notice from the Company, by any Holder.
New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:
(1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute;
(2) Limit unsuccessful logon attempts;
(3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions;
(4) Authorize wireless access prior to allowing such connections;
(5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity;
(6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions;
(7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles;
(8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services;
(9) Enforce a minimum password complexity and change of characters when new passwords are created;
(10) Perform maintenance on organizational systems;
(11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance;
(12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1;
(13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital;
(14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse;
(15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas;
(16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems;
(17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems;
(18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception);
(19) Protect the confidentiality of Student Data at rest;
(20) Identify, report, and correct system flaws in a timely manner;
(21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems;
(22) Monitor system security alerts and advisories and take action in response; and
(23) Update malicious code protection mechanisms when new releases are available.
Per-‐Registrar Transactions Report This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐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 per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Transfer of Servicing Between Master Servicer and Special Servicer; Record Keeping (a) Upon determining that any Serviced Loan has become a Specially Serviced Loan, the Master Servicer shall promptly give written notice thereof to the Special Servicer, any related Serviced Companion Loan Holder (in the case of a Serviced Loan Combination), the Operating Advisor, the Certificate Administrator, the Trustee, the related Directing Holder (prior to the occurrence and continuance of a Consultation Termination Event with respect to the related Mortgage Loan) and, for posting to the Rule 17g-5 Information Provider’s Website pursuant to Section 12.13 of this Agreement, the Rule 17g-5 Information Provider and shall promptly deliver a copy of the Servicing File to the Special Servicer and concurrently provide a copy of such Servicing File to the Operating Advisor and shall use its reasonable efforts to provide the Special Servicer with all information, documents (but excluding the original documents constituting the Mortgage File, but including copies thereof) and records (including records stored electronically on computer tapes, magnetic discs and the like) relating to such Serviced Loan and reasonably requested by the Special Servicer to enable it to assume its duties hereunder with respect thereto without acting through a Sub-Servicer. The Master Servicer shall use its reasonable efforts to comply with the preceding sentence within five (5) Business Days of the date such Serviced Loan became a Specially Serviced Loan and in any event shall continue to act as Master Servicer and administrator of such Serviced Loan until the Special Servicer has commenced the servicing of such Serviced Loan, which shall occur upon the receipt by the Special Servicer of the Servicing File. With respect to each such Serviced Loan that becomes a Specially Serviced Loan, the Master Servicer shall instruct the related Mortgagor to continue to remit all payments in respect of such Serviced Loan to the Master Servicer. The Master Servicer shall forward any notices it would otherwise send to the Mortgagor of such a Specially Serviced Loan to the Special Servicer who shall send such notice to the related Mortgagor. Upon determining that a Specially Serviced Loan has become a Corrected Loan, the Special Servicer shall promptly give written notice thereof to the Master Servicer, the Trustee, the Operating Advisor, the Certificate Administrator, any related Serviced Companion Loan Holder, the related Directing Holder (prior to the occurrence and continuance of a Consultation Termination Event with respect to the related Mortgage Loan) and, for posting to the Rule 17g-5 Information Provider’s Website pursuant to Section 12.13 of this Agreement, the Rule 17g-5 Information Provider and, upon giving such notice and the return of the Servicing File to the Master Servicer, such Serviced Loan shall cease to be a Specially Serviced Loan in accordance with the first proviso of the definition of Specially Serviced Loans, the Special Servicer’s obligation to service such Serviced Loan shall terminate and the obligations of the Master Servicer to service and administer such Serviced Loan as a Serviced Loan that is not a Specially Serviced Loan shall resume. In addition, if the related Mortgagor has been instructed, pursuant to the preceding paragraph, to make payments to the Special Servicer, upon such determination, the Special Servicer shall instruct the related Mortgagor to remit all payments in respect of such Specially Serviced Loan directly to the Master Servicer.
(b) In servicing any Specially Serviced Loan, the Special Servicer shall provide to the Custodian originals of documents included within the definition of “Mortgage File” for inclusion in the related Mortgage File (to the extent such documents are in the possession of the Special Servicer) and copies of any additional related Serviced Loan information, including correspondence with the related Mortgagor, and the Special Servicer shall promptly provide copies of all of the foregoing to the Master Servicer as well as copies of any analysis or internal review prepared by or for the benefit of the Special Servicer.
(c) Notwithstanding the provisions of subsections (a) and (b) of this Section 3.22, the Master Servicer shall maintain ongoing payment records with respect to each of the Specially Serviced Loans and, upon request, shall provide the Special Servicer and the Operating Advisor with any information reasonably required by the Special Servicer or the Operating Advisor to perform its duties under this Agreement to the extent such information is within the Master Servicer’s possession. Upon request, the Special Servicer shall provide the Master Servicer and the Operating Advisor with any information reasonably required by the Master Servicer or the Operating Advisor to perform its duties under this Agreement to the extent such information is within the Special Servicer’s possession.
